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.

Patches no longer welcome (I reckon we can do better) 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • I have my own svn repository [bulknews.net] for my CPAN modules and other tools, and having to create accounts for bug submitters will be painful.

    We need fully functional FreePAN? Or use OpenID-like distributed authentication system for svn auth? (like using PAUSE authentication system to give a commit bit to my svn repository)

    • Re:freepan? (Score:1)

      by Alias (5735) on 2006.04.14 23:04 (#47190) Homepage Journal
      Well, firstly I expect the number of people to actually get an account, who are willing to go beyond just complaining and actually fix it to be low, a dozen or so.

      And also I'm only doing it this way because I think I've finally found something (Insurrection) that does things the Right Way, and with low enough overhead, that it will be easier than the alternatives.

      All the accounts are based on email addresses. So it's as simple as typing in an email address, and that's it. It generates default passwords, mails it to the person, shows them how to update the password, and so on. And simply by insisting that people have their CPAN email as their account for my SVN, I ensure that the account will follow them around to wherever they go.

      Before now, I agree though. Going through 10 pages of SourceForge cruft to add an account was too painful. This only works for me because of Insurrection.
      • Well, firstly I expect the number of people to actually get an account, who are willing to go beyond just complaining and actually fix it to be low, a dozen or so.

        I'd be surprised if anyone gets one, given that you said they must have a "bug-free" module.

        • That was a joke right?

          Because you've got two of them :)
          • Oh, so "bug free" means all the tests pass. :) (The tests don't cover much in my modules.) Thanks for clarifying. I had in mind...a couple authors on CPAN might have a bugfree module...
            • No, it means the module has an empty RT queue.

              Which obviously is a highly imperfect way of restricting people, but I'd like to set some sort of minimum standard.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.