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.

cpan6 - moving forward 6 Comments More | Login | Reply /

 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 project structure, it's limiting participation.

        > By sending you and Jarkko the papers early, we were inviting your participation in this stage.

        I was given a copy to basically shut me up :) And asked not to comment until now...

        The JFDI element is from the "show us the code" population. There's nothing like a working demonstration to discover the design flaws.

        As for undermining, I think my only concern there is that merely by using the names "CPAN6" and "PAUSE6" you present yourselves as a successor to the CPAN, when that is not necesarily the case, you are more of a CMAN (Comprehensive Meta Archive Network).

        • I agree with Adam. I'm not sure how you selected Jarkko and Adam to be the early reviewers of the paper, but it seems to me that Andreas might have something good to say, and that the current PAUSE admins might have had a lot of wisdom to add. My first inkling that anything was happening is when someone subscribed me to the CPAN6 mailing lists. I suppose that's a nice jesture, but no personal note accompanied the subscriptions, and I promptly unsubscribed. I don't do mailing lists. Put it on nntp.perl.org a

          • I'm not sure how you selected Jarkko and Adam to be the early reviewers of the paper, but it seems to me that Andreas might have something good to say,

            Mark has been in contact with Andreas along the way.

            ... and that the current PAUSE admins might have had a lot of wisdom to add.

            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

        • And if you do not wish to send patches, you don't need to. Just raise issues like you have done.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.