4 ms·

I always choose permissive licenses for personal project, and I often avoid depending on other projects that aren't permissive. If I want to know that, if I nee

by 0xTJ 1y ago

I always choose permissive licenses for personal project, and I often avoid depending on other projects that aren't permissive. If I want to know that, if I need to, I can grab the code and change something. And I want others to be able to remix what I make as needed. The more limitations added on a license, the less open it is.

Panzer04 1y ago
Only for the next developer. They can do whatever they want, but they aren't obligated to contribute anything back.
GrantMoyer 1y ago
> And I want others to be able to remix what I make as needed. The more limitations added on a license, the less open it is. It's unintuitive, but permissive licenses are not the best way to acheive this. GPL's "limitations" are designed to maintain the right and abilty to remix code for the end user. So if say Microsoft forks your library and its fork becomes more popular, they can't make it proprietary after capturing the market and effectively stop people from remixing what you made.
- bigstrat2003 1y ago
  > So if say Microsoft forks your library and its fork becomes more popular, they can't make it proprietary after capturing the market and effectively stop people from remixing what you made. Neither can they stop people from such remixing if the project used a permissive license. The GP's project will still be there, still freely available for anyone to use however they see fit. Nobody is stopped from using it in any way.
  - pabs3 1y ago
    The GPs project will become less relevant as the Microsoft fork becomes more popular, when it is fully irrelevant due to incompatible changes they can rugpull and everyone will have to pay them.
consp 1y ago
I would like a relatively permissive software license which forbids any profiteering (CC-NC but then strictly software). I'm fine with people using my code, not fine with companies profiteering off my work. If you want to use it commercially, pay for it.
- 0xTJ 1y ago
  If it can't be used commercially, then that's not an open-source license. If you choose to license your work that way, that's your choice, but you're not making something open-source.
  - simondotau 1y ago
    Who said it can’t be used commercially? Just because they can’t profit from it doesn’t stop them using it.
    - 0xTJ 1y ago
      From the post to which I replied: "If you want to use it commercially, pay for it.". I am replying to them talking about a license that prevent commercial use.
      - simondotau 1y ago
        Ah, my mistake. It's an interesting idea for a license. "Free for non-commercial use" is an idea often used in closed source software, but not open source. If a software license like this doesn't already exist, it should, so that software developers can easily choose it.

by 0xTJ 1y ago

Panzer04 1y ago

Only for the next developer. They can do whatever they want, but they aren't obligated to contribute anything back.

GrantMoyer 1y ago

> And I want others to be able to remix what I make as needed. The more limitations added on a license, the less open it is. It's unintuitive, but permissive licenses are not the best way to acheive this. GPL's "limitations" are designed to maintain the right and abilty to remix code for the end user. So if say Microsoft forks your library and its fork becomes more popular, they can't make it proprietary after capturing the market and effectively stop people from remixing what you made.

bigstrat2003 1y ago
> So if say Microsoft forks your library and its fork becomes more popular, they can't make it proprietary after capturing the market and effectively stop people from remixing what you made. Neither can they stop people from such remixing if the project used a permissive license. The GP's project will still be there, still freely available for anyone to use however they see fit. Nobody is stopped from using it in any way.
- pabs3 1y ago
  The GPs project will become less relevant as the Microsoft fork becomes more popular, when it is fully irrelevant due to incompatible changes they can rugpull and everyone will have to pay them.

consp 1y ago

I would like a relatively permissive software license which forbids any profiteering (CC-NC but then strictly software). I'm fine with people using my code, not fine with companies profiteering off my work. If you want to use it commercially, pay for it.

0xTJ 1y ago
If it can't be used commercially, then that's not an open-source license. If you choose to license your work that way, that's your choice, but you're not making something open-source.
- simondotau 1y ago
  Who said it can’t be used commercially? Just because they can’t profit from it doesn’t stop them using it.
  - 0xTJ 1y ago
    From the post to which I replied: "If you want to use it commercially, pay for it.". I am replying to them talking about a license that prevent commercial use.
    - simondotau 1y ago
      Ah, my mistake. It's an interesting idea for a license. "Free for non-commercial use" is an idea often used in closed source software, but not open source. If a software license like this doesn't already exist, it should, so that software developers can easily choose it.