Overall summary

Matthew Revell and Graham Binns met on the 8th April to plan improvements to the help materials for Launchpad Bugs. These mini-specs, and their associated blueprints, are the result.

Mini Specs

bugs-project-startup-guide

https://blueprints.launchpad.net/launchpad-documentation/+spec/bugs-project-startup-guide

• Story: As a project owner/leader, I want to use Launchpad to track my project's bugs and need information to help me prepare for and then make the switch.
• Deliverables: A comprehensive guide that allows a project owner to go from considering Launchpad as a bug tracker, through preparing either for the switch from elsewhere or for starting off with a bug tracker for the first t ime, through to the steps immediately after taking up Launchpad Bugs.
  • Register your project, activate bug tracking
  • Moving your existing bug history over to LP
    • Provide us with the bugs in our LBIF format -- RelaxNG schema in tree under doc/bug-export.rnc
    • We have converters for Bugzilla, Trac and Sourceforge
  • Add bug reporting guidelines
  • Familiarise themselves with the statuses
  • Link off to the email interface
• Full spec: none
• Depends on: n/a
• Story Points:

bugs-link-external-bug-guide

https://blueprints.launchpad.net/launchpad-documentation/+spec/bugs-link-external-bug-guide

• Story: As a bug reporter/triager, I want to link a bug report tracked in Launchpad to its equivalent tracked in an external tracker.
• Deliverables: A guide to linking a bug report to its external equivalent, whether that's as a bug link, bug watch with status imports or a bug plugin link.
  • Options: bug watch with status, bug link, bug plugin link (two way comment sharing, only forward coments that are replies to comments pulled in from the remote tracker)
  • Also affects projects or a distro -- explain importance of difference between Ubuntu packages and upstream projects that use LP

  • If LP doesn't know the location of an upstream bug tracker: can add info for bug tracker, or give URL for a bug and LP will automatically add bug tracker, we get emails about -- https://bugs.staging.launchpad.net/malone/+bug/356656/+choose-affected-product

  • If it does: there are two scenarios -- 1) it knows everything and can help your search for it or file it or 2) it still doesn't know enough so just gives you the options above. Explain that the maintainer needs to set such gubbins.
  • If the bug plugin is set up it works the same!
• Full spec: none
• Depends on: n/a
• Story Points: