IMHO, the question is quite a simple one.
If you have a written (or oral) agreement which does not explicitly state
that you should hand over the source code, you should not need to do so.
If you have been hired to do a product, then the Product is what you need to
hand over. Nothing else.
Some
Give them the code. What are they going to do with it?
1. Hire some other dir developer who is equal to or beyond
you in ability,
and will likely just toss your code in the dumpster while
replicating the
functionality in his own style.
2. Is not as good of a coder, and will struggle to
Hi,
thanks for the replies. Wow, such a divide. :)
While I agree with Kurt's comments re: 'we constantly give away our lingo to
the members on the list', lists are a pretty unique environment (IMHO), with
the purpose of asking the community/like-minded individuals for help and
putting something
code snippets.
I bet our lives would be hell without this far-out cooperation...
Give something, and get loads in return.
- Original Message -
From: Karina Steffens [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 23, 2001 10:53 AM
Subject: RE: lingo-l OT: Giving away
You know, I even go a step farther and comment out all of my code as to
what each bit is doing.
I've never had an issue where someone ripped apart my stuff so they could
do it themselves -- although I was paid to train a few people in
basics...I had no problem with that.
Personally, I have
Basically, I have done three things in the past:
1. Give the source code to them for 10x development cost (which was clearly
stated in the contract prior)
2. Gave them the code but ran it through an obscufier first. This one was
only when the client threatened a lawsuit because they failed to
all contract and assume nothing and charge the clients if they want to
see the code.
Ike Eisenhauer
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of [EMAIL PROTECTED]
Sent: Thursday, August 23, 2001 2:49 AM
To: [EMAIL PROTECTED]
Subject: RE: lingo-l OT
it may be annoying, but if you are a subcontractor, you always have to hand
over the code, ( i thought).
even if you have a direct contact with someone, the debate is what you are
selling, if you are selling the source with the finished product, you
should draw a contract with this
I'm interested to find out how everyone handles clients'
requests for source files.
this comes up here fairly frequently. some folks never give out
source, some charge extra for it and some always give it to the client
(after the final check is delivered cashed of courst). personally I
have
NEVER GIVE AWAY YOUR SOURCE CODE THAT SMALL MEDIA DEPARTMENT TODAY WILL
BECOME A BIG ONE TOMMORROW AND REUSE YOUR LINGO TEMPLATE AS BASIS FOR OTHER
PROJECTS. YOU MIGHT BE ABLE TO SELL THE CODE TO THEM, BUT REMEMBER THEY WILL
STILL IT. I HAVE SEEN IT HAPPEN BEFORE AHEM!
On 8/22/01 1:36 PM, Ian
I lean towards the 'don't do it!' school of thought but I have done jobs
where the client insisted on having access to the source code.
One compromise that we came up with once was to put all the source code on
a disc which was then held in trust by a mutually agreed firm of solicitors
NEVER GIVE AWAY YOUR SOURCE CODE THAT SMALL MEDIA DEPARTMENT TODAY WILL
BECOME A BIG ONE TOMMORROW AND REUSE YOUR LINGO TEMPLATE AS BASIS FOR OTHER
PROJECTS. YOU MIGHT BE ABLE TO SELL THE CODE TO THEM, BUT REMEMBER THEY WILL
STILL IT. I HAVE SEEN IT HAPPEN BEFORE AHEM!
LOL. Get over
12 matches
Mail list logo
