TODO

Differences between revisions 27 and 55 (spanning 28 versions)
⇤ ← Revision 27 as of 2007-11-14 09:29:09 →
Size: 7981
Editor: i59F77A9D
Comment:
← Revision 55 as of 2013-08-25 03:48:06 → ⇥
Size: 2966
Editor: c-76-25-23-72
Comment: removing already done wxWindows work
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(MOTU/Headers/Menu)]] <<Include(MOTU/Headers/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 11: Line 11:
 * [http://merges.ubuntu.com/universe.html Merges/Syncs for Hardy]  * [[http://people.ubuntuwire.com/~lucas/merges.html|Merges/Syncs]]
Line 13: Line 13:
[[Anchor(NewSoftware)]] <<Anchor(NewSoftware)>>
Line 16: Line 16:
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]
 Check out '''[[MOTU/TODO/NewSoftware]]'''.
Line 25: Line 20:
=== Patch Testing and Review ===

Check out '''http://harvest.ubuntu.com/opportunities/''' and:
 1. Make sure the bug is still relevant.
 1. Assign it to you.
 1. Transform the patch into a [[PackagingGuide/Recipes/Debdiff|debdiff]] if necessary.
 1. Make sure it builds and fixes the bug.
 1. Add it to the [[SponsorshipProcess|sponsoring queue]] or upload it yourself.
Line 27: Line 32:
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]		 Help to fix packages that are not installable. A list can be found [[http://qa.ubuntuwire.com/debcheck/debcheck.py?list=relationship%2dDepends&arch=ANY|on debcheck]] updated 6-hourly.
 * Component-specific unmetdeps lists are also available: [[http://qa.ubuntuwire.com/debcheck/debcheck.py?list=universe-only-relationship%2dDepends&arch=ANY|universe]] [[http://qa.ubuntuwire.com/debcheck/debcheck.py?list=multiverse-only-relationship%2dDepends&arch=ANY|multiverse]]
Line 30: Line 35:
 * Best to use a clean `pbuilder` environment if possible. See: ["PbuilderHowto"].  * Best to use a clean `pbuilder` environment if possible. See: [[PbuilderHowto]].
Line 36: Line 41:
  * Incorporate Debian RC fixes: http://django.ajmitch.net.nz/rcbugs/   * Incorporate Debian RC fixes: http://qa.ubuntuwire.com/bugs/rcbugs/
  * Address FTBFS issues: http://qa.ubuntuwire.com/ftbfs
  * Review outstanding lintian issues: http://lintian.ubuntuwire.org/
  * Lists of packages needing updates due to depends on obsolete package names (e.g., library transitions): http://people.ubuntu.com/~ubuntu-archive/NBS/
  * Check out other QA activities: http://qa.ubuntuwire.com/
  * Piuparts Logs: http://people.ubuntu.com/~liw/piuparts/ ([[https://lists.ubuntu.com/archives/ubuntu-devel/2007-December/024893.html|instructions]])
Line 38: Line 48:
   * http://people.ubuntu.com/~pitti/ubuntu-cve/
Line 40: Line 49:
   * https://bugs.launchpad.net/~motu-swat
Line 41: Line 51:
  * Help migrate applications away from wxWindows2.4: ["MOTU/wx2.4Migration"]
Line 44: Line 53:
  * Port software to use Ubuntu information, rather than Debian: [[MOTU/PackagesToPort]]
Line 45: Line 55:
[[Anchor(Bugs)]] <<Anchor(Bugs)>>
Line 48: Line 58:
 * [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]
 * Bug related:
  * [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.		 Check out '''[[MOTU/TODO/Bugs]]'''.
Line 64: Line 61:
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)]]
Line 109: Line 62:
Go back to '''[:MOTU]'''.[[BR]]
["CategoryMOTU"]		 Go back to '''[[MOTU]]'''.<<BR>>
[[CategoryMOTU]]<<BR>>
[[CategoryTeamTODOPage]]

Home

Getting Started
Get started here!

Teams

FAQ

Events

TODO

Contact

Next MOTU Meeting (details)

Thursday, December 6th 2012, 16:00 UTC

Next Packaging Training Session (details)

TBD

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

Packaging New Software

Check out MOTU/TODO/NewSoftware.

Patch Testing and Review

Check out http://harvest.ubuntu.com/opportunities/ and:

  1. Make sure the bug is still relevant.
  2. Assign it to you.

  3. Transform the patch into a debdiff if necessary.

  4. Make sure it builds and fixes the bug.

  5. Add it to the sponsoring queue or upload it yourself.

Unmet Dependencies

Help to fix packages that are not installable. A list can be found on debcheck updated 6-hourly.

  • Component-specific unmetdeps lists are also available: universe multiverse

  • Some of them are main packages, please sort them out. If you want to take care of them... even better. Smile :)

  • 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

Universe / Multiverse Bugs

Check out MOTU/TODO/Bugs.

Go back to MOTU.
CategoryMOTU
CategoryTeamTODOPage

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