Differences between revisions 38 and 39
Revision 38 as of 2009-07-08 19:16:01
Size: 2392
Editor: evanrmurphy
Comment: Style/grammar cleanup
Revision 39 as of 2009-07-08 19:27:52
Size: 2395
Editor: evanrmurphy
Comment: Minor rephrasing
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 1. While running through the PackagingGuide, don't hesitate to ask for help in the `#ubuntu-motu` [[|IRC channel]] or attend the [[Packaging/Training]] sessions in `#ubuntu-classroom`.  1. While studying the PackagingGuide, don't hesitate to ask for help in the `#ubuntu-motu` [[|IRC channel]] and attend the periodic [[Packaging/Training]] sessions in `#ubuntu-classroom`.


Getting Started
Get started here!






Next MOTU Meeting (details)

Thursday, December 6th 2012, 16:00 UTC

Next Packaging Training Session (details)


Getting Started With MOTU

One of the best means of contributing to Ubuntu is by helping to package the thousands of different free software applications available. To get involved in this effort, we have the MOTU project (which stands for Masters Of The Universe). This team helps to train new packagers and get everyone up to speed maintaining software in Ubuntu.

This guide helps you get started in MOTU quickly and easy. If you get stuck at any point, see MOTU/Contact for how to get help.

  1. Before getting started, you should read how the Ubuntu system works, this will help you get an idea how the different pieces fit together. (UbuntuDevelopment/UsingDevelopmentReleases explains how to safely make use of the latest development release for your own development environment). Definitely check out UbuntuDevelopment/KnowledgeBase for a good list of in-depth guides, tutorials and guidelines.

  2. You should read the PackagingGuide, MOTU/Contributing, and play with the tools described in PackagingGuide/Recipes. (Also check out the MOTU Videos.)

  3. While studying the PackagingGuide, don't hesitate to ask for help in the #ubuntu-motu IRC channel and attend the periodic Packaging/Training sessions in #ubuntu-classroom.

  4. Once have gotten the hang of a few packages, why not fix an existing bug or review the harvest list of opportunities? For a more advanced test of your skills, try to package something new.

  5. Subscribe to the ubuntu-motu-mentors mailing list.

  6. Once you have produced a new package or one that fixes a bug, you are ready to get it reviewed! Read about the Sponsorship Process, and get follow the instructions given on that page.


  1. If you don't have a weblog yet, create one and blog about your progress as a MOTU.
  2. Add your blog to by following these instructions.

  3. Keep a copy of playbook.pdf near to remind you about this whole process.

Go back to MOTU.

MOTU/GettingStarted (last edited 2016-10-27 07:44:15 by dholbach)