License files have unfilled placeholders
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
The following license files have placeholder text. This seems wrong.
https://github.com/rust-lang/rust/blob/main/LICENSES/BSD-2-Clause.txt
Copyright (c) <year> <owner>
https://github.com/rust-lang/rust/blob/main/LICENSES/ISC.txt
<copyright notice>
https://github.com/rust-lang/rust/blob/main/LICENSES/MIT.txt
Copyright (c) <year> <copyright holders>
https://github.com/rust-lang/rust/blob/main/LICENSES/NCSA.txt
Copyright (c) <YEAR> <OWNER ORGANIZATION NAME>. All rights reserved.
Developed by: <NAME OF DEVELOPMENT GROUP>
<NAME OF INSTITUTION>
<URL FOR DEVELOPMENT GROUP/INSTITUTION>
Additionally, I'm not sure if the Apache-2.0 license is being applied properly: https://github.com/rust-lang/rust/blob/main/LICENSES/Apache-2.0.txt
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information.....
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review LICENSES/BSD-2-Clause.txt, ISC.txt, MIT.txt, NCSA.txt, and Apache-2.0.txt, starting with the reported placeholder text. Check the project’s licensing guidance and determine what information, if any, should replace each placeholder. Done means the files have agreed, legally appropriate text or a documented rationale for retaining the standard placeholders.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100