Sylvain Bauza wrote:
> While I agree with most of what Thierry said, I need clarifications
> though, on what a Program is,

A "team" is a group of people working on a given mission. They can be
freely created. They apply to become an "OpenStack Program" if they feel
their (well-established) mission is essential to the production of
"OpenStack" and would like to place themselves under the authority of
the Technical Committee.

> and what is the key point where an idea
> should get its own Program instead of being headed by an already
> existing Program.

Depends on who is involved, and if the proposed mission is overlapping
with an existing Program's mission. If those are two different sets of
people, or the missions diverge completely, then it makes sense to make
a new program. If those teams share a lot of contributors and their
missions can be aligned, making it a single program would probably be
beneficial. And then there are all the shades of grey in between.

Thierry Carrez (ttx)

OpenStack-dev mailing list

Reply via email to