Yes, I'm very interested in how to better track issues that involve changes at the Fedora level.<div><br></div><div>Not totally following whats going on below. Any advice/todos come out of it?</div><div><br></div><div>
Thanks,</div><div>Caroline<br><br><div class="gmail_quote">On Fri, Aug 7, 2009 at 2:06 AM, Mel Chua <span dir="ltr"><<a href="mailto:mel@melchua.com">mel@melchua.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
If it's a bug in the Sugar code, it should absolutely go into the Sugar<br>
trac (<a href="http://dev.sugarlabs.org" target="_blank">dev.sugarlabs.org</a>) - I believe the case Gary was mentioning was a<br>
bug in Fedora discovered while using Sugar (running on top of Fedora).<br>
<br>
In any case, it sounds like the three of us aren't in much of a position<br>
to tackle this problem, but a deployment hacker working with students<br>
during the school year may be. Copying the Boston list, since there are<br>
several groups working or planning to work with schools directly who<br>
might have someone interested in taking on the specific problem of a<br>
bugtracking workflow/interface for the coming semester.<br>
<br>
--Mel<br>
<br>
On 08/06/2009 06:02 AM, Steven M. Parrish wrote:<br>
>>> How would you like to receive (potential) bug feedback, via Fedora<br>
>>> tickets, or just via the mail list? Initial report chit chat usually<br>
>>> starts out as an email or two, but if via trac, do you have a 'parent'<br>
>>> tracker ticket I should reference so all tickets end up linked to one<br>
>>> tracker ticket you can see/reference?<br>
>>><br>
>>> I'm just cc:ing Mel (Hi Mel), on this as tackling Fedora<br>
>>> feedback/tickets is a fairly incessant, buzz/hum in a room fairly empty<br>
>>> of elegant solutions, so far.<br>
>> Yep. Gary and I have been talking<br>
>> (<a href="http://blog.melchua.com/2009/08/06/downstream-sugar-labs-reporting-fedora-" target="_blank">http://blog.melchua.com/2009/08/06/downstream-sugar-labs-reporting-fedora-</a><br>
>> tickets/) about it in the context of working on a downstream project (Sugar<br>
>> Labs) that finds Fedora bugs occasionally but isn't sure how to report them<br>
>> up, and the Websites list has also recently had a 'ticket workflow is<br>
>> confusing' conversation too<br>
>> (<a href="https://www.redhat.com/archives/fedora-websites-list/2009-August/msg00004" target="_blank">https://www.redhat.com/archives/fedora-websites-list/2009-August/msg00004</a>.<br>
>> html)<br>
>><br>
>> --Mel<br>
><br>
> The two of you bring up some very valid issues on bug reporting for Sugar and<br>
> Fedora. To me this seems like something that needs to be addressed as our<br>
> target audience (children) will be very confused. Off the top of my head this<br>
> is a quick idea.<br>
><br>
> We need a simple bug reporting tool to live either at <a href="http://laptop.org" target="_blank">laptop.org</a> or<br>
> <a href="http://sugarlabs.org" target="_blank">sugarlabs.org</a>. Normally in FedoraLand bugs reported against a Sugar component<br>
> would be referred to the upstream devs anyway. Until this can be realized<br>
> maybe we should just use the trak instance at <a href="http://laptop.org" target="_blank">laptop.org</a>.<br>
><br>
> This needs alot more thought.<br>
><br>
> Steven<br>
><br>
><br>
> =====================================================<br>
> Steven M. Parrish<br>
> -------------------------------------------------------------------------------------------------<br>
> gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0<br>
> <a href="http://tuxbrewr.fedorapeople.org/" target="_blank">http://tuxbrewr.fedorapeople.org/</a><br>
> <a href="http://irc.freenode.net" target="_blank">irc.freenode.net</a>: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar<br>
_______________________________________________<br>
OLPC_Boston mailing list<br>
<a href="mailto:OLPC_Boston@lists.laptop.org">OLPC_Boston@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/olpc_boston" target="_blank">http://lists.laptop.org/listinfo/olpc_boston</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Caroline Meeks<br>Solution Grove<br>Caroline@SolutionGrove.com<br><br>617-500-3488 - Office<br>505-213-3268 - Fax<br>
</div>