DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:from:to:content-type:content-transfer-encoding
	:mime-version:subject:date:x-mailer;
	b=m8a5m9l4Lix7uq94ZF+1H/yxa36BUgeE6GBQm1E7HjrTmZdrUXBsT3SHD8k5merKHK
	l69k7YStaeC7LWg/xqoaS4XdwEZjv6ruFH5jBC4quJXD41P7tJKEjGrGleXDEvQB00tB
	4bts8CBmAo8TbMNs5gM9SjHOHrjnQF8hS0FvQ=
Message-Id: <4B4D32B8-31E7-44F6-8A51-C5D51883DF99@gmail.com>
From: Will Robertson <wspr81@gmail.com>
To: team LaTeX <latex-team@latex-project.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Working externally with l3doc
Date: Sat, 6 Dec 2008 06:05:18 +1030
Precedence: list
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: latex-team-bounces@latex-project.org
Errors-To: latex-team-bounces@latex-project.org
Status: R

Hello,

Recently I asked for help on LaTeX-L to work on l3doc, and received an  
offer by one Arno Trautmann. He's fairly new to the expl3 code (as was  
I when I started) but he seems enthusiastic to help for now.

I have the idea to set up an external version control repository  
(probably at GitHub) with a copy of l3doc (only!) to encourage him to  
work on it; as per the intentions of the LPPL I'd call it "l3doc-dev"  
or something like that. I'd work on it with him and merge changes back  
into the official SVN repository.

However, I recognise that this idea might be a little controversial,  
so that's all it is at the moment -- an idea. What do you think?

Will

_______________________________________________
Latex-team mailing list
Latex-team@latex-project.org
https://lists.dante.de/mailman/listinfo/latex-team