since the name of this mailing list 'grass5' seems to become
inappropriate, I suggest a renaming of development mailing list
to
grass-dev@grass.itc.it
I can define an alias to keep the current grass5@grass.itc.it
address working.
Background:
During this month the grass.itc.it server will be
replaced with a new machine and I'll have to
setup all services, mailing lists etc from scratch.
This includes a migration to a recent Mailman version.
I am not sure yet if I should rebuild it from scratch
of if there is any chance to smoothly migrate from
Mailman 1.x to 2.x (to preserve the archive links).
All other updates will be less significant to the
GRASS community, just some work to set up things here.
If making cahnges, how about bugzilla? For NeXTGRASS
Yay, and, please, announce possible downtime - just in case
My 2c.
Maris.
2006/1/3, Markus Neteler <neteler@itc.it>:
Dear all,
since the name of this mailing list 'grass5' seems to become
inappropriate, I suggest a renaming of development mailing list
to
grass-dev@grass.itc.it
I can define an alias to keep the current grass5@grass.itc.it
address working.
Background:
During this month the grass.itc.it server will be
replaced with a new machine and I'll have to
setup all services, mailing lists etc from scratch.
This includes a migration to a recent Mailman version.
I am not sure yet if I should rebuild it from scratch
of if there is any chance to smoothly migrate from
Mailman 1.x to 2.x (to preserve the archive links).
All other updates will be less significant to the
GRASS community, just some work to set up things here.
I agree. Would all our current subscriptions be ported or will we need to do
something?
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402
From: Markus Neteler <neteler@itc.it>
Date: Tue, 3 Jan 2006 18:07:41 +0100
To: grass developers list <grass5@grass.itc.it>
Subject: [GRASS5] Rename of development mailing list?
Dear all,
since the name of this mailing list 'grass5' seems to become
inappropriate, I suggest a renaming of development mailing list
to
grass-dev@grass.itc.it
I can define an alias to keep the current grass5@grass.itc.it
address working.
Background:
During this month the grass.itc.it server will be
replaced with a new machine and I'll have to
setup all services, mailing lists etc from scratch.
This includes a migration to a recent Mailman version.
I am not sure yet if I should rebuild it from scratch
of if there is any chance to smoothly migrate from
Mailman 1.x to 2.x (to preserve the archive links).
All other updates will be less significant to the
GRASS community, just some work to set up things here.
On Tue, Jan 03, 2006 at 07:32:37PM +0200, M?ris Narti?s wrote:
If making cahnges, how about bugzilla? For NeXTGRASS
This is something to discuss. Bernhard already proposed
some alternatives.
Yay, and, please, announce possible downtime - just in case
Absolutely. But it will take some days/weeks since I cannot
dedicate too much time on this. Once the new machine is
functional (currently set up with different name), we go
for the migration.
Markus
My 2c.
Maris.
2006/1/3, Markus Neteler <neteler@itc.it>:
> Dear all,
>
> since the name of this mailing list 'grass5' seems to become
> inappropriate, I suggest a renaming of development mailing list
> to
> grass-dev@grass.itc.it
>
> I can define an alias to keep the current grass5@grass.itc.it
> address working.
>
> Background:
> During this month the grass.itc.it server will be
> replaced with a new machine and I'll have to
> setup all services, mailing lists etc from scratch.
> This includes a migration to a recent Mailman version.
> I am not sure yet if I should rebuild it from scratch
> of if there is any chance to smoothly migrate from
> Mailman 1.x to 2.x (to preserve the archive links).
>
> All other updates will be less significant to the
> GRASS community, just some work to set up things here.
>
> Any opinions?
>
> Markus
>
> _______________________________________________
> grass5 mailing list
> grass5@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass5
>
--
Markus Neteler <neteler itc it> http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy
If all the list server stuff is going to be created from scratch, how about renaming other lists as well with a consistent naming scheme?
ie grass-users@grass.itc.it
...
On Jan 3, 2006, at 11:07 AM, Markus Neteler wrote:
Dear all,
since the name of this mailing list 'grass5' seems to become
inappropriate, I suggest a renaming of development mailing list
to
grass-dev@grass.itc.it
I can define an alias to keep the current grass5@grass.itc.it
address working.
Background:
During this month the grass.itc.it server will be
replaced with a new machine and I'll have to
setup all services, mailing lists etc from scratch.
This includes a migration to a recent Mailman version.
I am not sure yet if I should rebuild it from scratch
of if there is any chance to smoothly migrate from
Mailman 1.x to 2.x (to preserve the archive links).
All other updates will be less significant to the
GRASS community, just some work to set up things here.
On Tue, Jan 03, 2006 at 12:26:13PM -0600, William Kyngesburye wrote:
If all the list server stuff is going to be created from scratch, how
about renaming other lists as well with a consistent naming scheme?
ie grass-users@grass.itc.it
...
Sounds good, but in this case we have to decide what to
do with Baylor. The user list is running there for a couple
a years, we don't have access from here.
Of course we could simply migrate all users to a list
here (maybe that's considered to be unfriendly?). So
far I don't know whom to contact at Baylor, all questions
to the list admin there remained unanswered.
Technically we can easily move to our server.
since the name of this mailing list 'grass5' seems to become
inappropriate, I suggest a renaming of development mailing list
to
grass-dev@grass.itc.it
I can define an alias to keep the current grass5@grass.itc.it
address working.
I wondered about that, when I first signed up. At first I thought grass5
was some old dev list (; IMO a good change. Also while you are at it,
perhaps make the list add a reply-to header that points back to the
list? Was this already discussed earlier and you want it not to
auto-reply to the list? In that case forget about my question (;
Also having all lists on the same server with the same ML manager is a
good idea.
On Tue, Jan 03, 2006 at 10:25:28PM +0200, Wolf Bergenheim wrote:
On 03/01/06 19:07, Markus Neteler wrote:
> Dear all,
>
> since the name of this mailing list 'grass5' seems to become
> inappropriate, I suggest a renaming of development mailing list
> to
> grass-dev@grass.itc.it
>
> I can define an alias to keep the current grass5@grass.itc.it
> address working.
I wondered about that, when I first signed up. At first I thought grass5
was some old dev list (; IMO a good change.
Good to get so much positive feedback
Also while you are at it,
perhaps make the list add a reply-to header that points back to the
list? Was this already discussed earlier and you want it not to
auto-reply to the list? In that case forget about my question (;
This is unfortunate and not desired. There have been too many accidents
where people sent a privat message to a list. Seek in the GRASS, PROJ
GDAL archives for examples...
All (good) mail user agents have a "reply all" button or
"group reply" key which solved the problem.
Also having all lists on the same server with the same ML manager is a
good idea.
Probably yes.
BTW:
Along with the change I'll have "bogofilter" to filter the spam for
*all* lists, not only for mails coming from the bugtracker. This
program works really great.
> Also while you are at it,
> perhaps make the list add a reply-to header that points back to the
> list? Was this already discussed earlier and you want it not to
> auto-reply to the list? In that case forget about my question (;
This is unfortunate and not desired. There have been too many accidents
where people sent a privat message to a list. Seek in the GRASS, PROJ
GDAL archives for examples...
All (good) mail user agents have a "reply all" button or
"group reply" key which solved the problem.
Yea, and then You receive at least 2 copies of mail - one from list
and one direct
I always press "reply to all" and then manually clear all other
addresses except lists address. That sucks.
There always will be users who after reading "Do not run 'rm -Rf /' !"
will run that command and there is nothing to do about it.
Some time a go one of KDE devs (I read it on planetkde) posted story
about security MS Windows vs KDE/Linux. This story contained url with
text "Do not open with Microsoft Internet Explorer" (or similar), cuz
opened site installed viruses and spy ware. After this post there
where lots of unhappy IE user comments about infecting they PCs. What
can You do to protect users from themselves?
On Wed, Jan 04, 2006 at 11:07:49AM +0200, M?ris Narti?s wrote:
> > Also while you are at it,
> > perhaps make the list add a reply-to header that points back to the
> > list? Was this already discussed earlier and you want it not to
> > auto-reply to the list? In that case forget about my question (;
>
> This is unfortunate and not desired. There have been too many accidents
> where people sent a privat message to a list. Seek in the GRASS, PROJ
> GDAL archives for examples...
> All (good) mail user agents have a "reply all" button or
> "group reply" key which solved the problem.
Yea, and then You receive at least 2 copies of mail - one from list
and one direct
I always press "reply to all" and then manually clear all other
addresses except lists address. That sucks.
Then use for example "mutt" [1] and press "l" (respond to list).
Only one mail will be sent.
But: I read many lists in digest mode. If I receive a message twice
(which sucks for you), the direct message arrives immediately in my
mailbox while the digest arrives at the end of the day (or even later).
This makes me responsive for messages addressing me directly while I
can calm down for messages where I am not necessarily involved.
There always will be users who after reading "Do not run 'rm -Rf /' !"
will run that command and there is nothing to do about it.
Some time a go one of KDE devs (I read it on planetkde) posted story
about security MS Windows vs KDE/Linux. This story contained url with
text "Do not open with Microsoft Internet Explorer" (or similar), cuz
opened site installed viruses and spy ware. After this post there
where lots of unhappy IE user comments about infecting they PCs. What
can You do to protect users from themselves?
My 2c.
Maris.
Look: I have seen such things happen to often, why enforcing personal
problems? I don't want to send pointers here, but I got even a request
to remove a message from the GRASS User list archive where a person
accidentially send a personal family/job problem to hundreds of GRASS
subscribers. This person ran into severe troubles later. This rarely
happens with "reply to author" settings as they are now.
> since the name of this mailing list 'grass5' seems to become
> inappropriate, I suggest a renaming of development mailing list
> to
> grass-dev@grass.itc.it
>
> I can define an alias to keep the current grass5@grass.itc.it
> address working.
I wondered about that, when I first signed up. At first I thought grass5
was some old dev list (; IMO a good change. Also while you are at it,
perhaps make the list add a reply-to header that points back to the
list? Was this already discussed earlier and you want it not to
auto-reply to the list? In that case forget about my question (;
It's been discussed in the past.
In short, the Reply-To header "belongs" to the sender. It's meant for
the case when the sender doesn't want personal replies to go to their
From address.
If the list sets the Reply-To address, there's no way to determine how
to reply to the sender personally (using the From address is incorrect
when a Reply-To header is present).
Users who don't want personal replies can always manually set the
Reply-To address to the list.
It is not a good thing that a critical part of our infrastructure is
outside our control. At minimum, when the new server is up and running
and if grass5 is migrated to grass-devel@grass.itc.it, a shadow
grass-users@grass.itc.it list should be set up "just in case".
I imagine when the Baylor server eventually dies one day they might not
bother to put grasslist back up in any sort of hurry, leaving us in a
lurch.
On the other hand, there is great value in continuity & delegation.
On Tue, Jan 17, 2006 at 11:02:45PM +1300, Hamish wrote:
re. grasslist@baylor.edu
It is not a good thing that a critical part of our infrastructure is
outside our control.
I agree.
At minimum, when the new server is up and running
and if grass5 is migrated to grass-devel@grass.itc.it, a shadow
grass-users@grass.itc.it list should be set up "just in case".
To carry over the list from Baylor to grass.itc.it is easily
done (in a few minutes, I just have to insert the list of
receipients from Baylor into our mailman).
I imagine when the Baylor server eventually dies one day they might not
bother to put grasslist back up in any sort of hurry, leaving us in a
lurch.
On the other hand, there is great value in continuity & delegation.
Well, they never created an archive. That's why I created the shadow
list here and re-created the archive from usenet messages and other
sources.
Why not make a poll here? If users agree, we move it here.
Postings still sent to Baylor will arrive here in any case as
the Mailman here is subscribed as user to the Baylor list
It is not a good thing that a critical part of our infrastructure is
outside our control.
I agree.
..
To carry over the list from Baylor to grass.itc.it is easily
done (in a few minutes, I just have to insert the list of
receipients from Baylor into our mailman).
..
Why not make a poll here?
For my part, as long as they work I don't really care what the mailing
lists are called, one way or the other.
On Tue, Jan 17, 2006 at 11:55:11PM +1300, Hamish wrote:
>> re. grasslist@baylor.edu
>>
>> It is not a good thing that a critical part of our infrastructure is
>> outside our control.
>
> I agree.
..
> To carry over the list from Baylor to grass.itc.it is easily
> done (in a few minutes, I just have to insert the list of
> receipients from Baylor into our mailman).
..
> Why not make a poll here?
For my part, as long as they work I don't really care what the mailing
lists are called, one way or the other.
I meant: poll to decide whether to move the user list to grass.itc.it
Why not make a poll here? If users agree, we move it here.
Postings still sent to Baylor will arrive here in any case as
the Mailman here is subscribed as user to the Baylor list
As long as you can transfer the subscriptions I'm all for it. (Yes I
know I'm lazy, but there is always the saying "Don't fix what ain't broken")
