| ▲ | orthogonal_cube 3 hours ago | |
I miss working at a place which allowed this. Some employers get tangled up in just the legal review process. Once I asked permission to submit a patch to a project and it had quite an interesting email trail. It came down to a single question: if the patch was written during hours billed to a customer for the purpose of fixing a bug in a deliverable product, and the library being patched had to be recompiled and delivered with the source code, and the contract states that all work and intellectual property associated to the product would be transferred to the customer, do we have authority to release the patch in the public domain? Legal didn’t want to answer it. | ||
| ▲ | bluGill 2 hours ago | parent | next [-] | |
The customer would probably prefer that you released it - that would mean next time they need a change the previous is up streamed. Note that the resulting patch is almost assuredly not public domain and you should never use that term. | ||
| ▲ | bandofthehawk 2 hours ago | parent | prev [-] | |
[dead] | ||