Open Stack

Russell Bryant wrote:
> On 11/24/2014 06:37 PM, Michael Still wrote:
>> I was thinking about this, and I think that we should do a spec for
>> the proposed changes in our shiny new spec repo when we've finished
>> the discussion round. That will force us to publicly document things
>> like the problem we think we're solving, which is important for
>> explaining any changes we make to ATCs.
> 
> I think that's a good idea.  Documenting the problem and proposed
> solution in a bit more free text would be a great step to take before
> doing the modifications to the charter to implement it since the
> governance repo changes don't really capture the "why" as well.

Agreed. Having that intermediary step between wild brainstorming and
precise implementation as governance changes will let us explain the
rationale and consequences for existing projects in more detail. Not
exactly what we created openstack-specs for but I guess we can host it
there :)

I can work on a spec draft once I feel we have something solid to
propose. Hopefully by the end of the week, so that we can discuss it at
next week meeting.

-- 
Thierry Carrez (ttx)