4 ms·

> 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

> 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 ago
  I wrote "your own code". Obviously if you accept contributions from others it's different.
b3morales 4y ago
I 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 ago
    As 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 ago
Not if I was writing it for someone else's closed source project at the time.

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 ago
I wrote "your own code". Obviously if you accept contributions from others it's different.

b3morales 4y ago

I 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 ago
  As 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 ago

Not if I was writing it for someone else's closed source project at the time.