[GRASS-PSC] Re: GRASS PSC
smitch at mac.com
Sat Oct 28 17:18:36 EDT 2006
I see the value of both approaches but I can be happy with either.
I originally stated that I favoured a separate list. I was thinking
that there would sometimes be discussion amongst ourselves that we
wouldn't necessarily want to have automatically broadcast to everyone
on the dev list, not for reasons of secrecy or anything like that,
just that sometimes there might be things we're working out that we
want to work out before bringing in the whole devlist. We may feel
more free to advance ideas or questions if we know that it won't go
to a huge number of inboxes (perhaps I'm oversensitive to that due to
my own out of control inbox). At the same time, I thought that the
fact that the list archives would be freely available would make the
discussion / process open, and that a lot of the "real" discussion
would still take place on dev- and/or user-list. It can even go
further, whereby we make the potential separate list still freely
subscribable, whereby PSC members are definitely subscribed, but
others can sign themselves up to in order to monitor (and contribute
to?) the discussion.
On the other hand, if there is a demand to keep the discussion in the
most open forum, and/or people don't like further segmenting
discussion into an ever increasing number of mailing lists, agreeing
to do things in devlist or devlist/userlist/wiki/IRC is fine with me
too. I agree that any system of having a subject prefix is great in
theory but hard to keep consistently applied in practice.
I guess I still slightly favour the idea of having a separate list,
but can be convinced otherwise. I wonder, though - if there is no
desire for something slightly separate from the devlist for SOME
communications, why aren't we having this email exchange on the list?
On 28 Oct 2006, at 11:02, Michael Barton wrote:
> I'm not strongly opposed to a dedicated and see the pragmatic
> value, only
> trying to be sensitive to the larger community.
> As someone pointed out, the archives could be read by all (I
> assume) and so
> it wouldn't be a secret list at all.
> Michael Barton, Professor of Anthropology
> School of Human Evolution & Social Change
> Center for Social Dynamics & Complexity
> Arizona State University
> phone: 480-965-6213
> fax: 480-965-7671
> www: http://www.public.asu.edu/~cmbarton
>> From: Markus Neteler <neteler.osgeo at gmail.com>
>> Date: Sat, 28 Oct 2006 16:34:09 +0200
>> To: Maciej Sieczka <tutey at o2.pl>
>> Cc: <debeaudette at ucdavis.edu>, Michael Barton
>> <michael.barton at asu.edu>, Frank
>> Warmerdam <warmerdam at pobox.com>, Hamish <hamish_nospam at yahoo.com>,
>> Massimiliano Cannata <massimiliano.cannata at supsi.ch>, Brad Douglas
>> <rez at touchofmadness.com>, Paul Kelly <paul-
>> grass at stjohnspoint.co.uk>, Helena
>> Mitasova <hmitaso at unity.ncsu.edu>, Scott Mitchell <smitch at mac.com>
>> Subject: Re: GRASS PSC
>> On 10/28/06, Maciej Sieczka <tutey at o2.pl> wrote:
>>> Dylan Beaudette wrote:
>>>>>> @GRASS-PSC: should I create a dedicated mailing list to get
>>>> +1 on Michael's comments. Having the custom subject line will
>>>> help people to
>>>> keep messages filed locally, and an alternate archive will increase
>>> The idea is interesting. I only wonder if this is a robust
>>> approach -
>>> we will occasionaly forget to add the custom subject element (eg.
>>> "PSC"). But the discussion will start anyway, making it to late to
>>> re-send another message with a corrected subject. And such GRASS PSC
>>> threads will be impossible to be found and copied into the dedicated
>>> GRASS PSC archive only by their subject.
>>> How about a dedicated PSC mailing list - automatically forwared to
>>> grass-dev? Then we have both a dedicated archive, only with PSC
>>> threads, and the discussion is still open for other GRASS folks.
>> While automated forwarding of PSC mailing list mails is easy, how
>> to treat responses from the community? This would require a
>> (if you generally open, you get tons of spam or unrelated stuff).
>> weblist AT grass.itc.it *is* not restricted and 'bogofilter' works
>> well to filter
>> it, I don't know if this would work equally well for a PSC list.
>> Well, that's probably a more technical question.
>> The general question is: dedicated list or not. It seems that we have
>> contrary opinions at the moment.
More information about the grass-psc