From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) by sourceware.org (Postfix) with ESMTPS id 4C9CA3857C52 for ; Sun, 11 Apr 2021 20:04:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 4C9CA3857C52 Received: by mail-qt1-x830.google.com with SMTP id 1so8447821qtb.0 for ; Sun, 11 Apr 2021 13:04:18 -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:from:date:message-id:subject:to; bh=oELoTFMVMGXp4b749hGYPErOmXSyr7nnUg6T7uBaMeo=; b=Aa62+nxIygp/7jLeIWIFqQ3l7V0hlYWu2TPt4n5sDnaHgTUSuHcK8s0vOeA2QSrmVD 0kvxaMUgd3nZPMA0+KgS2IYpa8R0ShZ/Loaztddz8Y0c3M02XaoWbB46iixiRQLx6/bL Ex6YiGRa8IzE721N4OZd1b0ZuyRNYnTzp2VhVn9omJgQn3eKkiitpV8wb048CCZZ4Zoe 8pcMesCheiu6psszpH5bTsYykf/x9Tb2XOVfyvx9kRGKrBaoOr89o8fVECaYS3xA3VN9 BH8xc/bqv8bWhmsneoXmup5O68RXX+ekukdWrDPQIiyob2Fh0VDL2SShgVJb5/bdXa4+ x6kg== X-Gm-Message-State: AOAM532CZ0FamL3TjqYq0cJH6Des5EXgT2hPq2Uh4kZknaaRnkKsqaRp ZIZzur+43PjgKoYIXSHRIzK/FEliUZZ0J1947ernI59HWyBGcQ== X-Google-Smtp-Source: ABdhPJwCczAL7Jgn0hcZ/h96bQD63YQLqDnfD9mLOyZt2Ypmd7celNHHsPFXXl4cgoDiU9HHRgQ/NS2xKTOtzW4mLb0= X-Received: by 2002:ac8:5ac6:: with SMTP id d6mr4617019qtd.18.1618171457738; Sun, 11 Apr 2021 13:04:17 -0700 (PDT) MIME-Version: 1.0 From: Ville Voutilainen Date: Sun, 11 Apr 2021 23:04:07 +0300 Message-ID: Subject: GCC association with the FSF To: GCC Development , oliva@gnu.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, 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: Sun, 11 Apr 2021 20:04:19 -0000 >However, the FSF does NOT control nor own the GNU project. That appears to be a very common misperception. >The FSF offers various pro-bono services to the GNU project, among them guarding some GNU assets for the GNU project, but the GNU project is an independent (unincorporated) organization, with its own separate and independent governance structure. >The conversation has supposedly moved on from being centered on the (very indirect) relationship with RMS to being centered around the (even more indirect) relationship with the FSF. >The trigger for the present movements seems to be RMS's reappointment to the board of directors of the FSF. >That makes no sense to me. Really? Well, it makes some amounts of sense to me. See below. >RMS's closest roles regarding GCC have been of initial developer, leader of the project that GCC belongs in, and occasional participant in discussions among the GCC SC, and none of this has changed recently. >What is the relevance of his reappointment to the board of a separate organization he's founded, long participated in, and presided for most of its history, and that has supported both the GNU project at large and the GNU toolchain specifically, in ways that haven't changed at all, not when he resigned from the board, not when he was reappointed?!? >Can anyone come up with any rational motivation for this move right now? This is fairly straightforward. FSF is not as separate an organization as you wish to depict it. It owns the copyright to GCC, and people associated with it have decided to act as the PR department of GCC developers. Multiple maintainers would rather not have that PR department, as they consider it a PR disaster. They'd rather improve the PR department, but if that can't be accomplished, another solution is to disassociate their work from FSF and the PR department. I don't love Jonathan Wakely's idea of forking libstdc++. I would much rather not have that fork happen. But I will follow that fork. I know him well enough that trying to talk him out of doing the fork is unlikely to succeed, we're far beyond the stage where such talking-out is on the table. This, of course, allows us to actually _see_ whether the predictions of doom and gloom will materialize if FSF and RMS are no longer associated with the work of various GCC developers. It also allows us to see how viable the origin of the fork is, when there sure are people suggesting that it can be lead by non-developers, but fair amounts of developers will just go elsewhere. If you wish to hear my wild guesses on those, they are a) that the doom and gloom will not materialize b) the origin of the fork will not remain viable. Bring on the forks. We have ruminated on this long enough, and that seems like a waste of bandwidth. The messages the various developers are conveying are not getting through, or are sinking into an abyss of neverending discussions about something completely different from what the developers are saying.