[User-committee] FW: [openstack] - [New Idea] - Automatically track non-engineering ATCs

Stefano Maffulli stefano at openstack.org
Fri Mar 8 18:01:15 UTC 2013


Hello folks,

i like the idea of capturing user feedback in a more consistent way. 
I'm wondering whether we can use Ask OpenStack for that and avoid 
multiplication of tools. Ask.openstack.org should be ready in a couple 
of weeks (the tool is being customised, skin and integration with 
launchpad, and some basic content). While not specifically dedicated 
like uservoice and ideascale, probably it can be adapted. The main 
advantage of Ask OpenStack is that in the next phase it will allow 
other languages, too. Do you think we can use Ask for capturing user 
feedback?

/stef

On Fri 08 Mar 2013 08:39:51 AM PST, Tim Bell wrote:
> Looking at the tools, I’m happy with ideascale… being able to identify
> the requester is necessary as we try to refine the requirement to a
> blueprint. Uservoice seemed to have a lot of other things that we
> would not be using.
>
> For people who wish to contribute anonymously, we’re looking at some
> form of NDA for the user committee members and thus, we could provide
> the information on behalf of an anonymous user but remain a good
> conduit for any feedback.
>
> Tim
>
> *From:*Joshua McKenty [mailto:joshua at pistoncloud.com]
> *Sent:* 07 March 2013 22:10
> *To:* Tim Bell
> *Cc:* user-committee at lists.openstack.org
> *Subject:* Re: FW: [openstack] - [New Idea] - Automatically track
> non-engineering ATCs
>
> Yes, exactly - this is targeting step 1. Uservoice allows anonymous
> ideas and feedback, while either of them can integrate with outside
> SSO solutions (using the user DB from the foundation is an obvious one).
>
> Joshua
>
> On Wed, Mar 6, 2013 at 12:01 PM, Tim Bell <Tim.Bell at cern.ch
> <mailto:Tim.Bell at cern.ch>> wrote:
>
>     What’s your impressions of the tool ?
>
>     I see there being several stages to define user requirements
>
>     1.User identifies need (but should not be expected to define the
>     solution)
>
>     2.Following technical analysis, blueprint(s) are created based on
>     the identified need which map into architecturally valid
>     components to solve the user need
>
>     3.Bugs/Features are raised, implemented and resolved to address
>     the need in the appropriate release cycle
>
>     Would the tool be a feasible method to gather needs or are there
>     others ? I would like to avoid further user registration if possible…
>
>     Tim
>
>     *From:*Joshua McKenty [mailto:joshua at pistoncloud.com
>     <mailto:joshua at pistoncloud.com>]
>     *Sent:* 05 March 2013 03:36
>     *To:* Tim Bell
>     *Subject:* Re: FW: [openstack] - [New Idea] - Automatically track
>     non-engineering ATCs
>
>     Sorry about that; I just wanted to see if it was possible and
>     forgot to set it back. The goal is to test using an ideation and
>     voting framework for ad-hoc user feedback; I'm also testing
>     uservoice at openstacker.uservoice.com
>     <http://openstacker.uservoice.com>.
>
>     On Mar 3, 2013 5:10 AM, "Tim Bell" <Tim.Bell at cern.ch
>     <mailto:Tim.Bell at cern.ch>> wrote:
>
>         Joshua,
>
>         These mails appear to be coming from the user committee. Can
>         you explain the goals ?
>
>         Tim
>
>         *From:*OpenStack User Committee
>         [mailto:user-committee at lists.openstack.org
>         <mailto:user-committee at lists.openstack.org>]
>         *Sent:* 03 March 2013 00:56
>         *To:* Tim Bell
>         *Subject:* [openstack] - [New Idea] - Automatically track
>         non-engineering ATCs
>
>         Idea: Automatically track non-engineering ATCs
>
>         Author: Joshua McKenty
>
>         Doc writers, bug reporters and blueprint authors should all
>         automatically be ATCs of the related project (and we have the
>         tools necessary to track this).
>
>         Click link
>         <http://openstack.ideascale.com/a/token/JsYbCizaKcUdO6VG0zhikHgK07QATo4x4mnYcEc8_pTOpHLlQzadFRODRQ9VdeTC_yZhYdLcSfEHqNLH7yCdT-JEDKy7AAejfKhmCurSJ1f7JSWDvVI93zEZTZmnrFlL>
>
>
>
> --
>
> --
> Joshua McKenty, CTO
> Piston Cloud Computing, Inc.
> w: (650) 24-CLOUD
> m: (650) 283-6846
> http://www.pistoncloud.com
>
> "Oh, Westley, we'll never survive!"
> "Nonsense. You're only saying that because no one ever has."
>
>
>
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee



More information about the User-committee mailing list