RFC: ODP Repository Naming Policy - #50
Conversation
There was a problem hiding this comment.
Pull request overview
This PR introduces an RFC document that defines a standardized repository naming policy for the Open Device Partnership (ODP) GitHub organization, aimed at making repository scope/purpose/temporary status discoverable from names.
Changes:
- Adds a new RFC establishing a
<scope>-<purpose>-<temporary_status>naming grammar and associated rules. - Defines reserved organization-wide scopes (
common,governance,platform) and how project scopes/purposes are chosen. - Provides guide-level examples mapping current repository names to the proposed convention.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
makubacki
left a comment
makubacki
left a comment
There was a problem hiding this comment.
Overall, this looks reasonable to me. I am concerned about "temporary forks" and "handoff repos" hanging around longer than expected or being created when direct upstreaming is more efficient, so I asked a couple of questions about anticipated usage of those.
jerrysxie
left a comment
jerrysxie
left a comment
There was a problem hiding this comment.
I am against renaming all the repos for repo discovery without doing a full impact analysis, because there are better ways to do this. The naming convention should only be scoped to the top-level repos where we are driving people.
RFC: ODP Repository Naming Policy
This RFC defines the naming policy for repositories in the Open Device Partnership (ODP) GitHub organization. The
policy communicates each repository's scope and purpose. For repositories temporarily hosted by ODP, it also
communicates whether the repository is a fork or is intended for handoff.