[User-committee] Feeding results from user survey into the products (was Re: User survey comment review)

Joshua McKenty joshua at pistoncloud.com
Tue Nov 19 00:28:09 UTC 2013


+1 - I tend to ignore the PTLs when making decisions about what we would invest in.

--

Joshua McKenty
Chief Technology Officer
Piston Cloud Computing, Inc.
+1 (650) 242-5683
+1 (650) 283-6846
http://www.pistoncloud.com

"Oh, Westley, we'll never survive!"
"Nonsense. You're only saying that because no one ever has."

On Nov 18, 2013, at 2:43 PM, Stefano Maffulli <stefano at openstack.org> wrote:

> On Fri 15 Nov 2013 11:04:43 AM PST, Tim Bell wrote:
>> To explain a bit of background for these various volunteer proposals,
>> we had a session at the Summit to discuss how to close the 'operator'
>> feedback loop, i.e. take the survey feedback, translate it into user
>> stories and blue prints and then determine a priority order.
> 
> I kept thinking about this since I saw the first slides of your
> presentation in HK: how do we effectively transform the results of the
> survey and the knowledge about users into decisions for the product?
> 
> I have the impression that talking to PTLs alone may not be sufficient
> and we may want to get in touch with product managers from companies
> shipping products based on OpenStack, asking their feedback and
> commitment. PTLs have their opinions about priorities of features and
> bug fixes, users have opinions about them  too and product managers are
> probably the ones more likely capable of dedicating resources to them
> anyway (PTLs in the end are generals with no army).
> 
> What do you think?
> 
> -stef
> 
> -- 
> Ask and answer questions on https://ask.openstack.org
> 
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20131118/54afbad1/attachment.html>


More information about the User-committee mailing list