fix broken link
stub}}== Introduction == It's meant for the triage/bugmastering team.
* Some assigned bug reports are written in an opaque (to outsiders) shorthand that may make sense for the developer involved, but could forestall anyone else from being able to pop into and contribute towards.
:* This is a very good point actually and I would like to see it our bug reporting guidelines. --[[User:Marcopg|Marcopg]]
* Do we have a team of verification volunteers? (Should they be recruited?)
:* We don't have one but we should totally recruit it. See my and Walter notes about the verification process on [[Talk:Triage]].:: would love to help with this, personally - need to get my feet underneath me first. Also, waiting for
sugarlabs to solidify in general before pulling in new people sounds like a good idea. [[User:Mchua|Mchua]] 04:50, 16 May 2008 (UTC)
* Do we want to make it easier to cross-reference bugs with each other by using something like the [http://trac-hacks.org/wiki/TracBacksPlugin TracBacks plugin]? (Full disclosure: I wrote this.) Also potentially helpful if there will be a separate Sugar Trac: [http://trac-hacks.org/wiki/TrashTalkPlugin the TrashTalk plugin], which does external trackbacks to tickets (useful for monitoring upstream/downstream trac instances, for instance).
:* We are having a discussion about infrastructure by mail, I'll make sure we include you in the next steps. Give this a few days though, we are still defining
SugarLabs infrastructure and it's relation to laptop.org. --[[User:Marcopg|Marcopg]]
* Do we have a "trac" component on trac (to report something's broken, to request plugins, etc)? Should we?
:* Yup dev.laptop.org has such component. --[[User:Marcopg|Marcopg]]
:: D'oh. Yeah. I should have checked that first. I noticed a lot of these tickets are owned by coderanger - not sure how active he is these days - so folks may need to do a little gentle pinging for the resolution of trac component tickets which would benefit Sugar development. I can't think of any immediate use cases (read: I can't think of trac things we need yet that we don't have), so I'll leave it at this for now. [[User:Mchua|Mchua]] 04:50, 16 May 2008 (UTC)
* Do we have a good way for newcomers to get set up for testing so they can help verify all the unverified tickets and write better bug reports?
:* Good question. I will send mail about this, added it at the top of my [[User:Marcopg#TODO|TODO]]. --[[User:Marcopg|Marcopg]]
:: Update - I'm now in my 8th hour and counting of trying to get sugar-jhbuild running on my machine (running Ubuntu Hardy), despite lots of help from patient people (Tomeu, Marco, Cjb, etc...) This does not bode well if we want more volunteers. I'd love an easier way to get the bleeding-edge stuff working. Cjb pointed out that keeping the debs (Jani Monoses's Ubuntu packages etc) super up-to-date makes a great experience for people running the latest version of Ubuntu, but no experience at all (that is to say, a terrible one due to nonexistence) for people not running the latest version of Ubuntu. What other options do we have? [[User:Mchua|Mchua]] 04:50, 16 May 2008 (UTC)
* What is [http://dev.laptop.org/ticket/6283 a snowflake]?
:* The way XO icons are clustered around a shared activity in mesh view is represented by code in snowflakelayout.py in sugar. With several participants, the shape is vaguely similar to a snowflake... I'll add a better description in that ticket, in case someone other than Marco works on it...--[[User:Morgs|Morgs]] 13:56, 15 May 2008 (UTC)
in need of a spotlighting.
* How would an external tester know what milestone a ticket should be assigned to, or is this the responsibility of a triage team? I've added tickets and not known why it should belong to any specific milestone, so left it at Never Assigned. Using Update.2 as the filter shows just 85 tickets, removing that constraint lists 492 tickets (filtering for Never Assigned is about 100 extra tickets)! --[[User:garycmartin|garycmartin]]
=== High priority ===
* [http://dev.laptop.org/ticket/5629 #5629] - '''Add a disable screencorners option in Sugar-control-panel''' - fun design discussion on the UI for hot corners. Also interesting: [http://dev.laptop.org/ticket/3936 #3936], which discusses hotcorners not working in Browse sometimes, and [http://dev.laptop.org/ticket/4429 #4429] which discusses the frame-on-hotcorner behavior being slow.
:* 5629 will be fixed by Simon control panel patch. 3936 and 4429 should be verified, if they are still there we need to figure out a way to reproduce (I think that's also something the bug triaging team can help out with)