From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by sourceware.org (Postfix) with ESMTPS id 004E63951CAE for ; Thu, 8 Apr 2021 16:43:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 004E63951CAE X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [213.165.168.94] ([213.165.168.94]) by web-mail.gmx.net (3c-app-mailcom-bs08.server.lan [172.19.170.176]) (via HTTP); Thu, 8 Apr 2021 18:43:30 +0200 MIME-Version: 1.0 Message-ID: From: Christopher Dimech To: David Brown Cc: Jonathan Wakely , David Malcolm , GCC Development , Mark Wielaard Subject: Re: GCC association with the FSF Content-Type: text/plain; charset=UTF-8 Date: Thu, 8 Apr 2021 18:43:30 +0200 Importance: normal Sensitivity: Normal In-Reply-To: References: <20210330151656.00007e20@tesio.it> <20210330232849.00001697@tesio.it> <20210331113417.GU2685@wildebeest.org> <20210406222225.GF2711@wildebeest.org> <5547d308f400aa62746b421dad2968dd6321aeae.camel@redhat.com> X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:STLdAYwykLn2P8+ncWTM0qscrUfpL5I8wCK5KjKreBQW+tJxRgqsUnpkk6e7ReFUXqOhu gsl3dRO52QMM6tdmRNP1Q5HEfYRkMZ+mVQqH22+wdWkp7MpNxAOvr75D2bwEItMSOcSQbQOaHcMD ZCEDLh880AddAByskhJKx+AwtTsR1LherZz7nDnGzpTaVDNsJyRR0p+oGRgx+z8ZP3jxfLtHwkuW V8Ffp20qBaL3F+VDxSeO/a2ST+pkg1xtM2dXc0dIINQodO7IJosotVWu8TS7iDhumeW+qZrlRbtA YE= X-UI-Out-Filterresults: notjunk:1;V03:K0:Agat5pud3lA=:LlSe/CFlvjapk/qid83GkB yOup04EWajsvJFXv3emp2CwtFwuyF8v6GRxG/FQy0o1St6HiHurS8I3Na/A71kt6zvMsBDzbd xjgaXq34NC+H1jFvNLeS7sdTRj3lz0QQ52KyYCx8DA9BTbaCDe1naskvJDzr1fqXgWz/EJ82U tZAs38TueENR4sov2PkxGGcCIOrxIly25F4CU/ZAoL0/qsmmX7A7HpyXP6NGO437B5y3zKPDk r/dOOhqj2e5+qgyXa9m5IfDzgaTyrz84fNUq/jMfIcOes3H5dEzWcNiiD6djgsYlBKYHEf/Aa +EKD0IDi9rL3f5UC719YnoKJ/9lbdYe2rqeBQWhEHbZLMqGkZNarLUnjjHdz5+H9jxcFP6mwk UkwQMm16CGpSNgZrO0HUST4qPMizWBhdR/IwIOF049swOhttkNtiQRhKcCCrMq8zCTXb4EqjH /bLOTwEZ2zRqSSZ9iEy+e9V/24UM5EUyhVx+AYpa0+Y6dQFwxo8Y2tShe30/jkPr0R/lqFVIG bfRwtrLE0JsliMA4VvcbZExBDHjPln9ckw+7ahsYig9YER1C/Vz1frQmSJiTOJb1NUV3OazME vSatBIpC8q8pAx11WIB0oMtOd+MdRkraCUXWFVWwboY0UOzHC15HaOkCI0Ev9e3btVE0ZObbC 6pdozAKmGvetAEZUIVRxYpp/bFAIO2MB0QUSo8UJY66raTF17/xkq7ZwNOlwkM0prb7srTNxA NHxIkgSO27IzlyEImqD/rVL41MYKmkZ+gveH41GBWup7datM76b3spTTTTNR+t8/8P1x/3r+j MjfsdyzGkZAHlAzOkmx8Rhd+omSRPgWdDWrT79Gpiy7sihNfJ4msAMSk/gE+k6hun2/6C9p0q LpUmhTJu1zNGbgJsB3yEggcf1k9J19nOGcnjMT7/Bs6Bd0p+KW/rkOVAUrHEF1 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, 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: Thu, 08 Apr 2021 16:43:50 -0000 > Sent: Friday, April 09, 2021 at 3:00 AM > From: "David Brown" > To: "Jonathan Wakely" , "David Malcolm" > Cc: "GCC Development" , "Mark Wielaard" > Subject: Re: GCC association with the FSF > > On 07/04/2021 19:17, Jonathan Wakely via Gcc wrote: > > On Wed, 7 Apr 2021 at 15:04, David Malcolm wrote: > >> For myself, I'm interested in copyleft low-level tools being used to > >> build a Free Software operating system, but the "GNU" name may be > >> permanently tarnished for me; I have no wish to be associated with a > >> self-appointed "chief GNUisance". I hope the FSF can be saved, since > >> it would be extremely inconvenient to have to move. > > > > This matches my feelings. If the FSF can be saved, fine, but I don't > > think GCC needs to remain associated with it. > > > > If the GNU name is a problem, rename the projects to be simply "GCC", > > "Glibc", "GDB" etc without being an initialism. > > > > It should remain an acronym, but it should now stand for "GCC Compiler > Collection". That allows the project to be disassociated from the GNU > name while still subtly acknowledging its heritage. > > I am a gcc user, but not a developer or contributor. I think it is > important to appreciate the good RMS has done for the software world, > and to accept history as it has happened rather than how we wish it had > been. But going forward I don't think any project or organisation has > anything to gain by association with RMS, but will have much to lose. > To a large extent, he has done his job - the free and open source worlds > are now far too big and well-established to fail easily. The time for > fanaticism, ideology and childish (ref. "Chief GNUisance") and > anti-social leadership is over - pragmatism, practicality and > cooperation are the way of the future. It is time for the FSF to say to > RMS, "Thank you for all you have done. Now move over for the next > generation, have a happy retirement, and please don't spoil the future > for the rest of us". (We still need a few ideologists involved, to > remind us of important principles if anyone strays too far. It's like a > healthy democratic parliament requiring a few representatives from the > greens, communists and other niche parties - you just don't want them > running the show.) > > For me as a person, I cannot condone certain aspects of RMS' behaviour. > I strongly disapprove of "proof by accusation and rumour" or "trial by > public opinion", but there is enough documented evidence in his own > publications and clearly established personal accounts that no one can > be in doubt that his attitudes and behaviour are not acceptable by > modern standards and are discouraging to developers and users in the > FOSS community. (And yes, I mean FOSS here, not just free software.) > > From a practical viewpoint, I am concerned that opinions about him will > spread. If the gcc project is not disassociated from anything involving > RMS, I fear the project will suffer from that assosiation, no matter how > unfair it may be. At some point, someone in the public relations > department at IBM, Google, Facebook, ARM, or other big supporters of the > project will get the impression that the FSF and GNU are lead by a > misogynist who thinks child abuse is fine if the child consents, and > will cut off all support from the top down. The other companies will > immediately follow. The gcc lead developers like Ian, Jonathan, Joseph > and Nathan will be given the choice of leaving gcc or leaving the job > that puts food on their tables. gcc is not a hobby project run by > amateurs in their free time - it is a serious project that needs > commercial backing as well as the massive personal dedication it receive= s. If RMS in not indispensable, Ian, Jonathan, Joseph and Nathan are likewise not indispensable. Someone could that over and make their own project and lead it how they wish. There are many projects where the original author knows best where to lead. Classic examples include medical project Gnu Health and my project. Although can also mess a project up, mistakes are allowed. Einstein did not get his ideas from committees, neither did Stal= lman. At work, I have never encountered any committee that done me any good. A good book to read is Maskell's "The New Idea of a University". If some think serious maintainers care about some public relations group at IBM, Google, or Facebook, they are highly mistaken. I don't care. Stallman can think whatever he likes. There exist many valid opinions on questions like exactly how young people can be to get married or be depicted in pornography. New Hampshire law allows 13 year olds to get married. The only problem is that many western people are too far freaked out in relation to children, sex, and colonial guilt. > It is my opinion - entirely personal, and as a long and happy user > rather than a developer, and not speaking for my company or anyone else > - that gcc would be a stronger project if it were to separate from the > FSF and GNU. It should have a "board of directors", or steering > committee, or something similar - but these should be selected > democratically and openly in some manner, perhaps by votes from major > contributors and/or subproject maintainers. This board or committee > could have representatives from the gcc developers, from major > commercial contributors, from major users (Linux kernel people, Debian > folk, etc.), from target manufacturers (Intel, ARM, etc.), from ordinary > users - in short, it should represent the people who have most interest > in the future success of the project. > > It might also make sense to gang together with other important toolchain > projects, such as the binutils folk. > > > David Brown > (A mostly happy embedded gcc user.) > >