Timeline for Is it ok to use my open-source projects as dependencies at work?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2021 at 13:46 | comment | added | Ralph Bolton | Assuming you own the copyrights, and so can set licenses, you could offer to give the company a perpetual, non exclusive license of their own for the software (you'll need this drafting by a lawyer, but it's quite easy). You can go on to give it to the world on any license you like, but the company gets a "do what you want" type license. | |
| Nov 29, 2021 at 5:18 | comment | added | Flydog57 | When you ask that question, you want to be very clear how your work is licensed. In particular if the work is licensed under the GPL or other license that carries similar restrictions, you need to be very clear what those are. | |
| Nov 28, 2021 at 17:59 | comment | added | EvilSnack | To add to this: Don't bring your off-the-clock work into work until you have gotten an answer from management, and until the answer is in writing, you do not have an answer. | |
| Nov 26, 2021 at 18:15 | comment | added | DWGKNZ | The added bonus of this is that it puts the ball in the company's court. Once they are aware that you have a solution available the onus will fall on them to decide whether they should use it and what the risks and liabilities that need to be mitigated are. | |
| Nov 26, 2021 at 8:59 | history | answered | Philip Kendall | CC BY-SA 4.0 |