Sam, I like this approach! That could work, but....unless it was in place with the originating party....the problem still exists, or rather it can be picked-up only from this specific point forward...I've not found a lot of companies open to these stipulations, but if you can swing it then more power to you...
GB, Bubba From: Samuel Neff Sent: Wednesday, June 11, 2008 9:50 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] OOP and Work for Hire Depends on the work for hire agreement. A good one would designate that the developer retains a perpetual non-exclusive rights to any works previously developed and used in the project and all general purpose code such as libraries and generic controls that are not unique to the business requirements or design of the project. Sam ----------------------------------------------------------------- We're Hiring! Seeking passionate Flex, C#, or C++ (RTSP, H264) developer. Position is in the Washington D.C. metro area. Contact [EMAIL PROTECTED] On Tue, Jun 10, 2008 at 5:27 PM, Amy <[EMAIL PROTECTED]> wrote: I was recently asked to sign an agreement that would designate a Flex project as "Work for Hire." I.e. I would not retain any ownership of the code I wrote for the project. This seems to defeat the purpose of OOP, if I create a whole body of code that I can't then reuse. How do most Flex developers handle the idea of Work for Hire? Thanks; Amy
