-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add standard opensource scaffolding #1
Comments
WRT licencing: The rust community has mostly standardised around dual licencing Apache2/MIT for maximum compatability/permissivenes. ie contributions come with explicit patent and relicencing grants via the Apache 2 on contributions while also retaining downstream GPLv2 compatability via the MIT licence. I suggest we follow suit. In terms of what this looks like i the the repo we'd need LICENCE_APACHE and LICENCE_MIT file and we'd probably want a COPYRIGHT file with something like the following (ripped off from the rust-lang/rust repo itself) in it
|
Hm! Interesting. I like their wording. Nice and clear. And links to licenses versus copy-pasta makes me happy. The dual-license thing fascinates me. I've only seen a dual open-source and closed-source license set done before, and it was defined very carefully in the codebase. In case anyone else reading this wants a further discussion, here's the Rust discussion: https://internals.rust-lang.org/t/rationale-of-apache-dual-licensing/8952 |
The
is also fairly significant, it means there's none of the awkward copyright assignment form to fill in. It doesn't negatively effect our ability to relicence as the code is MIT/Apache2'd anyway, but just to call out there's an explicit choice being made there. |
In no particular order Add
Docs/legal scaffoding:
Technical stuff:
Rust stuff:
Note we don't need all of this up front, but we should at least have the legal stuff and a README
The text was updated successfully, but these errors were encountered: