A client asked me to create some software (more like a module) which could be plugged in to their system. They stated that they didn't care about language or platform. So I told them that I would compile it for Windows and deliver an executable. I delivered the product and got paid. Now they want it for Linux and they also want the source code. How would you react to that?
Off-Topic: Releasing source code
Started by ●August 9, 2011
Reply by ●August 10, 20112011-08-10
On 8/9/11 10:50 PM, Peter wrote:> A client asked me to create some software (more like a module) which > could be plugged in to their system. > > They stated that they didn't care about language or platform. > > So I told them that I would compile it for Windows and deliver an > executable. > > I delivered the product and got paid. > > Now they want it for Linux and they also want the source code. > > How would you react to that? >i guess i would negotiate a deal for whatever i think the source code is worth. personally, *every* project i have ever done for anyone (employer or contract), my work product was either source code or a document of a procedure (math equations and step-by-step description). sometimes (nearly all of the time) the deal was non-exclusive, which meant i was free to use the same source code with another client. one client, who had a problem with that, asked me to not ever sell such non-exclusive code to a particular competitor of theirs and i agreed and it's in the contract (as old as it is). i dunno how you can release a working "module" that has some modicum of platform independence without source. -- r b-j rbj@audioimagination.com "Imagination is more important than knowledge."
Reply by ●August 10, 20112011-08-10
On Tue, 9 Aug 2011 22:50:31 -0400, "Peter" <peter@xyzinvalid.com> wrote:>A client asked me to create some software (more like a module) which could >be plugged in to their system. > >They stated that they didn't care about language or platform. > >So I told them that I would compile it for Windows and deliver an >executable. > >I delivered the product and got paid. > >Now they want it for Linux and they also want the source code. > >How would you react to that?Were the deliverables specified in the original contract or agreement? If the deliverables were specified and didn't include the source code, then it would be expected that getting the source code would incur an additional cost. If the deliverables weren't specified, then you may be in a position where the customer expected it and you just didn't deliver it or something. In that case you may have to tread a bit more lightly, but if you bid the job with the expectation of not delivering the source code and priced it as such, then you may be able to negotiate an additional fee for the source. If the customer's expectation was that you would deliver and they would own the IP, but didn't specify such, then you have a negotiation to get through. If they specified that they'd own the work product and that the source was deliverable, then you need to deliver it. So, IMHO, it mostly depends on how the original contract or agreement was set up. If it's nebulous it's going to require a discusion and, well, that's why agreements shouldn't be nebulous. ;) Eric Jacobsen http://www.ericjacobsen.org http://www.dsprelated.com/blogs-1//Eric_Jacobsen.php
Reply by ●August 10, 20112011-08-10
> > Were the deliverables specified in the original contract or agreement? > If the deliverables were specified and didn't include the source code, > then it would be expected that getting the source code would incur an > additional cost.In the agreement (if you can call an email exchange that?) the functionality of the module was specified by the client. They did not specify language, platform or anything else. I quoted a price based on the deliverable being a windows binary (console app). I stated to the client that the deliverable would be an executable file. Client accepted and paid when I delivered.
Reply by ●August 10, 20112011-08-10
On 10/08/2011 2:50 p.m., Peter wrote:> A client asked me to create some software (more like a module) which > could be plugged in to their system. > > They stated that they didn't care about language or platform. > > So I told them that I would compile it for Windows and deliver an > executable. > > I delivered the product and got paid. > > Now they want it for Linux and they also want the source code. > > How would you react to that? > > > > > >They pay you give it to them.
Reply by ●August 10, 20112011-08-10
Peter <peter@xyzinvalid.com> wrote:> A client asked me to create some software (more like a module) > which could be plugged in to their system.> They stated that they didn't care about language or platform.> So I told them that I would compile it for Windows and deliver an > executable.> I delivered the product and got paid. > Now they want it for Linux and they also want the source code. > How would you react to that?I would probably charge 2 or 3 times the original price, with full credit for the original payment. Also retain rights to use the source, modify it, as needed. Someone else mentioned an agreement not to sell to a competitor, which also seems fair. -- glen
Reply by ●August 10, 20112011-08-10
I can think of two cases where releasing source code may not be a good idea. 1. If your customer pays for your software/release by licensing. 2. If your code contains some IP that you want to protect (and which can be sold to other potential customers).
Reply by ●August 10, 20112011-08-10
On Aug 10, 4:50�am, "Peter" <pe...@xyzinvalid.com> wrote:> A client asked me to create some software (more like a module) which could > be plugged in to their system. > > They stated that they didn't care about language or platform. > > So I told them that I would compile it for Windows and deliver an > executable. > > I delivered the product and got paid. > > Now they want it for Linux and they also want the source code. > > How would you react to that?Very cautiosly: 1 writing portable code is a mess 2 releasing source code implies support Whatever you do, make sure to get � clear contract. Rune
Reply by ●August 10, 20112011-08-10
Peter wrote:> A client asked me to create some software (more like a module) which > could be plugged in to their system. > > They stated that they didn't care about language or platform. > > So I told them that I would compile it for Windows and deliver an > executable. > > I delivered the product and got paid. > > Now they want it for Linux and they also want the source code. > > How would you react to that?Give them the source code. Most likely they call you again. Vladimir Vassilevsky DSP and Mixed Signal Design Consultant http://www.abvolt.com
Reply by ●August 10, 20112011-08-10
robert bristow-johnson wrote:> On 8/9/11 10:50 PM, Peter wrote: > >> A client asked me to create some software (more like a module) which >> could be plugged in to their system. >> >> They stated that they didn't care about language or platform. >> >> So I told them that I would compile it for Windows and deliver an >> executable. >> >> I delivered the product and got paid. >> >> Now they want it for Linux and they also want the source code. >> >> How would you react to that? >> > > i guess i would negotiate a deal for whatever i think the source code is > worth. > > personally, *every* project i have ever done for anyone (employer or > contract), my work product was either source code or a document of a > procedure (math equations and step-by-step description). sometimes > (nearly all of the time) the deal was non-exclusive, which meant i was > free to use the same source code with another client. one client, who > had a problem with that, asked me to not ever sell such non-exclusive > code to a particular competitor of theirs and i agreed and it's in the > contract (as old as it is).It is stupid to set the clauses that could not be enforced. The more bullshit is involved in the contract, the less the parties are interested in getting the actual job done. Vladimir Vassilevsky DSP and Mixed Signal Design Consultant http://www.abvolt.com
