Re: Need arguments to keep my modules on CPAN

[Herkum]

As mentioned before, companies can claim code that was written as it relates to their business, even if it is in your free time. However, I would be very clear about the modules as they relate to their business.

For example does the module you put on CPAN really relate to their specific industry. You make a screw, it would be hard for them to claim that their Accounting business would depend on the type of screw that you just built, too generic. Maybe if you wrote some accounting type modules, there is business relevance but not something general that anyone in other industries can use as well.

Be polite about it, but make sure that they understand, they cannot lay claim to everything that you wrote just because they say so. Negotiate, but if you leave there really is nothing to prevent you from reimplementing those modules again on your own time as long as they are not trade secrets or patents.

[Limbic~Region]

Herkum,
I would like to point out for those reading this thread that it very much depends on what you as the employee has signed regarding intellectual property. I know in this case, dk indicated he had a verbal agreement but didn't mention what was signed when onboarded with the company. If you sign a legally binding contract, as a number of employees in IT do, not only can the company lay claim to what you write on your free time - they can do so even after you are no longer employed by them. A non-compete and intellectual property contract is usually very specific in terms of time and area so it is best to read carefully before signing.

[Anonymous Monk]

or NOT signing...