this post was submitted on 22 Aug 2024
48 points (98.0% liked)
Forgejo
140 readers
1 users here now
This is a community dedicated to Forgejo.
Useful links:
Rules:
- Posts must be relevant to Forgejo
- No NSFW content
- No hate speech, bigotry, etc
- Try to keep discussions on topic
- No spam of tools/companies/advertisements
- It’s ok to post your own stuff part of the time, but the primary use of the community should not be self-promotion.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'd opine that the MIT license has no requirements about avoiding ambiguity. That's kind of its thing, it's as unobtrusive as possible and minimizes the amount of having to think about license compliance minefields.
And incidentally they have done quite a bit to avoid ambiguity, in readme.md:
though they also distribute binary-only copies.. the main website even recommends downloading the binary. not even a tarball, just the plain binary. which even in old versions don't contain an MIT license at all. Even a hexdump of the binary does not contain any representation of the MIT text. I think that's actually an MIT license violation?
I think that's probably fine actually since the place they are distributing the binary from (Codeberg releases) has a copy of the licence easily available.
Err yeah of course not. The issue with creating ambiguous or conflicting legal requirements is that they might not get applied how you'd like if it went to court. For example Amazon might fork Forgejo and keep it closed source, saying "we copied the individual source files and those are MIT licensed" and they might win. The license text doesn't have to say anything about that for it to be true.