Terrific idea!  So what happens with the feedback you receive?
I am, of course, most interested in issues that might help us improve
the documentation, of course, but it's a general question about how
this information flows to the Product Engineering team.

meg

On Thu, Oct 23, 2014 at 11:46 PM, Tim Bell <tim.b...@cern.ch> wrote:

>  Angus,
>
>
>
> There are two groups which may be relevant regarding ‘consumers’ of Heat
>
>
>
> -        Application eco system working group at
> https://wiki.openstack.org/wiki/Application_Ecosystem_Working_Group
>
> -        API working group at
> https://wiki.openstack.org/wiki/API_Working_Group
>
>
>
> There are some discussions planned as part of the breakouts in the Kilo
> design summit (http://kilodesignsummit.sched.org/)
>
>
>
> So, there are frameworks in place and we would welcome volunteers to help
> advance these in a consistent way across the OpenStack programs.
>
>
>
> Tim
>
>
>
> *From:* Angus Salkeld [mailto:asalk...@mirantis.com]
> *Sent:* 24 October 2014 08:16
> *To:* Stefano Maffulli
> *Cc:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [all] How can we get more feedback from
> users?
>
>
>
> On Fri, Oct 24, 2014 at 4:00 PM, Stefano Maffulli <stef...@openstack.org>
> wrote:
>
> Hi Angus,
>
> quite a noble intent, one that requires lots of attempts like this you
> have started.
>
> On 10/23/2014 09:32 PM, Angus Salkeld wrote:
> > 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.
>
> One place to start is to pay attention to what happens on the operators
> mailing list. Posting this message there would probably help since lots
> of users hang out there.
>
> In Paris there will be another operators mini-summit, the fourth IIRC,
> one every 3 months more or less (I can't find the details at the moment,
> I assume they'll be published soon -- Ideas are being collected on
> https://etherpad.openstack.org/p/PAR-ops-meetup).
>
>
>
> Thanks for those pointers, we very interested in feedback from operators,
> but
>
> in this case I am talking more about end users not operators (people that
> actually use our API).
>
> -Angus
>
>
>
> Another effort to close this 'feedback loop' is the new working group
> temporarily named 'influencers' that will meet in Paris for the first
> time:
>
> https://openstacksummitnovember2014paris.sched.org/event/268a9853812c22ca8d0636b9d8f0c831
>
> It's great to see lots of efforts going in the same direction. Keep 'em
> coming.
>
> /stef
>
> --
> Ask and answer questions on https://ask.openstack.org
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to