SVN Migration

The Plan

Repository reorganisation
- We won't use cvs2svn to migrate but simply import the whole source into svn to have a clean start.
- Lazarus gets it's own repository.
- The following repositories are planned:
  - fpc
  - lazarus
  - contrib
  - projects
  - html (web page contents)
  - docs
  - logs
- another packages dir: packages/contrib with contains packages which are maintained externally. Something like the Delphi Companion CD. The long term goal is however to flatten the packages hierarchy (packages/base and packages/contrib?), work only with "build units/packages" in each directory. Making e.g. the fcl and fv a usual package as well.
- Stuff in packages/contrib which isn't maintained actively anymore is moved to the contrib repository.
In the first step only ssh based authentification will be possible.
After everything is setup and working, a read-only cvs mirror will be installed.
The SVN project is updated regularily and releases new versions, so it's necessary to have policy when to update the SVN server. The proposed policy is to keep up always with the latest stable svn version.
Each repository gets it's own unix user group so permissions can be easily managed.

svn can be used very similiar to cvs, _the_ svn book can be found here: http://svnbook.red-bean.com/en/1.0/svn-book.html. I have setup a sandbox repository on idefix so you can test svn if you've an idefix account. The URL of this repository is svn+ssh://www.freepascal.org/FPC/svn/sandbox1

People prefer gui tools instead of command line clients. A good client with explorer integration for win32 is TortoiseSVN (http://tortoisesvn.tigris.org/ ). How to use it with ssh authenfication can be found here: http://tortoisesvn.berlios.de/faq/index.php?action=artikel&cat=8&id=30&artlang=en.