UbuntuDevelopers

Differences between revisions 33 and 34
Revision 33 as of 2008-05-18 12:18:13
Size: 9049
Editor: 563413c5
Comment: Added introduction and schematic overview of Ubuntu Developers. Pls check!!!
Revision 34 as of 2008-05-18 12:39:39
Size: 9043
Editor: 563413c5
Comment: Minor formatting
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * [#Prospective | Ubuntu Prospective Developers] (Ubunteros)
 * [#ContribDev | Ubuntu Contributors]
 * [#MOTU | Ubuntu Developers (MOTU)] ([#http://launchpad.net/~motu MOTU Launchpad page])
 * [#CoreDev | Ubuntu Core Developers] ([http://launchpad.net/~ubuntu-core-dev core-dev] Core-dev Launchpad page)
 * [#Prospective Ubuntu Prospective Developers] (Ubunteros)
 * [#ContribDev Ubuntu Contributors]
 * [#MOTU Ubuntu Developers (MOTU)] ([http://launchpad.net/~motu MOTU Launchpad page])
 * [#CoreDev Ubuntu Core Developers (core-dev)] ([http://launchpad.net/~ubuntu-core-dev core-dev Launchpad page])
Line 15: Line 15:
The figure above illustrates the relation between the different developer groups. The increasing intensity of colors in the Ubuntu tricoleur represents the required skills, experience, and responsibility for the Ubuntu software archives. The figure above illustrates the relation between the different developer groups. The increasing intensity of colors in the Ubuntu ''tricouleur'' represents the required skills, experience, and responsibility for the Ubuntu software archives.
Line 17: Line 17:
Ubuntu users who wish to contribute must have signed the [http://www.ubuntu.com/community/conduct | Ubuntu Code of Conduct], will have an account at [http://launchpad.net | Launchpad] and will have a GPG signature. These users can contribute as "Ubunteros". Ubunteros typically contribute with bug reporting and testing of software, and interact with the developers on Launchpad and on IRC. Ubuntu users who wish to contribute must have signed the [http://www.ubuntu.com/community/conduct Ubuntu Code of Conduct], will have an account at [http://launchpad.net Launchpad] and will have a GPG signature. These users can contribute as "Ubunteros". Ubunteros typically contribute with bug reporting and testing of software, and interact with the developers on Launchpad and on IRC.

Anchor(Introduction)

Introduction

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 four types of Ubuntu developers:

attachment:ubuntu-developers2.png

The figure above illustrates the relation between the different developer groups. The increasing intensity of colors in the Ubuntu tricouleur represents the required skills, experience, and responsibility for the Ubuntu software archives.

Ubuntu users who wish to contribute must have signed the [http://www.ubuntu.com/community/conduct Ubuntu Code of Conduct], will have an account at [http://launchpad.net Launchpad] and will have a GPG signature. These users can contribute as "Ubunteros". Ubunteros typically contribute with bug reporting and testing of software, and interact with the developers on Launchpad and on IRC.

Ubunteros who demonstrate the necessary skills, team-focus and commitment to the project can qualify for becoming "Ubuntu Contributors". Ubuntu Contributors typically handle more complicated tasks such as merging new packages from Debian that have local Ubuntu changes, debug software or package software from scratch. Thus, to be an Ubuntu Contributor, you need some understanding of packaging, shell scripting and compilation of software under Linux. To become part of the Ubuntu Contributor team, you must apply to the MOTU-Council.

The MOTU are a group of developers who take responsibility for Ubuntu Universe which is the community-maintained part of Ubuntu. This work is not sponsored by Canonical. To become a MOTU you need to submit an application to the MOTU council, and you need positive advocacy from several MOTUs. The main difference between a MOTU and a Contributor is that the MOTU have the right to upload packages to the Ubuntu Universe archive. MOTU need to roughly have the technical proficency of a Debian Developer and have a comprehensive understanding of the Ubuntu development processes and community.

Core Developers are often recruited among the MOTUs, and in particular, those that take a special and sustained interest in several of the software components of the main archive. These software components are central to the correct functioning of Ubuntu, and it is critical that Core Developers show a high degree of competence, reliability and responsibility for those packages. Core Developers can do uploads to Ubuntu's main software archive.

Anchor(Prospective)

Prospective Developers

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

  • Work on bug fixes and new packages
  • Gain experience with Debian-format packaging
  • Request sponsor review of suggested changes, where sponsors:
    • review the packages prepared by the prospective developer
    • provide constructive feedback
    • upload the package when they are satisfied with its quality
    • for more information, please read ["SponsorshipProcess"]

  • May become Contributing Developers through participation in the development community and interaction with Ubuntu Developers

Anchor(ContribDev)

Ubuntu Contributing Developers

  • Are members of the [http://launchpad.net/~universe-contributors universe-contributors] team in Launchpad

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

  • merge new versions from Debian
  • continue with sponsored uploads of bugfixes and new packages
  • participate in technical discussions with other Ubuntu developers, providing ideas and feedback
  • May become MOTU through demonstration of technical skills and understanding of Ubuntu development processes

Anchor(JoiningContribDev)

Joining the universe-contributors team

  • Check out the general requirements for Ubuntu [:Membership].
  • after participating in the development community, apply to become a Contributing Developer following this process
    • write a mail to the public [:MOTU/Council:MOTU Council] mailing list (motu-council@lists.ubuntu.com) (add your name or nick to the subject of the mail, this adds clarity to the [https://lists.ubuntu.com/archives/motu-council/ mailing list threads])

      • be sure to CC your sponsors and kindly ask them to provide background and feedback on their work with you
      • 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 decided by the [:MOTU/Council:MOTU Council], and reported to the Community Council, who have the final say.

Anchor(MOTU)

Ubuntu Developers (MOTU)

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

  • 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

  • answer questions of other developers in order to expand their understanding of packaging work
  • provide guidance for prospective Ubuntu developers regarding technical issues
  • are encouraged to

Anchor(JoiningMOTU)

Joining the MOTU team

  • 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) (add your name or nick to the subject of the mail, this adds clarity to the [https://lists.ubuntu.com/archives/motu-council/ mailing list threads])

      • be sure to CC your sponsors and kindly ask them to provide background and feedback on their work with you
      • 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 decided by the MOTU Council, and reported to the Technical Board, who have the final say.

Anchor(CoreDev)

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

Anchor(JoiningCoreDev)

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

UbuntuDevelopers (last edited 2023-03-20 19:54:07 by racb)