From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) by sourceware.org (Postfix) with ESMTPS id B11F83865483 for ; Wed, 31 Mar 2021 15:43:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B11F83865483 Received: by mail-lf1-x131.google.com with SMTP id b14so29783883lfv.8 for ; Wed, 31 Mar 2021 08:43:47 -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=qPdX+8p60aj320WUUa8buTF0Gk46MmWsfpiWz3+hFY4=; b=mi6lAZZCECxofg/+9euAE2IPnST3g5ZVrFY/iaONQReJxqKsAszkL9jL6XcYDQTXPB lR1qDYFaiOz6IvSp+QRrgAyvErAiumQ76jaJQwkv1R0WTT4Kph55WsJ/l9GPoEz6BSCD C2lj9/Do+6MQ9KTSY1sQ2aKx7lVa1VmU6/jFt8bpF476IpQTM9czdZ9kRWSARkyadG9r /pf0iD1M2Y5zOYfOnKgYfNhNRLbZRwFDNhoc2WEmennguURusxM/wAJJ+n5B+MSjO6I+ TqefhFQ+HWhg6tRToWW+R9k3xyhlZHBYSP+kqUYjezj9PLL0Q/J4tv5KKG/uk0ijUpzJ dgqg== X-Gm-Message-State: AOAM532ukYBbaP3tLLoNQF4FhkScSjFW52kGcnES8Acx/v+5xrTrCTHc wOf/yz+VOXOv+rSMncuVz6WrHm3JG+bWO4SPqwKwXA== X-Google-Smtp-Source: ABdhPJwMpPj+gq/6miMOge6TvJUzp+sFA5MwCr2opnd16tyoEAETBoQVvIWaMJBRZfdGf32B/GzQL+xz+CSVZELw+QI= X-Received: by 2002:a19:68c:: with SMTP id 134mr2696842lfg.155.1617205426190; Wed, 31 Mar 2021 08:43:46 -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:43:34 -0700 Message-ID: Subject: Re: Remove RMS from the GCC Steering Committee To: Richard Biener Cc: Mark Wielaard , GCC Development , Nathan Sidwell Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-18.2 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: Wed, 31 Mar 2021 15:43:49 -0000 On Wed, Mar 31, 2021 at 5:28 AM Richard Biener via Gcc wrote: > > And just to repeat - all the GCC governance structure (the "SC") represents > all of the same non-openess as the FSF governance structure (because > the "SC" is in fact appointed by the Chief GNUisance "or his delegates"). While that is true in a formal sense it's not true in a practical sense. In practice the steering committee appoints its own members. That said I think it would be entirely reasonable to use a different structure. I just don't know what it would be. The steering committee doesn't really take very many actions, which is as it should be. The main and by and large only action is appointing, or perhaps a better word would be anointing, maintainers: the people listed in the MAINTAINERS file. Thoughts on changing the steering committee system should probably be on a separate thread from the RMS discussion. Ian