[openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?
Graham Hayes
gr at ham.ie
Mon Apr 23 15:20:46 UTC 2018
On 23/04/18 15:06, Doug Hellmann wrote:
> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> Over the last year we have seen some contraction in the number of
> companies and individuals contributing to OpenStack. At the same
> time we have started seeing contributions from other companies and
> individuals. To some degree this contraction and shift in contributor
> base is a natural outcome of changes in OpenStack itself along with
> the rest of the technology industry, but as with any change it
> raises questions about how and whether we can ensure a smooth
> transition to a new steady state.
>
> What aspects of our policies or culture make contributing to OpenStack
> more difficult than contributing to other open source projects?
Our scale.
To get a large feature merged can require get code
prioritised by 2 or 3 different teams, and merged into any number of
repositories.
To get a small feature merged on some projects can take some time as
well, purely from the amount of code that is submitted for review to
these projects.
> Which of those would you change, and how?
Well, I definitely wouldn't change our scale. What I think we need to is
start breaking down some of the gigantic mono repos we have, so that
reviewing a small feature does not need large amounts of contextual
knowledge. I think this is happening organically in some teams already
with a few teams completely plugin based and distributed (like the docs
team).
When code can be reviewed in isolation without the fear of breaking
something 2 projects away, it helps both review time, and new
contributor experience.
> Where else should we be looking for contributors?
Honestly, I don't know. The kind of work that our contributors do, does
require a certain level of equipment, and "upstream time" that makes any
serious feature development hard for a casual weekend contributor.
> Doug
>
> __________________________________________________________________________
> 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
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180423/7b19b56b/attachment.sig>
More information about the OpenStack-dev
mailing list