Re: Re: Report a bug directions

Sheila,
Just to clarify the utility is available to public, it's just not  
scaled to handle large number of users. I believe disk space is one  
of the main requirements.

Aparna

On Jun 15, 2007, at 4:42 PM, Sheila Mooney wrote:

> So it sounds like we don't currently have a way for users to submit  
> their repository so we shouldn't refer to that in the documentation  
> until we do. We could raise the priority but I don't know the  
> reality of getting this done for Preview at this stage. I think  
> this is why we made it a P4 in the first place. It's really a new  
> feature.
>
> It's assigned to Jared right now. Jared, do you have any thoughts?
>
> On Jun 15, 2007, at 4:31 PM, Dan Steinicke wrote:
>
>> This bug should not be closed.  The current repo-submit server is  
>> only intended for, and capable of dealing with internal users.  If  
>> we want to use repo-submit with the general public we need to move  
>> it to a different server and that is what this bug is about.
>> Currently this bug is P4, perhaps we need to raise the prioritly.
>>
>> Dan
>>
>> Sheila Mooney wrote:
>>> So if it already works, shouldn't this bug be closed?
>>>
>>> On Jun 15, 2007, at 4:18 PM, Bryan Stearns wrote:
>>>
>>>> Yep: https://bugzilla.osafoundation.org/show_bug.cgi?id=7139
>>>>
>>>> Sheila Mooney wrote:
>>>>> I thought there was a bug logged for a public repository submit  
>>>>> mechanism. I don't remember if we punted this or we are still  
>>>>> intending on doing this for Preview.
>>>>>
>>>>> On Jun 15, 2007, at 11:35 AM, Ted Leung wrote:
>>>>>
>>>>>> I think that the pages that Mimi is working on are really  
>>>>>> targetted for the Preview launch timeframe.   At that point, I  
>>>>>> think we want to deal with all users uniformly...
>>>>>>
>>>>>> Ted
>>>>>>
>>>>>> On Jun 14, 2007, at 9:14 PM, Aparna Kadakia wrote:
>>>>>>
>>>>>>> We also have the instructions for dogfooders page which  
>>>>>>> instructs users on how to report problems, log files,  
>>>>>>> repositories etc.
>>>>>>> There is also overlap between this page and the ReportABug page.
>>>>>>>
>>>>>>> http://chandlerproject.org/Projects/InstructionsForDogfooders
>>>>>>>
>>>>>>> Aparna
>>>>>>>
>>>>>>> On Jun 14, 2007, at 6:19 PM, Mimi Yin wrote:
>>>>>>>
>>>>>>>> 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

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general