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
Show All Mail Headers

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

Print Reply
Subject:
From:
Joseph Wright <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Wed, 26 Sep 2012 14:01:52 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
On 26/09/2012 10:05, Bruno Le Floch wrote:
>> That being the case, the immediate questions are what to have in such a
>> register and how to make contact to have material added. On the details,
>> things which come to mind are
>>
>>  - Prefix itself!
>>  - Contact details: I guess a publicly-recordable e-mail address is a
>>    must, plus a person or group name
>>  - Module name (may be different from the prefix)
>>  - Homepage for project
>>  - Issue database/code repo locations
> 
> Several prefixes can be attached to the same project (or even the same
> module).  So I'd say
> 
> - Project name (e.g., l3kernel)
> - Prefixes (e.g., int, expl, box, hbox)
> - Modules (or files?)
> - Contact details
> - Homepage
> - Issue database
> - Code repo

The reason I listed prefix first was that this is the 'primary key' in
the list. My thinking was that you have two likely use cases:

 1) Is prefix X available?
 2) Who do I contact about a problem with a function which has prefix X?

Both of these need a list by prefix, not by project or whatever. Of
course that does mean some duplication, but I'd hope it's manageable in
a simple flat file listing.

> If any of the latter 4 are missing, it shouldn't be a problem, as long
> as the maintainer is contactable, directly or indirectly.

Provided there is some contact method, we should be okay. I'd imagine
most people will have at least an e-mail address.
--
Joseph Wright

ATOM RSS1 RSS2