Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide Access Controls To Maintainers #45

Closed
andorsk opened this issue Oct 13, 2022 · 7 comments · Fixed by #14 or #49
Closed

Provide Access Controls To Maintainers #45

andorsk opened this issue Oct 13, 2022 · 7 comments · Fixed by #14 or #49
Assignees
@talltree
Labels
priority: critical Progress on this issue is critical to the group's forward progress. status: pr-accepted The issue is linked to a PR that has been accepted and is waiting for merge. type: admin This issue requires an action by an admin.

Comments

@andorsk
Copy link
Contributor

andorsk commented Oct 13, 2022

This ticket is to determine and provide the correct access controls to the maintains of this repo, so that relevant parties are given the correct permissions to maintain the repo per their responsibilities.

This was for example, an issue in #37 where I needed the access to create labels, and did not have it.
@andorsk
Copy link
Contributor Author

andorsk commented Oct 13, 2022 •
edited
Loading

My suggestion is we have some governance "roles":

A proposal:

  1. Maintainer <- Tagging issues, Closing issues, Creating issues, Review, and merging PRs
  2. Admins <- Has administrative power over the repo. These may include: adding issues, changing labels, updating permissions, blocking users if needed, etc.
  3. Public <- Can always create issues, set up PR ( ON A FORK ).

Nobody should be able to push directly to master IMO. We can add some branch rules to prevent a direct push to master

@andorsk
Copy link
Contributor Author

andorsk commented Oct 13, 2022

Some important documentation that @talltree put up, which will help inform this is here: https://wiki.trustoverip.org/display/HOME/GitHub+Issues+Management+Process.

@andorsk
Copy link
Contributor Author

andorsk commented Oct 13, 2022

TODO: Provide actions for role.
Drummond:
Editors: Come up with permissions for the role.
Permission to work with current admin Elisa for rights.

@andorsk
Copy link
Contributor Author

andorsk commented Oct 13, 2022

@elisatrevino

@andorsk
Copy link
Contributor Author

andorsk commented Oct 13, 2022

Proposed resolution: Revision to the wiki page with subgroup process edits. @talltree to lead that.

@andorsk andorsk added the type: admin This issue requires an action by an admin. label Oct 14, 2022
@talltree talltree added the priority: critical Progress on this issue is critical to the group's forward progress. label Oct 19, 2022
This was linked to pull requests Oct 26, 2022
Fixes #13 #14
Merged
governance files: CODEOWNERS, CONTRIBUTING.md, and GOVERNANCE.md #49
Merged
@a-fox a-fox added the status: pr-accepted The issue is linked to a PR that has been accepted and is waiting for merge. label Oct 26, 2022
@a-fox
Copy link
Contributor

a-fox commented Oct 26, 2022

This is resolved once the Contibuting & Governance files are merged, am I right?

@andorsk
Copy link
Contributor Author

andorsk commented Oct 26, 2022

@a-fox yea...I think we during the call this gets hashed out and merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@talltree talltree

Labels
priority: critical Progress on this issue is critical to the group's forward progress. status: pr-accepted The issue is linked to a PR that has been accepted and is waiting for merge. type: admin This issue requires an action by an admin.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes #13
governance files: CODEOWNERS, CONTRIBUTING.md, and GOVERNANCE.md
3 participants
@a-fox @talltree @andorsk