Please review CG Report requirements
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Hi all,
In looking at a sample Solid technical report such as:
https://solidproject.org/TR/protocol
I would like to draw the CG's attention to our CG Report requirements:
https://www.w3.org/community/reports/reqs/
Among them notably, we have style requirements (to help people understand the status of documents) and copyright statement requirements (per the CG policies), etc.
I'd like to request that the CG make appropriate changes based on these requirements. Don't hesitate to contact me on team-community-process if you have questions.
Cheers,
Ian
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 the sample Solid technical report at solidproject.org/TR/protocol with the CG Report requirements and the linked process summary. Identify the required style and copyright changes, then confirm the report meets those requirements; the issue does not name specific files or tests.
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
- 25/100