[openstack-dev] [all][tc][ptl] establishing project-wide goals

Doug Hellmann doug at doughellmann.com
Wed Aug 10 15:29:35 UTC 2016

Excerpts from Doug Hellmann's message of 2016-07-29 16:55:22 -0400:
> One of the outcomes of the discussion at the leadership training
> session earlier this year was the idea that the TC should set some
> community-wide goals for accomplishing specific technical tasks to
> get the projects synced up and moving in the same direction.
> After several drafts via etherpad and input from other TC and SWG
> members, I've prepared the change for the governance repo [1] and
> am ready to open this discussion up to the broader community. Please
> read through the patch carefully, especially the "goals/index.rst"
> document which tries to lay out the expectations for what makes a
> good goal for this purpose and for how teams are meant to approach
> working on these goals.
> I've also prepared two patches proposing specific goals for Ocata
> [2][3].  I've tried to keep these suggested goals for the first
> iteration limited to "finish what we've started" type items, so
> they are small and straightforward enough to be able to be completed.
> That will let us experiment with the process of managing goals this
> time around, and set us up for discussions that may need to happen
> at the Ocata summit about implementation.
> For future cycles, we can iterate on making the goals "harder", and
> collecting suggestions for goals from the community during the forum
> discussions that will happen at summits starting in Boston.
> Doug
> [1] https://review.openstack.org/349068 describe a process for managing community-wide goals
> [2] https://review.openstack.org/349069 add ocata goal "support python 3.5"
> [3] https://review.openstack.org/349070 add ocata goal "switch to oslo libraries"

The proposal was discussed at the TC meeting yesterday [4], and
left open to give more time to comment. I've added all of the PTLs
for big tent projects as reviewers on the process patch [1] to
encourage comments from them.

Please also look at the associated patches with the specific goals
for this cycle (python 3.5 support and cleaning up Oslo incubated
code).  So far most of the discussion has focused on the process,
but we need folks to think about the specific things they're going
to be asked to do during Ocata as well.


[4] http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-09-20.01.log.html

More information about the OpenStack-dev mailing list