Open Stack

There is a formal structure via the OpenStack user committee and the associated working groups (https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee). We have Monday afternoon and all of Thursday in the summit time dedicated to discussions. The specs review process was prepared with the TC to allow easy ways for deployers and consumers of OpenStack to give input before code gets written.

Further volunteers and suggestions on how to improve the process in this area would be more than welcome in the design summit tracks around the Ops summit and working groups. Please see http://kilodesignsummit.sched.org/.

Tim

From: Mike Spreitzer [mailto:mspreitz at us.ibm.com]
Sent: 24 October 2014 07:05
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all] How can we get more feedback from users?

Angus Salkeld <asalkeld at mirantis.com<mailto:asalkeld at mirantis.com>> wrote on 10/24/2014 12:32:04 AM:

> I have felt some grumblings about usability issues with Heat
> templates/client/etc..
> and wanted a way that users could come and give us feedback easily
> (low barrier). I started an etherpad (https://
> etherpad.openstack.org/p/heat-useablity-improvements) - the first
> win is it is spelt wrong :-O

> We now have some great feedback there in a very short time, most of
> this we should be able to solve.

> This lead me to think, "should OpenStack have a more general
> mechanism for users to provide feedback". The idea is this is not
> for bugs or support, but for users to express pain points, requests
> for features and docs/howtos.

> It's not easy to improve your software unless you are listening to your users.

> Ideas?

I very much agree with this.

I am actually surprised that OpenStack does not have something fairly formal and organized about this.  I suppose it is part of the TC's job, but I think we need more than they can do.  I would suggest some sort of user's council that gets involved in blueprint and change reviews.  Perhaps after first working toward some degree of consensus and some degree of shaping what the developers work on in each release (this latter is part of the overall program of improving review queue speed, by better focusing developers and reviewers on some shared agenda).

Other products have discussion fora, some explicitly dedicated to feedback.  You could approximate this with etherpads, or use some real discussion forum platform.

Regards,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141024/e89e361d/attachment.html>