On 2018-04-23 15:36:32 +0100 (+0100), Graham Hayes wrote: > 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. [...]
Taking this further, I really think that the spirit of our requirement that certain member organizations dedicate staff to contributing is that they be applied to under-served commons in the project (whether that's helping in horizontal teams and on cross-project goals, or triaging bugs and answering random usage questions). If they get to count the staff they put on some feature they needed for their new product launch, that's rather self-serving and doesn't really help us much. -- Jeremy Stanley
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
