Open Stack

I think many projects are now beginning to develop the sub-team structure
(e.g Nova, Ironic and Cyborg) and that might be part of the answer here.

Having a sub-team structure and also have volunteer as sub team leads could
also help people that are not good at code review to contribute
significantly and get recognized in another way.

On Tue, Apr 24, 2018 at 7:24 PM, Davanum Srinivas <davanum at gmail.com> wrote:

> Thierry,
>
> please see below:
>
> On Tue, Apr 24, 2018 at 6:24 AM, Thierry Carrez <thierry at openstack.org>
> wrote:
> > Fox, Kevin M wrote:
> >> OpenStack has created artificial walls between the various Projects. It
> shows up, for example, as holes in usability at a user level or extra
> difficulty for operators juggling around so many projects. Users and for
> the most part, Operators don't really care about project organization, or
> ptls, or cores or such.  OpenStack has made some progress this direction
> with stuff like the unified cli. But OpenStack is not very unified.
> >
> > I've been giving this some thought (in the context of a presentation I
> > was giving on hard lessons learned from 8 years of OpenStack). I think
> > that organizing development around project teams and components was the
> > best way to cope with the growth of OpenStack in 2011-1015 and get to a
> > working set of components. However it's not the best organization to
> > improve on the overall "product experience", or for a maintenance phase.
> >
> > While it can be confusing, I like the two-dimensional approach that
> > Kubernetes followed (code ownership in one dimension, SIGs in the
> > other). The introduction of SIGs in OpenStack, beyond providing a way to
> > build closer feedback loops around specific topics, can help us tackle
> > this "unified experience" problem you raised. The formation of the
> > upgrades SIG, or the self-healing SIG is a sign that times change. Maybe
> > we need to push in that direction even more aggressively and start
> > thinking about de-emphasizing project teams themselves.
>
> Big +1. Another thing to check into is how can we split some of the
> work the PTL does into multiple roles ... that are short term and is
> rotated around. Hoping that will help with the problem where we need
> folks to be totally available full time to do meaningful work in a
> project.
>
> > --
> > Thierry Carrez (ttx)
> >
> > ____________________________________________________________
> ______________
> > 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
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhipeng at huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipengh at uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180425/3c3c9fc9/attachment.html>