Re: Let's stop using CVS for debian.org website

On Sun, Nov 20, 2016 at 12:46:55PM +0800, Paul Wise wrote:
> On Sun, Nov 20, 2016 at 10:45 AM, Boyuan Yang wrote:
> > 
> > Hi all,
> > 
> > As a newcomer who wants to contribute to the Debian website, I was shocked 
> > when I heard that debian.org website is still using CVS to manage the source 
> > code.
> > 
> > I know there is a saying that "If things ain't broken, don't fix it.". But this 
> > is nearly 2017 today, not 2007 or 1997. CVS is seriouly outdated and largely 
> > replaced by SVN (or even Git).
> > 
> > If we continue to use CVS in the website source management, the disadvantages 
> > are clear:
> > 
> > * All the shortcomings that exist in CVS but solved by SVN or Git.
> > * Fewer and fewer people know how to manipulate with CVS, and most of the 
> > others won't be willing to learn it.
> > * Difficulty in setting up modern web interface. (Compare viewvc with GitHub, or 
> > for free software, GitLab or even cgit.)
> > * Difficulty in mirroring.
> > * ...which means the number of new content contributor would decrease.
> > 
> > Needless to say there are various tools that can help convert a CVS repo into 
> > a SVN repo or Git repo and they handle this job properly.
> 
> This idea comes up every few years but we haven't yet found someone
> with the time, skills and motivation to implement it.
> Some historical documents and discussions are in these links:
> 
> https://lists.debian.org/[email protected]
> https://wiki.debian.org/WebsiteVCSEvaluation
> https://wiki.debian.org/WebsiteSVNTransition
> 
> > I know the migration to other version control system would not be trivial and 
> > hurt the current workflow, but I strongly suggest that we set up a timetable or 
> > future plan. So will debian.org continue to use CVS to manage its source code? 
> > If yes, when will we re-analyze this choice? If not, when will we do the 
> > migration?

Roadmap
* Realize that we MUST adept. A change is really needed.
* Accept that there will be temporary breakage
* Announce that leaving CVS is coming up
* Have canned replies: "Currently this is going on, See URL for how to help"
* Do a last CVS change and commit
    echo "switched to git" > switch.announce.tmp
    echo "see URL" >> switch.announce.tmp
    mv README README.tmp
    cat switch.announce.tmp README.tmp > README
    # cvs add README
    cvs commit -m "thank you and goodbye"
* Make CVS read only
* Convert CVS repository to a git repository
* Put the git repository on-line
* Work with ( read from and write to ) the git repo
* Smile because now the journey is really started
* Focus on being able to update the website again
* Enjoy the milestone of a website update
* Now focus on getting a translation working again
* Make more translations possible
* Be happy surprised about whatelse showed up
* Conquer those challenges
* Replace CVS references with git ones. To avoid that people mis the new workflow
* Enjoy reaching the goal


Groeten
Geert Stappers
-- 
Leven en laten leven

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJYMV15AAoJECE10SPYwZvszrMQAJmi3AIRmCafRTqjp94TESON
aGsrl6GyX2rsjf42pKz76jzcIlGN7A/AKj5mwWL0y669057FGgRq1juY4aeAT7zf
yVmMeQZZ6hCyYyEAW+XyQLneghbpoTS8FUxJRUmlMK3RwI2B+BvXo/1B512cS3gw
oId4OLZ08U2pFyuq9VBGFCXtJor/KK1UWlglBz0+QiGleAUuR4d1HoXSEExbZM3m
D7f2csVu4xRcwaRuJPLLRLsCgel2+4wWC1uuxlzeHGcswlP8gpFGpRg2kXjkIyGG
OAZ0/7NOwvIs/9QwBaKn8kq0l3epI5CEUrs+0qV5HqsVyRv0sYLyGCZWD8yMs5Yw
gBZmkIXLlDH0eWUG0+sCwa8+IdfBd6Spyc/o3vR9G7NHYD6qlbZJ+5sLUTVKh3wa
pXLUDU5eiFit7PamTCFIdgxkZsgv5cdSbOFoSe3+Zbo1MNQIy1VekuxUhIqVX+zS
XvG/yTOZltizRX+poC4X9V4BCdvh9MggPrvQRj2+q2A2jHh7q1qopukoMsuTwn8d
18VpRRCa6Q6myL/49og3eZkPsd2mvJnxTRExZAFljEzcd3Uv2oy3Qimhz8snXz0P
I0zam1MI2CCflBfRQ1MTqrUXhFZmO3tmw7zh+qBFkSFOl2OICjvIgVL+SBhzK+BU
B13IY+wgHjS3pD7UTMNs
=TPL5
-----END PGP SIGNATURE-----