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.
  • Especially if we're talking about only a few. Emailing 100 people that their distros are immensely used and still fail quite a lot sounds reasonable, but I think it's more than fair to email 10 people.

    FAIL 100 can really help us focus efforts on bug resolution. Imagine a group in the community (composed of the community) that helps weave out bugs in CPAN/DarkPAN/whatever. Now, if they could only know which distros need the most hand... oh wait! Now they do!

    At any case, how hard can it be to email back and s

    • At any case, how hard can it be to email back....

      You don't get to decide that for other people receiving automated bulk mail.

      • True. I don't get to decide it, but I can reply to Adam's request for anyone's opinion, and per my opinion, I think that receiving one little measly email that you can just press the "Reply" button and say "no more for me" isn't the worst thing.

        I thought we're talking about some heavy-weight programmers (in a matter of skill, not body weight) that can write extremely useful modules. I would like to think that they can read an email and that they probably have some program that has a "reply" function or can

        • There is no general purpose agreement that by uploading something to PAUSE you grant permission for anyone with spare time and the desire to analyze what you uploaded has the right to send you automated e-mail as he or she sees fit.

          That fails the categorical imperative test. You may not be a Kantian (I'm not), but it's still a useful gauge for behavior.

          • There is likewise no agreement that by uploading something to PAUSE you grant permission for non-automated emails either. Or to judge your code, or to index it for searching, or to do anything else.

            I don't have the fancy book learning, so I had to look up most of your second paragraph on wikipedia, but I think it's total hyperbole to suggest my proposal imposes some kind of categorical imperative.

            I've suggest nothing of the kind.

            • The idea of the Categorical Imperative is essentially to guide your actions by asking the question, “would/could I want the action I’m going to take next to be raised to a universal law?” (ie. everyone has to do it all the time). So the question in your case would be, would/could you want everyone to constantly invent email notification services such as the one you are about to build? As in, how would that affect you, your inbox, and your email address?

              And in this case, if these notification services actually follow all the same constraints as the one you proposed (incl. implicit ones; too many to bother to list them here – I wrote a paragraph and still wasn’t done when I stopped and deleted it), I would say the answer is: sure, why not?