Open Stack

Mark McLoughlin wrote:
> On Mon, 2013-07-15 at 14:14 -0400, Russell Bryant wrote:
>> On 07/15/2013 11:39 AM, Dean Troyer wrote:
>>> DevStack plays multiple roles in the development process for OpenStack.
>>
>> Does it really make sense to be its own program?  There was mention of
>> just making it a part of infra or QA.  QA actually makes the most sense
>> to me, since devstack's primary use case is to make it easy to test
>> OpenStack.
> 
> How about if the title of the program was 'Developer Tools'?
> 
> Is devstack the only project which would fall into that bucket?

The trick with programs is that it's not just about finding themes and
aggregate existing projects around them. At the heart of a program is an
existing team of people that works (well) together towards that common goal.

Putting devstack in a "Developer tools" bucket only makes sense if the
team that cares about devstack also cares about those other "developer
tools". You don't really want to create an ugly stepchild effect by
adding random projects onto unwanting people's plates.

-- 
Thierry Carrez (ttx)