Open Stack

Excerpts from Emilien Macchi's message of 2016-11-29 19:39:03 -0500:
> A few months ago, our community started to find and work on
> OpenStack-wide goals to "achieve visible common changes, push for
> basic levels of consistency and user experience, and efficiently
> improve certain areas where technical debt payments have become too
> high – across all OpenStack projects".
> 
> http://governance.openstack.org/goals/index.html
> 
> We started to define a first Goal in Ocata (Remove Copies of Incubated
> Oslo Code) and we would like to move forward in Pike.
> I see 3 actions we could take now:
> 
> 1) Collect feedback of our first iteration of Community Goals in
> OpenStack during Ocata. What went well? What was more challenging?
> 
> Some examples:
> - should we move the goal documents into a separate repo to allow a
> shorter review time, where we could just have 2 TC members approve
> them instead of waiting a week?
> -  we expected all teams to respond to all goals, even if they have no
> work to do. Should we continue that way?
> - should we improve the guidance to achieve Goals?
> 
> I created an etherpad if folks want to give feedback:
> https://etherpad.openstack.org/p/community-goals-ocata-feedback

We also collected some feedback at the summit, with notes in
https://etherpad.openstack.org/p/ocata-summit-xp-community-wide-goals

One piece of feedback was that restricting the work of writing up goals
to TC members felt exclusionary. We set it up that way originally to
make it clear that the goals process was not just a replacement for
cross-project specs and writing up the goal in the governance repo
should happen late in the discussion process, rather than at the
beginning. Maybe we can achieve the same effect by switching to having
TC "sponsors" for goals that should be identified before something is
written up, but allowing anyone to do the writing?

> 2) Goals backlog - https://etherpad.openstack.org/p/community-goals
> - new Goals are highly welcome.
> - each Goal would be achievable in one cycle, if not I think we need
> to break it down into separated Goals (with connections).
> - some Goals already have a team (ex: Python 3) but some haven't.
> Maybe could we dress a list of people able to step-up and volunteer to
> help on these ones.
> - some Goals might require some documentation for how to achieve it.
> 
> I think for now 2) can be discussed on the etherpad, though feel free
> to propose another channel.
> 
> 3) Choose Goals for Pike.
> Some of us already did, but we might want to start looking at what
> Goals we would like to achieve during Pike cycle.
> I was thinking at giving a score to the Goals, that could be
> calculated by its priority (I know it's vague but we know what is
> really urgent for us versus what can wait 6 months); but also the
> number of people who are interested to contribute on a Goal (if this
> Goal doesn't have a team yet).
> For now, openstack/governance is the repository for Goals, please
> propose them here.
> 
> 
> Please give feedback, we're doing iterations here, and hopefully we'll
> improve our Community Goals over the next cycles.
> Thanks for your time,