launchpad development
Patch forwarding
Story 1
As a non-core developer using Launchpad and Bazaar,
I want to give my fix to upstream in a way they can merge it using their tools,
so that we both can use our tools we're comfortable with when collaboratingNotes:
- do we need a story about submitting a patch contained in a source package?
- point the upstream developers either to a URL they can merge from directly, or a page containing the diff, information about the patch, and instructions about how to merge the fix using their tools. E.g., if we have an import of a git branch, there should be instructions for how to merge the fix using git.
- push notifications about fixes ready for review through bug syncing
Story 2
As an Ubuntu developer,
I want to see which patches in my package that need to be sent upstream,
so that others can benefit from my workNotes:
- Helps the Ubuntu developer to see what needs to be done to reduce the delta to upstream, and to see how he can contribute to the upstream project
Story 3
As an Ubuntu developer,
I want to see which patches that have been sent upstream have been merged,
so that I can politely remind upstream to merge my work.Notes:
- This may be used for the Ubuntu developer to make sure that his work actually gets merged, and is not forgotten about.
- This will also make it possible for upstream, so see whether there are patches in Launchpad for them.
Story 4
As a drive-by upstream contributor (John)
I want to point upstream to my fix in Launchpad
So that my fix can be easily merged upstream.
Story 5
As a drive-by upsteam contributor (John)
I want the upstream bug tracker to be notified when my fix is ready in LP
So they can merge my fix
Story 6
As a developer
I want bug followers to be notified when my linked branch is ready for review
So that they can try out and review my fix
Automatic upstream releases discovery
Story 7
As an Ubuntu packager (Kara), possibly maintaining multiple packages,
I want to be notified when upstream makes available a new release
So that I can package it.
Story 8
As an Ubuntu user who has found their software is too old
I want to find newer versions of the package (in PPAs, backports, etc.) So that I can get past the bug I'm encountering.
Story 9
As the developer of an upstream project
I want the latest releases of my project automatically linked to the Ubuntu package
so I can be sure that they'll get into Ubuntu without me having to push for it
Translations forwarding
Story 10
As an upstream developer (John/Jeremy)
I want to see translations made for the Ubuntu package of my software shared with my project translation effort
So I feel that translation effort made on the distro benefits my project.
Story 11
As a developer on an upstream project
I want to have translations of my project that are on Launchpad get into my project automatically
so that I don't have to do the same task over and over.
Translations Import
Story 12
As an Ubuntu developer,
I want to see translations made for an upstream package automatically shared with the Ubuntu package's translation effort,
so that people don't waste time translatating strings for a package that have already been translated upstream.
Notifications control
Story 13
An an Ubuntu user
I want to be told only when a bug is believed to be fixed
So that I can test the fix (without lots of "noise" mail)Notes: Needs to know how to test (eg. "in Karmic" or "in this PPA")
Story 14
As a person who gets too much mail
I want to be able to selectively turn off some Launchpad mails
So that I can get less mail.
Story 15
As an irritable Ubuntu user
I want to stop _all_ mail LP
So that I don't feel spammed.
Story 16
As John the coder
I want to get mail when anything (in a product, in a distro, in a team, etc) changes
So that I can use my preferred client and search/read the data offline.
Bug forwarding
Story 17
An a Ubuntu developer
I want to make an external upstream aware of a triaged bug in Ubuntu
So that we don't have to deal with it anymore.
Story 18
As an non-LP hosted upstream developer
I want to be told when a bug in my software in Ubuntu is determined to be an upstream bug
So that I can investigate it.
Upstream registration
Story 19
As an Ubuntu QA engineer
I want just-in-time easy registration of an upstream project and bug tracker, as part of my bug-forwarding workflow
So that I can start forwarding bugs right away without breaking my workflow.
Integrated bug reporting / Bug imports
Story 20
As a Ubuntu user
I want when reporting a bug in Ubuntu to see if the problem is known upstream
So that I can follow the progress of the bug fix wherever that may happen, and maybe learn about a workaround.
Story 21
As an Ubuntu QA contact,
I want to have all the bug reports from an upstream project in Launchpad
so that I can easily relate bugs reported against Ubuntu packages to upstream bug reports.
Debian PPAs
Story 22
As someone who makes Ubuntu packages (whether distro or PPA),
I want to upload my package to Launchpad and have it published both for Ubuntu and Debian
So that it's easier for Debian to test my improvements (e.g., bug fixes that haven't been sent upstream yet)Notes: Bug #188564 ("Build also packages for Debian in PPA's")
User-driven imports
Story 23
As an Ubuntu developer,
I want an upstream branch available for all the packages in main
So that I can easily see the source code, for example to see if a bug has been fixed, or to see the delta between my package and recent upstream.
Story 24
- As a Ubuntu developer who found that the upstream branch not available in
Launchpad
I want to quickly register a code import for it
So that I can work with the source code from Launchpad right away, and so I (or someone else) can rebase the corresponding source package branch to use Launchpad.Notes: Low latency is key here.
Story 25
As an Ubuntu fan,
I want to quickly add upstream data for packages that are missing it
So that I can help the project although I'm not a coder (and earn karma and brag about it).
Story 26
As the driver of an Ubuntu release
I want to link all packages in the release to upstream releases
so that I can choose the best version to include in Ubuntu.
Crowdsourced bug QA
Story 27
As an Ubuntu developer (John)
I want to spend as little time as possible processing bugs (confirming and triaging)
So that I can spend as much time as possible coding fixes.Notes: Launchpad could ask questions and/or use "affects me too" information to suggest triages and even auto-triage. IOW, Launchpad could do more to support crowdsourcing technically.
Story 28
As an Ubuntu QA engineer
I want users viewing an untriaged bug page to be prompted for a question helping the bug report become complete
So that I can be more effective in my triaging effort.
Story 29
As an Ubuntu QA engineer,
I want to know how many users are affected by a bug
So that I can prioritise bugs more easily.
Story 30
As a developer
I want incomplete bugs to automatically go back to confirmed when the reporter provides the requested information
So that I don't have to mark them confirmed myself.
Better code imports
Story 31
As Kara (the gcc maint in Ubuntu)
I need to apply a mechanichal patch to 70 Gnome packages for a new gcc version
So that I can prepare them for shipment in Ubuntu.
Building community
Story 32
As an Ubuntu user in Serbia
I need to help with translations for tools I use
So that I can improve my own experience
Story 33
As John, the Ubuntu maintainer of Gwivver
I need to coordinate UI changes in the current release
So that address Ubuntu users' issues with this application
Story 34
As the MySQL release manager
I need to talk to the Ubuntu release manager
So that we can coordinate our next release cycle
Story 35
As the Ubuntu release manager
I need to like to quickly distinguish people who are important to me
So that focus on the right issues from incoming requests
Privacy for bug / branches
Story 36
As Bill, the OEM manager for Dell
I want to help my external, secret translations team that I hired for our upcoming secret release create package translations
So that I can ship our product in 20 languages
Story 37
As Bill, the OEM manager for Dell
I need to send our translations upstream from our previous release
So that stop maintaining our translation and reduce costs
Story 38
As as 3rd party contract developer for Dell
I need to maintain my specific versions of upstream changes
So that I can add them to Dell's product with current versions of packages
Story 39
As Bill, the OEM manager for Dell
I need to help my hired, secret coders for our upcoming secret release code
customize and continue to follow trunk So that I can ship customized and up to date versions of our packages
Story 40
As Bill, the OEM manager for Dell
I need to send our patches upstream from our previous release
So that stop maintaining our patches and reduce costs
Upstream / Package Links
Story 41
As someone who wants to interact with an upstream project
I want to get everything about that project in Launchpad
so that I don't have to learn new tools; and that I can take advantage of any network effects that Launchpad provides and that I don't have to context switch
Native source syncing
Story 42
As a package maintainer
I want to sync the full history of Debian packages to Ubuntu
so that the burden of maintaining these packages becomes lighter
Crack-of-the-day
Story 43
As an upstream developer,
I want my trunk built regularly in Ubuntu,
so that I know that it builds and testers can get to it easily,Notes:
- This gives the upstream a bigger testing ground. Ubuntu is a great means of getting their work to more people.
Story 44
As a bug triager,
I want to have people be able to easily confirm the bug against latest trunk,
so that I know whether the bug exists upstream.Notes:
- This helps bug triagers to decide whether the bug is in Ubuntu, or should be sent upstream.
- It's important that it's easy for the tester to test the latest version, without messing up his system.
Story 45
As a fanatic user of Firefox,
I want to always have the bleeding edge version installed,
so that I have the latest features (and bragging rights).Notes:
- Probably requires some sort of linking from products to PPAs.
- Worth considering whether other types of package archives are appropriate. e.g. "project package archives" as distinct from "personal package archives".
- We should also consider dealing with the lack of '~' in PPA urls.
Story 46
As the developer of an upstream project
I want the latest release of my project in ubuntu
So I stop getting out-of-date bug reports from Ubuntu users
Package branch permission
Story 47
As an Ubuntu developer
I want to upload to the official source package branch for a source package
so that I can use Bazaar to do my work, rather than shitty Debian tools.
Package from branch
Story 48
As an Ubuntu developer,
I want to be able to take a branch of code and have it built into an Ubuntu package and distributed in a PPA,
so that people interested in my package can test the tip code with minimal effort on my part and theirs.
Story 49
As an Ubuntu developer,
I want to be able to build my source package branch into an Ubuntu package,
so that it takes less of my time and effort to get the software that interests me into Ubuntu.
Bugs in PPA
Story 50
As Bill the OEM manager,
I want my QA team to test and give feedback as fast as possible for my distribution maitained in a PPA
So that I produce higher quality release for my hardware.
