> Thinking about your question, I'm not sure. On one hand, specifics > are good. On the other hand, it's actually hard to pin down exactly > what a technical decision is. For example, is an overhaul of the > website a technical decision? I would argue that it is, since it's an > "action" being taken by the community. > > It's a tough call... Does anyone (Alex?) want to see us describe > technical decisions better? If so, suggested phrasing? >
I think the technical decisions part should be defined elsewhere. I just see that as rather ambiguous as I read the bylaws but I think it will change as the community adapts but the bylaws shouldn't change. Maybe we can just add some language to say it's defined elsewhere. It is always my opinion that even the kitchen sink can be included in cloudstack as long as you wrap it inside a plugin that can be completely disabled. I always feel it's the community's role to ensure that all new code can be disabled. So to me technical decisions is always about did you fit it into a plugin mechanism or introduce a plugin interface to make sure it's properly isolated. --Alex
