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)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||