Open Stack

UserVoice can easily be installed as a widget into OpenStack-Dashboard:
this would allow us to gather feedback directly from a point of interaction
for all the users. (Obviously opt-in, but could be folded into the opt-in
stats tracking).

Ask is integrated into LP for login - that's exactly opposite of what I'm
trying to accomplish (make it easy for non-developers to participate).
Let's assume that for every developer, there are (eventually) 100
operators, and for every operator there are at least 100 consumers (cloud
end-users). Optimizing a low-friction process for those consumers to
provide feedback is what I'm aiming for.


On Fri, Mar 8, 2013 at 4:17 PM, Stefano Maffulli <stefano at openstack.org>wrote:

> On 03/08/2013 03:17 PM, Joshua McKenty wrote:
>
>> I'd like to emphasize that using the same tool for developers, and
>> users, is probably not ideal.
>>
>
> Totally agreed. Ask is not for developers, it's a replacement for the
> forums and a better system than a mailing list for (at least some)
> operators/devops.
>
>
>  Again, the Launchpad workflow is optimized
>> for the SOLUTION side - feedback, or user feature requests, aren't
>> QUESTIONS.
>>
>
> I agree they're not questions.
>
> My concern is that adding tools may create problems. I get the feeling
> that I'm missing something here: what's exactly the need? How do you think
> the processes will have to be? who's going to be responsible for what?
>
> /stef
>



-- 
--
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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20130308/66201d02/attachment.html>