GettingStarted

Differences between revisions 30 and 54 (spanning 24 versions)
Revision 30 as of 2008-08-06 16:14:55
Size: 2300
Editor: localhost
Comment: converted to 1.6 markup
Revision 54 as of 2016-10-27 07:44:15
Size: 3161
Editor: dholbach
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
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. One of the best means of contributing to Ubuntu is by helping to keep the thousands of different free software applications in form of Ubuntu packages in shape. 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.
Line 9: Line 9:
 1. Before you get started, you should read how the Ubuntu system works, this will help you get an idea how the different pieces fit together. To read about this, [[UbuntuDevelopment|click here]]. [[UbuntuDevelopment/UsingDevelopmentReleases]] explains how to safely make use of the latest development release for your own development environment.
 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 may want to attend some of the upcoming [[MOTU/Events#Packaging101|Packaging 101]] and [[MOTU/Events#QASession|MOTU Q+A]] sessions to get help. You can also ask for help on `#ubuntu-motu` on `irc.freenode.net`.
 1. When you have got the hang of a few packages, why not try to [[MOTU/TODO/Bugs|Fix An Existing Bug]] or Fix one of our [[MOTU/TODO#WeeklyTasks|Weekly Tasks]] and once you know the tools a bit better [[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. The [[http://packaging.ubuntu.com/html/|Packaging Guide]] is your friend on your MOTU journey. It gives you a nice overview over how packaging works generally. To get a first impression, you also might want to check out the [[MOTU/Videos|MOTU Videos]].
 1. Once you are a bit more familiar with the tools and the general concepts behind Packaging, you might want to check out [[MOTU/Contributing]] and see how the team works.
 1. To get started and actively participate in Ubuntu development, you need a development environment installed on your development machine. [[https://wiki.ubuntu.com/BeginnersTeam/FocusGroups/Development/Devbeginnings#Ubuntu%20Development%20Beginnings|Ubuntu Developers' Tools Installation Quick Start]] will take you step by step through the process and get you up and running quickly.
 1. Also you need to be running the latest Ubuntu release: [[https://wiki.ubuntu.com/QATeam/Testdrive | UsingDevelopmentReleases]] explains how to safely do that.
 1. If you ever get stuck with any of Ubuntu's development processes, you should consult [[UbuntuDevelopment|the Ubuntu Development overview]], this will help you get an idea how the different pieces fit together. Definitely check out [[UbuntuDevelopment/KnowledgeBase]] for a good list of in-depth guides, tutorials and guidelines.
 1. While studying the [[http://packaging.ubuntu.com/html/|Packaging Guide]], don't hesitate to ask for help in the [[irc://irc.freenode.net/ubuntu-motu|#ubuntu-motu]] [[https://help.ubuntu.com/community/InternetRelayChat|IRC channel]] and attend the periodic [[Packaging/Training]] sessions in [[irc://irc.freenode.net/ubuntu-classroom|#ubuntu-classroom]].
 1. Once you have gotten the hang of a few packages, why not [[MOTU/TODO/Bugs|fix an existing bug]]? 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|ubuntu-motu]] 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 20:
 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 proccess 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://planet.ubuntu.com|Planet Ubuntu]] by following [[https://wiki.ubuntu.com/PlanetUbuntu|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 keep the thousands of different free software applications in form of Ubuntu packages in shape. 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. The Packaging Guide is your friend on your MOTU journey. It gives you a nice overview over how packaging works generally. To get a first impression, you also might want to check out the MOTU Videos.

  2. Once you are a bit more familiar with the tools and the general concepts behind Packaging, you might want to check out MOTU/Contributing and see how the team works.

  3. To get started and actively participate in Ubuntu development, you need a development environment installed on your development machine. Ubuntu Developers' Tools Installation Quick Start will take you step by step through the process and get you up and running quickly.

  4. Also you need to be running the latest Ubuntu release: UsingDevelopmentReleases explains how to safely do that.

  5. If you ever get stuck with any of Ubuntu's development processes, you should consult the Ubuntu Development overview, this will help you get an idea how the different pieces fit together. Definitely check out UbuntuDevelopment/KnowledgeBase for a good list of in-depth guides, tutorials and guidelines.

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

  7. Once you have gotten the hang of a few packages, why not fix an existing bug? For a more advanced test of your skills, try to package something new.

  8. Subscribe to the ubuntu-motu mailing list.

  9. 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 Planet Ubuntu 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)