[OLPC_Boston] Gathering Sugar feedback [Was: Re: Another F11 build for the XO-1 has been released]

Caroline Meeks caroline at solutiongrove.com
Tue Aug 11 22:52:48 EDT 2009


Yes, I'm very interested in how to better track issues that involve changes
at the Fedora level.
Not totally following whats going on below. Any advice/todos come out of it?

Thanks,
Caroline

On Fri, Aug 7, 2009 at 2:06 AM, Mel Chua <mel at melchua.com> wrote:

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



-- 
Caroline Meeks
Solution Grove
Caroline at SolutionGrove.com

617-500-3488 - Office
505-213-3268 - Fax
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/olpc_boston/attachments/20090811/69a8eaf8/attachment.htm 


More information about the OLPC_Boston mailing list