830
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Jun 2024
830 points (97.9% liked)
Technology
55610 readers
2583 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
It's a bit odd, but isn't it equivalent to forking and putting up a fork elsewhere?
I guess I don't see the problem.
It depends on the software license.
Does it though? You can still put up a fork somewhere else as long as you uphold the license right? Unless I guess in the case where the license explicitly disallows forks, but I don't think that's very common (can you even do that?).
Forks are derivative works (quite obviously) so yes you can forbid them via license terms. Whether or not that's still open source, take it up with OSI. I vaguely recall that at least once upon a time there was some project that required modification to the code to be published as separate patches and it was generally accepted to be open source don't ask me which.
Most GitHub repos don't have a license, meaning you are not licensed to do anything with them. Rehosting them would be the same as rehosting an image you don't have a license for.