[openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

Zhipeng Huang zhipengh512 at gmail.com
Mon Apr 23 14:47:18 UTC 2018


big +1 to Graham's suggestion

On Mon, Apr 23, 2018 at 10:36 PM, Graham Hayes <gr at ham.ie> wrote:

> On 18/04/18 11:38, Chris Dent wrote:
> > On Tue, 17 Apr 2018, Thierry Carrez wrote:
> >
> >> So... Is there any specific topic you think we should cover in that
> >> meeting ?
> >
> > The topics:
> >
> > 1. What are we to do, as a community, when external pressures for
> > results are not matched by contribution of resources to produce
> > those results? There are probably several examples of this, but one
> > that I'm particularly familiar with is the drive to be able to
> > satisfy complex hardware topologies demanded by virtual network
> > functions and related NFV use cases. Within nova, and I suspect other
> > projects, there is intense pressure to make progress and intense
> > effort that is removing resources from other areas. But the amount
> > of daily, visible contribution from the interest companies [1] is
> > _sometimes_ limited. There are many factors in this, and obviously
> > "throw more people at it" is not a silver bullet, but there are
> > things to talk about here that need the input from all the segments.
> >
> > 2. We've made progress of late with acknowledging the concepts
> > and importance of casual contribution and "drive-by bug fixing" in
> > our changing environment. But we've not yet made enough progress in
> > changing the way we do work. Corporate foundation members need to be
> > more aware and more accepting that the people they provide to work
> > "mostly upstream" need to be focused on making other people capable
> > of contribution. Not on getting features done. And those of us who
> > do have the privilege of being "mostly upstream" need to adjust our
> > priorities.
> >
> > Somewhere in that screed are, I think, some things worth talking
> > about, but they need to be distilled out.
> >
> > [1] http://superuser.openstack.org/articles/5g-open-source-att/
>
>
> I think as an add on to this, would to ask the board to talk to members
> and see what contributions they have made to the technical side of
> OpenStack.
>
> This should not just be Number of commits / reviews / bugs etc but
> also the motivation for the work, e.g. - Feature for a product, bug fix
> found in a product, cross project work or upstream project maintenance.
>
> I don't necessarily want to shame corporate members of the foundation,
> but I think it is important to understand where our contributor base
> comes from, and what each member brings to the community table.
>
> We should also ask the board to try and formulate a plan for growing
> new cross project leaders (not just TC / PTLs). We need to grow more
> technical contributors in the horizontal teams, which requires more
> than assigning a contributor to the QA / Infra / Olso / Docs teams
> for a year or so - the people should be allowed a certain amount
> of stability in a role, while not necessarily driving business goals.
>
> >
> >
> >
> > ____________________________________________________________
> ______________
> > 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
>
>


-- 
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/20180423/538994ff/attachment.html>


More information about the OpenStack-dev mailing list