Open Stack

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.

-- 
Russell Bryant