From 22962eaa07528a23d32ebc2a4b6583f8b265244e Mon Sep 17 00:00:00 2001 From: Francisco Javier Arceo Date: Tue, 1 Apr 2025 09:04:39 -0400 Subject: [PATCH] changed filename Signed-off-by: Francisco Javier Arceo --- docs/source/community/governance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/community/governance.md b/docs/source/community/governance.md index 3f98251b4..8b620ca5f 100644 --- a/docs/source/community/governance.md +++ b/docs/source/community/governance.md @@ -20,7 +20,7 @@ A formal governance structure helps us to At a high level, the key moving parts of the community are: - **GitHub activity** (issues + pull requests + discussions) - **RFCs** for detailed discussions on new features or changes -- **Maintainer syncs** (monthly) for [maintainers](https://github.com/meta-llama/MAINTAINERS) to discuss project direction and health +- **Maintainer syncs** (monthly) for [maintainers](https://github.com/meta-llama/MAINTAINERS.md) to discuss project direction and health With this structure, users and contributors largely self-organize and contribute changes as per [lazy consensus](#lazy-consensus). If there is active opposition and unresolvable conflict, then maintainers step in to break ties or make decisions.