MeltanoLabs / MeltanoLabs/Meta
Document Permissions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Document how we manage permissions and teams in the README.
I couldnt find the issue where we decided on the Teams structure and what permissions are given to each role but this breakdown seemed right.
Role: Access Level
- maintainer: maintain
- contributor: write
- community member (anyone): read
- admin (internal): admin
Were we planning to create a team per repo like "tap-google-analytics-contributor" and "..-maintainer"? What is the current iteration of the Teams? I dont have permission them.
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 repository README and determine whether it already describes permissions or team structure. Confirm the current role access levels and whether teams are organized per repository before documenting them; done means the README reflects the agreed structure and permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100