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.
  • Sorry, you made some good points hopefully I have reinforced them here.

    Interested in forming a cabal - it would be nice if we had a list of who to contact about which websites and could try and make their lives easier.

    A little mailing list would be cool if anybody could set one up.

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • Interesting idea. But how would a list address the issue of trust that I keeps rearing its ugly head?

      Perhaps what we need is a committee that oversees (important) Perl websites. This committee could make "suggestions" to website managers, such as the ones in Jeremy's article. The committee could also set goals for the different websites, and perhaps arrange for trusted volunteers to lend assistance where necessary. And this committee should have a mailing list.

      The importance of Perl's net presence shoul

      • by TeeJay (2309) on 2004.09.27 16:43 (#34738) Homepage Journal
        You would build a web of trust as you would for development - people who submit patches and fixes will eventually be given cvs access, etc after the website maintainer feels they are trustworthy.

        With a mailing list, maintainers of websites will be able to share information and contributors will be able to prove their trustworthyness by the contributions to the list, face to face at meetings/conferences and irc. same as for development.

        If you have a committee it could get in the way and might not be suited to adhoc fixes, etc but it could be subscribed to a list and handle some of the admin tasks and work with people providing servers, sponsership, etc.

        --

        @JAPH = qw(Hacker Perl Another Just);
        print reverse @JAPH;
        • Anything helps! I am all for a list. Sign me up!

          I think an informal committee would help add an air of legitimacy (among the other things I already mentioned) to our efforts. I view this as a problem that should be addressed by the community at large. It would be nice if the Perl foundation could get involved somehow, too.