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.
  • I think you should let him make the final decision to publish. He'll feel more committed to it, then. You've sent him private encouragement; I'd put a little bit of public encouragement on the newsgroup. Take opportunities to mention he has the module (with parenthetical statements like, (Mike, when are you going to release?)).

    Make sure he's fully bought into the licensing scheme. I don't think anyone should release code if they're not clear on allowing everyone to do what they want with it. (Sell it on CD-ROM, use it in a corporation, make modifications without returning them to the author, and other things people sometimes don't like.)

    If you do it for him, he might conceivably get upset or feel pressured. You could volunteer to walk him through the process, though.

    I've never released anything publicly (except some code here in my journal), but I've hung around long enough to know what to do and to have no reservations when the time comes. Actually, I've got one three line patch in Perl, but that's it.

    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers