The Impact of Individual Contributors on OpenStack Community Strategic Priorities

May, 2018

What is a “Contribution”?

• Work done in repositories for official teams
• Focus on community work; no teams with single-vendor tag
• Activity on a review or patch:
• Creating a patch
• Updating a patch
• Voting +2 or -1
• Approving
• Ignores +1 votes that are easy to “game”

“Help Most Needed” Areas

https://governance.openstack.org/tc/reference/help-most-needed.html

Community Goals

https://governance.openstack.org/tc/goals/index.html

Cross-Project Teams

during Pike and Queens

Stable Branch Maintenance

Unmet Requirements

Conclusions

• Individuals, given time, can have a disproportionate impact on the community
• We have a small number of people doing this level of work; not enough
• Divide and conquer
• Dividing work into smaller tasks and distributing it makes an initiative or goal more successful
• This still takes someone with the time to understand how to split the work up
• Requires work to align the teams involved
• Need help with several teams
• Designate, Glance, Dependency Management, Release Management, Oslo
• Contributors need time to grow into those roles

How do we change our approach to recruiting help in strategic areas to have more success than past attempts?

Supporting Slides