[openstack-dev] Motion on Technical Committee membership for Spring 2013 session
thierry at openstack.org
Thu Jan 24 15:54:32 UTC 2013
John Dickinson wrote:
> First, the claimed problem that needs to be solved is growing the TC above 13 total members and the worry of unbounded growth in the future based on new projects being included in the combined release. There are currently two projects in incubation status. If they are included in the combined release, under the current rules, the TC will grow to 15 members. How is 15 members worse than 13 members? Rushing into a change for the TC framework because 2 new projects might* be added seems hasty. I don't see that we have a time pressure to change. Keeping the current rules and planning for a change in the fall elections allows more time without adding undue burden to the current structure.
I want to avoid that fear of dilution (or of committee bloat) factors in
the decision to accept or reject new projects. The only way to avoid
that is to have the same committee membership whatever our decision is.
I agree with you that the choice is between evolving now, or keeping the
same system for at least another 6 months. That's exactly what this
motion is about... If you prefer to keep the current system, then you
can vote against it. And since it's a "special motion" (changing the
charter), it's not exactly easy to pass. It will need 9 supporters over
13 members to succeed. I think that if it passes, it's safe to say that
it's because a large majority in the TC approved it, rather than because
it's reactionary and hasty.
Thierry Carrez (ttx)
More information about the OpenStack-dev