feat: allow external committee members to duplicate perms #570

thesuperRL · 2026-10-31T20:54:03Z

thesuperRL commented

2026-10-31 20:54:03 +00:00

now @gostmeaper can larp as a tech lead fr fr

thesuperRL added 1 commit

2026-10-31 20:54:03 +00:00

feat: allow external committee members to duplicate perms

CI / build (pull_request) Has been skipped

Details

atlantis/pre_workflow_hook: Install local-only OpenTofu providers succeeded.

Details

nixbot/nix-eval evaluation succeeded in 0s (1 warning)

Details

nixbot/nix-build 0 attributes built

Details

kennel/build build succeeded

Details

kennel/deploy deployment healthy

Validate / Governance (pull_request_target) Failing after 2m53s

Details

CI / check-1 (pull_request) Failing after 3m54s

Details

CI / check (pull_request) Failing after 0s

Details

a302cf126c

now @gostmeaper can larp as a tech lead fr fr

thesuperRL requested reviews from devops-leads, tech-director

2026-10-31 20:54:03 +00:00

scottylabs-bot commented

2026-10-31 20:54:46 +00:00

Kennel Deployments

Service	URL
docs	https://governance-docs-pr-570.scottylabs.net

Last updated for commit a302cf1.

### Kennel Deployments | Service | URL | | --- | --- | | docs | https://governance-docs-pr-570.scottylabs.net | Last updated for commit `a302cf1`.

anish requested changes

2026-11-02 07:47:27 +00:00

sites/docs/src/external.md

					
				@ -0,0 +1,30 @@

				# External Access

				Some people outside the Tech Committee need a team's or project's permissions without being part of that team. [`data/external.yaml`](https://git.cmu.dev/ScottyLabs/governance/src/branch/main/data/external.yaml) grants them a role they already would have had, rather than duplicating it:

Some people outside the Tech Committee need a team's or project's permissions without being part of that team.

I think this should never be the case, this whole feature is just opening the door to creating exceptions to tech's governance

For example, since labrador's head of onboarding and documentation requires lead-level access to devops resources, they should just be listed as a devops lead

grants them a role they already would have had, rather than duplicating it:

there is no duplication if they're just added directly

> Some people outside the Tech Committee need a team's or project's permissions without being part of that team. I think this should never be the case, this whole feature is just opening the door to creating exceptions to tech's governance For example, since labrador's head of onboarding and documentation requires lead-level access to devops resources, they should just be listed as a devops lead > grants them a role they already would have had, rather than duplicating it: there is no duplication if they're just added directly