Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • If you don't like Gravatars or CPAN Search, you don't have to participate. But, not only that, you can write your own. OF course, when you start that, you'll realize why the guy is asking for $10. Also, if Graham wants to spend his time doing other things and doesn't want to make his site open source, who cares? It's his project and he can do whatever he likes with it. You can start you're own project that meets your own non-technical. sociological, and political goals and do whatever you like with it.

    Pictures are amazingly calming to people. People are much nicer about articles in The Perl Review once I added author pictures, and I added author pictures because I knew that would happen. Schwern wants to do the same thing for CPAN. Perl is people, after all.

    Your points just sounds like more "I should get stuff for free" whining, which entails nobody buying themselves food or paying their rent and having to ask permission to do what they like with their own project. It certainly isn't based in Freedom. You, however, have the freedom of choice. Try Kobes' Search [] for a Gravatar-free alternative.

    So, good luck and let us know when you have your site ready. :)
    • I agree with much of what you said, but I think one of Earle's points you didn't address is:

      Before we start adding new stuff, can't we get our own house in order first?


      This didn't really have to do with gravatars, but I think it would help show the cohesiveness of the Perl community to outsiders if it did happen. Why wouldn't the community want that?

      I understand that it would create work for Graham to change the links from cpanforum and annocpan to and Maybe he doesn't want to do it and that's fine. But I think Earle was just bringing up the

      • I agree with the site naming part.

        It would also be a good idea to put links to the various sites on the front page of, because people will go there looking for various sites.
      • I like that projects have their own domains. I like to think that there are a lot of different people out there interested enough in Perl to do these cool things, rather than some big organization doing it. I like decentralization :)

        As for links on, that would be nice, but no normal people really cares what's in the HREF. All the links are in CPAN Search right with the module page :)
    • I agree. Everyone who wants to contribute:

      1. Should start his own project.
      2. Provide his own server infrastructure.
      3. Evangelise in the community for the weeks or maybe months until he has some semblance of traction.
      4. Continue maintaining his project in isolation from the other similar projects.

      I don’t understand why people would want to pool their resources. In a situation with limited volunteer tuits available, it’s most effective to divide them over as many similar projects as possible.

      • Well, it works. I did it with Perl Mongers and The Perl Review, and many people have done it with their projects.

        When you remove the irony, you are really saying:

        1. Everyone must let just anyone mess with their project
        2. Someone who doesn't get paid should make their infrastructure open to everyone else, and maintain it for them
        3. People shouldn't have to work hard to promote their own work
        4. Somebody else should do most of the work

        Thre's no problem here, except people thinking they have a right to somethin
        • Apologies in advance for the “quote every sentence and respond to it” style of this comment. I hate it and try to avoid it, but there’s no other way to write this one. It boggles my mind how you manage to get every single aspect exactly backwards.

          Everyone must let just anyone mess with their project

          How does setting up to make the contribution of patches possible imply that you are somehow forced to apply all patches you get?

          Someone who doesn’t get paid should make their infras

        • Step one is not being a public ass about it. You complain in public and attack people, and you just about kill your chances to help out. It's not a hard concept to understand, but geeks don't like it because it involves people skills.

          You were doing badly enough until you got to this part when you started insulting me. I had a nice, long, reasoned reply mentally queued up to go, but you just killed your chance of ever seeing it. Instead I feel moved to say this: brian, go fuck yourself.

          • brian, go fuck yourself.

            What a swell way to tell people that you're not someone to work with.



            • Whereas calling someone a 'public ass' is the perfect way to announce you're Mr Congeniality ;-)