[IAEP] Feedback on Launchpad
dfarning at sugarlabs.org
Wed Aug 26 09:27:24 EDT 2009
As we look at this, we need to think about it from two separate, yet
equally important perspective:
1. How feedback moves from the user to the channel (and back to the user)
2. How feedback moves from the channel to the developer.
It looks like you and Luke are the champions for this issues. Would
it make sense if you split the problem up, with you looking at #1 and
Luke looking at #2?
On Wed, Aug 26, 2009 at 7:18 AM, Caroline
Meeks<caroline at solutiongrove.com> wrote:
> We are currently evaluating GetSatisfaction and Launchpad as ways to engage
> users/deployments and manage roadmaps/features.
> Looking at the IAEP discussion on
> what we have accomplished and not accomplished my visions is:
> We have a list of features.
> People can
> discuss the features, problems, wishes, what it would do for them, what workarounds/ attempts they have made to fix these.
> People can +1 vote for them.
> We have a way of roughly associating votes with deployments and number of users.
> They system is reasonably friendly for a multilingual audience.
> Personally I'd like to choose
> Launch Pad. Its open source where Get Satisfaction is only free to us.
> However here is today's problem with LaunchPad
> I want to discuss a features in the roadmap/blueprint.
> To do this I tried to use Feedback, because I indeed what to ask a question
> about a feature. But I have to choose someone to ask! What if I don't know
> anyone? Why do I have to know someone to discuss a feature?
> I worked around by using the Whiteboard. Maybe this is good enough?
> There seems to be no way to vote for a feature/spec. Given our current
> focus on trying to be responsive to the needs of our users this seems like a
> really important feature.
> Caroline Meeks
> Solution Grove
> Caroline at SolutionGrove.com
> 617-500-3488 - Office
> 505-213-3268 - Fax
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
More information about the IAEP