Changes

Jump to navigation Jump to search
3 bytes removed ,  10:13, 17 September 2010
expand context of developers
Line 6: Line 6:  
== How to file a ticket ==
 
== How to file a ticket ==
   −
If you're using [[Sugar on a Stick]] or another [[Supported systems|distribution of Sugar]] and find something specific you think could be improved—maybe something isn't working the way you think it should work, or you have an idea for how something could be better—you can file a '''ticket.''' A ticket is a way for anyone to suggest to the software or project developers that they should work on something.
+
If you're using [[Sugar on a Stick]] or another [[Supported systems|distribution of Sugar]] and find something specific you think could be improved—maybe something isn't working the way you think it should work, or you have an idea for how something could be better—you can file a '''ticket.''' A ticket is a way for anyone to suggest to the software or project development community that they should work on something.
    
Tickets are used by [[Development Team|core developers]], [[Activity Team|Activity authors]], organized [[BugSquad/Testing|testers]], and [[Sugar Labs/Getting Involved|anyone]] who wants to help the greater effort!
 
Tickets are used by [[Development Team|core developers]], [[Activity Team|Activity authors]], organized [[BugSquad/Testing|testers]], and [[Sugar Labs/Getting Involved|anyone]] who wants to help the greater effort!
Line 29: Line 29:  
=== Create a summary for the ticket ===
 
=== Create a summary for the ticket ===
   −
You'll notice that the first text box is for a '''Summary''' of the ticket. Sometimes the '''Summary''' is also called the '''Title''' of the ticket. This is an important part of the ticket—in fact, some people say it is the ''most'' important part—because reading the title of a ticket is how a developer decides if he or she is going to work on it.
+
You'll notice that the first text box is for a '''Summary''' of the ticket. Sometimes the '''Summary''' is also called the '''Title''' of the ticket. This is an important part of the ticket—in fact, some people say it is the ''most'' important part—because reading the title of a ticket is how someone decides if he or she is going to work on it.
   −
Write a ticket summary/title that describes your idea. Try to write it succinctly, so that a developer reading the title of your ticket will go "oh, I know what I have to work on, and why this is important - I will read more about this ticket and maybe try to fix it."
+
Write a ticket summary/title that describes your idea. Try to write it succinctly, so that those reading the title of your ticket will go "oh, I know what I have to work on, and why this is important - I will read more about this ticket and maybe try to fix it."
    
A good ticket is in many ways like a good newspaper headline.
 
A good ticket is in many ways like a good newspaper headline.
Line 81: Line 81:  
The next sections we need to look at (highlighted in green) are the '''component''' and '''distribution/OS''' sections. Tickets specify '''components''' to tell us which part of the software or project that we should look at, and who might want to look at it. For instance, if we were working on a bicycle, you might report a bug in the "handlebar" component - that way, we know to just look at the handlebar when we're fixing things, and the people who only want to work on tires know they don't have to worry about that problem. '''For [[Sugar on a Stick]], the component is ''SoaS''.'''
 
The next sections we need to look at (highlighted in green) are the '''component''' and '''distribution/OS''' sections. Tickets specify '''components''' to tell us which part of the software or project that we should look at, and who might want to look at it. For instance, if we were working on a bicycle, you might report a bug in the "handlebar" component - that way, we know to just look at the handlebar when we're fixing things, and the people who only want to work on tires know they don't have to worry about that problem. '''For [[Sugar on a Stick]], the component is ''SoaS''.'''
   −
Finally, there's the '''distribution.''' '''For [[Sugar on a Stick]], the distribution is ''[http://fedoraproject.org Fedora]''.''' You can [[wikipedia:Linux_distribution |learn more about what Linux distributions are on Wikipedia]], but this probably isn't the most important information to know - it's just extra information that can help developers figure out what's going on.
+
Finally, there's the '''distribution.''' '''For [[Sugar on a Stick]], the distribution is ''[http://fedoraproject.org Fedora]''.''' You can [[wikipedia:Linux_distribution |learn more about what Linux distributions are on Wikipedia]], but this probably isn't the most important information to know - it's just extra information that can help people figure out what's going on.
    
See [[BugSquad/Status Fields]] for information on the Priority, Milestone, Version, Severity, Bug Status, & Resolution fields. These are usually set by maintainers and [[BugSquad/Triage Guide|Triagers]].  As you file and review bugs, you can help triage bugs by finding duplicates and sharing questions and comments with the reporters and maintainers to help advance the work.
 
See [[BugSquad/Status Fields]] for information on the Priority, Milestone, Version, Severity, Bug Status, & Resolution fields. These are usually set by maintainers and [[BugSquad/Triage Guide|Triagers]].  As you file and review bugs, you can help triage bugs by finding duplicates and sharing questions and comments with the reporters and maintainers to help advance the work.

Navigation menu