[horde] Using GIT for Horde?

[Chuck Hagenbuch]

Quoting Thomas Koch <thomas at koch.ro>:

> I'm very interested in the horde project and would like very much to start
> hacking on horde, but
>
> * CVS really pushes me back. My first VCS was allready SVN and I really don't
> want to learn a technology that's already history.

I'd challenge you to just learn it. CVS is still widely used, and for  
checkout, update, diff, and commit, the commands are darn near  
identical. To be fair I wouldn't really push you to learn CVS  
branching. :)

> * I think that most of the changes I'd like to make[1] would not be accepted
> by the whole horde project.

I'll address this below.

> Nevertheless it could be usefull for the whole
> project to have another dev looking over the code and maybe some of my
> changes could go "upstream". This upstream merge is much easier with a
> distributed VCS then with CVS/SVN.

I'll have to take your word on this, but I'd hate to lose your  
potential contributions to Horde over it.

> [1] Those changes are: Eliminating strict warnings, eliminating code in the
> global scope,

These are some of the core goals for Horde 4 - they're impossible now  
because Horde 3.2 maintains PHP 4 compatibility, however, when we move  
to PHP 5 code for Horde 4.0, this will be done.

> including eZComponents for configuration, authentication and
> mail transport,

Why? :)

> only one central index.php as a dispatcher.

http://dev.horde.org/routes/

-chuck