...

PSDM uses Subversion (SVN) for the code management and versioning task. Currently, official LCLS code such as PSANA, PYANA, etc. is located in the Software Repository which is enabled to LCLS software development team only. Those For those users who would like to develop their own code, contribute to the LCLS project, and share this their code with other user groups, there is a users' software repository, https://pswww.slac.stanford.edu/svn/userrepoImage Modified (this IS NOT a web reference!), assigned to environment variable SIT_SVN_USER.

...

Read-only access to both repositories is provided through the web interface:

• Public repository for users' code : https://pswww.slac.stanford.edu/trac/psdm/browser/user
• Main PSDM Subversion repository : https://pswww.slac.stanford.edu/trac/psdm/browser/psdm

Command line interface

SVN-based command-line interface is identical for both repositories. The only difference is that the key "-u" should be added to all the addpkg and newpkg commands for users' repository.
For example, to get package from users' repository one has to use command

svn addpkg <package-name> -u

newpkg <package-name> -u

which are explained in Typical development tasks.

Inclusion of the package in official release

Publicly available LCLS offline releases can be seen in the directory associated with $SIT_RELDIR environment variable. Inclusion in release means that the package will be compiled nightly and its modules and applications will be available by default to anyone who want to use them, with appropriate version tag. Packages from both repositories can be included in LCLS offline release system by a personal request to the release coordinator (currently Andy).

References

So up Up to the a minor difference in two commands

all other svn commands can be used with users' software repository.
Here is a list of useful references to the documents explaining how it works.:
Typical development tasks
Software Repository
Software releases