← Back to team overview

dhis2-devs team mailing list archive

Re: New blueprints/feature requests -on the list?

 

On Thu, May 14, 2009 at 8:39 PM, Saptarshi Purkayastha <sunbiz@xxxxxxxxx>wrote:

> We should follow Carl Fogel's advice<http://producingoss.com/en/bug-tracker.html#bug-tracker-mailing-list-interaction>and follow discussion only on mailing lists... Blueprints could act as
> outcome of those discussion or to summarize discussions
>
I agree. Would be great if blueprints could do as bugs though, and
automatically show up both in launchpad and on the list....


>
> ... And there are better ways to see the roadmap than what launchpad is
> showing us :(
>
Of course, but those we have to make ourselves using other tools. Feel
free....


>
> ---
> Regards,
> Saptarshi PURKAYASTHA
> Director R & D, HISP India
> Health Information Systems Programme
>
> My Tech Blog:  http://sunnytalkstech.blogspot.com
> You Live by CHOICE, Not by CHANCE
>
>
> 2009/5/14 Ola Hodne Titlestad <olati@xxxxxxxxxx>
>
>> Hi,
>>
>> Launchpad does not send out e-mails to the list when new blueprints
>> (feature requests, design ideas) are created  like it does when new bugs are
>> reported. Although its perfectly possible to follow the blueprints by
>> visiting the launchpad pages I have a feeling that we are loosing out on a
>> lot of important discussions here.
>>
>> So here is a reminder to those of you that are interested in following and
>> influencing the DHIS development that you should monitor changes to this
>> page:
>> https://blueprints.launchpad.net/dhis2
>>
>> If blueprints are administered properly (release series and milestonse
>> being set) this page gives a more roadmap like view:
>> https://blueprints.launchpad.net/dhis2/trunk/+specs?show=all
>> (Especially if you click two times on the Milestone column heading to sort
>> by milestone.)
>>
>> I feel some of the more important blueprints should be discussed on the
>> list and not only using the blueprint window in launchpad, what do others
>> think about this?
>> Maybe a good practice could be to write an e-mail to the list after
>> registering a blueprint, to let people know about it and invite to a list
>> discussion/feedback round?
>> I guess not all blueprints are worth discussing, but then again, it's a
>> big heterogeneous network and we do not really know what all the others are
>> interested in either...
>>
>> best regards,
>> Ola Hodne Titlestad
>> HISP
>> University of Oslo
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> More help   : https://help.launchpad.net/ListHelp
>
>

References