NewUI
|
⇤ ← Revision 1 as of 2009-08-19 07:48:29
Size: 1550
Comment:
|
Size: 3442
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| * '''Launchpad Entry''': UbuntuSpec:community-lucid-harvest-next-steps * '''Created''': 2009-12-01 * '''Contributors''': dholbach, james-w, rockstar, jonobacon == Summary == Now that Harvest is [[https://code.launchpad.net/~harvest-dev/harvest/django|ported to]] [[http://djangoproject.org|Django]] we can think of a new UI that is more flexible and accomodates all the use cases we're thinking of. == Rationale == The old Harvest was more of a proof-of-concept work than a system that was really usable. The code was unmaintainable and the UI did absolutely not scale, both in terms of accomodating the mass of opportunities and in terms of new requirements. |
|
| Line 6: | Line 15: |
| = Mockups = * [[http://people.canonical.com/~jamesw/harvest.png|James Westby's mockup]] * Comments (please "sign" with `@``SIG``@`): * ... * [[http://people.canonical.com/~dholbach/harvest-mockup2.jpg|Daniel Holbach's mockup]] * Comments (please "sign" with `@``SIG``@`): * ... |
|
| Line 14: | Line 16: |
| = Use Cases = | == User stories == |
| Line 20: | Line 22: |
| == Design == * [[http://people.canonical.com/~jamesw/harvest.png|James Westby's mockup]] * [[http://people.canonical.com/~dholbach/harvest-mockup2.jpg|Daniel Holbach's mockup]] == Implementation == This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: === UI Changes === [[http://people.canonical.com/~dholbach/harvest-mockup2.jpg|Daniel Holbach's mockup]] shows how you can * better pick opportunities based on their type of opportunity * better pick opportunities based on the set of packages you're interested in * mark opportunities as irrelevant * comment on opportunities === Code Changes === The porting of the backport is already done, the UI part is being worked on. === Migration === Harvest's data is still being read from [[https://code.launchpad.net/~harvest-dev/harvest-data/trunk|lp:harvest-data]], even faster than it was in the old Harvest. == BoF agenda and discussion == {{{ The ugly ;-) old one: http://daniel.holba.ch/harvest/ The beautiful new mockups: https://wiki.ubuntu.com/Harvest/NewUI The new implementation is going to be developed in Django === The UI === === Features ==== Commenting: * For indicate work is being done on the current opportunity or patch review === Current code for Harvest === bzr branch lp:harvest == New Ideas == - skill level: easy, medium, hard (set default per opportunity list) }}} |
|
| Line 22: | Line 74: |
| CategoryHarvest | CategoryHarvest <<BR>> CategorySpec |
Launchpad Entry: community-lucid-harvest-next-steps
Created: 2009-12-01
Contributors: dholbach, james-w, rockstar, jonobacon
Summary
Now that Harvest is ported to Django we can think of a new UI that is more flexible and accomodates all the use cases we're thinking of.
Rationale
The old Harvest was more of a proof-of-concept work than a system that was really usable. The code was unmaintainable and the UI did absolutely not scale, both in terms of accomodating the mass of opportunities and in terms of new requirements.
Now that Harvest is ported to Django we can think of a new UI that is more flexible and accomodates all the use cases we're thinking of.
User stories
- Daniel wants to sponsor a few patches. He can upload to all parts of Ubuntu. He logs into Harvest, picks Sponsoring and is all set.
- Sébastien is a Desktop guy, he just cares about Desktop packages. He logs into Harvest, selects Desktop packages and can see everything that "needs to be done".
- Jonathan, a new contributor, knows a bit about packaging and Ubuntu maintenance work and has a spare hour. He uses Kubuntu, so picks Kubuntu. Finds out there is a new upstream version to be packaged. Curious to learn more he clicks on the "?" after the "upgrade opportunity" and is sent to a page explaining how to go about software updates.
Benjamin finds out about a Fedora patch of the xmms2 package. He checks it out and finds that it only applies to an older version of xmms2. He marks the patch as "irrelevant".
Design
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Daniel Holbach's mockup shows how you can
- better pick opportunities based on their type of opportunity
- better pick opportunities based on the set of packages you're interested in
- mark opportunities as irrelevant
- comment on opportunities
Code Changes
The porting of the backport is already done, the UI part is being worked on.
Migration
Harvest's data is still being read from lp:harvest-data, even faster than it was in the old Harvest.
BoF agenda and discussion
The ugly ;-) old one: http://daniel.holba.ch/harvest/ The beautiful new mockups: https://wiki.ubuntu.com/Harvest/NewUI The new implementation is going to be developed in Django === The UI === === Features ==== Commenting: * For indicate work is being done on the current opportunity or patch review === Current code for Harvest === bzr branch lp:harvest == New Ideas == - skill level: easy, medium, hard (set default per opportunity list)
Harvest/NewUI (last edited 2009-12-03 12:46:41 by i59F77634)