Diff for "Ubuntu/InfrastructureNeeds"

Not logged in - Log In / Register
Differences between revisions 13 and 26 (spanning 13 versions)
⇤ ← Revision 13 as of 2011-10-13 01:37:07 →
Size: 6592
Editor: bryce
Comment: Move completed items to the history page
← Revision 26 as of 2011-11-15 21:55:59 → ⇥
Size: 7552
Editor: bryce
Comment: Incorporating various ideas for features that came up in UDS discussions
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
'''This is an old page that has not been updated recently; many of the items mentioned here are complete or obsolete, and the priorities need revisited on the remainder. -- bryce'''
Line 9: Line 7:

 1. Monitoring of Debian bugs
  * Tracked at: '''https://blueprints.edge.launchpad.net/malone/+spec/debian-bug-import-continuous-imports'''
  * Rationale: Nearly all Debian bugs also affect Ubuntu, and Debian's larger base of developers can find and fix a higher volume of bugs. We should be informed of these bugs so that we can make a decision about whether to act on them.
  * Status:
   * A script exists to import bugs from debbugs into Launchpad: '''https://blueprints.launchpad.net/malone/+spec/debian-bug-import-on-demand'''
   * Launchpad can already import comments from debbugs, and send replies back to debbugs. A separate issue is whether or not we proactively import ALL Debian bugs into Launchpad, or whether we only import a subset of bugs (say, RC bugs), or whether we only import Debian bugs which have been manually correlated to Ubuntu bugs.
   * '''https://blueprints.launchpad.net/malone/+spec/upstream-bug-searching-and-filing'''. The expensive implementation depends on bugzilla-launchpad-identification.
    * Depends on BugTrackerImport.context
    * From also-affects-upstream:
     * Offer link to search first and say "(opens in new window)"
     * Group in sections:
      * "Didn't find your bug?": Offer a button that says "Report bug upstream (requires account in bugzilla.gnome.org) (opens in new window)"
      * Offer a box to enter the existing bug URL
    * Post to enter_bug.cgi form containing:
     * description (include URL to Launchpad bug) - summary
     * product (which comes from BugTrackerImport.context)
    * User is redirected to login, he uses his credentials and then bug is filed.
     * demo URL: http://people.ubuntu.com/~jamesh/file-bug-gnome.html
    * Less cheap would include a special plugin for GNOME bugzilla to provide a URL to redirect the end-user to a special URL. The "from-launchpad" keyword would be useful as well.
    * If we import bugs regularly, bug watches can be created at scan time.
  * Ideas:
   * Create non-Launchpad infrastructure to monitor bugs - Where to get notification addresses? Scrape launchpad?
   * MoM's bug notifications could be the basis of a partial solution
Line 39: Line 13:
   * The "no upstream bug tracker exists" use case, which is described in '''https://blueprints.launchpad.net/malone/+spec/forwarding-to-email-address'''
   * Simplified/automatic filing of bugs in an external bug tracker
   * Comment synching to enable inter-bug-tracker replies		    * The "no upstream bug tracker exists" use case, which is described in '''https://blueprints.launchpad.net/malone/+spec/forwarding-to-email-address''' (Done?)
   * Comment synching to enable inter-bug-tracker replies (Done?)
   * Map remote bugtracker product/component to source package: '''https://dev.launchpad.net/LEP/BugzillaComponents''' (Nearly done)
   * Forwarding of selected attachments from LP bug to upstream - '''https://dev.launchpad.net/LEP/ForwardAttachmentsUpstream'''
   * Automatic user registration in remote tracker
   * Automatic fill-in of upstream bug report fields (title, description, priority, cc, etc.)

 1. Bug Q&A
   * Tracked at: https://dev.launchpad.net/Bugs/BugQ%26A
   * Status:
     * Is included on Roadmap - '''https://dev.launchpad.net/VersionFourDotO/Stories'''

 1. Bug Bookmarks
   * Tracked at https://bugs.launchpad.net/bugs/193585
   * Status: Needs escalation to Launchpad
Line 44: Line 30:


== Low priority ==

 1. Opening a new distrorelease before releasing the previous one (shortcoming relative to former dak infrastructure)
  * Tracked at: '''https://bugs.launchpad.net/soyuz/+bug/87012'''
  * Rationale: When opening a new distrorelease, uploads must be temporarily blocked until the toolchain and other basic infrastructure are in place. Opening the new release early would allow this work to happen in parallel, so that the new release would be immediately open for development.

  * Status:
   * PPAs make it possible to do some of the preparatory work for a new distro series
   * Fully handling this was not targeted for Launchpad 4.0
Line 71: Line 46:
 1. Prohibit filing bugs on obsolete packages (Bug:46385)

 1. Subscribe Team to Tag, e.g. 'regression'

 1. Hiding comments or removing comments (Req'd by kernel team)

 1. Soyuz archive index
  * Tracked at: '''https://dev.launchpad.net/ArchiveIndex'''
  * Rationale: Req'd by Software Center

 1. Structured bug json data - aka "tags with values"

 1. PPA developer usability enhancements

== Low priority ==

 1. Opening a new distrorelease before releasing the previous one (shortcoming relative to former dak infrastructure)
  * Tracked at: '''https://bugs.launchpad.net/soyuz/+bug/87012'''
  * Rationale: When opening a new distrorelease, uploads must be temporarily blocked until the toolchain and other basic infrastructure are in place. Opening the new release early would allow this work to happen in parallel, so that the new release would be immediately open for development.

  * Status:
   * PPAs make it possible to do some of the preparatory work for a new distro series
   * Fully handling this was not targeted for Launchpad 4.0
Line 78: Line 77:
 1. Search PPAs for version of app you want, for version of ubuntu you're on

 1. A new status for bugs between the in progress and fix committed, for when you fixed the bug and waiting for merge

 1. Ability to clone a bug

 1. Search across attachments
     * From previous discussion, sounds like this would be quite hard / resource intense

 1. Tarball visibility / navigation

== Undefined ==
Line 80: Line 92:
   * What does this mean exactly?

 1. Blueprints need love

 1. Improve mailing lists

 1. Answers needs either significantly improved, or scrapped in favor of just using AskUbuntu.com

 1. PPA improvements. Build status notification. Ability to host multiple versions of a given package (e.g. for bisection study purposes). Expose more of the internal API through the external Launchpad API.

 1. QA tracking. Some way to better flag bugs/branches/patches/etc. as needing testing, passed testing, failed testing, and so on. Ideally should also support hooking into automated testing in some fashion, with the goal of being able to delineate between code ready to be released from that needing additional work.

 1. Some sort of integrated task tracking. Would replace the makeshift work-items currently done in blueprint whiteboards. Could also consolidate the use of team subscriptions, bug tasks, tagging, merge review requests, sync requests, and other makeshift task-workflow-management systems currently in use.

 1. wiki-like functionality in various places throughout launchpad. E.g. PPA descriptions, project home/about pages, blueprints, whiteboards, etc. We need wiki-like markup (including tables), revision tracking, and easy cross-linking to other LP entities.

== Other stakeholder issues also relevant to Ubuntu: ==

 1. git support. Native git hosting.

 1. [[https://dev.launchpad.net/VersionFourDotO/OutOfScope/Blueprints|Wiki markup in blueprints]] (OEM)

 1. Task tracking in blueprints (aka [[https://dev.launchpad.net/VersionFourDotO/OutOfScope/Blueprints|Blueprint decomposition]]) (OEM)

 1. Add a "workaround" field to bug (Bug:54652). (Corp Services)

 1. Launchpad doesn't support multiple attachment (Bug:82652). (Corp Services)

See also: Launchpad's RoadMap and list of [[LEP|LEPs]].

This page discusses ways Launchpad could better serve the Ubuntu community. Please contact us with thoughts or questions.

Launchpad contact

Francis Lacoste

Ubuntu contact

Bryce Harrington

High Priority

  1. Semi-automatic bug forwarding to upstream bug trackers

    • Tracked at: ???

    • Rationale: Ubuntu receives a very high volume of bug reports which should be forwarded upstream. Making this process more efficient would improve both the quality of Ubuntu and its relationships with upstream projects.
    • Status: Some of the steps for this to happen are implemented. Additional work includes:

  2. Bug Q&A

  3. Bug Bookmarks

Medium Priority

  1. Temporarily adding the uploader as a bug contact for the package being uploaded
    • Rationale: Our development model is such that packages are often uploaded by a developer who has no ongoing relationship with the package. Because they do not receive bug reports for the package, it is easy for them to be unaware of having introduced a regression.
    • Status:
  2. Visual distinction between bug comments from authoritative Ubuntu people and bug comments from random Launchpad users

    • Tracked at: ???

    • Rationale: Users who view and file bugs in Launchpad are not always familiar with the way bug tracking works in a large community project like Ubuntu. When they receive a comment which is inappropriate, erroneous or poorly presented, they assume that it came from someone representing the project, when in fact anyone with an email address can post a response. Users who find these bugs via web searches have difficulty telling the difference between comments from users and authoritative information from developers and QA. We want to avoid this confusion and misrepresentation, while still allowing everyone to participate, by visually showing the user whether the commenter is a member of an official team (such as Ubuntu QA), perhaps by showing the team badge next to their name.
    • Status:

  3. Prohibit filing bugs on obsolete packages (46385)

  4. Subscribe Team to Tag, e.g. 'regression'
  5. Hiding comments or removing comments (Req'd by kernel team)
  6. Soyuz archive index
  7. Structured bug json data - aka "tags with values"
  8. PPA developer usability enhancements

Low priority

  1. Opening a new distrorelease before releasing the previous one (shortcoming relative to former dak infrastructure)

    • Tracked at: https://bugs.launchpad.net/soyuz/+bug/87012

    • Rationale: When opening a new distrorelease, uploads must be temporarily blocked until the toolchain and other basic infrastructure are in place. Opening the new release early would allow this work to happen in parallel, so that the new release would be immediately open for development.
    • Status:
      • PPAs make it possible to do some of the preparatory work for a new distro series
      • Fully handling this was not targeted for Launchpad 4.0
  2. Notifying the release team of new milestone targets

    • Tracked at: ???

    • Rationale: The release team tracks outstanding targets for milestones and their resolution. However, they currently must poll in order to obtain this information. Asynchronous notification would be more efficient.
    • Status:
      • Structural subscriptions were targeted for Launchpad 2.0 (2009-08-03: update, anyone? Do we push notification now?)
  3. Search PPAs for version of app you want, for version of ubuntu you're on
  4. A new status for bugs between the in progress and fix committed, for when you fixed the bug and waiting for merge
  5. Ability to clone a bug
  6. Search across attachments
    • From previous discussion, sounds like this would be quite hard / resource intense
  7. Tarball visibility / navigation

Undefined

  1. Package version tracking for bugs (shortcoming of Launchpad relative to debbugs)
    • Not targeted in Launchpad 2.0
    • What does this mean exactly?
  2. Blueprints need love
  3. Improve mailing lists

  4. Answers needs either significantly improved, or scrapped in favor of just using AskUbuntu.com

  5. PPA improvements. Build status notification. Ability to host multiple versions of a given package (e.g. for bisection study purposes). Expose more of the internal API through the external Launchpad API.
  6. QA tracking. Some way to better flag bugs/branches/patches/etc. as needing testing, passed testing, failed testing, and so on. Ideally should also support hooking into automated testing in some fashion, with the goal of being able to delineate between code ready to be released from that needing additional work.
  7. Some sort of integrated task tracking. Would replace the makeshift work-items currently done in blueprint whiteboards. Could also consolidate the use of team subscriptions, bug tasks, tagging, merge review requests, sync requests, and other makeshift task-workflow-management systems currently in use.
  8. wiki-like functionality in various places throughout launchpad. E.g. PPA descriptions, project home/about pages, blueprints, whiteboards, etc. We need wiki-like markup (including tables), revision tracking, and easy cross-linking to other LP entities.

Other stakeholder issues also relevant to Ubuntu:

  1. git support. Native git hosting.

  2. Wiki markup in blueprints (OEM)

  3. Task tracking in blueprints (aka Blueprint decomposition) (OEM)

  4. Add a "workaround" field to bug (54652). (Corp Services)

  5. Launchpad doesn't support multiple attachment (82652). (Corp Services)

See also: Launchpad's RoadMap and list of LEPs.

Historical infrastructure needs

Ubuntu/InfrastructureNeeds (last edited 2011-11-22 03:34:55 by bryce)