Quote:
Originally Posted by XD2
Sometimes I use php classes I wrote myself to acheive someones desired effect so why should I let that person resell it without consulting me.
I did mention this only applies to larger scripts and systems, small scripts don't really concern me. But I always ask for the above reason. If someone needs a script that will do a job and it is for their use and I have code already that can do it I can/will code for a much lower price.
However if someone wants a script that is exclusive to them and they hold the rights and can do what they want with it, then yeah I will be charging slightly more to cover my time.
It works the other way aswell, I have done many scripts for a fraction of the price if the person was happy for me to resell it or use it as part of another system. I am not just expecting my client to tell me their intentions, I state mine aswell. I just find it better to know whats happening from the start.
Anyway this is only my opinion.
|
And your opinion is absolutely correct and fair. It all comes down to the license agreement. If there is none, I'd tend to side with the person paying for it to do whatever he wants with it. However, I have a feeling that brassmonkey's situation is similar to what you bring up above. That is, the contractor had a majority of the work done in a personal library to achieve the implementation and therefore was able to do it cheaper as a per license script. The fault lands on the developer if he did not properly specify the intended use of the script and also, if he was so serious about owning the rights to the script, there should be some sort of licensing mechanism built in. If there were, it would be obvious that the script was intended for one site and not to be resold--because it would be impossible.
So my
, without knowing more, I'd side with BrassMonkey but I think there's a lesson to be learned by inexperienced IC to properly state how they intend their software to be used before agreeing to a project.