Interested in maintaining/updating a perl module?

lachoy on 2006-06-25T03:59:25

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:

• Workflow
• Class::Factory
• Class::Observable (and I'd be happy to provide a signed and dated document declaring that MJD's criticisms are about my crappy code, not yours)

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 cwinters.com; read original

---

Workflow

jonasbn on 2006-06-25T06:15:37

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.

jonasbn

Re:Workflow

lachoy on 2006-06-26T12:24:43

Great, it's yours! I'll hook up with you over email for the gory details.

Class::* maintenance

Aristotle on 2006-06-25T12:22:43

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.)

Re:Class::* maintenance

lachoy on 2006-06-26T12:24:03

I have another taker for Class::Factory, but Class::Observable is yours!