Hi,
On 2009-12-20 09:36:27 -0600, Ralph Baker Kearfott wrote:
I have created an account for John Pryce, our lead technical
editor. However, I think he could use additional help (in
addition to Christian Keil, who himself is rather busy
with postdoctoral activities). Volunteers, especially those
who already are comfortable with subversion, will be welcome:
Please contact me and John, and I will create accounts and passwords
for you.
Wouldn't it be better to have access to the repository via SSH
and public keys? This can be done securely, with a single Unix
account. See
http://svn.collab.net/repos/svn/trunk/notes/ssh-tricks
and
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=67687
if this is not clear enough.
I have seeded the repository with an informational file, whose
contents are as follows:
---------------------------------------------------------------
RBK - 2009/12/20/14:31GMT --
svn://hilbert.louisiana.edu/IEEE-P1788-working-drafts/readme.txt.
This repository is for working drafts of the P-1788 document.
The assumption is that the working document be in LaTeX. Anyone
can alter the document and post ("commit") the changes at any
time, and the system detects inconsistencies due to multiple
people working on multiple documents at a time. However, the
system works most smoothly if separate parts of the document are
put into separate files. Furthermore, when any person with
access to the repository updates their copy, they obtain a
complete copy of the repository (and all of the files in it).
It should be asked to the committers not to reformat source text
(except when there are many changes in a paragraph) to keep the
diff minimal and make "svn blame" work better. Also, for the
same reason, lines in the LaTeX source should not be longer than
80 (or even 72) characters.