Bugs, bugs, and more bugs.

6.4:
Here is the bug that we've been working on.  When the user enters in a profile name for their account during setup, the field currently does not trim any spaces entered on the left or right side.  This occurs during the initial setup of setting up the profile name, or if the user decides to edit it later.

This bug has been sitting around for about 3 months, and I have a decent idea why.  We sent an email to the development team asking where to get started on this bug, and they pointed us in the right direction.  Walter Bender wrote back within minutes pointing us to where we can fix this.  Minutes after, others began replying, and arguing whether or not this was actually a bug, or if it was more of a feature.  They argued that the user should be able to enter in spaces in their name if they prefer to.  The main reason this bug is because the community is unsure how to handle it.

6.5:
I've created an account on the Sugar Lab's bug tracker.

6.6: Bug report
This bug can be reproduced in two ways:
A.  Initial creation of the user account, following these steps.
1.  User launches the Sugar OS for the first time.
2.  The user is prompted to enter in a name.
3.  The user enters in text in the Name field, and puts spaces before or after the desired name.
4.  The user clicks the check sign, and continues to set up the Sugar OS for the first time.
5.  The user clicks on their main Sugar icon, then clicks on their name.
6.  The user clicks on My Settings, then About Me.
7.  The user clicks within the name text field, and finds space to the left and right of the desired name.

B.  Editing the user account name.
1.  The user opens the Sugar OS.
2.  The user clicks on their main Sugar icon, then clicks on their name.
3.  The user clicks on My Settings, then About Me.
4.  The user clicks within the name text field, and enters space to the left and right of their name.
5.  The user clicks the check mark to save the changes.
6.  The user clicks About Me again, then clicks within the Name field and finds space to the left and right of their name.

6.7:
Bug Triage:
SugarLab's bug tracker is organized into three priorities:  Low, Minor, Normal,  High, Major, and Immediate.
Bug #2564:  This bug has to do with the simplicity of backing up and restoring files in the Sugar OS.  While this bug is important, it may not be the most pressing one to complete, since most users aren't going to be backing up files often, especially kids.  I would say that this should be prioritized as Normal.
Bug #2352:  This bug is about documentation that is missing from Patchwork.  While it is important to keep documentation updated for programmers to use as a guide, it's definitely not a critical problem that would effect the user's experience.  I'd say this is a Low priority bug.
Bug #2227:  This bug contains a detailed log of an error thrown when trying to launch a Sugar OS component called XoPhoto.  I would argue that this is either a High, or Major priority bug, because the component is completely unusable by certain users.  While the component may not be used by a high number of users, it is still important because the users that are affected cannot use the software at all.
Bug #1741:  This bug is a complaint about the absence of a detailed report of a connection error when integrating a Jabber server in the Sugar OS.  The error given does not provide the user with any useful information about what the problem might be.  I'd say this is a Normal, maybe Low priority bug.
Bug #1936:  This bug talks about the Sugar OS datastore, which is a component that can be very large depending on the amount activities and other components installed in the Sugar OS.  When the datastore has a high amount of data, it returns an error, which is provided in the bug report.  This could potentially be a big problem if a high number of users have a lot of data stored in the Sugar OS.  This would be a High or Major priority bug.


Side note:  I finally remembered to sign up for the Alumni Symposium next week.