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.

    • 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 infrastructure open to everyone else, and maintain it for them

          How does accepting some patches (and others, not) equate to making your infrastructure available to other people and maintaining it for them?

          People shouldn’t have to work hard to promote their own work

          You misunderstood completely. The point isn’t that people shouldn’t have to promote a new site; it’s that they shouldn’t have to set up competing services in the first place when they could cooperate with an existing one. You championed a situation in which competition is the default. That makes no sense; there aren’t enough tuits to go around in the first place, never mind pitting them against each other. Cooperation should be the default.

          Somebody else should do most of the work.

          This makes no sense whatsoever. If you make it easy for people to send you patches, you say, the contributors would be letting somebody else do most of the work. What? Does not compute.

          Step one is not being a public ass about it.

          Yeah, says the guy who responded to a mostly reasoned critique by writing a comment titled “Good luck with your own CPAN site” wherein he tells the other guy to love it or leave it.

          It’s not a hard concept to understand, but geeks don’t like it because it involves people skills.

          Oh please, not the “geeks with no social skills” triticism again. Wasn’t it you just saying people should avoid being an ass in public?

          We’re the most kick ass community there is.