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.
  • by miyagawa (1653) on 2006.04.14 14:29 (#47183) Homepage Journal

    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)

    • What's wrong with existing systems such as Open Foundry [openfoundry.org] and Sourceforge [sourceforge.net], both of which offer subversion repositories and account management?

      I'm guessing that you'd prefer to host and control the subversion repository directly, and merely want to out-source the account management side.

      • Yeah, you're right. The main reason I want to host myself is that I really, really want to use (and hack) Trac. I prefer Trac to other ticket/browsing tools like RT/SourceForge/ViewCVS etc.

        Slap me if either of OpenFoundry/SourceForge has a support of Trac yet.

      • I totally agree.

        I've tried SourceForge several times. The PPI family of modules are still in SourceForge, and are yet to be moved back in-house.

        But I find sourceforge overly difficult. The overheads created by their authentication system have driven away potential maintainers or patchers.

        In comparison with the way pugs works, I'm finding more and more that for every minute of effort required, you lose 10% of your potential maintainers (broad generalisation).

        I'm sick of saying "do you have a sourceforge acco
    • 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, mai
      • 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.