Do you plan adding your plugin to official C::B /plugins/contrib CVS repository some day?
Hmm... does this work at all? If it does, then I don't know how. It sure is very easy with CVS to set svn:externals on a directory to include another SVN repository in the tree, but I have no idea if CVS has any such thing. Rather, I think it would be necessary to migrate the project to CVS.
But you are of course very right, generally. It sure would be better for its popularity if it was in the CVS tree.
Lets wait until it is in a little more finished. For now, I dread to think about using CVS. If I get the CVS support right, though, maybe CVS could be lived with
Note that not many users use version control system at all
Lol, yes, and CVS contributed a lot to that
When I first thought about using revision control (somewhere around 1995), I was told there was RCS and CVS, the latter being the tool of choice, as it was so much better. So I looked at CVS, and this experience put me off revision control entirely.
At some point in 2002, however, I decided that no matter how painful, I
had to start using revision control, as I spent a good quarter of my time messing with a hundred local copies of every file (well you know... you've been there).
Much to my surprise, subversion turned out to be not much of a pain at all. Setting up a functional repo and successfully importing a project took me 30 seconds after reading the docs (as opposed to 2 hours with CVS). And apart from very few occasions, it causes very very little grief (rarely, it gets a file access conflict, and bdb is not backwards compatible, so upgrading to Fedora 4 made my repos unusable - but well, one should use fsfs, anyway).
Thus it became he used subversion, and he lived long and happily ever after.After all, look at this thread title
Ah yes, but a man can dream, can't he
Maybe Sourceforge finally releases SVN access one day, then no one will be wanting to use CVS any more. At BerliOS (which uses the sourceforge web interface, too), they have it running.