docs: propose restricting private repo access before external onboarding - #183
Open
marcusburghardt wants to merge 1 commit into
Open
docs: propose restricting private repo access before external onboarding#183marcusburghardt wants to merge 1 commit into
marcusburghardt wants to merge 1 commit into
Conversation
Add OpenSpec change artifacts (proposal, design, spec, tasks) for restricting access to private repositories (nunya, roadmap) in preparation for onboarding external contributors to the org. Key proposal points: - Change default_repository_permission from read to none - Bring private repos into peribolos-managed config with closed teams - Retire the manually-managed nunya-access secret team - Three-phase migration to avoid access gaps This PR contains only spec/planning artifacts for admin review. No configuration or implementation changes are included. Assisted-by: OpenCode (claude-opus-4-6) Signed-off-by: Marcus Burghardt <maburgha@redhat.com>
marcusburghardt
requested review from
gxmiranda,
jflowers and
jpower432
as code owners
July 24, 2026 16:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR contains only planning/spec artifacts for admin review. No configuration or implementation changes are included.
Problem
Our org sets
default_repository_permission: read, which gives every org member implicit read access to all repositories including private ones (nunya, roadmap). When we onboard external contributors, they will automatically see private repos with sensitive information.Proposed solution
default_repository_permissiontonone-- org members only access repos through explicit team grantsnunya-accesssecret teamTrade-off
The current model hides the access structure but weakly protects the content (any org member sees everything). The proposed model exposes organizational metadata (repo names, team memberships) in the public config but strongly protects the actual content.
See the full threat model in
design.mdand testable requirements inspecs/private-repo-access-control/spec.md.Artifacts included
proposal.mddesign.mdspecs/private-repo-access-control/spec.mdtasks.mdAction requested
Review the proposal and risk analysis. If agreed, implementation follows in separate PRs.