Bitesize

Differences between revisions 1 and 23 (spanning 22 versions)
⇤ ← Revision 1 as of 2010-11-26 15:17:33 →
Size: 264
Editor: c-76-112-212-248
Comment:
← Revision 23 as of 2011-06-13 14:08:03 → ⇥
Size: 2014
Editor: c-71-238-27-165
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

{{attachment:bitesizelogo.png}}

Bitesize bugs are small bugs tagged by triagers as small and easy-to-fix bugs for Unity. We pick these bugs because they're a good place to start to get you familiar with the code and how the workflow for working with the DX team works out. See Jorge's [[http://castrojo.tumblr.com/post/2084859426/getting-started-working-on-unity|blog post]] or [[http://www.jonobacon.org/2010/12/06/get-started-hacking-on-unity-bitesize-bugs/|Jono's blog post]] for more information.

Feel free to grab on and work on as many as you want, and when you feel like you want more just let us know. This wiki page is for helping people get started, so feel free to add your own tips and tricks and help us push Unity forward!
Line 5: Line 11:
 1. Find the bug you want to work on from the list.
 1. Get the code and do the development.		  1. Run 11.04.
 1. Find the bug you want to work on from the [[http://goo.gl/tiheb|list of bugs]] or [[Unity/Bitesize/Opportunities|opportunities]].
 1. For the 11.10 cycle we will be adding templates [[https://wiki.ubuntu.com/Unity/FilingBugs#Canned "Call for Help" Template|explaining ideal solutions]] to bugs.
 1. Get the code and do the development and submit it to the team.
Line 8: Line 16:
 1. Propose your branch for merging and accept the contributor agreement.  1. Mark the bug as "In Progress" so the next person doesn't start working on it. If you get stuck or change your mind and want to give the bug up move it back to "Confirmed" and unassign yourself!
 1. Your work will be reviewed by someone on the DX team, after they review your code they will instruct you on what to do next.
 1. Celebrate!
 1. Go to step 1.
Line 10: Line 21:
  == Other ==

 * [[http://goo.gl/FdihT|Backlog bugs]] from design
 * [[http://castrojo.tumblr.com/tagged/bitesize|Weekly Status Reports]]

== Contacts ==

 * [[http://launchpad.net/~unity-community-hackers|Join our team]] on Launchpad
 * [[Mailing List|https://launchpad.net/~ayatana-dev]]
 * #ayatana on Freenode IRC
 * If you are totally lost contact JorgeCastro
----
CategoryDocumentation CategoryDocumentation

Unity Bitesize Bugs

bitesizelogo.png

Bitesize bugs are small bugs tagged by triagers as small and easy-to-fix bugs for Unity. We pick these bugs because they're a good place to start to get you familiar with the code and how the workflow for working with the DX team works out. See Jorge's blog post or Jono's blog post for more information.

Feel free to grab on and work on as many as you want, and when you feel like you want more just let us know. This wiki page is for helping people get started, so feel free to add your own tips and tricks and help us push Unity forward!

Workflow

  1. Run 11.04.

  2. Find the bug you want to work on from the list of bugs or opportunities.

  3. For the 11.10 cycle we will be adding templates explaining ideal solutions to bugs.

  4. Get the code and do the development and submit it to the team.
  5. Mark the bug as "In Progress" so the next person doesn't start working on it. If you get stuck or change your mind and want to give the bug up move it back to "Confirmed" and unassign yourself!
  6. Your work will be reviewed by someone on the DX team, after they review your code they will instruct you on what to do next.
  7. Celebrate!
  8. Go to step 1.

Other

Contacts

CategoryDocumentation CategoryDocumentation

Unity/Bitesize (last edited 2011-06-14 14:21:45 by 203-59-100-57)