UbuntuDevelopers
Differences between revisions 65 and 66
|
Size: 10370
Comment: Typo
|
Size: 8477
Comment: Redraft for ArchiveReorganisation
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''<<BR>><<TableOfContents(1)>>|| | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents(1)>>|| |
| Line 16: | Line 16: |
| 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: | 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 five types of Ubuntu developers: |
| Line 21: | Line 21: |
| * [[#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]]) |
* [[#DelegateDev|Ubuntu Developers (from delegated teams]] * [[#CoreDev|Ubuntu Core Developers (core-dev)]] |
| Line 24: | Line 24: |
{{attachment:ubuntu-developers6.png}}<<BR>> ''Please note that the "dashed routes" may require strong evidence of your involvement in Ubuntu Development.'' 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. <<Anchor(Applying)>> = Applying for team membership = To join the `ubuntu-universe-contributors`, `~motu` or `ubuntu-core-dev` team, the [[MOTU/Council]] needs to review your application first. In the case of `ubuntu-core-dev` the [[MOTU/Council|MC]] speaks out a recommendation for the [[DeveloperMembershipBoard|Developer Membership Board]], in all other cases it will make the final decision. ''(Read more about the individual teams and the differences below.)'' * Set up a personal wiki page for your application. Please make use of [[UbuntuDevelopment/DeveloperApplicationTemplate]]. * Talk to your [[SponsorshipProcess|sponsors]] beforehand and ask them to add some information to the wiki page. In a regular application, you will have 3-5 sponsors. * Add your application details to [[MOTU/Council/Meeting]], give a quick heads-up on the [[https://lists.ubuntu.com/mailman/listinfo/motu-council|motu-council list]] and pick a meeting time you'll be able to attend. Please allow at least one week of time for the MOTU Council members to review your application. ''(If you can't make it to one of the meetings, please email motu-council@lists.ubuntu.com for either a different meeting time or to process the application on the mailing list.)'' * Attend the meeting. All members of the development community are welcome to attend and ask questions, add your feedback (even if unsolicited) to the wiki page in question or ask questions on the [[https://lists.ubuntu.com/mailman/listinfo/motu-council|motu-council list]]. The [[MOTU/Council|MOTU Council]] will have prepared for the meeting (reviewed the application details, checked a few examples of your work, talked to sponsors, etc.) and ask questions to make sure the applicant qualifies for the team. During the meeting the MC members will cast their votes and if quorum is reached (4 of 7 currently), will add the applicant to the team or ask to re-apply in due time. <<Anchor(Success)>> == After your successful application == Your application was approved and your member of one of the development teams? * You will now enjoy all the benefits of Ubuntu [[Membership]]. * Add yourself to [[PlanetUbuntu|Planet Ubuntu]] and let the world know about your experience in the team and that you're part of it now. :-) |
|
| Line 65: | Line 38: |
| <<Anchor(JoiningProspective)>> == Becoming a prospective developer == There are no requirements to be a prospective developer, and anyone with interest is encouraged to become involved. Please see the links at the top of this page for pointers some of the many ways to start contributing to Ubuntu development. |
|
| Line 68: | Line 45: |
| * 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) |
* 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 |
| Line 73: | Line 50: |
| * are implicity considered Ubuntu Members | |
| Line 77: | Line 55: |
| * Follow the [[#Applying|process above]]. * The outcome of this will be decided by the [[MOTU/Council|MOTU Council]], and reported to the Community Council. |
* Apply to the [[DeveloperMembershipBoard|Developer Membership Board]] using the [[DeveloperMembershipBoard/ApplictionProcess|Application Process]] |
| Line 80: | Line 57: |
| <<Anchor(MOTU)>> = Ubuntu Developers (MOTU) = |
<<Anchor(DelegateDev)>> = Ubuntu Developers (from delegated teams) = |
| Line 83: | Line 60: |
| * are members of the [[http://launchpad.net/~motu|motu]] team in Launchpad | * are members of a delegated development group in launchpad * are collectively responsible for maintenance of some subset of packages in Ubuntu |
| Line 85: | Line 63: |
| * 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 |
* apply this knowledge by uploading new packages, and updating existing packages, in an area of expertise * may also contribute to other areas in Ubuntu in cooperation with another developer |
| Line 89: | Line 67: |
| * are encouraged to * consider joining [[https://launchpad.net/~ubuntu-universe-sponsors|ubuntu-universe-sponsors]] * consider joining the [[MOTU/Mentoring|MOTU Mentors]] |
* are implicity considered Ubuntu Members * are granted a vote when the Development Membership Board or Technical Board are polling Ubuntu Developers * are considered as [[#ContribDev|Ubuntu Contributing Developers]] when working outside the delegated subset of packages |
| Line 93: | Line 71: |
| <<Anchor(JoiningMOTU)>> == Joining the MOTU team == |
At the current time, the following teams are considered delegated teams: * [[DesktopTeam/Developers|Ubuntu Desktop Developers]] (Launchpad: [[https://launchpad.net/~ubuntu-desktop|~ubuntu-desktop]]) * [[http://www.mythbuntu.org/development/policy|Mythbuntu Developers]] (Launchpad: [[https://launchpad.net/~mythbuntu-dev|~mythbuntu-dev]]) * [[Kubuntu/KubuntuDevelopers|Kubuntu Developers]] (Launchpad: [[https://launchpad.net/~kubuntu-dev|~kubuntu-dev]]) * [[MOTU|Masters of the Universe]] (Launchpad [[http://launchpad.net/~motu|~motu]]) <<Anchor(JoiningDelegate)>> == Joining a delegated team == |
| Line 96: | Line 82: |
| * Follow the [[#Applying|process above]]. * The outcome of this will be decided by the [[MOTU/Council|MOTU Council]], and reported to the [[DeveloperMembershipBoard|Developer Membership Board]]. |
* Review the requirements for the specific team of interest, and apply to that team for membership |
| Line 102: | Line 87: |
| * are collectively responsible for the maintenance of packages in the `main` and `restricted` components | * are collectively responsible for the maintenance of all packages in Ubuntu |
| Line 114: | Line 99: |
| * are implicity considered Ubuntu Members * are granted a vote when the Development Membership Board or Technical Board are polling Ubuntu Developers |
|
| Line 118: | Line 105: |
| * Follow the [[#Applying|process above]]. * If successful, the [[MOTU/Council]] will speak out a recommendation and the [[DeveloperMembershipBoard|Developer Membership Board]] will get in touch with you. |
* Apply to the [[DeveloperMembershipBoard|Developer Membership Board]] using the [[DeveloperMembershipBoard/ApplictionProcess|Application Process]] |
| Line 125: | Line 111: |
| * are Ubuntu developers (ie: have a vote when the [[DeveloperMembershipBoard|Developer Membership Board]] and CC are polling Ubuntu developers) and implicitly members of Ubuntu. | |
| Line 133: | Line 118: |
| * are implicity considered Ubuntu Members * are granted a vote when the Development Membership Board or Technical Board are polling Ubuntu Developers |
|
| Line 134: | Line 121: |
| Where a developer is a generalist with an interest in a wide variety of packages, that developer is encouraged to strive for ubuntu-core-dev or MOTU membership. In cases where a given small set of packages attracts the interest of more than one specialised developer, the [[DeveloperMembershipBoard|Developer Membership Board]] may recommend the foundation of a team. | Where a developer has an interest in a wide variety of packages, that developer is encouraged to strive for membership in one or more existing development teams. In cases where a given small set of packages attracts the interest of more than one specialised developer, the [[DeveloperMembershipBoard|Developer Membership Board]] may recommend the foundation of a team. |
| Line 139: | Line 126: |
| * Follow the [[#Applying|process above]]. * If successful, the [[MOTU/Council]] will speak out a recommendation and the [[DeveloperMembershipBoard|Developer Membership Board]] will get in touch with you. |
* Apply to the [[DeveloperMembershipBoard|Developer Membership Board]] using the [[DeveloperMembershipBoard/ApplictionProcess|Application Process]] |
Getting Started |
Did you mean ...
If you have arrived here trying to find out how to take part in the development of Ubuntu, then you may find these pages more useful at first:
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 five types of Ubuntu developers:
Ubuntu 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
Becoming a prospective developer
There are no requirements to be a prospective developer, and anyone with interest is encouraged to become involved. Please see the links at the top of this page for pointers some of the many ways to start contributing to Ubuntu development.
Ubuntu Contributing Developers
are members of the universe-contributors team in Launchpad
- are collectively responsible for the maintenance of most of the packages in Ubuntu
- merge new versions from Debian, work on bugfixes and new packages
- continue with sponsored uploads
- participate in technical discussions with other Ubuntu developers, providing ideas and feedback
- are implicity considered Ubuntu Members
Joining the universe-contributors team
Check out the general requirements for Ubuntu Membership.
Apply to the Developer Membership Board using the Application Process
Ubuntu Developers (from delegated teams)
- are members of a delegated development group in launchpad
- are collectively responsible for maintenance of some subset of packages in Ubuntu
- understand packaging concepts, having substantial experience uploading packages through a sponsor
- apply this knowledge by uploading new packages, and updating existing packages, in an area of expertise
- may also contribute to other areas in Ubuntu in cooperation with another 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 implicity considered Ubuntu Members
- are granted a vote when the Development Membership Board or Technical Board are polling Ubuntu Developers
are considered as Ubuntu Contributing Developers when working outside the delegated subset of packages
At the current time, the following teams are considered delegated teams:
Ubuntu Desktop Developers (Launchpad: ~ubuntu-desktop)
Mythbuntu Developers (Launchpad: ~mythbuntu-dev)
Kubuntu Developers (Launchpad: ~kubuntu-dev)
Masters of the Universe (Launchpad ~motu)
Joining a delegated team
Check out the general requirements for Ubuntu Membership.
- Review the requirements for the specific team of interest, and apply to that team for membership
Ubuntu Core Developers
are members of the ubuntu-core-dev team in Launchpad
- are collectively responsible for the maintenance of all packages in Ubuntu
- 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
- are implicity considered Ubuntu Members
- are granted a vote when the Development Membership Board or Technical Board are polling Ubuntu Developers
Joining the ubuntu-core-dev team
Check out the general requirements for Ubuntu Membership.
Apply to the Developer Membership Board using the Application Process
Per-package Uploaders
- are developers with a specialisation in a specific set of packages in Ubuntu,
- are granted direct upload to the Ubuntu archive for that set of packages.
- have sufficient technical knowledge of the package(s) in question from documented work in the package through sponsorship, work in other distributions, or work upstream.
- have an understanding that such an access grant does not permit sole-maintainership, but rather the right to participate in the maintenance of the package as part of a team.
- have an understanding of the broad strokes of the release schedule, relevant freezes that would affect the package in question, and appropriate means by which to handle any exceptions.
- need to show advocation and support of existing developers indicating that previous work on the package demonstrated that unsupervised upload is warranted.
- need to have documented previous concern for the packages in question in Ubuntu, including previous uploads, effective bug management, and similar previous work.
- need to show a history of effective collaboration with other developers in Ubuntu.
- are specialist maintainers, not generalist maintainers. They are not expected to understand packaging best practices applicable to a wide variety of software or large number of packages in the archive, but they are expected to have exceptional technical expertise with the package(s) for which access is requested.
- are implicity considered Ubuntu Members
- are granted a vote when the Development Membership Board or Technical Board are polling Ubuntu Developers
Where a developer has an interest in a wide variety of packages, that developer is encouraged to strive for membership in one or more existing development teams. In cases where a given small set of packages attracts the interest of more than one specialised developer, the Developer Membership Board may recommend the foundation of a team.
Joining the Per-package Uploaders
Check out the general requirements for Ubuntu Membership.
Apply to the Developer Membership Board using the Application Process
UbuntuDevelopers (last edited 2025-10-01 09:46:10 by sally-makin)