USER AND ADMINISTRATION DOCUMENTATION
    Use the "Site Docs" link under "SF.net Resources" in the left panel.

Email addr:  unsaved@users.sourceforge.net.
Email list addresses:  projectname=listname@lists.sourceforge.net

shell servers:   shell.sourceforge.net
home dir at /home/users/u/us/username
They say to restrict cvs use on the shell servers to cvs1 via anonymous pserver.
(I don't understand the difference between cvs1 and cvs.  Maybe cvs1 is the
NFS master or something).
project home dir at /home/groups/u/us/username

PROJECT_HOME/html
PROJECT_HOME/cgi-bin

SHELL SERVERS lacking ant, ksh.

CVS Repositories.  There is no local access to cvs.sourceforge.net
(or cvs1.sourceforge.net).  No login shell and no file copies via cvs/cvs1.
    R/W:  -d :ext:unsaved@cvs.sourceforge.net:/cvsroot/PROJECT_NAME
    R:    -d :pserver:anonymous@cvs.sourceforge.net
          (Remember for pserver that you have to "cvs -d .. login" first)
Looks like they do not permit "cvs admin".
Since no fs access to the repository, you must run import to start a new
module.  To do same thing as "mkdir /repos/dir/newmodule", just
  mkdir /tmp/mt && cd /tmp/mt &&
  cvs... import -m 'Comment for import' newmodname vendorbranch releasetag
  (The last 2 tags serve no purpose in this context)

Output from cron jobs get emailed to you.  Shell login files do not
get sourced before running cronjobs.

FRS:  Sourceforge's file release system.
Must be a project Admin to use this.
Object hierarchy.
    Project
    Package (can just have one package for the project, and may use same name,
     more typically, there would be a devel package).
     Generally correspond to the CVS modules in your project CVS repository.
        But, if somebody wants source or bin between public releases, just use 
        CVS.  Probably makes sense to just have a package for each product.
    File Release, like jamama /  jamama / 1.2a.  (Don't have to have numbers).
      [One File Release consists of multiple files (usually), like a
      src zip, rpm, src rpm.]
Sample hierarchy
    Project: hsqldb
    Package: hsqldb, hsqldb-dev
    File Release:  hsqldb-src.zip, hsqldb.zip
The Admin has a FRS interface where you can define Packages and File Releases
and upload the individual files for a File Release.  Admin / File Releases.
Upload files via anonymous ftp to upload.sourceforge.net:/incoming.

SSH KEYS:  Can upload ssh keys to shell servers in normal fashion.
To upload keys to the CVS server, you must use the form under the 
Account Maint/Options (something like that) to update keys for
CVS and Compile farm.

COMPILE FARM.  Must opt in to create an account (on Account opts page).
cf.sourceforge.net
    Hokey CUI shell that pipes you through to selected server.
cf-shell.sourceforge.net.
Transfer files via s* to cf-shell.sourceforge.net.
Use pserver to fetch from CVS.
Can't log in with password.  Must use ssh key.
Note that the list of servers in the docs is NOT up to date, plus, some
of the servers listed when you login do not work.  The list at
/etc/compilefarm-hosts on cf-shell isn't very detailed!
Home directories are shared among all farm servers.

Sourcefoge policies
(I think I have a separate file about the FR, File Release, system).

Seems no more shell access to project web server host.
sftp joe,myproject@web.sourceforge.net:htdocs