From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) by sourceware.org (Postfix) with ESMTPS id 95259385801A for ; Mon, 12 Apr 2021 01:03:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 95259385801A Received: by mail-wm1-x335.google.com with SMTP id j20-20020a05600c1914b029010f31e15a7fso7702644wmq.1 for ; Sun, 11 Apr 2021 18:03: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; bh=P4VoAPjyjP4mmA9NTbHdYI1sLM9eOxUXrFuYLojhRrI=; b=HFndIDYzlnQd+6HHXONUAY9gJr4SN7ryR5E6yz8lVvgGl4E2GmTnfoMr54Wll8zkF8 d2oMJ3V62BL67vGMwJeNdVI/TDNnlKpNicrCnxnqp+MFrXoWAA/kV8KVsFBJkPWso7Bd 0y9tHH8+K7Opyqwac/VFk8Lke125zIdLGSK6yiCkZbhxmagGfZe3OFJk5UDg6LtZWr/8 PQ5KBWgqujWZ23ktKztDsz4t+amHmwCHs+ik4WgjzEHsyQnCokTZEboIE6iwLJR14B6q nSPHud48DKLNDR2uPoV75Cb0jRe6gtVDtrJDwt5keXk7EMiE9Vgfm99PRFwCEGsFEWzf zHfw== X-Gm-Message-State: AOAM533shy5DxQIXWl93Rv+QzWgK7I0jjSASO7fkoCEaX/HsAEY56rn5 btkHCPRbdP54NBlOj/YhllBW/fQYPJpI4srfzns= X-Google-Smtp-Source: ABdhPJyR1phJd1wezynhPh+13YtVZOwcXf2t/krxHKJioidbcvgirYOmxcmZXgFf433ZPuW2daTRWBBcwdRALEH/QQ8= X-Received: by 2002:a05:600c:2cd8:: with SMTP id l24mr23845555wmc.88.1618189412731; Sun, 11 Apr 2021 18:03:32 -0700 (PDT) MIME-Version: 1.0 References: <20210407162454.GA22759@jocasta.intra> <20210408064528.GA10349@jocasta.intra> <94ca414af699bab851008f86f006db4bd8bf1929.camel@redhat.com> <20210408182128.GA19715@jocasta.intra> <5f532c131146b9c7549f03eac7a9da3a29db1a2e.camel@redhat.com> <20210409063749.GA8596@jocasta.intra> <04fa3173-9809-b905-8fa3-f6554b8ae7d7@hesbynett.no> <06eb8287-e6bb-270f-e5a5-730c10bb31ef@hesbynett.no> <20210409183631.GA29274@jocasta.intra> <69BA3B4D-C798-4700-B607-994588BD5D87@tesio.it> In-Reply-To: From: David Edelsohn Date: Sun, 11 Apr 2021 21:03:21 -0400 Message-ID: Subject: Re: GCC association with the FSF To: Ian Lance Taylor Cc: Pankaj Jangid , GCC Development Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP 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: Mon, 12 Apr 2021 01:03:36 -0000 On Sun, Apr 11, 2021 at 8:40 PM Ian Lance Taylor via Gcc wrote: > > On Sat, Apr 10, 2021 at 4:36 AM Pankaj Jangid wrote: > > > > I think, it would be great help if someone can document what the SC > > does. > > I don't know whether anybody actually tried to answer this. > > The main job of the GCC steering committee is to confirm GCC > maintainers: the people who have the right to approve changes to > specific parts of GCC, and the people who have the right to make > changes to specific parts of GCC without requiring approval from > anybody else. These people are listed in the MAINTAINERS file in the > gcc repository (currently > https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=MAINTAINERS;h=db25583b37b917102b001c0025d90ee0bc12800f;hb=HEAD), > from the start of the file down to the list of "Write After Approval" > people. > > A secondary job of the GCC steering committee is to approve new > additions to GCC that are not under the GPL for one reason or another. > This happens rarely. > > A tertiary job of the GCC steering committee is to decide disputes > between maintainers that the maintainers are unable to resolve. I > can't recall this ever happening. > > The GCC steering committee is in principle a place to make decisions > that affect the entire project. There are very few such decisions. > One was the decision to change the implementation language of GCC from > C to C++, a decision made in 2010. Another was the decision to allow > GCC plugins. As a counter-example, moving GCC from Subversion to git > was supported by the steering committee members, but there was no > formal decision by the steering committee to approve the move. > > More generally, the GCC steering committee has historically served as > a point of contact between the FSF and the GCC developers. In my > opinion this has not amounted to much over the years that I've been on > the committee (since 2014). Also, because the FSF considers the GCC SC the "package maintainers" of GCC, the Steering Committee also receives and answers questions and requests from RMS and the FSF. And, as I mentioned in another thread, I believe that the role of the GCC SC is to perform some of the duties of a good technical manager: remove real or potential roadblocks so that the developers can focus on being productive. Some of us have initiated other activities and alliances to support and promote GCC and the GNU Toolchain, although it is not an official responsibility of the GCC SC. Thanks, David