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

use Perl Log In

Log In

[ Create a new account ]

lachoy (1663)


I am actually Chris Winters; I am actually living in Pittsburgh, Pennsylvania, USA; I am actually married and have three cats. (Guess what one of them is named?) I am the "OpenInteract" guy, which could be good or bad.

Journal of lachoy (1663)

Saturday June 24, 2006
10:59 PM

Interested in maintaining/updating a perl module?

[ #30033 ]

So I'm not using Perl at work and will not be for the foreseeable future. And my work is basically taking up all my spare brain cycles. And home life is getting more complicated in the near future.

As an entirely predictable result my perl modules haven't been updated in a while. For some it's not a big deal, for others it is. In particular, I get an email about the Workflow module about every week or two. And I shamefully just let them sit there. (Yes, I can be an asshole.)

So I need to get out of the way. Let me know if you're interested in maintaining:

Once you take it over, it's yours. I won't butt in and tell you how to do anything, cross my heart. (Ask Stevan about DBD::Mock.)

Posted from; read original

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.
  • I would be very much interested in maintaining Workflow, since I am using it professionally and I plan to be using it even morein the future.

  • I’ll happily take over maintenance for both of your Class::* modules. They seem simple enough that it shouldn’t be a big burden to maintain them. Do you have any todo lists for them, other than the two ::Observable bugs in RT? (I think I know how to fix them; the hard part will be to write failing tests for the panic bug.)