Open Stack

I think it's a great idea to develop a process for operators to go
through in suggesting work for dev teams.  One that alleviates a lot
of the burden of having to know what is and is not a valid bug or blue
print.  If the operations contributors can work together to self solve
problems and promote real issues that's a win for everyone.  Low
barrier of entry for operators of the stack, plus quality bug reports
and blue prints.

I really like the idea.

-Matt

On Thu, Nov 8, 2012 at 11:39 AM, Tim Bell <Tim.Bell at cern.ch> wrote:
>
> Lloyd,
>
> Not all of the openstack users are not as confident as you are :-) :-)
>
> Personally, I appreciate having other users validate that what I feel is a
> requirement is not my incorrect approach.  I'm sure there are ways of doing
> this sort of flow within Launchpad but getting a starter list together on a
> wiki as James has started is a good way to bootstrap the process.
>
> Tim
>
>> -----Original Message-----
>> From: Lloyd Dewolf [mailto:lloydostack at gmail.com]
>> Sent: 08 November 2012 20:22
>> To: Tim Bell
>> Cc: Michael Still; James R Penick; openstack-operators at lists.openstack.org
>> Subject: Re: [Openstack-operators] Operations use cases/pain points
>>
>> I've never hesitated to open issues containing only experienced issues or
>> symptoms. All successful software projects handle these with grace.
>>
>> On Thu, Nov 8, 2012 at 11:16 AM, Tim Bell <Tim.Bell at cern.ch> wrote:
>> >
>> > Our user community should not be obliged to understand the internals
>> > of OpenStack. Many high level pain points can have multiple project hits
>> (e.g.
>> > horizon/keystone/nova)
>>
>>
>> --
>> @lloyddewolf
>> http://www.pistoncloud.com/
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>