Open Stack

On 01/16/2017 04:02 PM, Jonathan Bryce wrote:
> 
>> On Jan 16, 2017, at 11:03 AM, Matt Riedemann
>> <mriedem at linux.vnet.ibm.com <mailto:mriedem at linux.vnet.ibm.com>> wrote:
>>
>> On 1/12/2017 7:30 PM, Melvin Hillsman wrote:
>>> Hey everyone,
>>>
>>> I am hoping to get a dialogue started to gain some insight around things
>>> Operators, Application Developers, and End Users would like to see
>>> happen in Pike. If you had a dedicated environment, dedicated team, and
>>> freedom to choose how you deployed, new features, older features,
>>> enhancements, etc, and were not required to deal with customer/client
>>> tickets, calls, and maintenances, could keep a good feedback loop
>>> between your team and the upstream community of any project, what would
>>> like to make happen or work on hoping the next release of OpenStack
>>> had/included/changed/enhanced/removed…?
>>>
>>
>> I just wanted to say thanks for starting this thread. I often wonder
>> what people would like to see the Nova team prioritize because we
>> don't get input from the product work group or Foundation really on
>> big ticket items so we're generally left to prioritizing work on our
>> own each release.
> 
> I agree; thanks Melvin! Great input so far.
> 
> Matt, on the input on big ticket items, I’d love to get your feedback on
> what is missing or you’d like to see more of in the Foundation reports
> or Product Working Group roadmaps to make them more useful for these
> kinds of items. Is this thread more consumable because specific
> functionality is identified over themes? Is it the way it’s scoped to a
> release? We could possibly even add in a similar question (“What would
> you like to see in the next release?”) to the user survey if this is
> info you’ve been looking for.

One of the challenges thus far on PWG input is it has often not been
very grounded in reality. It often misses key details about what's hard,
possible, or easy when it comes to the code and communities in question.
The operator list feedback is typically by teams that are much more
steeped in the day to days of running OpenStack, have sifted through
chunks of the code, chatted more with community members. It very often
starts from a place of much more common ground and understanding.

	-Sean

-- 
Sean Dague
http://dague.net