NewPackages

Differences between revisions 1 and 27 (spanning 26 versions)
Revision 1 as of 2007-11-15 08:07:46
Size: 3852
Editor: i59F720DB
Comment:
Revision 27 as of 2010-05-20 17:23:27
Size: 7324
Editor: static-72-81-252-22
Comment: Added more about getting packages into Debian.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(UbuntuDevelopment/Header/Menu)]] <<Include(UbuntuDevelopment/Header/Menu)>>
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]]|| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
Line 8: Line 8:
In order for a piece of software to be included in Ubuntu, it must meet the [http://www.ubuntu.com/community/ubuntustory/licensing Ubuntu License Policy]. In order for a piece of software to be included in Ubuntu, it must meet the [[http://www.ubuntu.com/community/ubuntustory/licensing|Ubuntu License Policy]].
Line 12: Line 12:
To get a package into Ubuntu, please [https://launchpad.net/ubuntu/+filebug?field.tags=needs-packaging file a bug in Launchpad] and make sure it has the tag [https://lists.ubuntu.com/archives/ubuntu-motu/2007-March/001471.html needs-packaging]. Please mention where to get the source for it and which license it is under. Make sure you check which [https://launchpad.net/ubuntu/+bugs?field.tag=needs-packaging packages have already been requested]. For packages in Debian, but not in ubuntu [https://launchpad.net/ubuntu/+filebug file a bug] with the summary field "please sync package <packagename> from debian <distro>" where packagename is the package you would like to see. To get a package into Ubuntu, please [[ https://bugs.launchpad.net/ubuntu/+filebug?no-redirect&field.tag=needs-packaging | file a bug in Launchpad ]] and make sure it has the tag [[https://lists.ubuntu.com/archives/ubuntu-motu/2007-March/001471.html|needs-packaging]]. Please mention where to get the source for it and which license it is under. An example request is [[https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages/ExamplePackageRequest|here]]. Make sure you check which [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-packaging|packages have already been requested]]. Packages that have recently been added to Debian unstable will be automatically synced into Ubuntu prior to the [[DebianImportFreeze|Debian Import Freeze (DIF)]]. After the Debian Import Freeze, you will have to [[https://launchpad.net/ubuntu/+filebug|file a bug]] with the summary field "Please sync <packagename> from debian <distro>" where <packagename> is the package you would like to see. Debian Import Freeze for lucid is on [[LucidReleaseSchedule|February 11, 2010]].
Line 16: Line 16:
Packages which are not in Ubuntu yet, require extra scrutiny and go through a special review process, before they get uploaded and get a final review by the [http://launchpad.net/~ubuntu-archive archive admins]. More information on the review process, including the criteria which will be applied, can be found on the [:UbuntuDevelopment/CodeReviews#NewPackage:Code Reviewers page]. Developers are encouraged to examine their own packages using these guidelines prior to submitting them for review. You can follow the [[PackagingGuide/Basic | Packaging Guide directives]].
Line 18: Line 18:
The ["MOTU"] team approval policy for new packages:
 * New MOTU contributors (who are not member of the [https://launchpad.net/~motu MOTU] team yet), need to get their packages reviewed and signed off by two [https://launchpad.net/~ubuntu-dev/+members Ubuntu Developers] to get them uploaded to Ubuntu.
 * MOTUs need no only a single additional ACK. (cf. ["MOTU/Council/Meetings/2007-02-23"])
Packages which are not in Ubuntu yet, require extra scrutiny and go through a special review process, before they get uploaded and get a final review by the [[http://launchpad.net/~ubuntu-archive|archive admins]]. More information on the review process, including the criteria which will be applied, can be found on the [[UbuntuDevelopment/CodeReviews#NewPackage|Code Reviewers page]]. Developers are encouraged to examine their own packages using these guidelines prior to submitting them for review.
Line 22: Line 20:
The ["MOTU"] team uses the following workflow: To receive higher quality bug reports write an [[ https://wiki.ubuntu.com/Apport#Per-package%20Apport%20Hooks | apport hook ]] for your package.

The [[MOTU]] team approval policy for new packages:
 * New MOTU contributors (who are not members of the [[https://launchpad.net/~motu|MOTU]] team yet), need to get their packages reviewed and signed off by two [[https://launchpad.net/~ubuntu-dev/+members|Ubuntu Developers]] to get them uploaded to Ubuntu.
 * MOTUs can upload new packages directly to the archive. However they are greatly encouraged to have a new package reviewed prior to uploading. (cf. [[MOTU/Council/Meetings/2007-02-23]])

The [[MOTU]] team uses the following workflow:
Line 24: Line 28:
 * Once you have an initial package and upload it to [wiki:MOTU/Packages/REVU REVU], add the link to the package in [wiki:MOTU/Packages/REVU REVU] to the description of the bug. From this point on, no further Launchpad entries are made until the package is uploaded.  * Once you have an initial package, upload it to [[MOTU/Packages/REVU|REVU]], add the link to the package in [[MOTU/Packages/REVU|REVU]] to the description of the bug. From this point on, no further Launchpad entries are made until the package is uploaded.
Line 26: Line 30:
 * When the package clears the NEW queue it will automatically be set to Fix Released (debian/changelog must close the needs-packaging bug).  * When the package clears the NEW queue it will automatically be set to Fix Released (debian/changelog must close the needs-packaging bug).  This is done with a bullet point that follows the format:
{{{
  * Initial release (LP: #242910)}}}
 where "LP" refers to "Launchpad". See the Packaging Guide for [[PackagingGuide/Howtos/PackagingFromScratchHelloChangelog|more information on changelogs]].
=== Deadline ===
Line 28: Line 36:
Alternative workflows:
 * These are permitted, but [wiki:MOTU/Packages/REVU REVU] is the official location for getting packages reviewed.
 * The key policy point is that two MOTUs must advocate the package. Most MOTUs use [wiki:MOTU/Packages/REVU REVU] and it may be more difficult to get packages in alternative locations reviewed.
[[FeatureFreeze|Feature Freeze]] is the latest approval date (February 18th for "Lucid" aka Ubuntu 10.04): it is recommended to get things done in a couple weeks earlier, as getting approval may take some time.
REVU days are planned through Feature Freeze, but the last days are likely only to grab packages that are really required to meet the feature goals for the release.
Line 32: Line 39:
Also of interest:
 * [http://mentors.debian.net/ mentors.debian.net], a website where people interested in getting their packages inside Debian can upload their packages. You need to [http://mentors.debian.net/debian/pool/ browse the directories] to find packages. ContributingToDebian has additional information on getting your work into Debian.
 * [http://svn.debian.org/wsvn Debian's WebSVN] It's possible that a package has been worked on for Debian but has a status of UNRELEASED. Check the appropriate directories that begin with "pkg" that your package may fall under. For example, game packages would be under "pkg-games".
=== Alternative workflows ===
 * These are permitted, but [[MOTU/Packages/REVU|REVU]] is the official location for getting packages reviewed.
 * The key policy point is that two MOTUs must advocate the package. Most MOTUs use [[MOTU/Packages/REVU|REVU]] and it may be more difficult to get packages in alternative locations reviewed.

=== NEW packages through Debian ===

Ubuntu regularly incorporates source packages from Debian, so it could be useful trying to upload a package to Debian first to automatically have it in Ubuntu in due time. In order to have faster reviews, several teams have been set up to manage a given subset of packages. Some of them are:

 * [[http://wiki.debian.org/Teams/DebianGnome|Debian GNOME Team]]
 * [[http://pkg-kde.alioth.debian.org/|Debian KDE Team]]
 * [[http://wiki.debian.org/Teams/DebianXfceGroup|Debian XFCE Group]]
 * [[http://wiki.debian.org/Games/Team|Debian Games Team]]
 * [[http://wiki.debian.org/DebianMultimedia|Debian Multimedia]]
 * [[http://wiki.debian.org/Teams/DebianPerlGroup|Debian Perl Group]]
 * [[http://wiki.debian.org/Teams/PythonModulesTeam|Debian Python Modules Team]]
 * [[http://wiki.debian.org/Teams/PythonAppsPackagingTeam | Debian Python Applications Packaging Team]]
 * [[http://wiki.debian.org/Teams/DebianCliAppsTeam|Debian CLI Applications Team]]
 * [[http://wiki.debian.org/Teams/DebianMozExtTeam|Debian Mozilla Extension Team]]

More teams can be found [[http://wiki.debian.org/Teams|here]].

Ubuntu does virtually all package maintenance in teams. If you have a deep interest in a particular package and a desire to be the primary person responsible for it, you would likely be happier to get the package into Debian and maintain it there. Debian has a strong culture around individual package maintainers that is not present in Ubuntu. Additionally there are roughly an order of magnitude more Debian Developers than Ubuntu developers. It is quite difficult to get a new package into Ubuntu due to the shear volume of requests compared to the available resources for reviews. In many cases people have an easier time getting their package into Ubuntu via Debian than directly.

=== Also of interest ===
 * Always check if there is an ITP (intent to package) [[http://bugs.debian.org/wnpp|bug filed against the wnpp package]] in Debian. That means, somebody is already working on packaging the software for Debian. Join forces with them rather than reinventing the wheel.
 * [[http://mentors.debian.net/|mentors.debian.net]], a website where people interested in getting their packages inside Debian can upload their packages. You need to [[http://mentors.debian.net/debian/pool/|browse the directories]] to find packages. ContributingToDebian has additional information on getting your work into Debian.
 * [[http://svn.debian.org/wsvn|Debian's WebSVN]] It's possible that a package has been worked on for Debian but has a status of UNRELEASED. Check the appropriate directories that begin with "pkg" that your package may fall under. For example, game packages would be under "pkg-games".
Line 37: Line 68:
Go back to '''[:UbuntuDevelopment]'''.[[BR]]
CategoryProcess[[BR]]CategoryUbuntuDevelopment
Go back to '''[[UbuntuDevelopment]]'''.<<BR>>
CategoryProcess<<BR>>CategoryUbuntuDevelopment

Criteria

In order for a piece of software to be included in Ubuntu, it must meet the Ubuntu License Policy.

Requesting a new package for Ubuntu

To get a package into Ubuntu, please file a bug in Launchpad and make sure it has the tag needs-packaging. Please mention where to get the source for it and which license it is under. An example request is here. Make sure you check which packages have already been requested. Packages that have recently been added to Debian unstable will be automatically synced into Ubuntu prior to the Debian Import Freeze (DIF). After the Debian Import Freeze, you will have to file a bug with the summary field "Please sync <packagename> from debian <distro>" where <packagename> is the package you would like to see. Debian Import Freeze for lucid is on February 11, 2010.

Packaging it yourself

You can follow the Packaging Guide directives.

Packages which are not in Ubuntu yet, require extra scrutiny and go through a special review process, before they get uploaded and get a final review by the archive admins. More information on the review process, including the criteria which will be applied, can be found on the Code Reviewers page. Developers are encouraged to examine their own packages using these guidelines prior to submitting them for review.

To receive higher quality bug reports write an apport hook for your package.

The MOTU team approval policy for new packages:

  • New MOTU contributors (who are not members of the MOTU team yet), need to get their packages reviewed and signed off by two Ubuntu Developers to get them uploaded to Ubuntu.

  • MOTUs can upload new packages directly to the archive. However they are greatly encouraged to have a new package reviewed prior to uploading. (cf. MOTU/Council/Meetings/2007-02-23)

The MOTU team uses the following workflow:

  • When you start to work on a new package, assign the needs-packaging bug to yourself and set it In Progress (if there is no needs-packaging bug, file one).
  • Once you have an initial package, upload it to REVU, add the link to the package in REVU to the description of the bug. From this point on, no further Launchpad entries are made until the package is uploaded.

  • Once the approved package is uploaded, the uploading MOTU will set the bug status to Fix Committed.
  • When the package clears the NEW queue it will automatically be set to Fix Released (debian/changelog must close the needs-packaging bug). This is done with a bullet point that follows the format:

  * Initial release (LP: #242910)

Deadline

Feature Freeze is the latest approval date (February 18th for "Lucid" aka Ubuntu 10.04): it is recommended to get things done in a couple weeks earlier, as getting approval may take some time. REVU days are planned through Feature Freeze, but the last days are likely only to grab packages that are really required to meet the feature goals for the release.

Alternative workflows

  • These are permitted, but REVU is the official location for getting packages reviewed.

  • The key policy point is that two MOTUs must advocate the package. Most MOTUs use REVU and it may be more difficult to get packages in alternative locations reviewed.

NEW packages through Debian

Ubuntu regularly incorporates source packages from Debian, so it could be useful trying to upload a package to Debian first to automatically have it in Ubuntu in due time. In order to have faster reviews, several teams have been set up to manage a given subset of packages. Some of them are:

More teams can be found here.

Ubuntu does virtually all package maintenance in teams. If you have a deep interest in a particular package and a desire to be the primary person responsible for it, you would likely be happier to get the package into Debian and maintain it there. Debian has a strong culture around individual package maintainers that is not present in Ubuntu. Additionally there are roughly an order of magnitude more Debian Developers than Ubuntu developers. It is quite difficult to get a new package into Ubuntu due to the shear volume of requests compared to the available resources for reviews. In many cases people have an easier time getting their package into Ubuntu via Debian than directly.

Also of interest

  • Always check if there is an ITP (intent to package) bug filed against the wnpp package in Debian. That means, somebody is already working on packaging the software for Debian. Join forces with them rather than reinventing the wheel.

  • mentors.debian.net, a website where people interested in getting their packages inside Debian can upload their packages. You need to browse the directories to find packages. ContributingToDebian has additional information on getting your work into Debian.

  • Debian's WebSVN It's possible that a package has been worked on for Debian but has a status of UNRELEASED. Check the appropriate directories that begin with "pkg" that your package may fall under. For example, game packages would be under "pkg-games".


Go back to UbuntuDevelopment.
CategoryProcess
CategoryUbuntuDevelopment

UbuntuDevelopment/NewPackages (last edited 2021-06-14 14:41:16 by ogra)