SubversionSubversion is our Source Code Repository for all projects.
Please be aware, the SVN SSL certs had to be reissued as a precaution due to the Heartbleed vulnerability. You may see the following warning:
Access to Subversion Repository (SVN)
The Kuali Subversion repositories are readable by anyone. The repositories can be found at https://svn.kuali.org/repos.
If you need commit access to the SVN repository, you must be on a project development group. Please contact your development manager to place you on the appropriate Development group. Please email email@example.com with the following information and CC your development manager on the email. We must have a signed CLA on file before we enable SVN commit access.
Contribution License Agreement (CLA)
We must have a hand-signed CLA on file before we enable SVN commit access. Email a scanned copy of the Contributor License Agreement (CLA) to firstname.lastname@example.org, you can download the CLA at: http://links.kuali.org/cla.
All developers must complete the OWASP Top 10 Security Risks training course. You do not have to score 100% on the quizzes in order to consider the training completed. It will be up to you to determine whether or not you have successfully internalized the material from each section, or whether you should retry any of the quizzes. It should take on average 2-3 hours to complete.
Once you have completed the training, login to the Kuali Information System - KIS (https://kis.kuali.org) and click on the "Add Security Training (OWASP)" link on the Training line of your
profile. Follow the instructions to indicate that you have completed the training materials and then email email@example.com to let us know to provision your account for commit access.
If you have any question please email firstname.lastname@example.org
Subversion Username and Password
Subversion SSL Certification
Subversion (https://svn.kuali.org/repos) does not currently ship with a list of trusted CAs and may need you to accept our SSL certificate.
With Subversion 1.6 you can use the --trust-server-cert --non-interactive option if you are using svn in scripts.
Do not use svn lock. Locks are almost always unnecessary. Good communication is preferable to locking even in this use case. (see http://www.apache.org/dev/version-control.html#lock)