Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • A while back I speculated on the various proposals for a "CPAN Replacement" I saw and mentioned that it appeared to me that there was a lack of planning.

    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
    • I see a lot of detail on what your solution looks like, but not so much detail on things like the underlying reason for it's existance, use cases, constraints, assumptions, priorities, and so on and so forth.

      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.

      How do you plan to deal with these sorts of issues ... and how willing are you to change

      • The setup you have there makes it really hard...

        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