[Sugar-devel] GPA follow up

David Farning dfarning at sugarlabs.org
Mon Sep 7 12:00:28 EDT 2009


Hey Greg,

Thanks for lending your time and skill to Sugar Labs.  Your work
caused three significant improvements in Sugar Labs:
1.  You and the rest of the GPA team identified and ticketed many bugs
which need fixing.
2.  You demonstrated through action and results how an effective bug
wrangler works.
3.  You created 'peer pressure' among deployments that GPA was getting
to much attention.

Hopefully, as a result of your lead, other deployments will see that
value of having a bug wrangler and find bug wrangles or their very
own.

Thanks for everything.  Look forward to seeing you again when things
settle down at your new job.

david

On Mon, Sep 7, 2009 at 9:47 AM, Greg Smith<gregsmithpm at gmail.com> wrote:
> Hi All,
>
> I have been off the list and unproductive on the Sugar front for
> several weeks. I'm starting a new job on Tuesday so I need to unsubscribe
> from the lists for a while. I enjoyed spending time with the kids
> at GPA this summer. The timing was great and its an experience I will value
> forever.
>
> I hope this e-mail finishes a piece of work that others can take forward.
>
> I read the head lines of 523 open bugs in the sugarlabs bug DB
> (http://dev.sugarlabs.org/). I
> flagged issues that we uncovered in class this summer with GPA in the
> keyword field.
>
> I didn't add myself on CC so unicast me if you need more info.
>
> See the GPA tagged bugs at this link:
>
> http://wiki.sugarlabs.org/go/Gardner_Pilot_Academy#How_you_can_help_-_Technical_Tickets
>
> I focused on the UI things in the reports so I
> probably missed USB boot problems (e.g. 596) and server
> issues. I also left out any Jabber issues assuming that
> the "local" collaboration strategy will work going forward.
>
> I just tagged existing bugs with GPA, I didn't file any new ones.
>
> We can classify the issues in to three main categories:
> 1 - Moving files from one activity to another (e.g. download image
> from wikipedia, then use in Memorize)
> 2 - Finding things in the journal (e.g. find one of several files just
> downloaded)
> 3 - Screen resolution not consistent on different Hardware.
>
> I believe design work is underway on the first two. My suggestion is
> to test new designs with the main use cases from the reports. e.g. try
> to create a
> Memorize or Turtle Art activity with 6 images from Wikipedia. When that is
> easy, you will have a winning design.
>
> Thanks,
>
> Greg S
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


More information about the Sugar-devel mailing list