Solid OIDC Introduction to clarify goals and proposed functionality
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
s/utilizing/using
Add more detail on what the implementer wants to achieve, i.e., to enable who and to do what.
Consider changing last paragraphs starting "The OAuth 2.0 [RFC6749]" to explain what they offer and why/how they are of use to the Solid ecosystem, what they're missing and how this spec extends with "additional functionality".
Contributor guide
No contributing guide indexed for this repository
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 with the Solid OIDC specification introduction and locate the wording change from “utilizing” to “using.” Clarify who the proposed functionality enables and for what purpose, then revise the final OAuth 2.0 paragraphs to explain their relevance, limitations, and the additional functionality for Solid; review the rendered introduction when done.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100