4 ms·
My single biggest incentive when I'm writing open source code is that I want to NEVER have to solve the same problem again, for the rest of my career, no matter
by simonw 4y ago
My single biggest incentive when I'm writing open source code is that I want to NEVER have to solve the same problem again, for the rest of my career, no matter who I am working for in the future.
That's why I chose the license that seems least likely to prevent me from being able to use the code I've written (currently Apache 2).
- goodpoint 4y ago> That's why I chose the license that seems least likely to prevent me from being able to use the code I've written (currently Apache 2). That's incorrect. As the upstream author you have every right to use your own code any way you want.
- bogwog 4y ago> As the upstream author you have every right to use your own code any way you want. Well, that depends on if the project accepts pull requests, and whether they have something like a contributor licensing agreement in place.
- goodpoint 4y agoI wrote "your own code". Obviously if you accept contributions from others it's different.
- b3morales 4y agoI think the parent is alluding to a situation where their employer has copyright for the code written on the job. If you take your own previously-written code and just "submit" it to the codebase, you've created a legal snafu for yourself if you ever want to use that same code again elsewhere. Of course you can take your code and license it to said employer in whatever way you both agree on. But this is going to be much easier if the code is already publicly available to everyone, with a known license: the employer doesn't need to even care really who the author is, just the license.
- goodpoint 4y ago> If you take your own previously-written code and just "submit" it to the codebase, you've created a legal snafu for yourself Not at all. The code you are going to submit already has a license file attached. Just update it with an accepted FOSS license before the submission. You don't have to provide any special license or make it public.
- b3morales 4y agoAs I said > Of course you can take your code and license it to said employer in whatever way you both agree on. but that's likely to be a manual step with a lot of raised eyebrows, frowns, and questions involved.
- simonw 4y agoNot if I was writing it for someone else's closed source project at the time.
- em-bee 4y agofor the same reason in one job i was able to change my employment contract to include a guarantee that all code i write on that job will be released under the GPL i thought that way i would always be able to use the code in my own FOSS projects but i would also not be able to sell out and make my work proprietary (since it would contain GPL code owned by my employer) this may seem less beneficial than an apache license but it was aligned with the company goals as far as my work was concerned, so i essentially had them put a verbal promise into writing, and i thought it was a neat way to commit myself to FOSS
- LawTalkingGuy 4y agoMakes sense. There are two broad classes of code, actual standalone projects, and handy code you don't want to rewrite at each job. The latter really fits BSD or Apache - you're trying to break down as many barriers to use as possible and you aren't concerned about receiving contributions.
- jlarocco 4y agoI don't think that's necessary, though. As the original creator, you're the "owner", not a licensee. As the owner you reserve the right to re-license it to anybody you'd like, under any license you'd like, as long as you don't give that right away. At a job, or on a contract, the employment agreement or the contract will almost always says you're giving that right to them in exchange for compensation.
- LtWorf 4y ago> My single biggest incentive when I'm writing open source code is that I want to NEVER have to solve the same problem again, for the rest of my career, no matter who I am working for in the future. You can tell your company to either buy a proprietary license from yourself or reimplement the whole thing.
- cxr 4y ago> I chose the license that seems least likely to prevent me from being able to use the code I've written (currently Apache 2) You won't be able to use it if the future project is under a GPLv2 (or GPLv2+) requirement, since Apache 2.0 and GPLv2 are not compatible.