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
Details
Details
Diff Detail
Diff Detail
- Repository
- R9 FreeBSD doc repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
| website/content/en/internal/cross-repo-commits.adoc | ||
|---|---|---|
| 18 | Maybe? | |
| website/content/en/internal/cross-repo-commits.adoc | ||
|---|---|---|
| 18 | Maybe Locked Areas: ports/Mk is a locked area, de-facto. It's special. Even build breakages there are off limits. | |
| 18 | "Restricted Areas" might be even better. | |
| 20 | 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? | |
Comment Actions
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.
| website/content/en/internal/cross-repo-commits.adoc | ||
|---|---|---|
| 18 | Now that I've thought about it, Stricter Rules likely is best. | |