comment on

it would be nice to have both svn.cpan.org and git.cpan.org available. I wonder what it would take to get that up and running?

Jarkko Hietaniemi owns cpan.org; I have trouble just pushing CPAN mirror updates to him, good luck trying to get new subdomains set up. DrHyde tried getting deps.cpan.org to point to cpandeps.cantrell.org.uk last year and Jarkko refused.

On the other hand, svn.perl.org already exists, although it's currently only used for a few Perl projects. I'm not sure whether that's by chance or design.

When 5.8.9 is released the perl5 porters will move from Perforce to git for the revision control system. Rafaël Garcia-Suarez has said he will host git.perl.org at $work. There is talk of making things easier for maintainers of dual-life modules to use it for both blead and CPAN releases. I don't think there are any plans to open its use out to the wider community.

Be that as it may, if you have a host and bandwidth to donate, I suggest you get in touch with Robert Spier and see about getting a different A record, like git-contrib.perl.org, set up.

• another intruder with the mooring in the heart of the Perl

In reply to Re^4: Losing faith in CPAN - unresponsive module authors (ownership--) by grinder
in thread Losing faith in CPAN - unresponsive module authors by andreas1234567

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks