[General] tracking end-user feedback...

[Sheila Mooney]

I agree with Mimi. Bugzilla is the right place for this information  
and we have been doing a pretty good job at logging these now. In a  
sense we are using one system.

I notice when I do the design summaries that bugs do get logged after  
we have some level of back and forth conversation to isolate the  
exact issue. Mimi does a pretty good job extracting this information  
and logging both the future and current items as well as circling  
back and letting people know they have been logged. Many times people  
will proactively log bugs or a feature request and never make that  
request on the the list so I think having everything put in bugzilla  
makes sense.

Of course as we get more users on the list, going through these and  
logging them will be time consuming but perhaps this will simply be  
part of everyone's role in responding to mails on this list. For  
straightforward bugs we should probably encourage people to log them  
into bugzilla themselves.

Sheila

On Jun 26, 2007, at 7:39 AM, Mimi Yin wrote:

> Hi Aparna, I would be up for tracking all three forms of feedback  
> in bugzilla if they haven't already been logged. Some of the issues  
> may be hard to frame just right in bugzilla because they will take  
> some amount of back and forth on the list to tease out exactly what  
> the issue is. I can take responsibility for logging those kinds of  
> bugs.
>
> I think Andre's latest D/F Usage Notes has a mixture of no-brainer  
> bugs and bugs that need a bit more discussion. I can go through the  
> list and divvy them up? I've already started one thread about the  
> Update button, but there are a couple of others that I'd like to  
> discuss a bit more before logging bugs.
>
> Does that help?
>
> Mimi
>
> On Jun 25, 2007, at 2:48 PM, Aparna Kadakia wrote:
>
>> Hello all,
>> While we are slowly approaching the Preivew end game, we are  
>> seeing an increased communication from end-users about their  
>> dogfood feedback. I had a general question about how we want to  
>> track these.
>>
>> Some of the feedback is coming consolidated over email, like  
>> Andre's this morning, while others as bug reports while a few are  
>> coming verbally(Mitch and Esther case). Also the issues brought up  
>> in the feedback fall into one of the 3 categories:
>> 1. genuine bugs
>> 2. nice to have/design improvements
>> 3. known issues that are currently punted to future
>>
>> Are we looking at consolidating all the feedback in 1 system?
>> With that I mean are we tracking the feedback on chandler-users  
>> list?  Or are we tracking it in bugzilla?
>> Also, for the issues brought up in the feedback that refer to  
>> punted bugs, should we append the bug reports with the additional  
>> feedback so we track how many people are encountering it.
>>
>> Depending on the convention we decide to follow, we might need to  
>> either log the issues in Bugzilla or send emails to the users list.
>>
>> I am all for tracking them in bugzilla. I can take the  
>> responsibility of transitioning the issues brought up on the users  
>> list over to Bugzilla, if we indeed decide to go that route.
>>
>> Let me know if you have any thoughts,
>> Aparna
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "General" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/general
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "General" mailing list
> http://lists.osafoundation.org/mailman/listinfo/general