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 q8QDGOHr017418 for ; Wed, 26 Sep 2012 15:16:25 +0200 Received: (qmail 8894 invoked by alias); 26 Sep 2012 13:16:19 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 26 Sep 2012 13:16:18 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx030) with SMTP; 26 Sep 2012 15:16: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 q8QDEP9S004627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Sep 2012 15:14:25 +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 q8Q9XQCY010144; Wed, 26 Sep 2012 15:14:24 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 3422707 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 26 Sep 2012 15:14:24 +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 q8QDEO5C012414 for ; Wed, 26 Sep 2012 15:14:24 +0200 Received: from smtp.demon.co.uk (mdfmta005.mxout.tch.inty.net [91.221.169.46]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id q8QDDvHn015119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 26 Sep 2012 15:14:00 +0200 Received: from mdfmta005.tch.inty.net (unknown [127.0.0.1]) by mdfmta005.tch.inty.net (Postfix) with ESMTP id 5B62318C2E0 for ; Wed, 26 Sep 2012 14:13:57 +0100 (BST) Received: from mdfmta005.tch.inty.net (unknown [127.0.0.1]) by mdfmta005.tch.inty.net (Postfix) with ESMTP id 3C58E18C0A5 for ; Wed, 26 Sep 2012 14:13:57 +0100 (BST) Received: from [139.222.113.143] (unknown [139.222.113.143]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mdfmta005.tch.inty.net (Postfix) with ESMTP for ; Wed, 26 Sep 2012 14:13:57 +0100 (BST) User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; 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> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MDF-HostID: 18 Message-ID: <5062FF94.5040108@morningstar2.co.uk> Date: Wed, 26 Sep 2012 14:13:56 +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: <5062E92E.4080400@residenset.net> 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: 7158 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