this post was submitted on 19 Oct 2024
38 points (100.0% liked)
Open Source
31372 readers
42 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
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
What does "better coverage" mean? A compilation or collective work is not a modification and is exactly what the license allows. Do you want hinder that? Can it be called Open Source, if you don't even allow the distribution of your work? First it would be good to know what your goal is.
How about a license which will also make the collective work into the same license as the work itself? Coverage as in it could reach more in terms of copyleft-ness.
I struggle with the goal here. If you don't want hinder anyone from using your work in collective work, then its basically already covered in the sense that it is allowed. I see only a reason to cover that, if you actively want to hinder your project from distribution in collective works. With CC-BY-SA the license allows the distribution of your work in any collective work.
Can you describe a specific situation as an example you want to solve?
It's better for OP to explain, but from what I read they don't mind it being used in a collective work, but they want to make sure that collective work will also be CC-BY-SA. What from what they read it is no guarantee.
So you mean like GPL to enforce same license when reused? I don't think anyone using works licensed as CC-BY-SA is allowed to relicense it under a different license: https://creativecommons.org/licenses/by-sa/4.0/
CC BY-SA 4.0 is one way compatible with GPLv3.
It does mean that anything released under older CC SA licenses aren't, so they can't be used in GPL projects. And MIT isn't compatible at all.
Wow I read that. And it means one can take the CC-BY-SA 4.0 work and relicense it as GPLv3. Its' not just about being compatible in a project, it literally means re-licensing is allowed. But that is only for the adapted work. Meaning if you change something from his work, you are able to release your work as both licenses. While the original untouched work is still CC-BY-SA 4.0 only. So a collection has no rights to make changes to its original license.
It means a GPLv3 project can use something licensed as CC BY-SA 4.0 by converting it to GPLv3, as is required. E.g using a CC BY-SA photograph as a background or a splash image in a program.
And while you technically can't take the original, yeah, practically everything except "here is the image file alone in a folder" counts as modifying and a derivative work. Resize it, crop it, change a .png to a .jpg etc - all modify the original work.