Skip to content

LICENSE for Code of Conduct? #14160

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.

Sign up for GitHub

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

Jump to bottom
Closed
isaacs opened this issue May 12, 2014 · 4 comments
Closed

LICENSE for Code of Conduct? #14160

isaacs opened this issue May 12, 2014 · 4 comments

Comments

@isaacs
Copy link

isaacs commented May 12, 2014

I'm writing a code of conduct for npm.

I'd really love to use some of the language found in the "Conduct" section here: https://github.com/mozilla/rust/wiki/Note-development-policy#conduct

Is this document Creative Commons of any sort? I was thinking of a simple statement in the footer of our CoC, with something like:

This Code of Conduct uses language originally found in the [Rust Code of Conduct][].

I'm also borrowing liberally from the Stumptown Syndicate Citizens' Code of Conduct, and our CoC will be CC BY-SA-3.0
@brson
Copy link
Contributor

brson commented May 12, 2014

Although the wiki does not make it clear, the Rust Code of Conduct is licensed the same as Rust and its documentation: MIT + Apache 2. I imagine we can be flexible and if that license doesn't work for you we can reconsider. Let me know.

@isaacs
Copy link
Author

isaacs commented May 13, 2014

I believe that's ok, since MIT allows derivative works and sublicensing.

It's not exactly what I'd call a "substantial portion", so is it ok if I just mention the source, and release the result under CC-By-SA?

@brson
Copy link
Contributor

brson commented May 13, 2014

Yes, I'm fine with that.

@thestinger
Copy link
Contributor

Closing in favour of #5831.

bors added a commit to rust-lang-ci/rust that referenced this issue Feb 20, 2023
@bors
Auto merge of rust-lang#14160 - Veykril:hover-call, r=Veykril
1f2d33f 
fix: Bring back hovering call parens for return type info
flip1995 pushed a commit to flip1995/rust that referenced this issue Apr 3, 2025
@Alexendoo
Move uninlined_format_args back to style (rust-lang#14160)
a001ae3 
The `uninlined_format_args` was temporarily downgraded to `pedantic` in
part because rust-analyzer was not fully supporting it at the time, per
rust-lang#10087. The support has been added over [a year
ago](rust-lang/rust-analyzer#11260), so seems
like this should be back to style.

Another source of the initial frustration was fixed since then as well -
this lint does not trigger by default in case only some arguments can be
inlined.

changelog: [`uninlined_format_args`]: move back to `style`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@isaacs @brson @thestinger