solid / solid/data-interoperability-panel
Refactor standalone Access Invitation specification
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Access Invitations will be split into their own specification via #191, but there's a significant amount of refactoring needed on Access Invitations not only to make them sensible in their own spec, but also to align with all of the changes made to Access Consent in general.
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 by reading the Access Invitation specification material and issue #191, then compare it with the broader changes to Access Consent. The issue does not name files, tests, or specific acceptance criteria, so confirm the intended standalone structure and the complete refactoring scope before beginning.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100