openstack: upstream first
TRANSCRIPT
OPENSTACK: UPSTREAM FIRST RUSSELL BRYANT - @RUSSELLBRYANT
TECHNICAL DIRECTOR, OPENSTACK
OFFICE OF TECHNOLOGY
https://redhat.slides.com/rbryant/openstack-east-august-2016
UPSTREAM FIRST CODE
WHAT?
design, dev, test
all upstream
VALUE
influence
maintenance
quality and security
interoperability
RISKS OF FORKING
quality
user expectations
technical debt
interoperability
DEVELOPMENT
MY FIRST SIX WEEKS IN PATCHES
1 - Trivial doc fix
2 - Small bug fix
3 - API docs and code cleanup
4 - My new feature
5-15 - Cleanup and fixes mostly unrelated to my feature
HORIZONTAL TEAMSOpenStack has 58 official project teams
A lot of support and coordination required
Horizontal teams work across all projects
How can you help?
RELEASE MANAGEMENTMission
Coordinating the release of OpenStack deliverables, by defining theoverall development cycle, release models, publication processes,versioning rules and tools, then enabling project teams to produce
their own releases.
RELEASE MANAGEMENTHow can you help?
Be aware of the release cycle:
http://releases.openstack.org
Serve as a liaison.
HORIZONTAL TEAM LIAISONSServe as the primary interface between a horizontal team
and a project focused team.
INFRASTRUCTUREMission
Develop and maintain the tooling and infrastructure needed tosupport the development process and general operation of the
OpenStack project.
INFRASTRUCTURE
Day (last week) Nodes Used
Monday 14,868
Tuesday 19,310
Wednesday 21,329
Thursday 24,930
INFRASTRUCTUREHow can you help?
(besides donating cloud capacity)
More long-term half to full-time contributors.
Across all time zones.
Manage both code and systems.
Serve as a liaison.
DOCUMENTATIONMission
Provide documentation for core OpenStack projects to promoteOpenStack. Develop and maintain tools and processes to ensure
quality, accurate documentation. Treat documentation likeOpenStack code.
DOCUMENTATIONFantastic team developing great content.
http://docs.openstack.org/
If we don't document features, they might as well not exist.
DOCUMENTATIONHow can you help?
Need more active and engaged subject matter experts.
Serve as a liaison.
Contributions can be raw source content.
1 Open a bug with some bullet points.
2 Provide a link to a blog post explaining the feature.
3 Write a patch and get doc team editorial help.
4 Write a patch and incorporate doc team feedback yourself.
MORE HORIZONTAL TEAMSOslo
QA (devstack, grenade, tempest)
Stable branch
Vulnerability Management
I18n
LIAISON OPPORTUNITIESAPI Working Group
Logging Working Group
Inter-project liaisons
Cross-project specs
https://wiki.openstack.org/wiki/CrossProjectLiaisons
FURTHER UPSTREAMReported contributions from OpenStack community members to
projects that somehow touched OpenStack.
Doug asked the openstack-dev mailing list.
86 projects listed.
https://doughellmann.com/blog/2016/06/23/openstack-contributions-to-other-open-source-projects/
BEYOND DEVELOPMENTGive your teams time to help make OpenStack successful.
Product Working Group
Join discussions and review proposals.
Share your experience.
twitter.com/RedHatNews
youtube.com/redhat
facebook.com/redhatinc
THANK YOU!
plus.google.com/+RedHat
linkedin.com/company/red-hat