Atunci cind incepi sa utilizezi redmine in fiecare zi te lovesti integrarea svn – redmine. In mod normal serverul de svn si redmine-ul se pun pe masini separate si fiecare cu sistemul lui de gestionare de proiecte  / useri. Cind ai multi developeri , unii care vin , altii care pleaca , altii uita parole,  problemele de gestionare a sistemului pot deveni serioase. Redmine-ul rezolva aceste probleme prin:

1) Integrarea redmine cu ActiveDirectory ( sau cu un alt server LDAP ). Am spus integrare cu AD pentru ca in majoritatea firmelor medii / mari exista AD.  Asta inseamna ca sarcina crearii de useri / intretinerea de parole / access controlul / password policy se muta catre Active Directory sau LDAP. Ca avantaj major este ca administrarea poate fi centralizata.  Utilizatorul  poate sa isi schimbe singur parola ,  poate fi fortat sa schimbe parola o data la x luni si se poate impune o politica de parole ( n caractere din care m cifre si p semne speciale ). Un foarte bun punct de start se gaseste aici : http://www.redmine.org/projects/redmine/wiki/redmineldap

2) Integrarea si crearea automata a tree-urilor de svn atunci cind un proiect nou se adauga in redmine. Asta inseamna ca administratorul de redmine nu trebuie sa creeze de mina tree-ul de svn , sa adauge useri la svn scutind mult timp. Pentru a realiza acest lucru puteti citi http://www.redmine.org/projects/redmine/wiki/HowTo_configure_Redmine_for_advanced_Subversion_integration

Submitting patches to the software you use is the way that software gets better. My first patch to timesheet plugin for redmine got aproved . It’s not much but it’s a start.

1. How do I get the code?
1a. Where is the repository, and what type (cvs, svn…)?
1b. What branch/version should I check out?
1c. What external projects/libraries/etc. does it depend on, and how do I get them, and which versions of them do I need? (If allowed by the license, consider hosting a version with your source for one-stop shopping.)
1d. Ideally put this in a step-by-step “for dummies” set of instructions on your project’s web page. Or you could make available a script to run that does it all for you – but well-documented so I can figure out what the script is doing and why. Oh, and make sure it works for you if you follow it exactly on a virgin machine!

2. How do I build it?
2a. What language(s) is the source written in?
2b. What compiler(s)/build system(s) do I need, and where do I get them?
2c. Where are the makefile(s)/build files etc. and what does each of them build, exactly?
2d. See 1d.

3. How do I run/use it, and where is the target(s) (executable, shared lib, whatever…) that was built?

4. How can I get help if I need it?
4a. IRC chat is useful, but if most of the developers are on the other side of the world, it would be nice to also have a mailing list to which to post so I don’t have to stay up all night. Preferably a mailing list that allows attachments for error output or screenshots.
4b. Ideally your FAQ should actually be made up of questions people have actually asked, especially if they are asked frequently. FAQs rarely do this for some reason – I’ve often seen the same question asked over and over in help forums, and never answered.
4c. Answer the questions people are asking. Even if the answer is “if you can’t figure this out, you don’t belong here” – try to phrase that as nicely as you can.

5. What is your process for managing versions and how/when they are changed in your repository?
5a. If you allow checkins of incomplete code, how do I know if I’ve found a real bug that I should fix, versus something that will be “fixed” when the person working on the feature checks in the rest of it?