From 8d13ef33e1a4f2606b5b59a47241ce8dd8fa2fd8 Mon Sep 17 00:00:00 2001 From: Mike McQuaid Date: Wed, 29 Aug 2018 19:52:08 +0100 Subject: [PATCH] Maintainer-Guidelines: mention code of conduct. --- docs/Maintainer-Guidelines.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/Maintainer-Guidelines.md b/docs/Maintainer-Guidelines.md index d2bb0dbd8d..d88d29ce26 100644 --- a/docs/Maintainer-Guidelines.md +++ b/docs/Maintainer-Guidelines.md @@ -116,6 +116,8 @@ All communication should ideally occur in public on GitHub. Where this is not po This makes it easier for other maintainers, contributors and users to follow along with what we're doing (and, more importantly, why we're doing it) and means that decisions have a linkable URL. +All maintainers (and lead maintainer) communication through any medium is bound by [Homebrew's Code of Conduct](CODE_OF_CONDUCT.md#code-of-conduct). Abusive behaviour towards other maintainers, contributors or users will not be tolerated; the maintainer will be given a warning and if their behaviour continues they will be removed as a maintainer. + ## Lead maintainer guidelines There should be one lead maintainer for Homebrew. Decisions are determined by a consensus of the maintainers. When a consensus is not reached, the lead maintainer has the final say in determining the outcome of any decision (though this power should be used sparingly). They should also be seen as the product manager for Homebrew itself and ensuring that changes made to the entire Homebrew ecosystem are consistent and providing an increasingly positive experience for Homebrew's users.