in reply to Take Back Your Modules!

One way to help, which can be useful to authors, other comaintainers and everyone interested in the module(s) is to have a publicly hosted version control repository.

This way, you have a trunk, which is the latest pre-release version of your module; tags trees for your released versions and branches trees for development and major projects. I recommend granting read access to all, but restricting commits to known users via htpasswd.

I have recently set one up for my CPAN modules - mine and comaint. I also have some vapourware modules in there. I am willing to include other modules in there, by request.

If any monks want to use it, drop me a /msg.

You can always set up an SVK mirror for developing modules and patches locally - this is recommended.


Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)