MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <LISTSERV%200809221214001575.01B1@LISTSERV.UNI-HEIDELBERG.DE>
Message-ID:  <27990a880809220403y7c6fcca7m4a3a965174a317de@mail.gmail.com>
Date:         Mon, 22 Sep 2008 20:33:40 +0930
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: Key management for LaTeX3 ("l3keys")
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <LISTSERV%200809221214001575.01B1@LISTSERV.UNI-HEIDELBERG.DE>
Precedence: list
Status: R

On Mon, Sep 22, 2008 at 7:44 PM, Joseph Wright
<joseph.wright@morningstar2.co.uk> wrote:
> On Sat, 20 Sep 2008 17:17:23 +0930, Will Robertson <wspr81@GMAIL.COM> wrote:
>
>> Can I recommend that you start up a (say) GitHub repository[*] for
>> this code to make it easier to (a) track changes in it, and (b) for
>> *me* to be able to keep your code in sync with changes that we will
>> end up making to the expl3 repository?
>
> I'd be keen to know how others see this.  My aim in quickly writing l3keys
> was to provide a starting point for discussion here on how keys might be
> managed in LaTeX3.

True. I can't really comment before I get into the details of
template; they are very different approaches to a similar problem, I
think.

> I'm imagining that a lot of the core names are reaching a point of stability
> (recent discussions on l3messages notwithstanding).  Most things seem to
> work quite well.

Lots of little changes, it's looking like. But nothing will be
changing in the short term until we've got more of a "unified view" of
everything that needs attention.

Cheers,
Will