Access control responsibility management of shared spaces
Open
Nobody has claimed this yet.
fix: inaccuracy ⚠️
system: cheaha 🖧
system: cloud.rc ☁️
system: storage 🛢
- Dominant language
- Python
- Stars
- 24
- Forks
- 15
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 1
Description
What would you like to see added?
Top-level permissions are the responsibility of RC to handle in a timely fashion. Permission management within a shared allocation is the owner's responsibility and we can help as a courtesy as time allows, where possible and reasonable to do so.
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
The issue states a policy distinction between top-level permissions and permissions within shared allocations, but it names no documentation file or entry point. First locate the relevant shared-space or access-control documentation, then confirm with maintainers where this responsibility guidance belongs and what wording is considered complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100