Jump to: navigation, search

BugSquad/Triage Team

1,707 bytes removed, 14:47, 6 June 2019
fix broken link
<noinclude>{{stubGoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>{{TOCright}}== Introduction = Questions ===It's meant for the triage/bugmastering team.
The current page is for the latest updates on progress, bugs, questions, and suchnot. For older notes, see the [[/Archive]] - this is one of those rare cases where the archives may be just as useful (if not more so) than the current notes. Thoughts on restructuring this page are welcomed.
== Summary =What are the priorities for Sugar development? ===:* The [ 1.0 Roadmap] should give you a good idea of what are the medium term priorities. --[[User:Marcopg|Marcopg]]
Attempts from May 14* What is the goal for this upcoming milestones?:* For 0.82, the next Sugar release, we are going to work mainly on OLPC [ priorities]. I've refrained need to extract the major Sugar features and changes from actually doing anything in Trac this time because I want there and add to see if my comments are onthe [[Development Team/Release/Roadmap]]. Other than that 0.82 will be mostly bug fixes. --track here.[[User:Marcopg|Marcopg]]
:* What about moving this outside your Userare the big annoyances/obstacles to making the above happen? [[TriageTeam]] or something:* I don't see big obstacles. We already have [[Triage]] which could use too, but that's Involving the community more about setting up processes and infrastructure correctlybetter would certainly get us faster though. --[[User:Marcopg|Marcopg]]:: Moved (as you see here) - I'll transfer this set of notes to the archives after I respond to everything and create a new set of notes for the work I do tonight.
I did not thoroughly weed for duplicates, but suspect there might be dupes in tickets involving USB keys, mimetypes, or Activity icons, as well as discussions for simpler implementations/interfaces for Tubes and other collaborative APIs.
:* I suspect there are duplicates too. Perhaps posting about them on the sugar list would be a good way to get feedback by developers on them, and close or clarify the relations between them.--[[User:Marcopg|Marcopg]]
:: Good call. It's on the todo list now. [[User:Mchua|Mchua]] 04:50, 16 May 2008 (UTC)
=== Questions ===
* Who is doing Sugar development?
:* Sugar is a community project. Many of the developers are contracted by OLPC, many are volunteers. You can get a raw idea of the people involve from the [[Modules]] page. A few of us are also trying to setup [[Announcing SugarLabs|SugarLabs]], a foundation to sustain development. --[[User:Marcopg|Marcopg]]
* What are the priorities for Sugar development?
:* The [;a=blob;f=roadmap.txt;hb=HEAD 1.0 Roadmap] should give you a good idea of what are the medium term priorities. --[[User:Marcopg|Marcopg]]
:: I note that this list of priorities doesn't actually [[Talk:Triage#Priorities|prioritize the priorities]], as mstone pointed out in your triage discussion... should it? [[User:Mchua|Mchua]] 04:50, 16 May 2008 (UTC)
* What is the goal for this upcoming milestones?
:* For 0.82, the next Sugar release, we are going to work mainly on OLPC [ Update.2 priorities]. I need to extract the major Sugar features and changes from there and add to the [[Roadmap]]. Other than that 0.82 will be mostly bug fixes. --[[User:Marcopg|Marcopg]]
* What are the big annoyances/obstacles to making the above happen?
:* I don't see big obstacles. Involving the community more and better would certainly get us faster though. --[[User:Marcopg|Marcopg]]
* Do we have a sense of what makes a good Sugar bug report? (What does?)
:* Some of your notes are actually very good in this respect. What about starting a [[BugReport]] page and put your notes there? I can step in and add my ideas. --[[User:Marcopg|Marcopg]]
:: Lo, it is done. [[BugReport]] it is. [[User:Mchua|Mchua]] 04:50, 16 May 2008 (UTC)
* 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:BugSquad/ContentToEdit/Triage]].:: would love to help with this, personally - need to get my feet underneath me first. Also, waiting for sugarlabs Sugar Labs 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 [ TracBacks plugin]? (Full disclosure: I wrote this.) Also potentially helpful if there will be a separate Sugar Trac: [ 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 Sugar Labs infrastructure and it's relation to --[[User:Marcopg|Marcopg]] 
* Do we have a "trac" component on trac (to report something's broken, to request plugins, etc)? Should we?
:* Yup 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 [ a snowflake]?
:* The way XO icons are clustered around a shared activity in mesh view is represented by code in 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]]
:* Assigning milestones should be left up to the triage team, yeah. In the last few months no one really triaged tickets, so we need to go through all the 492 tickets and make sure they are triaged sensibly. -- [[User:Marcopg|Marcopg]]
=== High priority ===
* [ #5629] - '''Add a disable screencorners option in Sugar-control-panel''' - fun design discussion on the UI for hot corners. Also interesting: [ #3936], which discusses hotcorners not working in Browse sometimes, and [ #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)

Navigation menu