this post was submitted on 11 Jul 2024
145 points (96.8% liked)
Open Source
31224 readers
338 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Can you explain how this works?
Say a contributer downloads v1.1 of floorp, checks the code and makes a PR. Floop sees this and accepts the change and publishes v1.2. If a new contributer downloads floorp, they get v1.2 where they can see the previous merged PR.
How is it that they are not giving back? I can understand that not being on a repository makes it difficult but it's technically possible.
The contribution is automatically relicensed under that licence and as such, it remains property of the org that made floorp, so they're technically getting free labour, support and maintenance
Sounds like bsd with extra steps
It's way worse.
With bsd you could at least take the code you got and make your own fork, with these shared source licenses you get nothing.