lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New LilyPond Spanish Users list at GNU


From: John Mandereau
Subject: Re: New LilyPond Spanish Users list at GNU
Date: Sat, 26 Dec 2009 23:26:44 +0100

Le samedi 26 décembre 2009 à 14:13 -0600, David R. Linn a écrit :
> As I recall, the "plan" in the migration from the GMP lists to the
> LilyPond lists was to annnounce the new lists and deprecate the old
> lists in one stable release and kill off the old lists with the
> *following* stable release.  I actually monitored the old lists for a
> couple of years after the official end-of-life because I know that
> someone people work with pretty old software.

Did the old and new lists had exactly the same purpose?  This would be
the case for lilyond-user-fr and lilypond-fr.


>   I don't have any
> responsibility for -fr list (or administrative access to it) but I
> suggest that any renaming, if any occurs, be accomplished by a similar
> plan.

If the old archives could be imported into those of the new list
lilypond-fr, this would compensate half of the pain of renaming the list
by creating a new one; this is not more complicated than copying a few
mbox files and generating the archive manually using MHonArc, but I'm
not sure if we can expect this from gnu.org lists admins.  I just resent
my two-years old request for upgrading MHonArc on lists.gnu.org to
address@hidden but this time I also set address@hidden as a
recipient; if I get no reply within one month, I'll conclude than we
cannot make any custom request to the administrators.

For the other half, I thought that setting up an email alias would be
simpler or cleaner than creating a new list, but it may not be so if
email aliases are only exceptionally granted by gnu.org email server
admins.  Renaming the list would not remove the problem of moving the
archives, anyway.

Finally, I'm for renaming lilypond-user-fr into lilypond-fr anyway, but
if it's not possible to move and/or copy old archives and generate HTML
archives with correct encoding, we'll generate them ourselves :-/

Best,
John

Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée


reply via email to

[Prev in Thread] Current Thread [Next in Thread]