4 ms·
> except that you can’t use it at work due to the license Just to clarify: If you hold the copyright over the code, you can change the license to whatever you
by kibwen 2y ago
> except that you can’t use it at work due to the license
Just to clarify:
If you hold the copyright over the code, you can change the license to whatever you want, whenever you want.
In other words, if you are the lone dev of a library that has been GPL for 20 years, and then you get hired, and you want to use that library at your job, you can just make a copy of it and say "this copy is yours to do with as you please, have fun". You don't even need to mess around with dual-licensing. Licenses affect only people who aren't the copyright holder.
- skybrian 2y agoThat's true, but it sounds rather informal. A risk-adverse company would probably want you to assign copyright formally. They need to know what they own and what they have a license for. Otherwise, the situation will be confusing when someone comes along years later. "Hmm, this code looks familiar. Wait, why do we have a copy of GPL-licensed code in our system, with the licenses removed?"