Page MenuHomeFreeBSD

policy: Cross Repo Commit Policy
ClosedPublic

Authored by imp on Tue, Jun 9, 10:36 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jul 4, 10:31 AM
Unknown Object (File)
Thu, Jul 2, 11:34 PM
Unknown Object (File)
Thu, Jul 2, 4:19 AM
Unknown Object (File)
Thu, Jul 2, 4:12 AM
Unknown Object (File)
Wed, Jul 1, 10:55 PM
Unknown Object (File)
Wed, Jul 1, 6:57 PM
Unknown Object (File)
Wed, Jul 1, 6:57 PM
Unknown Object (File)
Wed, Jul 1, 6:20 PM
Subscribers

Details

Summary

Add Cross Repo Commit policy that was originally discussed in January
2023 by core, and ratified by the current core team on XXXX.

Sponsored by: Netflix

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 73777
Build 70660: arc lint + arc unit

Event Timeline

imp requested review of this revision.Tue, Jun 9, 10:36 PM
imp created this revision.

draft cross repo policy.

Gemini made good readablity suggestions to my overly-verbose prose.

This revision is now accepted and ready to land.Tue, Jun 9, 11:48 PM
ziaee added a subscriber: ziaee.
ziaee added inline comments.
website/content/en/internal/cross-repo-commits.adoc
17

Maybe?

website/content/en/internal/cross-repo-commits.adoc
17

Maybe Locked Areas: ports/Mk is a locked area, de-facto. It's special. Even build breakages there are off limits.

17

"Restricted Areas" might be even better.

19

I'm not completely sure about the ending here of 'followed by a case-by-case review'. Maybe 'followed by more review before recommit'? Sounds dorky, but maybe less dorky?

kevans added a subscriber: kevans.

This lines up with what I'd already been telling people despite the policy being unwritten. An interesting datapoint: most of the people I've told this is fine and wanted to commit to a different repo generally *wanted* review for even nearly-trivial changes, which I think is an interesting progression from our review culture just 5-10 years ago.

This revision now requires review to proceed.Fri, Jun 19, 1:40 PM
This revision is now accepted and ready to land.Fri, Jun 19, 1:41 PM
website/content/en/internal/cross-repo-commits.adoc
17

Now that I've thought about it, Stricter Rules likely is best.

This revision was automatically updated to reflect the committed changes.