|
|
|
| P is for Practical | |
| PerlMonks |
comment on |
| ( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
|
I tend to agree with [id://juerd] on this one. You're likely to use plenty of CPAN modules, and that code has been donated for free to everyone, as has Perl. That spirit seems to conflict a little with a hard line on who "owns" other code.
If it were me, I'd push for make sure you can share any generic code that might be useful. I'm not talking about the business stuff that might reveal something, but some module that might come out of your effort. I don't work as a contractor, but we hire them where I work. Our agreements tend to be verbal, not written, but we've had a long-term relationship with one contractor. We would never try to re-sell code, so that isn't an issue. We've had the best relationship when we keep the code he's written, but he can take bits and pieces if it suits him--and he asks to make sure it is OK. In one case some code turned into a module and ended up on CPAN as well. The only restriction we've had to include is that we don't get mentioned specifically in any code or modules that are shared. The main reason here is we don't want to get hit with any potential liability if someone down the road used a module, had problems, and wanted to sue someone. This requirement comes from the higher-ups as a sort of condition for us playing in the open source sandbox and contributing back. In reply to Re^2: On Code Ownership
by cbrandtbuffalo
|
|