Ubuntu Wiki

Ubuntu developers represent an important part of the creation of Ubuntu. They have a direct influence on the software included in Ubuntu and whether it meets the needs of end users. They are responsible for ensuring that Ubuntu works, and works as well as it can with the resources available. There are three types of Ubuntu developers:

Prospective Developers

This is where you should start if you are interested in joining the development team. Prospective developers:

• work with an existing developer or core developer as a sponsor and mentor, who:
  • reviews the packages prepared by the prospective developer
  • provides constructive feedback
  • uploads the package when they are satisfied with its quality

  • for more information, please read ["SponsorshipProcess"]

• participate in the development community by interacting with [:MOTU] and core developers
• after gaining experience, apply to become an Ubuntu Developer following this process

  • write a mail to the public MOTU Council mailing list (motu-council@lists.ubuntu.com) and CC your sponsors

    • mention packages you maintain or specific uploads that you think were done quite well
    • The council will check the references and reply back within 12 days (Launchpad's /+packages page, talk to select team members, etc.)
  • The outcome of this will be presented to the TB, who have the final say. The exchange with the TB happens via mail.

Ubuntu Developers (MOTU)

• are members of the [http://launchpad.net/~motu motu] team in Launchpad

• are collectively responsible for the maintenance of most of the packages in Ubuntu (the universe and multiverse components)

• understand packaging concepts, having substantial experience uploading packages through a sponsor

• apply this knowledge by uploading new packages, and updating existing packages, in the universe component

• may also contribute to the main component in cooperation with a core developer

• merge new versions from Debian
• ask questions of other developers in order to expand their understanding of packaging work
• provide guidance for prospective Ubuntu developers regarding technical issues
• participate in technical discussions with other Ubuntu developers, providing ideas and feedback
• after gaining experience, may choose to expand their participation even further by applying to become a core developer
• are encouraged to

  • consider joining [https://launchpad.net/~ubuntu-universe-sponsors ubuntu-universe-sponsors]

  • consider joining the [:MOTU/Mentoring:MOTU Mentors]

Ubuntu Core Developers

• are members of the [http://launchpad.net/~ubuntu-core-dev ubuntu-core-dev] team in Launchpad

• are collectively responsible for the maintenance of packages in the main and restricted components

• have a strong working knowledge of packaging concepts and techniques, refined through experience
• have a strong working knowledge of Ubuntu project procedures, especially those related to the release process and support commitments, and an understanding of the reasons why they exist
• are able to apply this knowledge to a variety of packages and subsystems
• have a history of substantial direct contributions to the distribution
• take a leading role in new development projects to improve Ubuntu
• specify, develop and deploy new features for the default installation of Ubuntu
• exercise great care in their work, with the understanding that their efforts have a direct impact on others, including:
  • every Ubuntu user
  • the Ubuntu release team
  • corporate partners who provide support for Ubuntu
• feel a sense of personal responsibility for the quality of Ubuntu releases and for the satisfaction of Ubuntu users

Joining the ubuntu-core-dev team

Prospective core developers must be approved by the Technical Board.

Candidates should mail the [:MOTU/Council:MOTU Council] and in the mail conversation

1. Have their sponsor(s) attest to the quality of their work and their progress during the mentoring process, according to the UbuntuDevelopers criteria

2. Provide a hyperlink to a wiki page with some aggregated information about their qualifications
3. Discuss their specific technical interests and plans for contributing to Ubuntu
4. Present examples of past contributions
5. Answer direct technical questions about packaging
6. Answer questions about the Ubuntu project and its processes

The MOTU Council will then present the aggregated information to the TechnicalBoard. The TB will review and respond, usually setting up an appointment to attend a meeting.

CategoryProcess