Skip to content

Conversation

@amburi
Copy link
Contributor

@amburi amburi commented Dec 10, 2025

This document outlines a governance pattern for managing repository settings across large organizations. It details the problems of inconsistent settings, the proposed solution of a central governance repository, and the components involved in implementing automated audits.

This document outlines a governance pattern for managing repository settings across large organizations. It details the problems of inconsistent settings, the proposed solution of a central governance repository, and the components involved in implementing automated audits.
Updated the Centralised Repository Governance document to clarify the importance of a governance repository, enhance the narrative around repository drift, and refine the structure and examples for better understanding.
@amburi amburi changed the title [Draft] Add Centralised Repository Governance pattern Add Centralised Repository Governance pattern Dec 10, 2025
@amburi amburi changed the title Add Centralised Repository Governance pattern Add New Pattern: Centralised Repository Governance Dec 10, 2025
@amburi amburi closed this Dec 10, 2025
@spier
Copy link
Member

spier commented Dec 11, 2025

Hi @amburi. Great to see your contribution here!

Did you close this PR by accident or on purpose?

@amburi
Copy link
Contributor Author

amburi commented Dec 11, 2025

Hi @spier Thanks for your comment 😄
It’s not accidental — this pattern needs some additional work. I’ll address it in a separate PR once that’s done.

@spier
Copy link
Member

spier commented Dec 11, 2025

@amburi cool, I am looking forward to that.

As an aside, at a previous org I maintained a service that I called github-like-a-pro.
It was performing very basic checks (README, description, stale branches, CODEOWNERS).
In my case in all happened in github (i.e. using github issues, webooks, etc).

Now back to your pattern, some other thoughts:

  • What are the things that the governance would control that related immediately to InnerSource?
  • I vaguely remember somebody talking about an "InnerSource linter", which also meant a thing that would check check for certain files. I had quick look but I don't think anybody wrote a pattern about it yet

And last but not least: Feel free to share your pattern in a PR early and often, so that I and others here can help you to make it awesome :)

Thanks again for thinking of sharing your work in this repo!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants