Re: 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.

http://www.ivorw.com/svn/cpan

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)

Comment on Re: Take Back Your Modules!

Replies are listed 'Best First'.
Re^2: Take Back Your Modules! by petdance (Parson) on Sep 11, 2006 at 20:27 UTC
I've started using Google's code hosting for my projects: http://code.google.com/hosting/ xoxo, Andy	[reply]
Re^3: Take Back Your Modules! by Anonymous Monk on Sep 19, 2006 at 11:02 UTC
Why (compared to your prevous host)?	[reply]
Re^4: Take Back Your Modules! by petdance (Parson) on Sep 25, 2006 at 02:16 UTC
My previous host was either my own Subversion box, or svn.perl.org. My own box isn't nearly as snazzy and featureful as Google, and svn.perl.org requires me to bug Robrt and Ask for stuff if I need changes, and I'd rather not. I only use that for stuff that is core Perl or nearly so, like Mech. xoxo, Andy	[reply]