Open Stack

I agree in principle that why's are a good thing. I've been feeling recently that several of the things we do are just treated as a rule by folks. Since every single project rule and decision actually does have a reason for existence and a problem it was trying to solve, reasons listed and documented could certainly help things feel less like rule by fiat to newcomers.

On Apr 14, 2014 5:25 AM, Thierry Carrez <thierry at openstack.org> wrote:
>
> Sean Dague wrote: 
> > [...] 
> > So the question is: how do people feel about changing the tone of this 
> > document to include the rationales baked directly into it? 
> > 
> > If the answer is general positive, I can take a spin on it. But want at 
> > least some nod before moving forward. 
>
> My gut feeling is that the document including the whys would become a 
> bit too wordy, but I'm ready to be convinced, so feel free to have a 
> try. If it's too wordy we could put a "why" paragraph above the 
> checklist instead... 
>
> -- 
> Thierry Carrez (ttx) 
>
> _______________________________________________ 
> OpenStack-TC mailing list 
> OpenStack-TC at lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc