Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id q8QEJLoq007842 for ; Wed, 26 Sep 2012 16:19:22 +0200 Received: (qmail 2719 invoked by alias); 26 Sep 2012 14:19:15 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 26 Sep 2012 14:19:15 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx022) with SMTP; 26 Sep 2012 16:19:15 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id q8QEC9SD008522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Sep 2012 16:12:10 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.8/8.13.1) with ESMTP id q8QDqepC010144; Wed, 26 Sep 2012 16:12:09 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 3429354 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 26 Sep 2012 16:12:09 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.8/8.13.1) with ESMTP id q8QEC87O008951 for ; Wed, 26 Sep 2012 16:12:08 +0200 Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id q8QEBvhn008374 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Wed, 26 Sep 2012 16:12:00 +0200 Received: by vcqp16 with SMTP id p16so1045524vcq.22 for ; Wed, 26 Sep 2012 07:11:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.16.9 with SMTP id m9mr296838vca.72.1348668716850; Wed, 26 Sep 2012 07:11:56 -0700 (PDT) Received: by 10.220.112.145 with HTTP; Wed, 26 Sep 2012 07:11:56 -0700 (PDT) References: <504FAAC6.8000605@morningstar2.co.uk> <50620A53.4030600@morningstar2.co.uk> <5062E92E.4080400@residenset.net> <5062FF94.5040108@morningstar2.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id q8QEC87O008952 Message-ID: Date: Wed, 26 Sep 2012 16:11:56 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Bruno Le Floch Subject: Re: Managing/tracking module prefixes To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <5062FF94.5040108@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=5D7Q89H36p6bhYZPhtRQLBki23VYO/U3y8hbir4Lb1B3hbEa6YC9P1aGU02tfsOAyLrV/ a7Vopyy1zyWVPYrlNbe0p+DObqeEatt12uwtqYruP9sXRZFKAGvysHr+PVONY4d0vsH7FWjmyZEQ 8L9sCRo5Gj3T+cjnPPjNw8PAJI=V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 7159 On 9/26/12, Joseph Wright wrote: > On 26/09/2012 12:38, Lars Hellström wrote: >> I'd suggest that you initially set up a dedicated e-mail address which >> redirects to LATEX-L. >> >> The rationale for the latter is that in order to establish a convention, >> it is seldom sufficient to just post the rules and set up the >> administrative machinery; one must also raise communal awareness of the >> convention. One of the most effective ways of doing this is to let >> members of the community observe how others are following the >> convention, but that won't happen if traffic goes to a list only seen by >> team members. >> >> The point of having a dedicated email address is that if it later turns >> out that LATEX-L is getting flooded by this (IMHO unlikely, especially >> in view of how much LATEX-L traffic historically varies anyway) then you >> can change the forward to the team list. Or alternatively switch to some >> manner of digest format. Having a separate email address also simplifies >> regularising the postings before forwarding them, e.g. using a specific >> Subject heading to make it easier to search for these messages later. >> >> Lars Hellström > > All sounds reasonable, with the only issue being I don't actually have > the ability to do anything about it :-) (I'll need to talk to Rainer). > > Assuming it is feasible, what would be a sensible address? My first > thought is > > modules@latex-project.org > > or > > module-prefixes@latex-project.org > > An alternative would be to go with the plan that messages are sent to > the team list (which already exists), and that we (I) post a formalised > message to LaTeX-L before adding to the master list, in a similar way to > how CTAN 'new package' announcements are made. Something like > > *Subject* Module prefix registration: X > > The LaTeX3 module prefix X was registered on with the > following details. > > Module name: ... > ... > > The downside here is that the team (or at least some of us) get the > messages twice. I think that's probably survivable :-) > -- > Joseph Wright The drawback of transferring manually is that one of us has to do it :). I otherwise agree with what you said. Bruno