On Tue, 2009-08-04 at 11:02 -0700, Mike Rooney wrote: ... > One other issue is that editing and manipulating blueprints can be a > little tedious as Priority, Definition, Milestone, and the People are > all edited separately and not via AJAX, so to change a blueprint you > are generally talking about visiting 4-8 pages. If this were cleaned > up I think people might find blueprints more usable as well. There are two problems here. The UI and the workflow. We can and will fix some of the UI issues as a part of Launchpad 3.0. The workflow itself has not evolved. It is modeled on Ubuntu sprints from few years ago. Many, maybe most, projects do not need a process with so many statues and people involved. The Launchpad project does not use blueprints as much as it did two years ago because the process is not agile. Too much effort is spent tracking. -- __Curtis C. Hovey_________ http://launchpad.net/
Attachment:
signature.asc
Description: This is a digitally signed message part
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)