That's a great idea. It'd be fairly straightforward to make a simple drupal-specific frontend to CVS that cover the common-use cases. It'd even make coders lives easier as in my case, whenever I want to update my module I still have to look-up the documentation as I use other RCS systems then CVS.<br>
<br>Kyle<br><br><div class="gmail_quote">On Fri, Feb 22, 2008 at 10:11 AM, Wim Leers <<a href="mailto:work@wimleers.com">work@wimleers.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Feb 22, 2008, at 14:27 , Karoly Negyesi wrote:<br>
> However great git is, given the huge number of our contributors<br>
> using Windows and on various levels of knowledge about RCS systems,<br>
> anything without a proper Windows port and a Tortoise-alike<br>
> interface has no chance. To my knowledge, current this means<br>
> Mercurial: 2007-12-02: First public release (0.0.1) of TortoiseHg<br>
> with binary installer. Since then there were three more releases --<br>
> quite an active project. There is a <a href="http://repo.or.cz/w/git-cheetah.git/" target="_blank">http://repo.or.cz/w/git-cheetah.git/</a><br>
> which says "This is an explorer extension in its infancy. Do not<br>
> expect anything to work, unless you are fixing it." -- unless this<br>
> becomes useable, git is out of question.<br>
><br>
</div>> ...<br>
<div class="Ih2E3d">><br>
> Do we want to change? I presume that the project-VCS API integration<br>
> happens eventually so <a href="http://drupal.org" target="_blank">drupal.org</a> is ready (this is quite a stretch).<br>
> Well, after many years I am not so sure. Are the niceties of SVN<br>
> over CVS are enough to make such a big change? What this buys us?<br>
> Will the hard concepts of branching and tagging become easier for<br>
> our contrib authors? I doubt.<br>
<br>
<br>
</div>At first, I found using CVS a hurdle. I managed, but I had to look up<br>
several of the commands every time. Until I discovered the usage<br>
of .bash_profile. Now I absolutely don't mind using CVS, since all<br>
ugly things are abstracted away (although several of these commands<br>
are Drupal-specific, but that doesn't matter to me, as I use SVN<br>
everywhere else).<br>
<br>
My point is: the biggest problem people have with CVS, is the<br>
usability aspect (actually the concepts, but it's usability<br>
improvements that should make the core concepts obvious). However,<br>
that can be overcome by using your shell effectively – any coder<br>
should know how to use a RCS and the shell. But that doesn't solve the<br>
other problem: themers generally don't know how to use a RCS in the<br>
first place.<br>
Changing to a different RCS won't fix any of these problems, at least<br>
not to the level where we need it.<br>
<br>
So I think a good candidate "solution" ("improvement" would be more<br>
accurate), would be to code our own CVS front-end, tied specifically<br>
to Drupal purposes. If written in C++/Qt, it would be possible to<br>
provide a cross-platform interface. Cross-platform is important to us:<br>
we want to support both Windows and Mac OS X (and perhaps more). This<br>
would probably be used by many coders too, not just themers.<br>
Does anybody think this is a good idea? Or perhaps it could not work?<br>
If so, for which reasons?<br>
<br>
So I fully agree with you, Karoly, changing the RCS won't fix any of<br>
the *real* issues we're currently having :)<br>
<font color="#888888"><br>
Wim Leers ~ <a href="http://wimleers.com/work" target="_blank">http://wimleers.com/work</a></font></blockquote></div><br><br clear="all"><br>-- <br>Research Assistant<br>eBusiness Center @ BYU<br><a href="http://kyle.mathews2000.com/blog">kyle.mathews2000.com/blog</a>