[Gnumed-devel] Launchpad Blueprints vs Bug vs Wiki todo-list

[James Busser]

was Re: [Bug 268522] Re: Develop "patient overview" widget to inform  
as "initial plug-in" after a patient search

==========================

Blueprint opened.

I expect a Launchpad "blueprint" is best used for things like modules  
or other functionality that needs to be built.

Should it also be used to store and manage the status of ToDo items?  
I am looking to make clear any separation between what we would want  
as bug-reportable items which are however just wishlist, from  
anything we would wish to log as a Blueprint request.

For example my suggestion that in the Progress notes, the datetime  
stamp and last-editor of a SOAP note be "unwrapped" to make the  
clinical content easier to read, also Rogerios's offlist suggestion  
that an extra line of white space be added between sections... where  
shall we put these?

Maybe the guide should be:

- if it needs enough detail that the detail should link to a  
description on the wiki of what is needed, it should be a Blueprint  
item.

- if it is only a request that something be changed or adjusted which  
requires minimal other information, let it be a bug-report-requested  
wishlist item?

Basically I am wondering how much of what is on the ToDo list page  
could / should be migrated off into Bugs and Blueprints?


On 10-Sep-08, at 9:29 AM, Gour wrote:

> If it's on TODO, then maybe we can open a blueprint which connects to
> it?
>
>
> Sincerely,
> Gour
>
> --
> Develop "patient overview" widget to inform as "initial plug-in"  
> after a patient search
> https://bugs.launchpad.net/bugs/268522
> You received this bug notification because you are a member of GNUmed
> development, which is subscribed to GNUmed.