|The stupid question is the question not asked|
Re: Perl contract problemsby Elgon (Curate)
|on Sep 26, 2002 at 15:48 UTC||Need Help??|
Well we have all got our knickers in a twist here, haven't we? The technically correct, but not necessarily useful, answer to your query is 'it depends.' Not very helpful I agree but read on...
As has already been noted, unless you put in some nasty clause into the contract about the IP rights to the code belonging to you, all modification must be done by you or your authorised representative etc... then they can do whatever the hell they like to the code, either themselves or via another contractor and there is very little you can do about it. BUT they cannot force you to do anything to the code that you haven't included in the contract - provided that you've reasonably commented the code in line with good development practice - unless they have some kind of leverage, non-paying of bonus, witholding other forms of payment etc...
This leaves you with several options...
Personlly, I'd stay and comment the code: This should at least engender some goodwill from the PHB and will keep you in gainful employment for a while longer. If they really want to give some other muppet the code to ply with, they will anyway - this way they will at least consider asking you to come back and do the job (if you want to...)
The main point here is that the contract should clearly state what the expectations of the company are and what should constitute a reasonable fulfilment of these criteria. That way if things get nasty, chances are that their lawyers will tell them to settle out of court.
PS - IANAL, usual stuff about not being held responsible for believing me yada, yada yada.
"What this book tells me is that goose-stepping morons, such as yourself, should read books instead of burning them."