Skip to content

No indication of license for content on the Rust wiki #5831

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
asb opened this issue Apr 11, 2013 · 14 comments
Closed

No indication of license for content on the Rust wiki #5831

asb opened this issue Apr 11, 2013 · 14 comments
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@asb
Copy link

asb commented Apr 11, 2013

I had a look, but couldn't see any indication for the intended license of content on the Rust wiki. This isn't necessarily a major issue, but it's not inconceivable people could contribute content that would be useful to pull in to official Rust documentation.
@toddaaro
Copy link
Contributor

toddaaro commented Jul 3, 2013

A license for this would be great to have. @graydon can you take a look at this?

@thestinger
Copy link
Contributor

We should probably just use the same dual licensing as Rust itself, to allow freely copying to and from the wiki.

@asb
Copy link
Author

asb commented Sep 19, 2013

Bumping this issue (I suppose @brson is best placed to look in to it now?) because it's been open for a long time, and it's one of these cases where it just gets harder and harder to fix as time goes on, as more contributions are made to the wiki with an uncertain licensing situation.

@brson
Copy link
Contributor

brson commented Oct 18, 2013

This problem also exists with our in-tree documentation. It's something we need to address for sure. I'm not entirely sure what do do for the wiki - can we just put a disclaimer on the front page saying the license? Do we need a license on every page? I probably need to consult the lawyers... grumble.

@asb asb mentioned this issue Dec 23, 2013
Merged
@brson
Copy link
Contributor

brson commented Jan 3, 2014

I've belatedly pinged the lawyers about this issue.

@brson
Copy link
Contributor

brson commented Jan 8, 2014

After consulting with people who understand these matters, this is what I intend to do:

  • All Rust documentation will also be MIT/ASL2 licensed.
  • Add the license as a footer to existing in-tree documentation, under the argument that it is already licensed according to the same terms as the rest of the repo.
  • Gather new statements from wiki contributors asserting that they contrtibuted under the MIT/ASL2, as we did when we relicensed Rust.
  • Put the license as footers on all pages of the wiki.

@cartazio
Copy link
Contributor

i consent to have any comments i make be MIT licensed.

@brson brson mentioned this issue Feb 6, 2014
Closed
@steveklabnik
Copy link
Member

This can be closed since #12094 has been merged, and we're not really putting anything but meeting notes on the wiki anymore.

@brson
Copy link
Contributor

brson commented Jun 24, 2014

I prefer to keep this open as long as there is incorrectly-licensed content on the wiki. We're pretty anal about licenses...

@thestinger thestinger mentioned this issue Aug 19, 2014
Closed
@brson
Copy link
Contributor

brson commented Jan 13, 2015

It seems unlikely that I'm ever going to get around to fixing this. It's just not that important. The most important thing remaining is policy documentation and that rightly belongs somewhere not world-editable.

@steveklabnik
Copy link
Member

Does this mean we can just remove the wiki then?

@steveklabnik steveklabnik mentioned this issue Feb 10, 2015
Closed
@steveklabnik steveklabnik mentioned this issue Feb 13, 2015
Merged
steveklabnik added a commit to steveklabnik/rust that referenced this issue Feb 16, 2015
@steveklabnik
CONTRIBUTING.md redux
f645cad 
This redux of CONTRIBUTING.md adds in more information, including
subsuming both compliment-bugreport.md and Note-development-policy
in the wiki.

I only glanced at the broad TOC of Note-development-policy, and did
not use the text as the basis for the re-write. This will then address
the last outstanding part of rust-lang#5831.
@steveklabnik steveklabnik mentioned this issue Feb 16, 2015
Closed
Manishearth added a commit to Manishearth/rust that referenced this issue Feb 17, 2015
@Manishearth
Rollup merge of rust-lang#22282 - steveklabnik:gh5831, r=brson
edac2a0 
This redux of CONTRIBUTING.md adds in more information, including
subsuming both compliment-bugreport.md and Note-development-policy
in the wiki.

I only glanced at the broad TOC of Note-development-policy, and did
not use the text as the basis for the re-write. This will then address
the last outstanding part of rust-lang#5831.
@steveklabnik
Copy link
Member

I have backed up the wiki to https://github.com/rust-lang/rust-wiki-backup , so we have a copy, and am disabling it in the main repository. If there's more important content that needs replacing, please open issues. Thanks.

@alexchandel
Copy link

This is rather depressing. I used to regularly curate the "Community libraries" wiki page.

@lahwran
Copy link

lahwran commented May 1, 2015

When is the wiki coming back?

flip1995 pushed a commit to flip1995/rust that referenced this issue Aug 28, 2020
@bors
Auto merge of rust-lang#5831 - chansuke:to_string_in_display, r=flip1995
e522ca3 
Don't use `to_string` in impl Display

fixes rust-lang#3876

this PR is derived from [Toxyxer's implementation](rust-lang/rust-clippy#5574).
changelog: add [`to_string_in_display`] lint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@asb @cartazio @steveklabnik @brson @toddaaro @lahwran @alexchandel @thestinger