| Chris Hedemark on Fri, 03 Jan 2003 19:30:33 -0500 |
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In my experience, most employers will make you sign a form when you start working there full time. But you have the option to change the wording on the agreement (yes, believe it or not, you can negotiate these things). You can specify that projects you have already been working on in your own spare time still belong to you (and detail those programs). If you start a project *after* signing an agreement like this, well, not a smart thing to do without first getting written permission from your employer and have them waive rights to the software. If it is outside of their business interests this may not be a problem to procure.
I have been working as an independent contractor for a company almost full time for a few years now, I am just thinking about taking the position as an employee and getting on a payroll so I don't have to worry about taxes, but I am worried about rights to my code. For example, I have *heard* that anything I write on my own time belongs to my employer, etc, things like that. On one end, what if I put together my own software product which I want to sell, does profit really belong to my employer, on the lower extreme, what if I write my own library and decide to use it in a project for work, how do I keep that part of the code as my own. ....Just examples, does anyone know where I can find more info on this?
iD8DBQE+FiXdYPuF4Zq9lvYRAl8WAJ9XSJHPWYX2P3NB51bOS2ogi1tP1gCg5wc3 6vduaSpHAwZRf6NlQdDIkTc= =QFYr -----END PGP SIGNATURE----- _________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|