[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Best Practices (was: rapidsvn feedback)

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-08-01 17:41:47 CEST

Josef Wolf <jw@raven.inka.de> writes:
> I still think it is not worth to create a separate document because
> most of the things I can think of to put there are already written by
> Ben Collins-Sussman in his original article which was the start of
> this thread. There are only two or three Items I would like to
> add. But when the majority of the core team thinks it should be a
> separate document, I will try to put the peaces together so someone
> could commit it into the svn repo. After a while (1.0?) we can again
> take a look at it and let it alone if it has grown large or move it
> into the appendix of the handbook if they are still only a couple of
> pages.

Sorry to have to restate this again:

No, *not* in the svn repo. In its own repo. New document, new
project. Not related to Subversion.

Of course, most of this stuff is *already* in the svn repo, in the
HACKING file. That's the document you want. It exists. We've had it
for a long time. It is the guide to Subversion contributors, and a
handbook section on contributing to Subversion can of course reference
it. But it's there because it's what a Subversion contributor has to
know. It's Subversion-specific -- it is not a separate project to
document the best practices of all open source projects.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 1 17:56:42 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.