Re: [Gnumed-devel] pre release todo

[Ian Haywood]

J Busser wrote:

> We have so far 2 public lists (gnumed-devel, gnumed-update) and 1 
> private (gnumed-announce)
>
> gnumed-devel (81 subscribed)
*eighty-one*!! Who the hell are these people?!
> "information exchange for gnumed developers and contributors"
>
> gnumed-update
> "This list informs about relevant file updates within the gnumed project"
> - is this meant to inform about updates to CVS
> - are file updates *other* than CVS (like binaries) proposed to be 
> advertised
>    on gnumed-announce?
yes
> - this list is accumulating (mostly) spam, see
> http://lists.gnu.org/archive/html/gnumed-update/2005-04/index.html
> ... shall I re-classify it as "private"? Will that cause anything we 
> need to bounce?
It distributes regular reports on CVS changes which are autogenerated
by my account on gnu.org, personally I find this quite useful. I didn't
know about the spam (my filter is working)
It would be good to stop outsiders from posting (is that want "private" means?)
> gnumed-announce
> - announcements regarding the gnumed project (low volume)
When we have releasable versions we will use this.
> > gnumed-users
When we have end-users, sure ....
> > gnumed-documentation
> > gnumed-public-relations
gnumed-doc and gnumed-advocacy would be the customary names.

> Is it expected that gnumed-devel members will direct certain postings to 
> the new list INSTEAD of onto gnumed-devel? Or do we expect that they 
> will continue to post everything to gnumed-devel? So that the new lists 
> would only be of interest to people not already on gnumed-devel?
Different lists are useful for big projects where there is a clear separation
between users and developers. Gnumed has no "users" as it's not usable in its 
own right,
so everyone who is involved in any way is a developer (although not necessary a 
coder),
so IMHO we have no current need for any more lists.

Ian

signature.asc
Description: OpenPGP digital signature