Re^3: When is it time for the CPAN?

...and it expands your horizons and imposes disiplines that you might otherwise miss. All that guff you have read about testing and documentation suddenly becomes relevant.

A plea though: a CPAN module is for life, not just for Christmas. Please only put stuff on CPAN if you intend to maintain it and look after your users. When you place a module on CPAN you take on a responsibility.

Comment on Re^3: When is it time for the CPAN?

Replies are listed 'Best First'.
Re^4: When is it time for the CPAN? by stevieb (Canon) on Sep 11, 2009 at 12:58 UTC
Thanks cdarke, I truly appreciate the feedback. It's going to take me a month to get everything together, de-customize certain aspects and better my documentation. That in itself will be a learning and betterment experience, so once that is done, I'll have a better idea of where things should go. Point well taken about the commitment/responsibility angle, and if I do put the code on CPAN, it will be because I'm ready and prepared for such a task. Cheers, Steve	[reply]

Replies are listed 'Best First'.

Re^4: When is it time for the CPAN?
by stevieb (Canon) on Sep 11, 2009 at 12:58 UTC

Thanks cdarke,

I truly appreciate the feedback. It's going to take me a month to get everything together, de-customize certain aspects and better my documentation.

That in itself will be a learning and betterment experience, so once that is done, I'll have a better idea of where things should go.

Point well taken about the commitment/responsibility angle, and if I do put the code on CPAN, it will be because I'm ready and prepared for such a task.

Cheers,

Steve

[reply]