Website VCS Transition

Summary: The current website uses CVS as backend. It was suggested multiple times in the last years to move to some other version control system, but noone dared to do the work it would involve with converting the various helper infrastructure for translators and others to a different version control system.

Required skills:

Perl programming

Good understanding of the proposed VCS to move to, including change tracking and changed revision counting.

Description: It was tried before to move to svn but there are too many obstacles in that path: It is crucial that most of the stuff can be done offline, especially counting the changed revisions of a file since its last translation. Git might work out but given that the repository is quite huge there might be issues related to that, too.