TR rights and license
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
IANAL.
🐰🕳️
Currently the TRs either use the text "MIT License" or refer to http://purl.org/NET/rdflicense/MIT1.0 (or similar as the MIT license template) or possibly something else or undefined.
TRs (and perhaps any other documents under solidproject.org) should link to a human- and/or machine-readable license document that clarifies the rights, e.g., copyright year, rights holder, license.
The solid/specification repository includes LICENSE.md that's using the MIT License with Copyright to "W3C Solid Community Group".
The Solid Technical Reports Contributing Guide's Publication Rules mentions the use of http://purl.org/NET/rdflicense/MIT1.0 .
Participants in the W3C Solid Community Group have signed the W3C Community Contributor License Agreement.
The Solid Project website links to https://solidproject.org/license and that document describes the licenses that are used for its assets.
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
Start by comparing LICENSE.md with the Publication Rules in CONTRIBUTING.md and the license information linked from solidproject.org/license. Review how the Technical Reports currently identify their licenses and determine the intended human- and machine-readable rights information. Done means the applicable license, copyright year, and rights holder are consistently clarified for the relevant reports or documents.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100