GettingStarted

Differences between revisions 37 and 38
Revision 37 as of 2009-06-23 21:45:58
Size: 2354
Editor: 99-164-75-208
Comment:
Revision 38 as of 2009-07-08 19:16:01
Size: 2392
Editor: 99-164-75-208
Comment: Style/grammar cleanup
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 1. Before you get started, you should read [[UbuntuDevelopment|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 do check out [[UbuntuDevelopment/KnowledgeBase]] for a good list of in-depth guides, tutorials and guidelines.
 1. You should now read the [[PackagingGuide]], [[MOTU/Contributing]], and play with the tools described in [[PackagingGuide/Recipes]]. (Also check out the [[MOTU/Videos|MOTU Videos]].)
 1. While running through the PackagingGuide, you can also ask for help on `#ubuntu-motu` on `irc.freenode.net` and come to the [[Packaging/Training]] sessions in `#ubuntu-classroom`.
 1. When you have got the hang of a few packages, why not try to [[MOTU/TODO/Bugs|fix an existing bug]] or review [[http://daniel.holba.ch/harvest|the harvest list]] of opportunities. ''(Once you know the tools a bit better you could [[MOTU/TODO/NewSoftware|package something new]]?)''
 1. sign up for [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu-mentors|ubuntu-motu-mentors@lists.ubuntu.com]]
 1. When you have produced your new package or produced a package that fixes a bug, read about the [[SponsorshipProcess|Sponsorship Process]].
 1. Before getting started, you should read [[UbuntuDevelopment|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.
 1. You should read the [[PackagingGuide]], [[MOTU/Contributing]], and play with the tools described in [[PackagingGuide/Recipes]]. (Also check out the [[MOTU/Videos|MOTU Videos]].)
 1. While running through the PackagingGuide, don't hesitate to ask for help in the `#ubuntu-motu` [[https://help.ubuntu.com/community/InternetRelayChat|IRC channel]] or attend the [[Packaging/Training]] sessions in `#ubuntu-classroom`.
 1. Once have gotten the hang of a few packages, why not [[MOTU/TODO/Bugs|fix an existing bug]] or [[http://daniel.holba.ch/harvest|review the harvest list of opportunities]]? For a more advanced test of your skills, try to [[MOTU/TODO/NewSoftware|package something new]].
 1. Subscribe to the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu-mentors|ubuntu-motu-mentors]] mailing list.
 1. Once you have produced a new package or one that fixes a bug, you are ready to get it reviewed! Read about the [[SponsorshipProcess|Sponsorship Process]], and get follow the instructions given on that page.
Line 17: Line 17:
 1. If you don't have a blog yet, create one and blog about your progress as a MOTU.
 1. Add your weblog to http://ubuntuweblogs.org by following [[http://ubuntuweblogs.org/submit.html|these instructions]].
 1. We have generated a "cheat sheet" called a Playbook that you can print out and use to remind you how the process works. [[attachment:playbook.pdf]]
 1. If you don't have a weblog yet, create one and blog about your progress as a MOTU.
 1. Add your blog to http://ubuntuweblogs.org by following [[http://ubuntuweblogs.org/submit.html|these instructions]].
 1. Keep a copy of [[attachment:playbook.pdf]] near to remind you about this whole process.

Home

Getting Started
Get started here!

Teams

FAQ

Events

TODO

Contact

Next MOTU Meeting (details)

Thursday, December 6th 2012, 16:00 UTC

Next Packaging Training Session (details)

TBD

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 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.

  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.

Optional:

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

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


Go back to MOTU.
CategoryMOTU

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