RFC 0036: Update ODP Private Repository Access Control - #48
Open
makubacki wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates RFC 0036 to broaden the policy from “default private repo access behavior” into a more general statement about the intended role of private repositories in the OpenDevicePartnership (ODP) GitHub organization—positioning private repos as temporary staging for content intended to become public, and explicitly excluding confidential/no-public-plan work from the org.
Changes:
- Reframes the RFC motivation/goals around organizational openness while constraining when private repos are appropriate.
- Simplifies and updates the normative requirements and guidance (including adoption/transition checklist).
- Updates the Alternatives section to align with the revised private-repo role.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
makubacki
force-pushed
the
rfc_0036_rev_private_repos_allowed
branch
from
August 4, 2026 00:32
101344f to
096e0ea
Compare
Updates the RFC to more generally cover private repository policy in the OpenDevicePartnership GitHub organization. Adds a requirement that private repositories are only for staging content to go public and should not contain any confidential content or material with no public plan. Simplifies requirements and overall policy accordingly while still retaining GitHub teams to manage and audit private repository access on a per-repository basis. Overall, reduces administrative overhead for managing private repositories. Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
makubacki
force-pushed
the
rfc_0036_rev_private_repos_allowed
branch
from
August 4, 2026 16:46
096e0ea to
dcb6917
Compare
dhillonk
approved these changes
Aug 5, 2026
jerrysxie
reviewed
Aug 5, 2026
makubacki
added a commit
that referenced
this pull request
Aug 5, 2026
Adds a topic for the PR #48 to the agenda. Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
jerrysxie
approved these changes
Aug 5, 2026
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
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.
Updates the RFC to more generally cover private repository policy in
the OpenDevicePartnership GitHub organization.
Adds a requirement that private repositories are only for staging
content to go public and should not contain any confidential content
or material with no public plan. Simplifies requirements and overall
policy accordingly while still retaining GitHub teams to manage and
audit private repository access on a per-repository basis. Overall,
reduces administrative overhead for managing private repositories.