Stewardship Working Group

Scope
The OpenStack Technical Committee adopted a resolution to setup the Stewardship Working Group (SWG).

It was the stated intent in establishing this working group that the community would benefit from establishing a small group to review the leadership, communication, and decision making processes of the TC and OpenStack projects as a whole, and propose a set of improvements based on the the concepts of "Servant Leadership" and "Stewardship". The SWG will be responsible for producing actionable recommendations and improvements that the TC can then consider for adoption and roll out to the OpenStack community. Anyone interested in leadership, stewardship, and OpenStack is welcome to join the working group. The SWG is an advisory body. Final decisions about any changes proposed by the SWG will be made by the TC.

In particular, the SWG is interested in tackling:
 * How to improve the Technical Committee: write a vision, adopt consensus-based decision making, create distraction-free venues for TC discussion
 * What tools in the servant leadership could be used in OpenStack: look into building visions, using the bottom-line change framework, communicate more about servant leadership
 * Develop better leaders for OpenStack: expand training opportunities
 * Explore options to be more inclusive: Support non-native speakers, weird timezones, different cultures, non full-time contributors, first contributors
 * Address papercuts: facilitate keeping up with incoming information, address the difficulty to get ACKs on actions, make IRC more friendly

How to play
Join us on the #openstack-swg channel on Freenode. Start threads (marked with "[swg]" subject prefix) on openstack-dev@lists.openstack.org.

Build a vision for the TC

 * Status
 * Active


 * Contact(s)
 * Colette Alexander (gothicmindfood)


 * Goal
 * Create a two-year vision for the Technical Committee (based on Zingerman's visioning framework) to help drive decisions


 * Current state
 * Draft vision was built in an in-person workshop in Boston, then refined and posted for comments at.


 * Next steps/actions
 * Collect feedback and brainstorm needed modifications until the Boston summit
 * Presentation at the summit (gothicmindfood, johnthetubaguy, ttx)
 * Post second draft shortly after

Develop an alternative to weekly meetings

 * Status
 * Active


 * Contact(s)
 * Flavio Percoco (flaper87) and Thierry Carrez (ttx)


 * Goal
 * Drop meetings for the SWG as an experiment, and develop alternatives (status whiteboard, async discussions...)


 * Current state
 * SWG dropped meetings but hasn't moved much since. Posted a status tracking wikipage (this page) as a way to keep track of progress


 * Next steps/actions/notes
 * ACTION: Try to get momentum around this status page (ttx)
 * ACTION: Explore solutions for the TC itself (flaper87)
 * (johnthetubaguy) I prefer some kind of rhythm to things, a weekly status email that points to this page could be a good start for SWG

Collect and share best practices around being a globally inclusive community

 * Status
 * Active


 * Contact(s)
 * John Garbutt (johnthetubaguy)


 * Goal
 * Make it easy for all parts of the community to be inclusive to contributors from across the globe
 * Share current best practices to help spark ideas on how we improve


 * Current state
 * Docs team have merged some great guidance: https://docs.openstack.org/contributor-guide/non-native-english-speakers.html


 * Next steps/actions/notes
 * ACTION: Prepare a project team guide patch to help discuss current best practices https://review.openstack.org/#/c/441923 (johnthetubaguy)
 * ACTION: Prepare governance patch around decisions at in person meetings (TBC)
 * ACTION: Debate around frequency of in-person meetings (TBC)