$FreeBSD$

Guidelines for what can go in /user
-----------------------------------

First of all, everybody needs to keep in mind that this repository is
replicated as a unit.  Anything that goes into the repository uses project
and volunteer resources.  Once something goes in, it essentially never comes
out.  Therefore, these are not dumping grounds to put random junk in the
tree that we have to mirror forever.

General guidelines:

* Should be relevant to FreeBSD.
* Should be at least conceivably of interest to somebody else.
* Should be something that is worth people's time to read commit mail for.
* Write decent commit messages!

The difference between /projects and /user wasn't very clear in the past.
Going forward /projects is reserved for branches of FreeBSD itself for possible
re-integration into /head. Branches shall not be nested into e.g.
/projects/foo/stable8, instead /projects/foo_stable8 shall be used.

/user can be used for tools and software tightly related to FreeBSD, but which
is not a copy/branch of FreeBSD itself.

Layout:

Since this is for auxiliary/experimental projects that might not be branched
from head, an argument can be made that we teach the pre-commit scripts to
sanity check WIP as it goes in.

Initial creation:
  Assume user/pho/stress2.   BASE="svn+ssh://svn.freebsd.org/base"

  $ svn mkdir $BASE/user/pho/stress2

Then check it out:
  $ svn co $BASE/user/pho/stress2
  $ hack, hack, hack
  $ svn add .
  (should schedule all files/dirs for addition)
  $ svn status
  (verify all files you want added, and only those are scheduled)
  $ svn commit

Other:

If it is not covered here, and there's no established practice of doing what
you're trying to achieve, always ask your peers first!