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 <vkuk...@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 <slukja...@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@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-requ...@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 > > vkuk...@mirantis.com > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
