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
(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
We should follow Carl Fogel’s advice and follow discussion only on mailing lists… Blueprints could act as outcome of those discussion or to summarize discussions
… And there are better ways to see the roadmap than what launchpad is showing us
···
Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme
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
(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
We should follow Carl Fogel’s advice 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…
···
On Thu, May 14, 2009 at 8:39 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme
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
(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
Never read Carl Fogel's advice before but I have to find myself
agreeing with him. I am a mailing list person.
Still Ola is right - there is a whole lot of stuff happening on
launchpad and elsewhere which we need to track. One approach is an
ancient one adopted by the tcl project (still the greatest little
programming language ever invented) where some one of us takes the
responsibility once a week to write a short summary of DHIS2
happenings to this list - Page not found. Any new blueprints.
Changes to existing ones. Summary of interesting discussions. Great
bugs which were squashed etc. The tcl community have weekly archives
going back to 1998 of messages with a subject line "Tcl-URL". It has
worked very well and has been copied by many projects.
The idea is that someone does it for a month or two then passes on the baton.
Any takers? I will give it a go if no one else wants to, though maybe
someone who has been with the project longer would do it better.
We should follow Carl Fogel's advice and follow discussion only on mailing
lists... Blueprints could act as outcome of those discussion or to summarize
discussions
... And there are better ways to see the roadmap than what launchpad is
showing us
---
Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme
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
I like this idea Bob. Lars has tried something similar with the Development Update mail, but that is not frequent enough and I haven’t seen it for a while.
We are quite poor at communicating new ideas (blueprints), features implemented (commit mails so not always give the full picture), work in progress etc and this has consequences around the network. People are facing the same problems in different countries and often end of with duplicating efforts due to poor communication across borders. I definely support this weekly summary e-mail and think you’re an excellent candidate Bob to get this off the ground. If you miss out on something I am sure others can fill in with replies to the summary mail, so no need to worry about not being in the project long enough. Great initiative!
OK. I will attempt a weekly round up. Because of the relatively high
frequency the content will be short mostly consisting of links. I
will use Cameron Laird's example here - http://groups.google.com/group/comp.lang.tcl/msg/9986800b92ce96be - as
my guide. Notice there are only 8 news items.
Look out for a mail with subject line DHIS2-URL! sometime between
Sunday and Monday.
Regards
Bob
···
2009/5/14 Ola Hodne Titlestad <olati@ifi.uio.no>:
On Thu, May 14, 2009 at 9:12 PM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:
Never read Carl Fogel's advice before but I have to find myself
agreeing with him. I am a mailing list person.
Still Ola is right - there is a whole lot of stuff happening on
launchpad and elsewhere which we need to track. One approach is an
ancient one adopted by the tcl project (still the greatest little
programming language ever invented) where some one of us takes the
responsibility once a week to write a short summary of DHIS2
happenings to this list - Page not found. Any new blueprints.
Changes to existing ones. Summary of interesting discussions. Great
bugs which were squashed etc. The tcl community have weekly archives
going back to 1998 of messages with a subject line "Tcl-URL". It has
worked very well and has been copied by many projects.
The idea is that someone does it for a month or two then passes on the
baton.
Any takers? I will give it a go if no one else wants to, though maybe
someone who has been with the project longer would do it better.
I like this idea Bob. Lars has tried something similar with the Development
Update mail, but that is not frequent enough and I haven't seen it for a
while.
We are quite poor at communicating new ideas (blueprints), features
implemented (commit mails so not always give the full picture), work in
progress etc and this has consequences around the network. People are facing
the same problems in different countries and often end of with duplicating
efforts due to poor communication across borders. I definely support this
weekly summary e-mail and think you're an excellent candidate Bob to get
this off the ground. If you miss out on something I am sure others can fill
in with replies to the summary mail, so no need to worry about not being in
the project long enough. Great initiative!
Ola
---------
Regards
Bob
2009/5/14 Saptarshi Purkayastha <sunbiz@gmail.com>:
> We should follow Carl Fogel's advice and follow discussion only on
> mailing
> lists... Blueprints could act as outcome of those discussion or to
> summarize
> discussions
>
> ... And there are better ways to see the roadmap than what launchpad is
> showing us
>
> ---
> 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@ifi.uio.no>
>>
>> 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
>> Post to : dhis2-devs@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help : https://help.launchpad.net/ListHelp
>
>
OK but go easy - this is meant to be a weekly thing not an annual! By
all means put your implementation stories on the wiki, then send an
email to the list which I will probably pick up on - or send me a mail
directly with the link.
OK. I will attempt a weekly round up. Because of the relatively high
frequency the content will be short mostly consisting of links. I
will use Cameron Laird's example here - http://groups.google.com/group/comp.lang.tcl/msg/9986800b92ce96be - as
my guide. Notice there are only 8 news items.
Look out for a mail with subject line DHIS2-URL! sometime between
Sunday and Monday.
Regards
Bob
2009/5/14 Ola Hodne Titlestad <olati@ifi.uio.no>:
> On Thu, May 14, 2009 at 9:12 PM, Bob Jolliffe <bobjolliffe@gmail.com> >> > wrote:
>>
>> Never read Carl Fogel's advice before but I have to find myself
>> agreeing with him. I am a mailing list person.
>>
>> Still Ola is right - there is a whole lot of stuff happening on
>> launchpad and elsewhere which we need to track. One approach is an
>> ancient one adopted by the tcl project (still the greatest little
>> programming language ever invented) where some one of us takes the
>> responsibility once a week to write a short summary of DHIS2
>> happenings to this list - Page not found. Any new blueprints.
>> Changes to existing ones. Summary of interesting discussions. Great
>> bugs which were squashed etc. The tcl community have weekly archives
>> going back to 1998 of messages with a subject line "Tcl-URL". It has
>> worked very well and has been copied by many projects.
>>
>> The idea is that someone does it for a month or two then passes on the
>> baton.
>>
>> Any takers? I will give it a go if no one else wants to, though maybe
>> someone who has been with the project longer would do it better.
>
> I like this idea Bob. Lars has tried something similar with the
> Development
> Update mail, but that is not frequent enough and I haven't seen it for a
> while.
> We are quite poor at communicating new ideas (blueprints), features
> implemented (commit mails so not always give the full picture), work in
> progress etc and this has consequences around the network. People are
> facing
> the same problems in different countries and often end of with
> duplicating
> efforts due to poor communication across borders. I definely support
> this
> weekly summary e-mail and think you're an excellent candidate Bob to get
> this off the ground. If you miss out on something I am sure others can
> fill
> in with replies to the summary mail, so no need to worry about not being
> in
> the project long enough. Great initiative!
>
> Ola
> ---------
>
>
>>
>> Regards
>> Bob
>>
>> 2009/5/14 Saptarshi Purkayastha <sunbiz@gmail.com>:
>> > We should follow Carl Fogel's advice and follow discussion only on
>> > mailing
>> > lists... Blueprints could act as outcome of those discussion or to
>> > summarize
>> > discussions
>> >
>> > ... And there are better ways to see the roadmap than what launchpad
>> > is
>> > showing us
>> >
>> > ---
>> > 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@ifi.uio.no>
>> >>
>> >> 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
>> >> Post to : dhis2-devs@lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~dhis2-devs
>> >> More help : https://help.launchpad.net/ListHelp
>> >>
>> >
>> >
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~dhis2-devs
>> > Post to : dhis2-devs@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~dhis2-devs
>> > More help : https://help.launchpad.net/ListHelp
>> >
>> >
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to : dhis2-devs@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help : https://help.launchpad.net/ListHelp
>
>
