Subversion (SVN)

SVN (Subversion) is a tool used by many software developers to manage changes within their source code tree; it is an open source version control system. It allows users to keep track of changes made over time to any type of electronic data; typical uses are versioning source code, web pages or design documents. Read more at Wikipedia.

You can browse the current SVN tree using the following address:

http://drakecms.svn.sourceforge.net/viewvc/drakecms/

Client software

How to checkout

Create a new folder under your localhost root (for example c:/inetpub/wwwroot under Windows), right click and perform a checkout from the following URL

 https://drakecms.svn.sourceforge.net/svnroot/drakecms/trunk

If you are using a unix/linux system the command line syntax is

 svn co https://drakecms.svn.sourceforge.net/svnroot/drakecms/trunk drakecms

Logging in

You will be asked login credentials, if you have write permissions use your SourceForge login credentials otherwise just user drakecms and no password for anonymous read only access.

Bug hunting

Use the Sourceforge.net bug tracker for your bug reports and post your patches using this other separate Sourceforge.net tracker; but always be sure that you are working with the latest SVN revision!

Developing

If you are going to actively contribute ask to be added to developers list and you will get the commit write permissions to add your changes directly into the main trunk.

See also our feature requests.

Commit rules

If you are using Subversion only to get the files, you will not need to read and understand the commit rules.

  1. Do not commit copyrighted material! Committed code and material must be compatible with the GPL license
  2. Always update before beginning your edit session
  3. Test your modifications before committing to the trunk
  4. Always commit when finishing your edit session
  5. Use descriptive log lines and start each line with an asterisk '*' (theoretically, for each edited file you should summarize the changes in functions' behaviours or user interface or fixes)
  6. Update also /trunk/version.php revision number if you have fixed a bug or implemented a feature

External Links