NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Questions, Concerns, Complaints, oh my! (Score:1)
Mark asked me to not comment on CPAN6 until after the release at YAPC::EU and gave me an early copy of the paper, and I've happily done so.
But reading through the final version of the paper, some concerns remain.
Without wanting to get too much into specifics, I was wondering how you plan to deal with this type of thing. I see a lot of detail on what your so
Re: (Score:1)
The "Emerging problems" section of the Global Design Document [cpan6.org] cover a lot of the shortcomings of the current CPAN. Also see the section "Projects" in the chapter "Pause6 Organization" for some more examples.
Re: (Score:1)
I'm already on a billion mailing lists, unless you plan to have it go onto nntp.perl.org I really don't want to be on two more.
I don't know how I'm supposed to generate patches to a postscript file (why isn't everyhing just text or HTML) and in any case, I'm useless with patches, and so is Windows.
Not to mention I can't actually read the postscript file on this system.
OK, I may be bitching here, but if 90% of the computer users can't play nicely without projec
Re: (Score:2)
We have been consulting with people. (Score:1)
Mark has been in contact with Andreas along the way.
We basically sent it to the people who asked for it. We have taken the initial design, subjected it to review and now we are asking the wider community for input. There's no point in releasing something before it is ready, it just spreads too much disinformation. Please consider it a matter of politeness of not giving you something until it was something like ready, rather than a young undeveloped brainfart.
That is a shame. There was an offer to move it to 'perl6-cpan' on lists.cpan.org; but that's not right, either - this project is not specifically perl6 related, it just came from the requirements of perl6. So therefore it does not fit under the perl6- space. I hope once this impasse is resolved through early discussions that we can move it there and get your input, too.
Excellent, you are describing the cpan6 part in a nutshell, though we are also adding auditing and cryptography.
Yes, that is the idea - the core cpan6 network distributes releases, and this is a logical layer for tools like pause6 to provide CPAN- and PAUSE-like services atop of.
Reply to This
Parent