Skip to content
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

License change #82

Open
ghost opened this issue Jun 12, 2018 · 22 comments
Open

License change #82

ghost opened this issue Jun 12, 2018 · 22 comments

Comments

@ghost
Copy link

ghost commented Jun 12, 2018

The README currently specifies this as being released under public domain, which can lead to issues in some countries (including the US, where I am). I'm proposing that we release this under MIT instead, as this is the license used by the X11 libraries that are wrapped by this project. Please reply with "yes" if you agree to this change. If I get a "yes" from most contributors but not all, I'll rewrite any remaining contributions myself before pushing this change.


Edit: The main concern is that "public domain" does not provide the protection of a warrantly clause. I don't know of a particular time that this has been a problem, but it's better to be safe.

* [x] @Daggerbot
* [x] @meh
* [ ] @darkstalker
* [x] @alxkolm
* [ ] @mason-larobina
* [x] @SimonSapin
* [x] @jespino
* [x] @francesca64
* [x] @bennofs
* [x] @sleeparrow
* [x] @crumblingstatue
* [x] @Eijebong
* [x] @nox
* [x] @arielb1
* [x] @EPashkin
* [x] @mgsloan
* [x] @joshtriplett
* [x] @myfreeweb
* [x] @nicokoch
* [x] @mbrubeck
* [x] @jdm
* [ ] @wartman4404
* [ ] @aweinstock314
* [ ] @BOTBrad
@mbrubeck
Copy link
Contributor

Yes

@francesca64
Copy link
Contributor

Yes!

unless somebody else takes over as maintainer.

If you want someone to do that, I'm probably a good candidate, seeing as I've become the maintainer of winit (and I imagine winit is probably your biggest consumer?). I also noticed you talking about the idea of a high-level API over in #81 (comment), and you might be happy to hear that I've gradually been creating such an API in an effort to keep winit more maintainable. It's still a bit rough and narrow in scope (since it's only been designed for internal usage), but I've been planning to spin it off into its own crate eventually.

@joshtriplett
Copy link
Contributor

Yes, feel free.

@ghost ghost mentioned this issue Jun 12, 2018
@mgsloan
Copy link
Contributor

mgsloan commented Jun 12, 2018

Yes

6 similar comments
@jespino
Copy link
Contributor

jespino commented Jun 12, 2018

Yes

@EPashkin
Copy link
Contributor

Yes

@crumblingstatue
Copy link
Contributor

Yes

@Eijebong
Copy link
Contributor

Yes

@meh
Copy link
Contributor

meh commented Jun 12, 2018

Yes

@nicokoch
Copy link
Contributor

Yes

@valpackett
Copy link
Contributor

Yes

By the way, the Cargo.toml files say

license = "CC0-1.0"

Which is not the same as just "public domain". Like other similar licenses (e.g. Unlicense), CC0 contains "fallback" terms for jurisdictions where you can't put your work into public domain.

@nox
Copy link
Contributor

nox commented Jun 12, 2018

Yes

1 similar comment
@bennofs
Copy link
Contributor

bennofs commented Jun 12, 2018

Yes

@ghost
Copy link

ghost commented Jun 12, 2018

yes

@SimonSapin
Copy link
Contributor

Yes

1 similar comment
@jdm
Copy link
Contributor

jdm commented Jun 12, 2018

Yes

@alxkolm
Copy link
Contributor

alxkolm commented Jun 13, 2018

Yes.

@arielb1
Copy link
Contributor

arielb1 commented Jun 30, 2018

Yes

@aweinstock314
Copy link
Contributor

Yes, MIT license works.

@vn971
Copy link

vn971 commented Oct 12, 2018

Sorry, I'm not a contributor or anything, but doesn't "public domain" mean I can just take the code and assume it as MIT (or proprietary, or however I want)?

If there are some good well-known links on this, I'd read.

@joshtriplett
Copy link
Contributor

You don't need permission to go from public domain to MIT, no. And in particular, while it's polite to ask contributors and get consensus, you certainly don't need to rewrite code.

@wartmanm
Copy link
Contributor

Yes (even if it's not technically required)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests