|XP is just a number|
self developed modules for client useby arc_of_descent (Hermit)
|on Feb 05, 2006 at 20:02 UTC||Need Help??|
arc_of_descent has asked for the
wisdom of the Perl Monks concerning the following question:
What would be the best way to deal with the following scenario?
A coder has been developing her own modules for use in her soon to be released product/service. Along comes a client (the coder is a freelancer), and wants a program which could benefit greatly from one of the modules.
In short, the client would want all code delivered as his own property. Now I could very well put some subroutines of the modules inside the Perl script, but then its more work for me, and I would love to deliver the script along with the modules exactly as I wrote them. This solves the client's problem as well as mine, as I would just need to write s simple script to access the module.
Any legal stuff to watch out for here?
The above module is just a small example and the bigger question deals with my codebase of modules, snippets, and utilities. I save my time by reusing my code libraries, but still don't want them to be delivered to a client as a module, but then extra work for me.
Sorry for not being very clear about this.