TODO

Differences between revisions 1 and 27 (spanning 26 versions)
Revision 1 as of 2007-02-23 11:39:32
Size: 1395
Editor: i59F7190D
Comment:
Revision 27 as of 2007-11-14 09:29:09
Size: 7981
Editor: i59F77A9D
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(MOTU/Headers/Menu)]]

||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]||
Line 5: Line 9:
== General Tasks ==

 * [http://merges.ubuntu.com/universe.html Merges/Syncs for Hardy]

[[Anchor(NewSoftware)]]
=== Packaging New Software ===

Packaging new software is a valuable task, but sometimes not trivial. More information on how to do it:

 * [https://launchpad.net/ubuntu/+bugs?field.tag=needs-packaging Packages requested by others]
 * [:UbuntuDevelopment#NewPackages:Policy for inclusion of new packages]
 * [:PackagingGuide/Basic:How to package from scratch]


== Packaging related ==

=== Unmet Dependencies ===

Help to fix packages that are not installable. A list can be found [http://alt.qeuni.net/~william/debcheck/debcheck.py?list=relationship%2dDepends&arch=ANY on debcheck] updated 6-hourly.
 * Component-specific unmetdeps lists are also available: [http://alt.qeuni.net/~william/debcheck/debcheck.py?list=universe-only-relationship%2dDepends&arch=ANY universe] [http://alt.qeuni.net/~william/debcheck/debcheck.py?list=multiverse-only-relationship%2dDepends&arch=ANY multiverse]
 * Some of them are main packages, please sort them out. If you want to take care of them... even better. :)
 * Best to use a clean `pbuilder` environment if possible. See: ["PbuilderHowto"].
 * `apt-get source <package>` and `debuild or `dpkg-buildpackage`
 * Many of the packages just need a fresh rebuild.

=== Other Packaging tasks ===

  * Incorporate Debian RC fixes: http://django.ajmitch.net.nz/rcbugs/
  * Look for potential security fixes:
   * http://people.ubuntu.com/~pitti/ubuntu-cve/
   * http://security-tracker.debian.net/
 * Code Needed:
  * Help migrate applications away from wxWindows2.4: ["MOTU/wx2.4Migration"]
  * Help develop GUI tool for monitor/resolution configuration: https://launchpad.net/~displayconfig-gtk
  * Help develop failsafe X mode: https://blueprints.launchpad.net/ubuntu/+spec/bullet-proof-x

[[Anchor(Bugs)]]
== Universe / Multiverse Bugs ==

 * [https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&assignee_option=any&field.assignee=&field.owner=&field.component=4&field.component=3&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_no_package.used=&search=Search All open universe/multiverse bugs]
Line 6: Line 50:
  * [http://tinyurl.com/2nu8rm Universe and Multiverse bugs]. There are a lot of bugs, some might even be easy to fix.
  * [http://tinyurl.com/2kr36e Universe and Multiverse bugs with patches attached]. If you can help to review the patches, we'd probably get some good fixes in.
  * [http://tinyurl.com/2mqom8 Universe and Multiverse NeedsInfo bugs]. Some of the `Needs Info` bugs have been in that state for a long time, let's review them.
  * [http://tinyurl.com/2szdcv Universe and Multiverse bugs that need forwarding Upstream]. These bugs need to get forwarded upstream.
  * [http://tinyurl.com/2v9m9v Universe and Multiverse Fix Committed bugs]. Make sure that these `Fix Committed` bugs are really in the process of getting fixed.
  * [http://tinyurl.com/368977 Universe and Multiverse bugs marked as packaging]. These bugs are all packaging related.
  * [http://tinyurl.com/2us2se Universe and Multiverse bugs marked as bitesize]. These bugs are for new contributors.
  * Help mark bugs as
   * `packaging`: if the bug lies in the packaging.
   * `bitesize`: if the bug is easy to be solved and suited for a new contributor.
 * Packaging related:
  * Help to fix packages that are not installable: `apt-cache -i unmet`.
  * [http://tinyurl.com/2leltj Universe and Multiverse bugs]. There are a lot of bugs, some might even be easy to fix.
  * [http://tinyurl.com/39w2p3 Universe and Multiverse bugs with patches attached]. If you can help to review the patches, we'd probably get some good fixes in.
  * [http://tinyurl.com/34njoy Universe and Multiverse Incomplete bugs]. Some of the `Incomplete` bugs have been in that state for a long time, let's review them.
  * [http://tinyurl.com/2oay6v Universe and Multiverse bugs that need forwarding Upstream]. These bugs need to get forwarded upstream.
  * [http://tinyurl.com/2s2yer Universe and Multiverse Fix Committed bugs]. Make sure that these `Fix Committed` bugs are really in the process of getting fixed.
  * [http://tinyurl.com/2ulotw Universe and Multiverse crasher bugs]. Let's forward them upstream and check for dups.
  * Tagged bugs:
   * [http://tinyurl.com/2szf29 Universe and Multiverse bugs marked as packaging]. These bugs are all packaging related.
   * [http://tinyurl.com/3cbrps Universe and Multiverse bugs marked as bitesize]. These bugs are for new contributors.
   * [http://tinyurl.com/2pwln3 Universe and Multiverse bugs marked as upgrade]. Bugs that request new upstream versions - please help reviewing them carefully.
   * [http://tinyurl.com/2tqg3u Universe and Multiverse bugs marked as ftbfs]. Bugs describing build failures of packages.
   * [http://tinyurl.com/3y7ch2 Universe and Multiverse bugs marked as unmdetdeps]. Bugs that indicate packages not being installable due to missing dependencies.


However you contribute to Universe bug squashing, you are welcome to come and join the Universe bug squashers in {{{#ubuntu-bugs}}} and {{{#ubuntu-motu}}} on IRC. In these channels we have a bug bot called {{{ubotu}}}, that can give us more information on bug numbers.

=== Filing Bugs ===
For general information about bug fixing and helping with bugs, please read ReportingBugs and HelpingWithBugs. Before filing bugs, consider reading [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively]. Also search for the bug in [https://launchpad.net/ubuntu/+bugs Launchpad]: somebody might have found it before you!

=== Tagging Bugs ===

To make bugs easier to find for new contributors and to group them into helpful classes, you can help by tagging bugs on launchpad as:
 * `packaging` if you think that the bug lies only in the packaging.
 * `bitesize` if you think that it's suitable for a beginner.
 * `upgrade` if the upgrade of a package is suggested and the request should be carefully checked.
 * `ftbfs` if the bug described a problem to build the package.
 * `unmetdeps` if the package is not installable due to missing dependencies.
 * `needs-packaging` if it's a request for an application which isn't in the repositories.
 * `patch` if there is a patch attached to the bug.

=== Fixing Bugs ===

If you DO NOT have upload permissions, check out SponsorshipProcess on how to get your changes included in Ubuntu.

If you DO have upload permissions, check the [https://bugs.launchpad.net/~ubuntu-universe-sponsors/+subscribedbugs bugs that u-u-s is subscribed to] from time to time: if the package was uploaded and built on all architectures, you can close the bug by marking it as "Fix released".

=== Contributing Upstream ===

Try to check if your report or your fix could be sent to Debian as well. Read ContributingToDebian for more information.

=== Teams ===

We already managed to build teams, whose launchpad IDs can be found in the comprehensive list: ["MOTU/Teams"]

=== Unassigned Bugs ===

Some bugs, however, are still [https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=datecreated&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&assignee_option=none&field.assignee=&field.owner=&field.component=4&field.component=3&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_no_package.used=&search=Search unassigned] and will have to be assigned to the right people/teams.


== Useful links ==
 * The [http://bugs.debian.org/ Debian bug tracking system] might already have a bug open (or already fixed!) waiting for your package. And the [http://packages.qa.debian.org/ Debian Package Tracking System] might have some info too. It's always worth looking!
 * When you fix a bug in Ubuntu, don't forget (if applicable) to file a bug in Debian and attach your patch. It will make more people happier if the bug is fixed in both Debian and Ubuntu, and we won't have to merge our fix when Debian releases a new version of the package. See [http://www.debian.org/Bugs/Reporting this page about reporting bug to Debian by email].
 * [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively], by Simon Tatham. A must rea

== Weekly Tasks ==

[[Include(MOTU/TODO/Weekly)]]

----
Go back to '''[:MOTU]'''.[[BR]]
["CategoryMOTU"]

Include(MOTU/Headers/Menu)

There's always a lot of work to do in Ubuntu's Universe and Multiverse.

Here a quick list of suggestions, where you can help out:

General Tasks

Anchor(NewSoftware)

Packaging New Software

Packaging new software is a valuable task, but sometimes not trivial. More information on how to do it:

Unmet Dependencies

Help to fix packages that are not installable. A list can be found [http://alt.qeuni.net/~william/debcheck/debcheck.py?list=relationship%2dDepends&arch=ANY on debcheck] updated 6-hourly.

Other Packaging tasks

Anchor(Bugs)

Universe / Multiverse Bugs

However you contribute to Universe bug squashing, you are welcome to come and join the Universe bug squashers in #ubuntu-bugs and #ubuntu-motu on IRC. In these channels we have a bug bot called ubotu, that can give us more information on bug numbers.

Filing Bugs

For general information about bug fixing and helping with bugs, please read ReportingBugs and HelpingWithBugs. Before filing bugs, consider reading [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively]. Also search for the bug in [https://launchpad.net/ubuntu/+bugs Launchpad]: somebody might have found it before you!

Tagging Bugs

To make bugs easier to find for new contributors and to group them into helpful classes, you can help by tagging bugs on launchpad as:

  • packaging if you think that the bug lies only in the packaging.

  • bitesize if you think that it's suitable for a beginner.

  • upgrade if the upgrade of a package is suggested and the request should be carefully checked.

  • ftbfs if the bug described a problem to build the package.

  • unmetdeps if the package is not installable due to missing dependencies.

  • needs-packaging if it's a request for an application which isn't in the repositories.

  • patch if there is a patch attached to the bug.

Fixing Bugs

If you DO NOT have upload permissions, check out SponsorshipProcess on how to get your changes included in Ubuntu.

If you DO have upload permissions, check the [https://bugs.launchpad.net/~ubuntu-universe-sponsors/+subscribedbugs bugs that u-u-s is subscribed to] from time to time: if the package was uploaded and built on all architectures, you can close the bug by marking it as "Fix released".

Contributing Upstream

Try to check if your report or your fix could be sent to Debian as well. Read ContributingToDebian for more information.

Teams

We already managed to build teams, whose launchpad IDs can be found in the comprehensive list: ["MOTU/Teams"]

Unassigned Bugs

Some bugs, however, are still [https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=datecreated&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&assignee_option=none&field.assignee=&field.owner=&field.component=4&field.component=3&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_no_package.used=&search=Search unassigned] and will have to be assigned to the right people/teams.

  • The [http://bugs.debian.org/ Debian bug tracking system] might already have a bug open (or already fixed!) waiting for your package. And the [http://packages.qa.debian.org/ Debian Package Tracking System] might have some info too. It's always worth looking!

  • When you fix a bug in Ubuntu, don't forget (if applicable) to file a bug in Debian and attach your patch. It will make more people happier if the bug is fixed in both Debian and Ubuntu, and we won't have to merge our fix when Debian releases a new version of the package. See [http://www.debian.org/Bugs/Reporting this page about reporting bug to Debian by email].

  • [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively], by Simon Tatham. A must rea

Weekly Tasks

Include(MOTU/TODO/Weekly)


Go back to [:MOTU].BR ["CategoryMOTU"]

MOTU/TODO (last edited 2016-10-27 07:45:07 by dholbach)