Open Stack

Serg,

Thanks for agreeing to officiate this cycle's component lead elections
for us!

-- 
Dmitry Borodaenko


On Thu, Mar 24, 2016 at 12:55:57PM -0700, Serg Melikyan wrote:
> Hi folks,
> 
> I'd like to announce that we're running the Component Leads elections.
> Detailed information is available on wiki [0].
> 
> Component Lead: defines architecture of a particular module or
> component in Fuel, resolves technical disputes in their area of
> responsibility. All design specs that impact a component must be
> approved by the corresponding component lead [1].
> 
> Fuel has three large sub-teams, with roughly comparable codebases,
> that need dedicated component leads:
> 
> * fuel-library
> * fuel-web
> * fuel-ui
> 
> Nominees propose their candidacy by sending an email to the
> openstack-dev at lists.openstack.org mailing-list, with the subject:
> "[fuel] <component> lead candidacy"
> (for example, "[fuel] fuel-library lead candidacy").
> 
> Timeline:
> * March 25 - March 31: Open candidacy for Component leads positions
> * April 1 - April 7: Component leads elections
> 
> References
> [0] https://wiki.openstack.org/wiki/Fuel/Elections_Spring_2016
> [1] https://specs.openstack.org/openstack/fuel-specs/policy/team-structure.html
> 
> -- 
> Serg Melikyan, Development Manager at Mirantis, Inc.
> http://mirantis.com | smelikyan 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