Re: Re: Report a bug directions

How about this?

http://chandlerproject.org/Journal/ReportABug

At the top, I added a short definition of what a bug is and a pointer  
to the Chandler Users list for people who don't feel like their issue  
is concrete enough for a bug report.

Right below that are 2 columns, 1 for the Desktop and the other for  
Chandler Hub/Server.

The instructions are very brief. Mostly telling you to check to see  
if your problem has been logged and a note about what extra info to  
include.

I've consolidated the overlapping material at the bottom. It's mostly  
process stuff about how to log a good bug report and how bugs are  
process.

Anything else we want to add? Do I have the right prioritization in  
terms of what info should be above the fold / below the fold?

Mimi


On Jun 14, 2007, at 5:49 PM, Ted Leung wrote:

> IOn Jun 14, 2007, at 4:55 PM, Mimi Yin wrote:
>
>> http://chandlerproject.org/Projects/ReportingBugs
>> http://chandlerproject.org/bin/view/Projects/ReportingBugsCosmo
>>
>> Who is the target audience for Reporting bugs?
>> Do we expect end-users to report bugs?
>
> I definitely expect end users to report bugs.
>
>>
>> Should we unify these pages? There's a lot of overlap and it seems  
>> like for end-users, we mostly want to pinpoint where they  
>> experienced their problem and send them on their way accordingly...
>>
>> + Chandler Desktop
>> + Chandler Hub / Chandler Server
>
> There's a bunch of common stuff about how/when to file a bug, and  
> it seems like a waste to duplicate that.   But I also agree that we  
> want it to be clear and easy to report problems on the correct  
> product.
>
> Ted
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> 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