From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) by sourceware.org (Postfix) with ESMTPS id F0311384C001 for ; Thu, 15 Apr 2021 20:02:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org F0311384C001 Received: by mail-lf1-x136.google.com with SMTP id f17so34078324lfu.7 for ; Thu, 15 Apr 2021 13:02:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=CNjN2/vNEEzTY5RvC4DzsDcLnobQ6wxLm7XcifkOXQI=; b=YvtMzCFlKstyjAYrUhZ5SBw2N7GyoH8iPvdqmmfynPlTsx3QgPO7/AAYCWHFqIFp6+ r6v+EW5s9LLHZJ/Bq2ucIbxX9l0dIOzgBhFU48p4TzZ/eznFXJP37px5GJ1d7ab8s+xv mWA3x8cgf8VyFrfjv8aUFoQTpzi/ACHe8GwsV3KMfjnVBW+OiiBmQUd/jYmGlp2U3W+u QD55bFBmEwgWYY3IviQb/49bQomuncIPRmcOsgpUHq5p6JV15+Z8yr8DgpX4+wPbiBun wHGMgEzaNgdtdwLBKBy0NgDGwdMzIBQNs6r1+6AvcuWJd1abqicCug1dtg3OcSGEOQaZ CNew== X-Gm-Message-State: AOAM533PtBobLKq7klaFOURKk3l+3sDA52xu9vHpi66QY/mnSK3/ZUiT uEU+uMp53J3OVqkRk3tnS4BYTr3lklPpOE/sjLfPIA== X-Google-Smtp-Source: ABdhPJzRS+ZaCNuQLF1eNuYqW1bvo3h3umn9Miy6SOrZdIEQORESKjq4v19UEtYjlMHX29NT2D0xku1RqruyPk26T/M= X-Received: by 2002:ac2:414e:: with SMTP id c14mr545519lfi.155.1618516952316; Thu, 15 Apr 2021 13:02:32 -0700 (PDT) MIME-Version: 1.0 References: <20210414131843.GA4138043@thyrsus.com> <093dbfde-a7b5-a55c-8a03-3e82460bce67@acm.org> <82189248-2E7D-46FF-A0A4-7C3D79463D54@comcast.net> <20210415140057.GB51340@thyrsus.com> <6E1497BE-EF6F-4B31-9BAE-27D91C541804@comcast.net> <7EC5CBE6-1A1C-460E-9778-62B2463E579F@sandoe.co.uk> In-Reply-To: From: Ian Lance Taylor Date: Thu, 15 Apr 2021 13:02:20 -0700 Message-ID: Subject: Re: removing toxic emailers To: Christopher Dimech Cc: Iain Sandoe , GCC Development Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-17.4 required=5.0 tests=BAYES_00, DKIMWL_WL_MED, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, USER_IN_DEF_DKIM_WL, USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Apr 2021 20:02:35 -0000 On Thu, Apr 15, 2021 at 12:45 PM Christopher Dimech via Gcc wrote: > > Proposing the guidelines essentially means that the community accepts the= fact > that many of us are incapable of navigate everyday problems and dilemmas = by making > =E2=80=9Cright=E2=80=9D decisions based on the use of good judgment and v= alues rather than sterile > sets of rules and conventions that typically disregard the individual, th= e particular, > or the discrete. Thusly, it is wrong to suggest that the problems are si= mply associated with RMS, FSF and GNU. I think you are conflating two different things. Iain was describing general guidelines for communication, not saying anything about RMS, FSF, or GNU. Personally I would say that the purpose of communication guidelines for GCC mailing lists is not for existing members of the community. As several people have said, the GCC mailing lists are normally civil. It is to provide a mechanism for blocking people whose goal is, for whatever reason, to disrupt the community. Such a mechanism requires a lot of sensitivity to context and care on the part of the moderators. But it still helps to have a set of guidelines to refer to. Ian