Open Stack

I've updated the policy document to explicitly spell out committers to
which repositories vote for PTL and for CLs:

https://review.openstack.org/#/c/225376/3..4/policy/team-structure.rst

This policy document is going to become the primary source of truth on
our governance process, I encourage all Fuel contributors, especially
core reviewers, to read it carefully, provide comments, and vote. So far
only Mike and Alexey have done that.

-- 
Dmitry Borodaenko

On Thu, Sep 24, 2015 at 01:17:58PM +0300, Vladimir Kuklin wrote:
> Dmitry
> 
> Thank you for the clarification, but my questions still remain unanswered,
> unfortunately. It seems I did not phrase them correctly.
> 
> 1) For each of the positions, which set of git repositories should I run
> this command against? E.g. which stackforge/fuel-* projects contributors
> are electing PTL or CL?
> 2) Who is voting for component leads? Mike's email says these are core
> reviewers. Our previous IRC meeting mentioned all the contributors to
> particular components. Documentation link you sent is mentioning all
> contributors to Fuel projects. Whom should I trust? What is the final
> version? Is it fine that documentation contributor is eligible to nominate
> himself and vote for Library Component Lead?
> 
> Until there is a clear and sealed answer to these questions we do not have
> a list of people who can vote and who can nominate. Let's get it clear at
> least before PTL elections start.
> 
> On Thu, Sep 24, 2015 at 4:49 AM, Dmitry Borodaenko <dborodaenko at mirantis.com
> > wrote:
> 
> > Vladimir,
> >
> > Sergey's initial email from this thread has a link to the Fuel elections
> > wiki page that describes the exact procedure to determine the electorate
> > and the candidates [0]:
> >
> >     The electorate for a given PTL and Component Leads election are the
> >     Foundation individual members that are also committers for one of
> >     the Fuel team's repositories over the last year timeframe (September
> >     18, 2014 06:00 UTC to September 18, 2015 05:59 UTC).
> >
> >     ...
> >
> >     Any member of an election electorate can propose their candidacy for
> >     the same election.
> >
> > [0] https://wiki.openstack.org/wiki/Fuel/Elections_Fall_2015#Electorate
> >
> > If you follow more links from that page, you will find the Governance
> > page [1] and from there the Election Officiating Guidelines [2] that
> > provide a specific shell one-liner to generate that list:
> >
> >     git log --pretty=%aE --since '1 year ago' | sort -u
> >
> > [1] https://wiki.openstack.org/wiki/Governance
> > [2] https://wiki.openstack.org/wiki/Election_Officiating_Guidelines
> >
> > As I have specified in the proposed Team Structure policy document [3],
> > this is the same process that is used by other OpenStack projects.
> >
> > [3] https://review.openstack.org/225376
> >
> > Having a different release schedule is not a sufficient reason for Fuel
> > to reinvent the wheel, for example OpenStack Infrastructure project
> > doesn't even have a release schedule for many of its deliverables, and
> > still follows the same elections schedule as the rest of OpenStack:
> >
> > [4] http://governance.openstack.org/reference/projects/infrastructure.html
> >
> > Lets keep things simple.
> >
> > --
> > Dmitry Borodaenko
> >
> >
> > On Wed, Sep 23, 2015 at 01:27:07PM +0300, Vladimir Kuklin wrote:
> > > Dmitry, Mike
> > >
> > > Thank you for the list of usable links.
> > >
> > > But still - we do not have clearly defined procedure on determening who
> > is
> > > eligible to nominate and vote for PTL and Component Leads. Remember, that
> > > Fuel still has different release cycle and Kilo+Liberty contributors list
> > > is not exactly the same for "365days" contributors list.
> > >
> > > Can we finally come up with the list of people eligible to nominate and
> > > vote?
> > >
> > > On Sun, Sep 20, 2015 at 2:37 AM, Mike Scherbakov <
> > mscherbakov at mirantis.com>
> > > wrote:
> > >
> > > > Let's move on.
> > > > I started work on MAINTAINERS files, proposed two patches:
> > > > https://review.openstack.org/#/c/225457/1
> > > > https://review.openstack.org/#/c/225458/1
> > > >
> > > > These can be used as templates for other repos / folders.
> > > >
> > > > Thanks,
> > > >
> > > > On Fri, Sep 18, 2015 at 7:45 PM Davanum Srinivas <davanum at gmail.com>
> > > > wrote:
> > > >
> > > >> +1 Dmitry
> > > >>
> > > >> -- Dims
> > > >>
> > > >> On Fri, Sep 18, 2015 at 9:07 PM, Dmitry Borodaenko <
> > > >> dborodaenko at mirantis.com> wrote:
> > > >>
> > > >>> Dims,
> > > >>>
> > > >>> Thanks for the reminder!
> > > >>>
> > > >>> I've summarized the uncontroversial parts of that thread in a policy
> > > >>> proposal as per you suggestion [0], please review and comment. I've
> > > >>> renamed SMEs to maintainers since Mike has agreed with that part,
> > and I
> > > >>> omitted code review SLAs from the policy since that's the part that
> > has
> > > >>> generated the most discussion.
> > > >>>
> > > >>> [0] https://review.openstack.org/225376
> > > >>>
> > > >>> I don't think we should postpone the election: the PTL election
> > follows
> > > >>> the same rules as OpenStack so we don't need a Fuel-specific policy
> > for
> > > >>> that, and the component leads election doesn't start until October 9,
> > > >>> which gives us 3 weeks to confirm consensus on that aspect of the
> > > >>> policy.
> > > >>>
> > > >>> --
> > > >>> Dmitry Borodaenko
> > > >>>
> > > >>>
> > > >>> On Fri, Sep 18, 2015 at 07:30:39AM -0400, Davanum Srinivas wrote:
> > > >>> > Sergey,
> > > >>> >
> > > >>> > Please see [1]. Did we codify some of these roles and
> > responsibilities
> > > >>> as a
> > > >>> > community in a spec? There was also a request to use terminology
> > like
> > > >>> say
> > > >>> > MAINTAINERS in that email as well.
> > > >>> >
> > > >>> > Are we pulling the trigger a bit early for an actual election?
> > > >>> >
> > > >>> > Thanks,
> > > >>> > Dims
> > > >>> >
> > > >>> > [1] http://markmail.org/message/2ls5obgac6tvcfss
> > > >>> >
> > > >>> > On Fri, Sep 18, 2015 at 6:56 AM, Vladimir Kuklin <
> > vkuklin at mirantis.com
> > > >>> >
> > > >>> > wrote:
> > > >>> >
> > > >>> > > Sergey, Fuelers
> > > >>> > >
> > > >>> > > This is awesome news!
> > > >>> > >
> > > >>> > > By the way, I have a question on who is eligible to vote and to
> > > >>> nominate
> > > >>> > > him/her-self for both PTL and Component Leads. Could you
> > elaborate
> > > >>> on that?
> > > >>> > >
> > > >>> > > And there is no such entity as Component Lead in OpenStack - so
> > we
> > > >>> are
> > > >>> > > actually creating one. What are the new rights and
> > responsibilities
> > > >>> of CL?
> > > >>> > >
> > > >>> > > On Fri, Sep 18, 2015 at 5:39 AM, Sergey Lukjanov <
> > > >>> slukjanov at mirantis.com>
> > > >>> > > wrote:
> > > >>> > >
> > > >>> > >> Hi folks,
> > > >>> > >>
> > > >>> > >> I'd like to announce that we're running the PTL and Component
> > Leads
> > > >>> > >> elections. Detailed information available on wiki. [0]
> > > >>> > >>
> > > >>> > >> Project Team Lead: Manages day-to-day operations, drives the
> > project
> > > >>> > >> team goals, resolves technical disputes within the project
> > team. [1]
> > > >>> > >>
> > > >>> > >> Component Lead: Defines architecture of a module or component in
> > > >>> Fuel,
> > > >>> > >> reviews design specs, merges majority of commits and resolves
> > > >>> conflicts
> > > >>> > >> between Maintainers or contributors in the area of
> > responsibility.
> > > >>> [2]
> > > >>> > >>
> > > >>> > >> Fuel has two large sub-teams, with roughly comparable codebases,
> > > >>> that
> > > >>> > >> need dedicated component leads: fuel-library and fuel-python.
> > [2]
> > > >>> > >>
> > > >>> > >> Nominees propose their candidacy by sending an email to the
> > > >>> > >> openstack-dev at lists.openstack.org mailing-list, which the
> > subject:
> > > >>> > >> "[fuel] PTL candidacy" or "[fuel] <component> lead candidacy"
> > > >>> > >> (for example, "[fuel] fuel-library lead candidacy").
> > > >>> > >>
> > > >>> > >> Time line:
> > > >>> > >>
> > > >>> > >> PTL elections
> > > >>> > >> * September 18 - September 28, 21:59 UTC: Open candidacy for PTL
> > > >>> position
> > > >>> > >> * September 29 - October 8: PTL elections
> > > >>> > >>
> > > >>> > >> Component leads elections (fuel-library and fuel-python)
> > > >>> > >> * October 9 - October 15: Open candidacy for Component leads
> > > >>> positions
> > > >>> > >> * October 16 - October 22: Component leads elections
> > > >>> > >>
> > > >>> > >> [0] https://wiki.openstack.org/wiki/Fuel/Elections_Fall_2015
> > > >>> > >> [1] https://wiki.openstack.org/wiki/Governance
> > > >>> > >> [2]
> > > >>> > >>
> > > >>>
> > http://lists.openstack.org/pipermail/openstack-dev/2015-August/072406.html
> > > >>> > >> [3] https://lwn.net/Articles/648610/
> > > >>> > >>
> > > >>> > >> --
> > > >>> > >> Sincerely yours,
> > > >>> > >> Sergey Lukjanov
> > > >>> > >> Sahara Technical Lead
> > > >>> > >> (OpenStack Data Processing)
> > > >>> > >> Principal Software Engineer
> > > >>> > >> Mirantis Inc.
> > > >>> > >>
> > > >>> > >>
> > > >>>
> > __________________________________________________________________________
> > > >>> > >> OpenStack Development Mailing List (not for usage questions)
> > > >>> > >> Unsubscribe:
> > > >>> > >> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > > >>> > >>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > >>> > >>
> > > >>> > >>
> > > >>> > >
> > > >>> > >
> > > >>> > > --
> > > >>> > > Yours Faithfully,
> > > >>> > > Vladimir Kuklin,
> > > >>> > > Fuel Library Tech Lead,
> > > >>> > > Mirantis, Inc.
> > > >>> > > +7 (495) 640-49-04
> > > >>> > > +7 (926) 702-39-68
> > > >>> > > Skype kuklinvv
> > > >>> > > 35bk3, Vorontsovskaya Str.
> > > >>> > > Moscow, Russia,
> > > >>> > > www.mirantis.com <http://www.mirantis.ru/>
> > > >>> > > www.mirantis.ru
> > > >>> > > vkuklin at mirantis.com
> > > >>> > >
> > > >>> > >
> > > >>>
> > __________________________________________________________________________
> > > >>> > > OpenStack Development Mailing List (not for usage questions)
> > > >>> > > Unsubscribe:
> > > >>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > > >>> > >
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > >>> > >
> > > >>> > >
> > > >>> >
> > > >>> >
> > > >>> > --
> > > >>> > Davanum Srinivas :: https://twitter.com/dims
> > > >>>
> > > >>> >
> > > >>>
> > __________________________________________________________________________
> > > >>> > OpenStack Development Mailing List (not for usage questions)
> > > >>> > Unsubscribe:
> > > >>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > > >>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > __________________________________________________________________________
> > > >>> OpenStack Development Mailing List (not for usage questions)
> > > >>> Unsubscribe:
> > > >>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Davanum Srinivas :: https://twitter.com/dims
> > > >>
> > __________________________________________________________________________
> > > >> OpenStack Development Mailing List (not for usage questions)
> > > >> Unsubscribe:
> > > >> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > >>
> > > > --
> > > > Mike Scherbakov
> > > > #mihgen
> > > >
> > > >
> > __________________________________________________________________________
> > > > OpenStack Development Mailing List (not for usage questions)
> > > > Unsubscribe:
> > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > >
> > > >
> > >
> > >
> > > --
> > > Yours Faithfully,
> > > Vladimir Kuklin,
> > > Fuel Library Tech Lead,
> > > Mirantis, Inc.
> > > +7 (495) 640-49-04
> > > +7 (926) 702-39-68
> > > Skype kuklinvv
> > > 35bk3, Vorontsovskaya Str.
> > > Moscow, Russia,
> > > www.mirantis.com <http://www.mirantis.ru/>
> > > www.mirantis.ru
> > > vkuklin at mirantis.com
> >
> > >
> > __________________________________________________________________________
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe:
> > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> 
> 
> -- 
> Yours Faithfully,
> Vladimir Kuklin,
> Fuel Library Tech Lead,
> Mirantis, Inc.
> +7 (495) 640-49-04
> +7 (926) 702-39-68
> Skype kuklinvv
> 35bk3, Vorontsovskaya Str.
> Moscow, Russia,
> www.mirantis.com <http://www.mirantis.ru/>
> www.mirantis.ru
> vkuklin at mirantis.com

> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev