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 q8QKKNXc020472 for ; Wed, 26 Sep 2012 22:20:24 +0200 Received: (qmail 15303 invoked by alias); 26 Sep 2012 20:20:18 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 26 Sep 2012 20:20:18 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx064) with SMTP; 26 Sep 2012 22:20:18 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id q8QKIMno023523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Sep 2012 22:18:22 +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 q8QEpCuQ010144; Wed, 26 Sep 2012 22:18:21 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 3431555 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 26 Sep 2012 22:18:21 +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 q8QKILPZ005475 for ; Wed, 26 Sep 2012 22:18:21 +0200 Received: from smtp.demon.co.uk (mdfmta009.mxout.tbr.inty.net [91.221.168.50]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id q8QKIBJA001227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 26 Sep 2012 22:18:14 +0200 Received: from mdfmta009.tbr.inty.net (unknown [127.0.0.1]) by mdfmta009.tbr.inty.net (Postfix) with ESMTP id DAFF4384081 for ; Wed, 26 Sep 2012 21:18:10 +0100 (BST) Received: from mdfmta009.tbr.inty.net (unknown [127.0.0.1]) by mdfmta009.tbr.inty.net (Postfix) with ESMTP id B8787384080 for ; Wed, 26 Sep 2012 21:18:10 +0100 (BST) Received: from palladium.local (unknown [81.149.193.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mdfmta009.tbr.inty.net (Postfix) with ESMTP for ; Wed, 26 Sep 2012 21:18:10 +0100 (BST) User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 References: <504FAAC6.8000605@morningstar2.co.uk> <50620A53.4030600@morningstar2.co.uk> <5062E92E.4080400@residenset.net> <5062FF94.5040108@morningstar2.co.uk> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-MDF-HostID: 4 Message-ID: <50636302.7040703@morningstar2.co.uk> Date: Wed, 26 Sep 2012 21:18:10 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: Managing/tracking module prefixes To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Sender is in whitelist: joseph.wright@MORNINGSTAR2.CO.UK); Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnBi0P5cROEGjO+pG7NAH/K+tf9SrVFtpLrKONl 2T9EL4W4U4jgzLbnCcGpk1z/zwmKT/K1fv3lD0=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: 7160 On 26/09/2012 15:11, Bruno Le Floch wrote: >> 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 Well as currently-proposed someone from the team will have to add each prefix to the 'master list' in any case. So this would simply be an associated task. -- Joseph Wright