Commentary on copyright / licenses for regular contracted application applications

Question

I am working on a contract that needs source code for the application that I am writing. For the new files that I write for the client, I give them copyright. However, there are some utility files (for OS abstractions, such as threads). I use what I developed myself (and not on the client’s penny). I want to keep the right to use these files for my future projects or future contracts.

My question is: what type of license and copyright do I provide at the top of the source code file? I am looking at something similar to a Boost Software license:

Copright (c) 2009 [my legal name]

It is hereby provided free of charge [client's legal name] in order to use, reproduce, modify, display, distribute, execute and transmit the Software, and prepare derivative works of the Software and permit third parties for whom the Software is provided for this, all are subject to the following:

The copyright notices in the Software and all this expression, including the aforementioned license grant, this limitation and the following disclaimer, should be included in all copies of the Software in whole or in part and all derivative works of the Software, except when such copies or derivatives works exclusively in the form of machine-executable code of an object generated by the processor of the source language.

" ", - , , , ​​ , , . , , , , .

? - , ?

, , - (, ). , , , .

, , ( , , ).

, , , , .

Answer 1

, - . .

Answer 2

, . .

, , , .

---

: , , . , , , , , - , . , , .

, , , - , -, , -, , .

Answer 3

MIT , . , , , - -.

.

, -, , , . , , , , , .

I assume that the offer “as is” will not actually save you from liability if you intentionally sell them a code that wipes their hard drives and sends emails to death threats to all your customers; -)