On Tue, 2009-08-04 at 13:53 -0300, Christian Robottom Reis wrote: > On Mon, Aug 03, 2009 at 12:56:40PM -0700, Charlie Poole wrote: > > BUT I never imagined blueprints as being a place for > > wishes, ideas without solutions or bugs. Maybe the biggest > > problem is that there is nothing in Launchpad to encouorage > > you to avoid using them that way. > > And this I agree with. I think the larger problem that any project > publically using blueprints faces is that, similarly to the bug tracker, > any end-user can come in and post a new feature request, and there's of > course an expectation that the request will at least be read; because of > the UI and [shortcomings of the] email interface this actually requires > polling from the side of the project team, and it just doesn't work. Yes this is a problem. Without a place to suggest features and explore them. Engineers (and I am thinking of Launchpad developers too) spend lots of time creating specifications that will never be implemented. Even those that are implemented are in dispute because the implementation (reality) differs from the blueprint -- it is half implemented according to a historic document. A better system would rely on a repository of simple ideas. Simple because they should be considered atomic; either they are implemented or they are not, no half state. Ideas are not deleted because while they may not match the current focus of an application it may in the future. The ideas can mature in the repository so that when they are a well understood story, it is easy for someone to commit implementing it -- not spend months thinking about it with some sense of deadline. Blueprints are constructed from a set of stories. Each story is either essential, expected, or optional. There is no beta until all the essential ideas are implemented. We expect progress to be quick because the stories are mature ideas. The blueprint is complete when the essential and expected stories are complete. Uncompleted optional can be implemented in another effort. Stories can change priority in a blueprint to meet the immediate needs of the project, no one want to implement an unwanted feature. -- __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.)