git: 072353ccfc - main - policy: Cross Repo Commit Policy

The branch main has been updated by imp:

URL: https://cgit.FreeBSD.org/doc/commit/?id=072353ccfc5ddb7e794d7633d44a585b32e4e175

commit 072353ccfc5ddb7e794d7633d44a585b32e4e175
Author:     Warner Losh <imp@FreeBSD.org>
AuthorDate: 2026-06-26 14:59:45 +0000
Commit:     Warner Losh <imp@FreeBSD.org>
CommitDate: 2026-06-26 15:00:42 +0000

    policy: Cross Repo Commit Policy
    
    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
    Reviewed by:            ziaee, 0mp, kevans, glebius, adrian
    Approved by:            core (24-hour rule)
    Differential Revision:  https://reviews.freebsd.org/D57514
---
 website/content/en/internal/cross-repo-commits.adoc | 21 +++++++++++++++++++++
 website/content/en/internal/policies.adoc           |  1 +
 2 files changed, 22 insertions(+)

diff --git a/website/content/en/internal/cross-repo-commits.adoc b/website/content/en/internal/cross-repo-commits.adoc
new file mode 100644
index 0000000000..bb8019479e
--- /dev/null
+++ b/website/content/en/internal/cross-repo-commits.adoc
@@ -0,0 +1,21 @@
+---
+title: "Cross Repo Commit Policy"
+sidenav: docs
+---
+
+= Cross Repo Commit Policy
+
+This policy provides flexibility for contributors to commit across repositories without heavyweight processes for small, low-impact changes, while ensuring larger changes still undergo normal review and oversight.
+
+== Policy Guidelines
+
+* *Obvious Fixes:* Anyone may make obvious, small changes (e.g., typo or build break fixes) to any repository, subject to repository-specific rules.
+* *Repository Rules:* Committers must know, understand, and follow the specific rules and validation tools of the repositories they are modifying.
+* *Cross-Repository Trust:* When committing outside their primary area, committers are trusted to use their best judgment based on the following framework:
+** *Sufficient Review:* The change has received appropriate peer review for its size and complexity.
+** *Expert Consultation:* Repository experts are consulted for non-trivial changes.
+** *Stricter Rules:* The committer remains deferential to areas requiring formal oversight (e.g., the `ports/Mk` tree).
+** *Scale:* The larger or more complex the change, the more critical it is to seek review and wait for explicit approval.
+* *Accountability:* Committers must accept feedback on both process and content. If a mistake occurs, the default action is an immediate backout, followed by a more formal review, as appropriate.
+
+When in doubt, ask first and seek a sanity check.
diff --git a/website/content/en/internal/policies.adoc b/website/content/en/internal/policies.adoc
index 0012cb0a99..88a4a8f7db 100644
--- a/website/content/en/internal/policies.adoc
+++ b/website/content/en/internal/policies.adoc
@@ -27,6 +27,7 @@ It contains almost everything a new committer to the FreeBSD Project needs to kn
 * link:../software-license[Software License Policy]
 * link:../data[User Data Policy]
 * link:../members[FreeBSD Project Membership]
+* link:../cross-repo-commits[Cross Repo Committing Policy]
 
 == *The FreeBSD Documentation Project*