LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Wed, 26 Sep 2012 21:18:10 +0100
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID:
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
Content-Type:
text/plain; charset=ISO-8859-1
From:
Joseph Wright <[log in to unmask]>
Parts/Attachments:
text/plain (31 lines)
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 <date> 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

ATOM RSS1 RSS2