Python Interview Questions
rosuav at gmail.com
Tue Jul 10 18:05:40 CEST 2012
On Wed, Jul 11, 2012 at 1:55 AM, BartC <bc at freeuk.com> wrote:
> There's also the risk of mixing up software created at home, with that done
> at work, with all the intellectual property issues that might arise.
You just make the matter clear from the beginning, for instance:
what's done at work stays at work, and copyright is assigned by the
act of pushing to the repository. I've lifted oddments of code from my
home projects to use at work; it's no different from using skills
learned at home, which is exactly what a programmer is being paid for.
This is another good reason to make license terms clear and explicit
on every project you ever put a hand to. Doesn't matter who's lifting
code from where to where, it's easy to work out whether it's
permissible or not.
More information about the Python-list