From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) by sourceware.org (Postfix) with ESMTPS id DF7753857C75 for ; Wed, 31 Mar 2021 15:49:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org DF7753857C75 Received: by mail-lj1-x232.google.com with SMTP id o16so10388391ljp.3 for ; Wed, 31 Mar 2021 08:49:41 -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; bh=UjXfQmVPvsaxzm1X2pG8fCShrHM7DuXq6JkFQjzjhjQ=; b=T+qogtU94UH+7O8WTCbPOWxzBr20hXhYx4XlfUfoLdw/PRXSLvCTAn/E2VTc1XRqps Qqx3Yhs4i0z0pChuoiXsAm0Ssaw9psVf4h2j2PeENnAkZTftY7NWjPbCxOJgjUVPMwbg 3naPwwOcDBWyAYsoNk5qcuklW/iXHD02yJhZtALCno8ffUtfvtP0UQMmT/1Gar68HI2m tOvzuJiiiiN7MQaN347Hn0c2kex4Hhiea2p8ygTLk3FXfhcml9KmWoh0sXY6O7t1GtP/ HDzvsSHo+Lh5NBQJk7dKbWquRwzJ3fBSa2+0Ip6aXXY7PUcbLXPfFk97kA8zwWKXyROQ dyhQ== X-Gm-Message-State: AOAM533FlGkVkHjW/EZQeJKo2VIOOtlDFy1pXEW1tmS9/0u9dhznzQYC QaDFqPRuK57ehs7zkuBVNe8TwwEKdG2o7/WjCsCr8g== X-Google-Smtp-Source: ABdhPJx1KzPLv9NOfkPWbw1cnW1dlpYeAZyeNthq7NFanEVZyYCSpHME5I/gQn5993kqbGbGtoQ8c1E/2267vAd/DwA= X-Received: by 2002:a2e:544d:: with SMTP id y13mr2425841ljd.95.1617205780411; Wed, 31 Mar 2021 08:49:40 -0700 (PDT) MIME-Version: 1.0 References: <20210330151656.00007e20@tesio.it> <20210330232849.00001697@tesio.it> <20210331113417.GU2685@wildebeest.org> In-Reply-To: From: Ian Lance Taylor Date: Wed, 31 Mar 2021 08:49:29 -0700 Message-ID: Subject: Re: Remove RMS from the GCC Steering Committee To: Joel Sherrill Cc: Paul Koning , GCC Development Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-18.3 required=5.0 tests=BAYES_00, DKIMWL_WL_MED, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH, KAM_SHORT, 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: Wed, 31 Mar 2021 15:49:43 -0000 On Wed, Mar 31, 2021 at 7:44 AM Joel Sherrill wrote: > > On Wed, Mar 31, 2021 at 9:23 AM Paul Koning via Gcc wrote: > > > I may have lost it in the enormous flood of text, but I want to ask these > > general questions. > > > > 1. Is there a published code of conduct for GCC community members, > > possibly different ones depending on which level of the organization you're > > in? > > > > As a GNU project, this should apply.: > > https://www.gnu.org/philosophy/kind-communication.en.html Yes, although that is, by design, not a code of conduct as the term is normally used. > > 2. Is there a formal process for receiving claims of infraction of this > > code, and for adjudicating such claims? > > > > I admit to not looking for one but does any FLOSS organization have this? Yes, many. For example: LLVM: https://llvm.org/docs/CodeOfConduct.html Go: https://golang.org/conduct Apache: https://www.apache.org/foundation/policies/conduct.html and there are many more. The GNU Cauldron also has a code of conduct: https://gcc.gnu.org/wiki/cauldron2019#Code_of_Conduct Ian