Diff for "VersionFourDotO/Stories"

Not logged in - Log In / Register

Differences between revisions 4 and 5
Revision 4 as of 2009-10-01 13:23:40
Size: 13947
Editor: kfogel
Comment:
Revision 5 as of 2009-10-01 13:25:21
Size: 13726
Editor: kfogel
Comment:
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:
  * As a drive-by upstream contributor (John)<<BR>>
  I want the upstream developers to be able to merge the fix I
  developped in a bzr branch<<BR>>
  So that I don't need to use git and they don't need to use bzr

Patch forwarding

  • 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 collaborating

    • Notes:

      • 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
  • 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.

  • 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

  • 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

  • As an OEM engineer who has fixed a bug in an Ubuntu package,
    I want to ensure the fix is upstream
    so that I don't have to maintain the patch.

  • 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 work

    • Notes:

      • 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
  • 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 not is forgotten about.
      • This will also make it possible for upstream, so see whether there are patches in Launchpad for them.

Automatic upstream releases discovery

  • 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.

  • As an Ubuntu packager (Kara)
    I want to be notified when upstream makes available a new release
    So that I can package it.

  • As an ubuntu package maintainer maintaining multiple packages
    I want launchpad to tell me about new releases
    so that I know when to package these new releases

  • 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

  • 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 that I don't feel the translation effort made on the distro is not benefiting my project.

  • 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.

  • As a developer on an upstream project
    I want my project to be translated into as many languages as possible
    so that I will get more users

  • As a developer on an upstream project
    I want to get the translations of my project that are on Launchpad into my project
    so that I don't have to organize the work myself

Translations Import

  • As a non-English speaker using Ubuntu
    I want the software that I use to be translated into my language
    so that I can actually use it!

  • As an Ubuntu translator
    I want the translation data for any upstream project to be available in Launchpad
    so that I can translate the upstream into my language and get it into Ubuntu

  • As an Ubuntu translator
    I want to be able to use the translation already done on Ubuntu or an upstream to be available whenever I translate something new
    so that I avoid duplicating work and thus wasting my time

Notifications control

  • As a person who gets too much mail
    I want to see all the reasons (or channels/causes/sources) why Launchpad is sending me email
    So that I can turn some off.

  • As John the coder
    I want to get mail when anything changes
    So that I can search/read it offline.

  • 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")

  • As an irritable Ubuntu user
    I want to stop _all_ mail LP
    So that I don't feel spammed.

Bug forwarding

  • An a Ubuntu developer
    I want to make an external upstream aware of a triaged bug in Ubuntu
    So that they can fix it

  • 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

  • As an Ubuntu QA engineer
    I want to register very quickly an upstream project and bug tracker
    So that I can forward bugs to them

Integrated bug reporting / Bug imports

  • As a Ubuntu user
    I want when reporting a bug to see if the problem is known in Ubuntu or upstream
    So that I don't file a duplicate and maybe find a work-around.

  • As an Ubuntu user,
    I want to have one place to find out whether the problem I'm experiencing has already been reported whether that's upstream or in Ubuntu,
    so that I can follow the progress of the bug fix wherever that may happen.

  • As an Ubuntu QA user
    I want to search the external upstream bug tracker through Launchpad
    So that I can if an issue is already known/fixed

  • 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

  • As a Gnome-Do developer,
    I want to provide Debian packages in our project PPA
    So that Debian users can get the latest releases

    • Notes: Bug #188564

  • As an Ubuntu developer who also maintain the Debian package,
    I want to upload my package to Launchpad and have it published both for Ubuntu and Debian
    So that it's easier to keep Ubuntu and Debian version of the package in sync.

    • Notes: Bug #188564

User-driven imports

  • As an Ubuntu developer,
    I want an upstream branch available for all the packages in main
    So that I can easily have access to the source code.

  • 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 access the source code from Launchpad.

    • Notes: Implies low-latency

  • As an Ubuntu fan,
    I want to quickly add upstream data for all 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).

  • As the driver of an Ubuntu release
    I want to all packages in the release linked to upstream releases
    so that I can choose the best version to include in Ubuntu

User driven bug QA

  • As an Ubuntu developer (John)
    I want to be distracted as little as possible by unconfirmed bugs and fixed bugs
    So that I can spend as much time as possible coding fixes.

Self-completing / self-sorting bug

  • As an Ubuntu QA engineer
    I want the bug reports to complete itself
    So that most of the bug that I triage are complete.

  • 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.

  • 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.

  • 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

  • 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

  • As an Ubuntu user in Serbia
    I need to help with translations for tools I use
    So that I can improve my own experience

  • 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

  • As the MySQL release manager
    I need to talk to the Ubuntu release manager
    So that we can coordinate our next release cycle

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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.
  • 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.
  • 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).

  • 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

  • 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

  • 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.

  • 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

  • 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.

VersionFourDotO/Stories (last edited 2010-01-05 07:14:36 by jml)