Bitesize

Differences between revisions 13 and 24 (spanning 11 versions)
⇤ ← Revision 13 as of 2010-12-10 15:47:40 →
Size: 1844
Editor: c-76-112-212-248
Comment:
← Revision 24 as of 2011-06-14 14:21:45 → ⇥
Size: 2082
Editor: 203-59-100-57
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

{{attachment:bitesizelogo.png}}
Line 9: Line 11:
 1. Run Natty. You can either do this by running Alpha 1 on your bare metal or [[Unity/InstallUSBKey|creating a USB key]] for this purpose. I've added documentation to that page so you can install a development environment on it so you can hack on code and keep the entire updated Unity environment on the key itself.
 1. Find the bug you want to work on from the [[http://goo.gl/tiheb|list of bugs]].		  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.
Line 18: Line 21:
== Other ==

 * [[http://goo.gl/FdihT|Backlog bugs]] from design
 * [[http://castrojo.tumblr.com/tagged/bitesize|Weekly Status Reports]]
 * [[Unity/Bitesize/DebuggingUnity|Tools to help debugging Unity]]
Line 20: Line 29:
 * [[http://launchpad.net/~unity-community-hackers|Join our team]] on Launchpad

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)