Remove RMS from the GCC Steering Committee

Remove RMS from the GCC Steering Committee

[Nathan Sidwell]

[double sigh, attaching a pdf causes it to be blocked, and I guess the number of 
URLs is also triggering a spam trap for the follow up.  I have removed many of 
the URLS from this, you'll have to use your google-fu for sources.  I emailed 
several members of the SC, and don't want to bomb them with yet a third copy. ]

Dear members of the GCC Steering Committee (SC),  I ask you to remove Richard 
Stallman (RMS) from the SC, or, should you chose not to do so, make a clear 
statement as to why he remains.

I am writing this publicly, as it is important we address the issue. In 2019, 
when RMS resigned from the FSF, I asked the SC about his status on the SC (the 
web site continued to list his affiliation as FSF).  I never saw as response. I 
failed to follow up. (FWIW, I never received a response to a technical licensing 
issue I asked in 2020. Something seems amiss.)

As this is public, even though I know you, the SC, know who I am, and I am lucky 
enough to count several of you as friends, I present some bona fides:
     • I am a long-time developer of GCC, having become involved during the EGCS 
days of the late 1990’s.
     • While there has been a time when I wasn’t as active as before or since, I 
have made many thousands of commits to GCC. Particularly in the C++ Front End.
     • You, the SC, have recognized my skills and named me as a co-maintainer of 
the C++ Front End.
     • In addition to the front end, I have implemented middle-end and backend 
changes and improvements.  For instance the core of the OpenAcc execution model, 
building on the excellent OpenMP support developed by Redhat.
     • Outside of upstream, I have ported GCC to several architectures.  Sadly 
several never saw the light of day, but they did pay the bills.
     • Historically, I reimplemented the gcov coverage system, and was a 
co-maintainer of that subsystem for some time.
     • I implemented several pieces of the Itanium C++ ABI – the nearest thing 
we have to a cross-platform ABI standard.
     • I was named a maintainer of the morpho (since removed) backend, and the 
nvidia backend originally authored by Bernd Schmidt (Tom de Vries has taken over 
that maintainance).
     • I’m nowhere near as prolific as other contributors, but I have been 
fortunate enough to work on a program that is exciting and useful to so many people.

I would rather not have to write this email.  Like many developers, I just want 
to write code. Right now we’re working towards the GCC 11 release.  I thought 
about deferring this email. But there’s never a good time, and bad behaviour 
needs to be addressed in the moment.  I have left this for too long already.

I used to think of GCC development as egalitarian, and therefore fair, and, by 
assumption, welcoming. That is not true. I’m a white dude with a British accent. 
/Of course/ I have white male privilege.  I used to joke that I fell into every 
job I’ve had (including my doctorate) – that, right there, is white male 
privilege.  I have so much, that I can move to a xenophobic racist country and 
get a complete pass from the ‘immigrants are bad’ mentality. Many of you on the 
SC have such privilege – if you don’t think such privilege affects you, /then 
you have it/.

Just letting the code speak for itself, /is not enough/. Egalitarianism would be 
fine in an equal world.  We do not live in that world.

Perhaps you discount the benefits of white male privilege.  You’re wrong.  Of 
course I cannot speak from experience, but being female in a misogynistic 
environment is /exhausting/. Being non-white in a racist society is 
/exhausting/.  You may think the current pre-release crunch is tiring – but it 
has an end and will stop. The adverse affects of white male privilege never stop.

Perhaps you do not see the need to attract a diverse population of developers. 
Why do you not want to evangelize to everyone the fun it is in writing 
compilers?  /You’re writing a program that writes programs!/ /You’re writing a 
program that can rewrite itself to run on a different CPU!/ /How meta do you 
want to go!?/

You cannot have missed the sparsity of women and people of color in compiler 
engineering (kaporcenter black tech workforce).  Maybe you fallaciously put that 
down to imbalances in education (leakytechpipeline)  How can we, the GCC 
community, be expected to address that?  Representation matters, we’re the problem.

In the before-time, I had heard that RMS was ‘difficult’, or ‘socially awkward’. 
  I had ignored the true toxicity he engenders. I’m sure you have too. It didn’t 
directly affect me. I didn’t need to interact with him.  I’m not a woman. It 
diminishes all of us to ignore it.
Let me list a few of the cases I have found.  Warning, this are extremely 
offensive repugnant opinions. Mostly referenced via  geekfeminism.wikia.org. It 
didn’t take me long to find them – I should have done so sooner and for that I 
am sorry.
     1. 'skeptical that voluntarily pedophilia harms children.’  stallman's own 
  archives 2006-mar-jun  I note that children are *incapable* of consenting. 
That’s what the age of consent means.
     2. 'end censorship of “child pornography”’. Stallman's archives 
2012-jul-oct.html Notice use of “quotes” to down play what is actually being 
requested.
     3. 'gentle expressions of attraction’ Stallman's archives 2012-jul-oct.html 
Condoning a variant of the wolf-whistle.  Unless one’s talking to one’s lover, 
‘gentle invitations for sex’ by a stranger is *grooming* (be it child or of-age).
     4. Defends someone charged with ‘"sexual assault" on a "child" after a 
session with a sex worker of age 16.’ stallman's archives 2018-jul-oct  Notice 
the quoting here, implying the *child* is not a child. ‘The article refers to 
the sex worker as a "child", but that is not so. Elsewhere it has been published 
that she is 16 years old. That is late adolescence, not childhood.’ No, they are 
a child, that’s what the ages of majority and consent mean.
     5. The ‘St Ignatius’ ‘EMACS virgins’ non-joke. ‘The commenter writes about 
seeing the routine when she was only 15, and how RMS singled her out several 
times during that performance:
        He actually pointed to me in the back and proclaimed, into the mic, "A 
GIRL!" causing the audience to turn and look. Mortifying. Then he proceeded to 
gesture toward me every time he referred to "EMACS Virgins." (I cannot believe 
that he is still doing the same talk 10+ years later.)’
        No wonder women want nothing to do with him.
     6. A business card that is completely repelling image on oreilly
     7. He knows those cards are inappropriate.  He broke the code of conduct he 
helped author. wiredferret's twitter feed.
     8. I understand he’s tried to circumvent such codes of conduct by asking 
women to meet him outside of the conference venue. _sagesharp_'s twitter feed.
     9. He doesn’t acknowledge the few women he has worked with ‘I don’t have 
any experience working with women in programming projects; I don’t think that 
any volunteered to work on Emacs or GCC.’  Completely ignoring Sandra Loosemore, 
who is a coauthor, with him, of the Glibc manual. Sandra was involved with LISP 
standardization, so I would be surprised if he was unaware of her involvement 
there. As you well know, she has worked significantly on GCC,  GCC has several 
other women contributors, but too few for complacency.
     10. ‘My first interaction with RMS was at a hacker con at 19. He asked my 
name, I gave it, whether I went to MIT (I had an MIT shirt on), and after 
confirmation I did, asked me on a date. I said no. That was our entire 
conversation.’ corbett's twitter feed. This is but one of many reports of 
utterly inappropriate social interactions.
That list is no where near exhaustive, nor is it prioritized. As a personal 
anecdote, an acquaintance of mine who was at MIT, related that she was warned 
about RMS’s behaviour, and to never be alone with him.  It wasn’t an isolated 
warning.

Perhaps you’ll discount these as hearsay, or construct a rationale that the 
reporter was misinterpreting intent or something.  This is not a court of law. 
So many are pointing in the same direction that you cannot ignore the 
implication.  Perhaps you’ll claim my request is ‘cancel culture’.  That is the 
cry of the hypocrite – this is ‘actions have consequences’.  While I know 
neither you nor RMS will make a fallacious ‘but my rights’ accusation, others 
may.  The USA is not the world and the SC is not the US government.  For those 
in the USA, the (inapplicable) first amendment provides 5 rights, including 
showing an unwelcome guest the door.

The GCC web site mentions that SC membership is a /personal membership/:

‘Membership in the steering committee is a personal membership. Affiliations are 
listed for identification purposes only; steering committee members do not 
represent their employers or academic institutions. Generally speaking, 
committee members were chosen to represent the interests of communities (e.g. 
Fortran users, embedded systems developers, kernel hackers), not companies.’		 
gcc website steering committee
Thus, /you/, the SC members are each personally endorsing RMS via his SC 
membership. At best, /you/ are saying that his behaviour is not a hindrance to 
GCC’s mission.  At worse, /you/ are saying his behaviour is acceptable.  By 
accepting RMS on the SC, /we/, the GCC developer community, are saying the same. 
We should think about that.

RMS is no longer a developer of GCC, the most recent commit I can find regards 
SCO in 2003.  Prior to that there were commits in 1997, but significantly less 
than 1994 and earlier.  GCC’s implementation language is now C++, which I 
believe RMS neither uses nor likes.  When was RMS’ most recent positive input to 
the GCC project? Even if it was recent and significant, that doesn’t mean his 
toxic behavior should be accepted.

Our intent is to be welcoming, but RMS’s toxicity is repellent. We might not 
desire that toxicity reflect upon us, but it does. Our intent may be good, but 
intent is not important – impact is, and /harm is being done/. Fix it.

I am asking you to make a positive move towards more inclusivity and diversity. 
Perhaps you don’t think that is important – we’re about the code.  That’s a 
privileged view point. The other popular open source compiler has a much more 
inclusive community, and its conferences are a joy because of that.  And they 
put paid to the fallacious argument that women ‘just don’t like compilers’ – 
what rot!

My current workplace is a joy because of the huge step towards gender equality 
amongst the engineers.  You might not realize how enlightening that is without 
experiencing it. (And yes, it could be better.)

In the alternative, I want you to make a definitive statement about why you 
choose not to make such a change.  Do not hide behind silence.  Silence is 
agreeing with the status quo.  Further, if you choose not to make a change, do 
not hide behind a technicality. (My understanding is that RMS has veto power.) 
The rules of the SC are not immutable laws of the universe, nor does humanity 
have immutable laws cast in stone.  The EGCS project showed that we can make 
changes with GCC’s social organization.  If we fail to do so, it will continue 
to be harder and harder to attract new talent to GCC development.

Address this as a priority. Address it now.
-- 
Nathan Sidwell

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

What is this?  The usual rant of freaked out madness!!!

---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Saturday, March 27, 2021 at 8:02 AM
> From: "Nathan Sidwell" <nathan@acm.org>
> To: "GCC Development" <gcc@gcc.gnu.org>
> Subject: Remove RMS from the GCC Steering Committee
>
> [double sigh, attaching a pdf causes it to be blocked, and I guess the number of 
> URLs is also triggering a spam trap for the follow up.  I have removed many of 
> the URLS from this, you'll have to use your google-fu for sources.  I emailed 
> several members of the SC, and don't want to bomb them with yet a third copy. ]
> 
> Dear members of the GCC Steering Committee (SC),  I ask you to remove Richard 
> Stallman (RMS) from the SC, or, should you chose not to do so, make a clear 
> statement as to why he remains.
> 
> I am writing this publicly, as it is important we address the issue. In 2019, 
> when RMS resigned from the FSF, I asked the SC about his status on the SC (the 
> web site continued to list his affiliation as FSF).  I never saw as response. I 
> failed to follow up. (FWIW, I never received a response to a technical licensing 
> issue I asked in 2020. Something seems amiss.)
> 
> As this is public, even though I know you, the SC, know who I am, and I am lucky 
> enough to count several of you as friends, I present some bona fides:
>      • I am a long-time developer of GCC, having become involved during the EGCS 
> days of the late 1990’s.
>      • While there has been a time when I wasn’t as active as before or since, I 
> have made many thousands of commits to GCC. Particularly in the C++ Front End.
>      • You, the SC, have recognized my skills and named me as a co-maintainer of 
> the C++ Front End.
>      • In addition to the front end, I have implemented middle-end and backend 
> changes and improvements.  For instance the core of the OpenAcc execution model, 
> building on the excellent OpenMP support developed by Redhat.
>      • Outside of upstream, I have ported GCC to several architectures.  Sadly 
> several never saw the light of day, but they did pay the bills.
>      • Historically, I reimplemented the gcov coverage system, and was a 
> co-maintainer of that subsystem for some time.
>      • I implemented several pieces of the Itanium C++ ABI – the nearest thing 
> we have to a cross-platform ABI standard.
>      • I was named a maintainer of the morpho (since removed) backend, and the 
> nvidia backend originally authored by Bernd Schmidt (Tom de Vries has taken over 
> that maintainance).
>      • I’m nowhere near as prolific as other contributors, but I have been 
> fortunate enough to work on a program that is exciting and useful to so many people.
> 
> I would rather not have to write this email.  Like many developers, I just want 
> to write code. Right now we’re working towards the GCC 11 release.  I thought 
> about deferring this email. But there’s never a good time, and bad behaviour 
> needs to be addressed in the moment.  I have left this for too long already.
> 
> I used to think of GCC development as egalitarian, and therefore fair, and, by 
> assumption, welcoming. That is not true. I’m a white dude with a British accent. 
> /Of course/ I have white male privilege.  I used to joke that I fell into every 
> job I’ve had (including my doctorate) – that, right there, is white male 
> privilege.  I have so much, that I can move to a xenophobic racist country and 
> get a complete pass from the ‘immigrants are bad’ mentality. Many of you on the 
> SC have such privilege – if you don’t think such privilege affects you, /then 
> you have it/.
> 
> Just letting the code speak for itself, /is not enough/. Egalitarianism would be 
> fine in an equal world.  We do not live in that world.
> 
> Perhaps you discount the benefits of white male privilege.  You’re wrong.  Of 
> course I cannot speak from experience, but being female in a misogynistic 
> environment is /exhausting/. Being non-white in a racist society is 
> /exhausting/.  You may think the current pre-release crunch is tiring – but it 
> has an end and will stop. The adverse affects of white male privilege never stop.
> 
> Perhaps you do not see the need to attract a diverse population of developers. 
> Why do you not want to evangelize to everyone the fun it is in writing 
> compilers?  /You’re writing a program that writes programs!/ /You’re writing a 
> program that can rewrite itself to run on a different CPU!/ /How meta do you 
> want to go!?/
> 
> You cannot have missed the sparsity of women and people of color in compiler 
> engineering (kaporcenter black tech workforce).  Maybe you fallaciously put that 
> down to imbalances in education (leakytechpipeline)  How can we, the GCC 
> community, be expected to address that?  Representation matters, we’re the problem.
> 
> In the before-time, I had heard that RMS was ‘difficult’, or ‘socially awkward’. 
>   I had ignored the true toxicity he engenders. I’m sure you have too. It didn’t 
> directly affect me. I didn’t need to interact with him.  I’m not a woman. It 
> diminishes all of us to ignore it.
> Let me list a few of the cases I have found.  Warning, this are extremely 
> offensive repugnant opinions. Mostly referenced via  geekfeminism.wikia.org. It 
> didn’t take me long to find them – I should have done so sooner and for that I 
> am sorry.
>      1. 'skeptical that voluntarily pedophilia harms children.’  stallman's own 
>   archives 2006-mar-jun  I note that children are *incapable* of consenting. 
> That’s what the age of consent means.
>      2. 'end censorship of “child pornography”’. Stallman's archives 
> 2012-jul-oct.html Notice use of “quotes” to down play what is actually being 
> requested.
>      3. 'gentle expressions of attraction’ Stallman's archives 2012-jul-oct.html 
> Condoning a variant of the wolf-whistle.  Unless one’s talking to one’s lover, 
> ‘gentle invitations for sex’ by a stranger is *grooming* (be it child or of-age).
>      4. Defends someone charged with ‘"sexual assault" on a "child" after a 
> session with a sex worker of age 16.’ stallman's archives 2018-jul-oct  Notice 
> the quoting here, implying the *child* is not a child. ‘The article refers to 
> the sex worker as a "child", but that is not so. Elsewhere it has been published 
> that she is 16 years old. That is late adolescence, not childhood.’ No, they are 
> a child, that’s what the ages of majority and consent mean.
>      5. The ‘St Ignatius’ ‘EMACS virgins’ non-joke. ‘The commenter writes about 
> seeing the routine when she was only 15, and how RMS singled her out several 
> times during that performance:
>         He actually pointed to me in the back and proclaimed, into the mic, "A 
> GIRL!" causing the audience to turn and look. Mortifying. Then he proceeded to 
> gesture toward me every time he referred to "EMACS Virgins." (I cannot believe 
> that he is still doing the same talk 10+ years later.)’
>         No wonder women want nothing to do with him.
>      6. A business card that is completely repelling image on oreilly
>      7. He knows those cards are inappropriate.  He broke the code of conduct he 
> helped author. wiredferret's twitter feed.
>      8. I understand he’s tried to circumvent such codes of conduct by asking 
> women to meet him outside of the conference venue. _sagesharp_'s twitter feed.
>      9. He doesn’t acknowledge the few women he has worked with ‘I don’t have 
> any experience working with women in programming projects; I don’t think that 
> any volunteered to work on Emacs or GCC.’  Completely ignoring Sandra Loosemore, 
> who is a coauthor, with him, of the Glibc manual. Sandra was involved with LISP 
> standardization, so I would be surprised if he was unaware of her involvement 
> there. As you well know, she has worked significantly on GCC,  GCC has several 
> other women contributors, but too few for complacency.
>      10. ‘My first interaction with RMS was at a hacker con at 19. He asked my 
> name, I gave it, whether I went to MIT (I had an MIT shirt on), and after 
> confirmation I did, asked me on a date. I said no. That was our entire 
> conversation.’ corbett's twitter feed. This is but one of many reports of 
> utterly inappropriate social interactions.
> That list is no where near exhaustive, nor is it prioritized. As a personal 
> anecdote, an acquaintance of mine who was at MIT, related that she was warned 
> about RMS’s behaviour, and to never be alone with him.  It wasn’t an isolated 
> warning.
> 
> Perhaps you’ll discount these as hearsay, or construct a rationale that the 
> reporter was misinterpreting intent or something.  This is not a court of law. 
> So many are pointing in the same direction that you cannot ignore the 
> implication.  Perhaps you’ll claim my request is ‘cancel culture’.  That is the 
> cry of the hypocrite – this is ‘actions have consequences’.  While I know 
> neither you nor RMS will make a fallacious ‘but my rights’ accusation, others 
> may.  The USA is not the world and the SC is not the US government.  For those 
> in the USA, the (inapplicable) first amendment provides 5 rights, including 
> showing an unwelcome guest the door.
> 
> The GCC web site mentions that SC membership is a /personal membership/:
> 
> ‘Membership in the steering committee is a personal membership. Affiliations are 
> listed for identification purposes only; steering committee members do not 
> represent their employers or academic institutions. Generally speaking, 
> committee members were chosen to represent the interests of communities (e.g. 
> Fortran users, embedded systems developers, kernel hackers), not companies.’		 
> gcc website steering committee
> Thus, /you/, the SC members are each personally endorsing RMS via his SC 
> membership. At best, /you/ are saying that his behaviour is not a hindrance to 
> GCC’s mission.  At worse, /you/ are saying his behaviour is acceptable.  By 
> accepting RMS on the SC, /we/, the GCC developer community, are saying the same. 
> We should think about that.
> 
> RMS is no longer a developer of GCC, the most recent commit I can find regards 
> SCO in 2003.  Prior to that there were commits in 1997, but significantly less 
> than 1994 and earlier.  GCC’s implementation language is now C++, which I 
> believe RMS neither uses nor likes.  When was RMS’ most recent positive input to 
> the GCC project? Even if it was recent and significant, that doesn’t mean his 
> toxic behavior should be accepted.
> 
> Our intent is to be welcoming, but RMS’s toxicity is repellent. We might not 
> desire that toxicity reflect upon us, but it does. Our intent may be good, but 
> intent is not important – impact is, and /harm is being done/. Fix it.
> 
> I am asking you to make a positive move towards more inclusivity and diversity. 
> Perhaps you don’t think that is important – we’re about the code.  That’s a 
> privileged view point. The other popular open source compiler has a much more 
> inclusive community, and its conferences are a joy because of that.  And they 
> put paid to the fallacious argument that women ‘just don’t like compilers’ – 
> what rot!
> 
> My current workplace is a joy because of the huge step towards gender equality 
> amongst the engineers.  You might not realize how enlightening that is without 
> experiencing it. (And yes, it could be better.)
> 
> In the alternative, I want you to make a definitive statement about why you 
> choose not to make such a change.  Do not hide behind silence.  Silence is 
> agreeing with the status quo.  Further, if you choose not to make a change, do 
> not hide behind a technicality. (My understanding is that RMS has veto power.) 
> The rules of the SC are not immutable laws of the universe, nor does humanity 
> have immutable laws cast in stone.  The EGCS project showed that we can make 
> changes with GCC’s social organization.  If we fail to do so, it will continue 
> to be harder and harder to attract new talent to GCC development.
> 
> Address this as a priority. Address it now.
> -- 
> Nathan Sidwell
>

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Fri, 26 Mar 2021, 20:03 Nathan Sidwell, <nathan@acm.org> wrote:

>
> Dear members of the GCC Steering Committee (SC),  I ask you to remove
> Richard
> Stallman (RMS) from the SC, or, should you chose not to do so, make a
> clear
> statement as to why he remains.
>

I second Nathan's request, and agree with everything he said.

It's important for GCC today, and for potential future contributors.

Re: Remove RMS from the GCC Steering Committee

[Mark Wielaard]

On Fri, Mar 26, 2021 at 08:51:21PM +0000, Jonathan Wakely via Gcc wrote:
> On Fri, 26 Mar 2021, 20:03 Nathan Sidwell, <nathan@acm.org> wrote:
> >
> > Dear members of the GCC Steering Committee (SC), I ask you to
> > remove Richard Stallman (RMS) from the SC, or, should you chose
> > not to do so, make a clear statement as to why he remains.
> 
> I second Nathan's request, and agree with everything he said.
> 
> It's important for GCC today, and for potential future contributors.

Thanks for starting this discussion. I agree given the recent
controversy and the long history of problematic behavior it would be
good for the Steering Committee to consider whether it still wants to
be associated with the FSF. And whether to remove or replace RMS on
the steering committee.

Thanks,

Mark

Re: Remove RMS from the GCC Steering Committee

[David Malcolm]

On Fri, 2021-03-26 at 20:51 +0000, Jonathan Wakely via Gcc wrote:
> On Fri, 26 Mar 2021, 20:03 Nathan Sidwell, <nathan@acm.org> wrote:
> 
> > 
> > Dear members of the GCC Steering Committee (SC),  I ask you to
> > remove
> > Richard
> > Stallman (RMS) from the SC, or, should you chose not to do so, make
> > a
> > clear
> > statement as to why he remains.
> > 
> 
> I second Nathan's request, and agree with everything he said.

To any observers seeing this email unfamiliar with the project, I
wanted to note that Jonathan is currently one of the most prolific
contributors to GCC, showing up as #2 on this list for commit count to
GCC over the last year, with 590 commits:
  https://www.openhub.net/p/gcc/contributors?query=&time_span=&sort=twelve_month_commits
[1]

I too second Nathan's request, and agree with what he said.

(Nathan shows up as #7 on that list, and Marek who has also replied
whilst I've been writing this shows up as #9; I'm #11 on that list).

> It's important for GCC today, and for potential future contributors.

Agreed.

I own an autographed copy of RMS's book from when I used to look up to
him, but, frankly, I think the cause of Free Software would have been
helped greatly by him taking retirement from the FSF/GNU at least a
decade ago.

I should note that I'm writing this in a personal capacity, not on
behalf of Red Hat, though FWIW Red Hat has said the following on the
matter of RMS's return to the FSF board:
https://www.redhat.com/en/blog/red-hat-statement-about-richard-stallmans-return-free-software-foundation-board


Now to get back to fixing bugs...
Dave

[1] actually the 12 month period ending 2 months ago, since that was
the last time the project was rescanned by openhub

Re: Remove RMS from the GCC Steering Committee

[Marek Polacek]

On Fri, Mar 26, 2021 at 04:02:30PM -0400, Nathan Sidwell wrote:
> [double sigh, attaching a pdf causes it to be blocked, and I guess the
> number of URLs is also triggering a spam trap for the follow up.  I have
> removed many of the URLS from this, you'll have to use your google-fu for
> sources.  I emailed several members of the SC, and don't want to bomb them
> with yet a third copy. ]
> 
> Dear members of the GCC Steering Committee (SC),  I ask you to remove
> Richard Stallman (RMS) from the SC, or, should you chose not to do so, make
> a clear statement as to why he remains.

[...]

> I am writing this publicly, as it is important we address the issue. In
> 2019, when RMS resigned from the FSF, I asked the SC about his status on the
> SC (the web site continued to list his affiliation as FSF).  I never saw as
> response. I failed to follow up. (FWIW, I never received a response to a
> technical licensing issue I asked in 2020. Something seems amiss.)
> In the alternative, I want you to make a definitive statement about why you
> choose not to make such a change.  Do not hide behind silence.  Silence is
> agreeing with the status quo.  Further, if you choose not to make a change,
> do not hide behind a technicality. (My understanding is that RMS has veto
> power.) The rules of the SC are not immutable laws of the universe, nor does
> humanity have immutable laws cast in stone.  The EGCS project showed that we
> can make changes with GCC’s social organization.  If we fail to do so, it
> will continue to be harder and harder to attract new talent to GCC
> development.

I support this and believe we ought to act now.

Marek

Re: Remove RMS from the GCC Steering Committee

[Hi-Angel]

Hello! I don't know all the details, and it surprises me nobody is
asking for them. Let me be the first.

On Fri, 26 Mar 2021 at 23:03, Nathan Sidwell <nathan@acm.org> wrote:
> I’m a white dude with a British accent.
> /Of course/ I have white male privilege.

So, this text makes me feel sorry for the author, but at the same time
makes it clear he is writing under some emotional burnout that he
unambiguously shown he is experiencing.

I think before making any kind of decision it would be fair to ask the
author to provide references to the points he has written below.
Because someone's career is at stake, so that kind of decision
shouldn't be done that easily, just because someone wrote that on the
internet, right? And yes, I realize that "someone" is or was a
prolific developer, but so was RMS whom we are discussing here.

We all do code-review to look for developer's mistakes, and I think
it's useful to do the same here.

So, Nathan Sidwell, could you please provide references for the
problems you mentioned below?

> In the before-time, I had heard that RMS was ‘difficult’, or ‘socially awkward’.
>   I had ignored the true toxicity he engenders. I’m sure you have too. It didn’t
> directly affect me. I didn’t need to interact with him.  I’m not a woman. It
> diminishes all of us to ignore it.
> Let me list a few of the cases I have found.  Warning, this are extremely
> offensive repugnant opinions. Mostly referenced via  geekfeminism.wikia.org. It
> didn’t take me long to find them – I should have done so sooner and for that I
> am sorry.
>      1. 'skeptical that voluntarily pedophilia harms children.’  stallman's own
>   archives 2006-mar-jun  I note that children are *incapable* of consenting.
> That’s what the age of consent means.
>      2. 'end censorship of “child pornography”’. Stallman's archives
> 2012-jul-oct.html Notice use of “quotes” to down play what is actually being
> requested.
>      3. 'gentle expressions of attraction’ Stallman's archives 2012-jul-oct.html
> Condoning a variant of the wolf-whistle.  Unless one’s talking to one’s lover,
> ‘gentle invitations for sex’ by a stranger is *grooming* (be it child or of-age).
>      4. Defends someone charged with ‘"sexual assault" on a "child" after a
> session with a sex worker of age 16.’ stallman's archives 2018-jul-oct  Notice
> the quoting here, implying the *child* is not a child. ‘The article refers to
> the sex worker as a "child", but that is not so. Elsewhere it has been published
> that she is 16 years old. That is late adolescence, not childhood.’ No, they are
> a child, that’s what the ages of majority and consent mean.
>      5. The ‘St Ignatius’ ‘EMACS virgins’ non-joke. ‘The commenter writes about
> seeing the routine when she was only 15, and how RMS singled her out several
> times during that performance:
>         He actually pointed to me in the back and proclaimed, into the mic, "A
> GIRL!" causing the audience to turn and look. Mortifying. Then he proceeded to
> gesture toward me every time he referred to "EMACS Virgins." (I cannot believe
> that he is still doing the same talk 10+ years later.)’
>         No wonder women want nothing to do with him.
>      6. A business card that is completely repelling image on oreilly
>      7. He knows those cards are inappropriate.  He broke the code of conduct he
> helped author. wiredferret's twitter feed.
>      8. I understand he’s tried to circumvent such codes of conduct by asking
> women to meet him outside of the conference venue. _sagesharp_'s twitter feed.
>      9. He doesn’t acknowledge the few women he has worked with ‘I don’t have
> any experience working with women in programming projects; I don’t think that
> any volunteered to work on Emacs or GCC.’  Completely ignoring Sandra Loosemore,
> who is a coauthor, with him, of the Glibc manual. Sandra was involved with LISP
> standardization, so I would be surprised if he was unaware of her involvement
> there. As you well know, she has worked significantly on GCC,  GCC has several
> other women contributors, but too few for complacency.
>      10. ‘My first interaction with RMS was at a hacker con at 19. He asked my
> name, I gave it, whether I went to MIT (I had an MIT shirt on), and after
> confirmation I did, asked me on a date. I said no. That was our entire
> conversation.’ corbett's twitter feed. This is but one of many reports of
> utterly inappropriate social interactions.
> That list is no where near exhaustive, nor is it prioritized. As a personal
> anecdote, an acquaintance of mine who was at MIT, related that she was warned
> about RMS’s behaviour, and to never be alone with him.  It wasn’t an isolated
> warning.

Re: Remove RMS from the GCC Steering Committee

[Thomas Rodgers]

On 2021-03-26 15:53, Hi-Angel via Gcc wrote:

> Hello! I don't know all the details, and it surprises me nobody is
> asking for them. Let me be the first.
> 

A cursory reading of the top of Nathan's email states the reason for not 
including the URLs, but ~half of the cited points come from Stallman's 
own archives, which can be found at -

https://stallman.org/archive.html

And for the rest, Nathan clearly indicates where (for those skilled in 
the ways of Let Me Google That For You) to find the same information.

<... snip ...>

> (disclaimer: I'm just a random reader of the ML)

Noted.

Re: Remove RMS from the GCC Steering Committee

[Didier Kryn]

    I've been lurking on this list for a while but never contributed in
any way to the project. Therefore I understand my voice has little weight.

    I'm terrified by this campaign of harassment against the person who
has given the biggest contribution to free software. This confirms to my
eyes that the People *is not* the defensor of Liberty and only the law
can defend it. The success of this campaign will prove that even the
liberty to express personnal opinions seems excessive to the People.
This is how terror begins.

--     Didier

Re: Remove RMS from the GCC Steering Committee

[Andrea Corallo]

Didier Kryn <kryn@in2p3.fr> writes:

>     I'm terrified by this campaign of harassment against the person who
> has given the biggest contribution to free software.

FWIW I find this terrifying too.  What scare me the most is that people
supporting RMS are indeed scared of coming out publicly by the
aggressiveness of the campaign itself.

Each one of us can be morally judged by others: how do we behave, what
we write, what's the company we work for...  I can myself be very
sensitive to some of these topics, but this is not what Free Software is
about.  Free Software is about Free Software and IMHO we should be here
just to progress on that.

Regards

  Andrea

Re: Remove RMS from the GCC Steering Committee

[Christophe de Dinechin]

> On 27 Mar 2021, at 08:08, Didier Kryn <kryn@in2p3.fr> wrote:
> 
>     I've been lurking on this list for a while but never contributed in
> any way to the project. Therefore I understand my voice has little weight.
> 
>     I'm terrified by this campaign of harassment against the person who
> has given the biggest contribution to free software.

+1

> This confirms to my
> eyes that the People *is not* the defensor of Liberty and only the law
> can defend it. The success of this campaign will prove that even the
> liberty to express personnal opinions seems excessive to the People.
> This is how terror begins.
> 
> --     Didier
> 
> 

Re: Remove RMS from the GCC Steering Committee

[Alexandre Oliva]

Nathan,

I think you identify an important problem of gender imbalance in our
community.  It is quite likely that finding ways to make our community
more welcoming to demographic groups that are currently less present
than in the distribution in the global population could reduce this
imbalance.

However, your diagnosis as to the supposed cause of the problem makes no
sense to me.  You said yourself that Stallman has not participated in
our community for decades.  Much as I know, his very hands-off influence
in the SC has been mostly limited to licensing and strategic issues,
e.g. the GPLv3 and Runtime Exception relicensing, to ensure copyleft
defenses were in place to avoid abuse of such features as plugins.


It may be very convenient to paint a boogey-man and expel it because
that became fashionable.  But sacrificing a goat or a lamb does not
expiate our own sins, and expelling someone who hasn't even been present
in the community can't be expected to make any real difference to that
matter; it would rather make us seem *less* welcoming and more
intolerant, and suggest other motivations for the move.


Let's be real and honest, when was the last time anyone in the GCC
community was called out for sexist behavior?  When was there even
conversation about it, and about how sexist behavior is not acceptable
and not to be accepted among participants in the GCC community?  What
was our latest collective action to promote e.g. gender equity within
the community?

If we were to shift our collective blame over this very real and
undesirable problem to someone who has any direct authority over the
project, why not suggesting expelling e.g. the entire Steering Committee
for its evident failure to address the problem?  (I don't think it's a
good idea, but that would be the first thing to try if we were to blame
"management"/"leadership" rather than ourselves for it)

What could support any rational belief that having RMS one extra level
removed from our technical community would bring about anything
resembling a solution to the very undesirable and unjust gender
imbalance you've correctly identified?


The action you propose, besides the absence of effect in making our
community actually more welcoming, because he's already absent, would
send the opposite of a welcoming signal to people with controversial or
impopular opinions, to people at a certain spot in the neurodiversity
spectrum, and to many others who oppose this sort of mob rule.


How about we set out to take individual and collective actions that
actually address the problem *in* our community?  We don't need anyone's
approval to call out sexist acts, nor to invite and train people with an
interest in compiler technology, nor to maintain a welcoming atmosphere.

A regime of terror to maintain a false appearance of a welcoming
atmosphere won't get us there.

If we undertake such actions, individually or collecetively, you might
be surprised (but I won't be) that he, even absent from the community,
would support these actions, which is the very opposite of the picture
you paint.

Our taking effective action on our own would help show what the real
issues and intents are, and it would tell apart those who are really
interested in solving the gender imbalance and the social injustices
causing it, like you and me, from those who are abusing that flag as a
trojan horse to serve nefarious purposes, as suggested and illustrated
in https://ultralux97.medium.com/stallman-must-be-removed-a3061b09fb22


-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Sat, 27 Mar 2021, 13:40 Alexandre Oliva via Gcc, <gcc@gcc.gnu.org> wrote:

>
> What could support any rational belief that having RMS one extra level
> removed from our technical community would bring about anything
> resembling a solution to the very undesirable and unjust gender
> imbalance you've correctly identified?
>

I completely agree that more work is needed to address the very real
imbalance. But listing his name on our web page as a leader of the project
surely makes a difference to how the project is perceived.

The active developers know he is not involved in any significant way, but
you wouldn't know that from the web page. The link to the SC is right at
the top of the gcc.gnu.org home page. Surely that gives a misleading
impression to potential new contributors, of all genders and backgrounds.
Is it helpful to give that impression?

If the SC decision is that it's fine, then making a statement to that
effect seems necessary. Which is the alternative Nathan asked for. Act or
explain, but don't stay silent. I think it's fair to ask for that.

Re: Remove RMS from the GCC Steering Committee

[Alexandre Oliva]

On Mar 27, 2021, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:

> But listing his name on our web page as a leader of the project
> surely makes a difference to how the project is perceived.

You're probably right that it does, just maybe not quite in the way you
seem to perceive it.

The Free Software community is a lot more diverse in opinions than the
corporate-centered fossal scene where the present moral panic (no
offense intended with this term; I aim to *not* pass a judgment on its
legitimacy by using it) appears to be running strongest.

If FSF's experiences in 2019 are of any use, though the wave of
community pressure for Richard's removal or resignation hit hard, the
wave of complaints that he had resigned, shortly thereafter, was about
an order of magnitude stronger, according to my analysis of the data
that was made available to me.

Right now, published voices are quite divided, but there are also lots
of people being driven into silence by the aggressiveness of the
emotional peer pressure.  There are also reports of one-sided corporate
pressure.  Richard's support base is not quite as vocal, furious or
deep-pocketed, but it's far more numerous and more discrete.

All in all, it looks to me like, in the long term, a public stance in
alignment with present emotional demands is more likely to backfire, and
make the project seem less welcoming, than staying put.

> The active developers know he is not involved in any significant way, but
> you wouldn't know that from the web page.

You wouldn't know about allegations against him from the web page
either.  It's quite easy to find them in web searches, and they're also
consistent in disclaiming his direct participation in software
development projects, so it should be fine.

> Is it helpful to give that impression?

At least in my circles, his name signals strong commitment to respect
for the freedoms of software users, and that's the criterion that IMHO
should matter the most for GNU and all of its subprojects.

As for being inclusive and kind, these are also very important goals
that we should devote attention and effort to.  But despite numerous
claims, these are not points of dissent with him.  The fears spread by
this sort of campaign are far more effective at pushing contributors
away than the reality that they twist and exaggerate.


> If the SC decision is that it's fine, then making a statement to that
> effect seems necessary.

It looks like statements of any position whatsoever are invitations for
pressure and trouble right now.


Now, there's another thing I've learned during my tenure at the FSF:
pressure upon decision-making bodies is not conducive of or propitious
for long-term reasoning or rational, thought-through decisions.  It
takes time for difficult decisions to mature, even for an individual,
let alone for a group that may require multiple cycles of interaction
for convergence.

I've learned that this kind of pressure is undesirable, when I worked to
foment it and then was taught, even by the very person who was supported
by that pressure, that, rather than offer useful guidance, pressure
created difficulties for the collective decision-making body.


So, thanks for listening, and for keeping this conversation civil and
kind despite the very strong emotions that a lot of people are feeling
and expressing,

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: Remove RMS from the GCC Steering Committee

[Siddhesh Poyarekar]

On 3/27/21 7:08 PM, Alexandre Oliva via Gcc wrote:
> It may be very convenient to paint a boogey-man and expel it because
> that became fashionable.  But sacrificing a goat or a lamb does not
> expiate our own sins, and expelling someone who hasn't even been present
> in the community can't be expected to make any real difference to that
> matter; it would rather make us seem *less* welcoming and more
> intolerant, and suggest other motivations for the move.

Except that it's not a boogeyman.  There is evidence for the documented 
instances of misconduct and have been corroborated by multiple people.

> Let's be real and honest, when was the last time anyone in the GCC
> community was called out for sexist behavior?  When was there even
> conversation about it, and about how sexist behavior is not acceptable
> and not to be accepted among participants in the GCC community?  What
> was our latest collective action to promote e.g. gender equity within
> the community?

The discussion is about RMS' damaging conduct (especially with 
non-privileged groups) over the years and the steering committees stand 
on it, not about steps we take to make the community more welcoming to 
non-privileged groups.  The latter definitely needs a discussion, but as 
far as this thread is concerned, it is a digression.

> If we were to shift our collective blame over this very real and
> undesirable problem to someone who has any direct authority over the
> project, why not suggesting expelling e.g. the entire Steering Committee
> for its evident failure to address the problem?  (I don't think it's a
> good idea, but that would be the first thing to try if we were to blame
> "management"/"leadership" rather than ourselves for it)

Nope, you're the one shifting blame for RMS' conduct on to the steering 
committee and the gcc community.

> What could support any rational belief that having RMS one extra level
> removed from our technical community would bring about anything
> resembling a solution to the very undesirable and unjust gender
> imbalance you've correctly identified?

No but it will make it clear that toxic behaviour has no place in the 
gcc community.  That's step zero.  The FSF still hasn't got its act 
together in that regard unfortunately.

> How about we set out to take individual and collective actions that
> actually address the problem *in* our community?  We don't need anyone's
> approval to call out sexist acts, nor to invite and train people with an
> interest in compiler technology, nor to maintain a welcoming atmosphere.

Sexist acts, discriminatory comments and inappropriate behaviour by RMS 
have been called out.  It is now the steering committee's responsibility 
to share their stand on it.

On 3/27/21 9:15 PM, Alexandre Oliva via Gcc wrote:
 > It looks like statements of any position whatsoever are invitations
 > for pressure and trouble right now.

On the flip side, not making a statement would be a statement in itself. 
  You know that though, which is why you advocate silence.

Siddhesh

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

It's not a good idea to disrespect the Gnu Father.

---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Sunday, March 28, 2021 at 5:12 AM
> From: "Siddhesh Poyarekar" <siddhesh@gotplt.org>
> To: "Alexandre Oliva" <oliva@gnu.org>, "Nathan Sidwell" <nathan@acm.org>
> Cc: "GCC Development" <gcc@gcc.gnu.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> On 3/27/21 7:08 PM, Alexandre Oliva via Gcc wrote:
> > It may be very convenient to paint a boogey-man and expel it because
> > that became fashionable.  But sacrificing a goat or a lamb does not
> > expiate our own sins, and expelling someone who hasn't even been present
> > in the community can't be expected to make any real difference to that
> > matter; it would rather make us seem *less* welcoming and more
> > intolerant, and suggest other motivations for the move.
>
> Except that it's not a boogeyman.  There is evidence for the documented
> instances of misconduct and have been corroborated by multiple people.
>
> > Let's be real and honest, when was the last time anyone in the GCC
> > community was called out for sexist behavior?  When was there even
> > conversation about it, and about how sexist behavior is not acceptable
> > and not to be accepted among participants in the GCC community?  What
> > was our latest collective action to promote e.g. gender equity within
> > the community?
>
> The discussion is about RMS' damaging conduct (especially with
> non-privileged groups) over the years and the steering committees stand
> on it, not about steps we take to make the community more welcoming to
> non-privileged groups.  The latter definitely needs a discussion, but as
> far as this thread is concerned, it is a digression.
>
> > If we were to shift our collective blame over this very real and
> > undesirable problem to someone who has any direct authority over the
> > project, why not suggesting expelling e.g. the entire Steering Committee
> > for its evident failure to address the problem?  (I don't think it's a
> > good idea, but that would be the first thing to try if we were to blame
> > "management"/"leadership" rather than ourselves for it)
>
> Nope, you're the one shifting blame for RMS' conduct on to the steering
> committee and the gcc community.
>
> > What could support any rational belief that having RMS one extra level
> > removed from our technical community would bring about anything
> > resembling a solution to the very undesirable and unjust gender
> > imbalance you've correctly identified?
>
> No but it will make it clear that toxic behaviour has no place in the
> gcc community.  That's step zero.  The FSF still hasn't got its act
> together in that regard unfortunately.
>
> > How about we set out to take individual and collective actions that
> > actually address the problem *in* our community?  We don't need anyone's
> > approval to call out sexist acts, nor to invite and train people with an
> > interest in compiler technology, nor to maintain a welcoming atmosphere.
>
> Sexist acts, discriminatory comments and inappropriate behaviour by RMS
> have been called out.  It is now the steering committee's responsibility
> to share their stand on it.
>
> On 3/27/21 9:15 PM, Alexandre Oliva via Gcc wrote:
>  > It looks like statements of any position whatsoever are invitations
>  > for pressure and trouble right now.
>
> On the flip side, not making a statement would be a statement in itself.
>   You know that though, which is why you advocate silence.
>
> Siddhesh
>

Re: Remove RMS from the GCC Steering Committee

[Alexandre Oliva]

Hello, Siddhesh,

Thanks for clarifying your understanding of Nathan's goal.

I may indeed have misread and mistaken Nathan's goal and means.

I thought the goal was to improve the GCC community by addressing the
gender imbalance, and that the means (misguided, IMHO) was to distance
ourselves from RMS.

Your assertiveness came across to me as a correction of my mistake, but
I didn't see any reason to prefer your understanding over mine, until
Nathan posted today's followup.

Now it looks like you were right, but I still find that a little hard to
believe.  Are you really sure about your understanding?

Do you know for a fact that Nathan agrees with your understanding?

Do you know with certainty of anyone else who shares that understanding
with you and him?

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: Remove RMS from the GCC Steering Committee

[Alexandre Oliva]

On Mar 28, 2021, Alexandre Oliva <oliva@gnu.org> wrote:

> Nathan posted today's followup.

Erhm...  Nathan, please accept my apologies.

I misread someone else's message under the false impression
it had come from you.

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: Remove RMS from the GCC Steering Committee

[Siddhesh Poyarekar]

On 3/28/21 8:20 PM, Alexandre Oliva wrote:
> Thanks for clarifying your understanding of Nathan's goal.
> 
> I may indeed have misread and mistaken Nathan's goal and means.
> 
> I thought the goal was to improve the GCC community by addressing the
> gender imbalance, and that the means (misguided, IMHO) was to distance
> ourselves from RMS.

There's only one point of departure; you chose to interpret RMS' removal 
from the steering committee to be the solution while I (and others) have 
pointed out that it is a notable step in that direction.

> Your assertiveness came across to me as a correction of my mistake, but
> I didn't see any reason to prefer your understanding over mine, until
> Nathan posted today's followup.

My reading of every gcc contributor that has participated in this 
discussion seems to reinforce my understanding over yours.  Not one of 
them has conveyed IMO that RMS' removal from the board will magically 
solve gender or diversity issues with the community.

> Now it looks like you were right, but I still find that a little hard to
> believe.  Are you really sure about your understanding?
> 
> Do you know for a fact that Nathan agrees with your understanding?
> 
> Do you know with certainty of anyone else who shares that understanding
> with you and him?

In my opinion there is nothing to indicate from any of the contributors' 
statements that they see RMS' removal from the steering committee as a 
final solution to D&I issues in the GNU community.  I'm happy to be 
corrected by others if they think I've misinterpreted their comments and 
if they indeed think that RMS' removal from the steering committee will 
solve all diversity issues.

Siddhesh

Re: Remove RMS from the GCC Steering Committee

[Óscar Fuentes]

We on the West are on the brink of entering into a new cycle of social
madness, fueled by Postmodern nonsense.

Thank you for being brave enough to confront the self-righteous mob, and
thank you for doing it with such equanimity and eloquence.

Alexandre Oliva via Gcc <gcc@gcc.gnu.org> writes:

> Nathan,
>
> I think you identify an important problem of gender imbalance in our
> community.  It is quite likely that finding ways to make our community
> more welcoming to demographic groups that are currently less present
> than in the distribution in the global population could reduce this
> imbalance.
>
> However, your diagnosis as to the supposed cause of the problem makes no
> sense to me.  You said yourself that Stallman has not participated in
> our community for decades.  Much as I know, his very hands-off influence
> in the SC has been mostly limited to licensing and strategic issues,
> e.g. the GPLv3 and Runtime Exception relicensing, to ensure copyleft
> defenses were in place to avoid abuse of such features as plugins.
>
>
> It may be very convenient to paint a boogey-man and expel it because
> that became fashionable.  But sacrificing a goat or a lamb does not
> expiate our own sins, and expelling someone who hasn't even been present
> in the community can't be expected to make any real difference to that
> matter; it would rather make us seem *less* welcoming and more
> intolerant, and suggest other motivations for the move.
>
>
> Let's be real and honest, when was the last time anyone in the GCC
> community was called out for sexist behavior?  When was there even
> conversation about it, and about how sexist behavior is not acceptable
> and not to be accepted among participants in the GCC community?  What
> was our latest collective action to promote e.g. gender equity within
> the community?
>
> If we were to shift our collective blame over this very real and
> undesirable problem to someone who has any direct authority over the
> project, why not suggesting expelling e.g. the entire Steering Committee
> for its evident failure to address the problem?  (I don't think it's a
> good idea, but that would be the first thing to try if we were to blame
> "management"/"leadership" rather than ourselves for it)
>
> What could support any rational belief that having RMS one extra level
> removed from our technical community would bring about anything
> resembling a solution to the very undesirable and unjust gender
> imbalance you've correctly identified?
>
>
> The action you propose, besides the absence of effect in making our
> community actually more welcoming, because he's already absent, would
> send the opposite of a welcoming signal to people with controversial or
> impopular opinions, to people at a certain spot in the neurodiversity
> spectrum, and to many others who oppose this sort of mob rule.
>
>
> How about we set out to take individual and collective actions that
> actually address the problem *in* our community?  We don't need anyone's
> approval to call out sexist acts, nor to invite and train people with an
> interest in compiler technology, nor to maintain a welcoming atmosphere.
>
> A regime of terror to maintain a false appearance of a welcoming
> atmosphere won't get us there.
>
> If we undertake such actions, individually or collecetively, you might
> be surprised (but I won't be) that he, even absent from the community,
> would support these actions, which is the very opposite of the picture
> you paint.
>
> Our taking effective action on our own would help show what the real
> issues and intents are, and it would tell apart those who are really
> interested in solving the gender imbalance and the social injustices
> causing it, like you and me, from those who are abusing that flag as a
> trojan horse to serve nefarious purposes, as suggested and illustrated
> in https://ultralux97.medium.com/stallman-must-be-removed-a3061b09fb22

Re: Remove RMS from the GCC Steering Committee

[Óscar Fuentes]

This was meant to be sent by private e-mail. I'm sorry it was sent to
the list by mistake, it was not my intention to stir this debate.

I invite everyone to keep discussing this topic in a cold-headed way.
Specially, I'll like to see the base problem (lack of diversity)
addresed, instead of its hypothetical cause (and even more hypothetical
solution.) Let's see if, for once, instead of grand symbolic gestures
that solve nothing the problem is attacked with effective and sustained
measures.

Sorry again for my intrusion on the list.

Óscar Fuentes <ofv@wanadoo.es> writes:

> We on the West are on the brink of entering into a new cycle of social
> madness, fueled by Postmodern nonsense.
>
> Thank you for being brave enough to confront the self-righteous mob, and
> thank you for doing it with such equanimity and eloquence.
>
> Alexandre Oliva via Gcc <gcc@gcc.gnu.org> writes:
>
>> Nathan,
>>
>> I think you identify an important problem of gender imbalance in our
>> community.  It is quite likely that finding ways to make our community
>> more welcoming to demographic groups that are currently less present
>> than in the distribution in the global population could reduce this
>> imbalance.
>>
>> However, your diagnosis as to the supposed cause of the problem makes no
>> sense to me.  You said yourself that Stallman has not participated in
>> our community for decades.  Much as I know, his very hands-off influence
>> in the SC has been mostly limited to licensing and strategic issues,
>> e.g. the GPLv3 and Runtime Exception relicensing, to ensure copyleft
>> defenses were in place to avoid abuse of such features as plugins.
>>
>>
>> It may be very convenient to paint a boogey-man and expel it because
>> that became fashionable.  But sacrificing a goat or a lamb does not
>> expiate our own sins, and expelling someone who hasn't even been present
>> in the community can't be expected to make any real difference to that
>> matter; it would rather make us seem *less* welcoming and more
>> intolerant, and suggest other motivations for the move.
>>
>>
>> Let's be real and honest, when was the last time anyone in the GCC
>> community was called out for sexist behavior?  When was there even
>> conversation about it, and about how sexist behavior is not acceptable
>> and not to be accepted among participants in the GCC community?  What
>> was our latest collective action to promote e.g. gender equity within
>> the community?
>>
>> If we were to shift our collective blame over this very real and
>> undesirable problem to someone who has any direct authority over the
>> project, why not suggesting expelling e.g. the entire Steering Committee
>> for its evident failure to address the problem?  (I don't think it's a
>> good idea, but that would be the first thing to try if we were to blame
>> "management"/"leadership" rather than ourselves for it)
>>
>> What could support any rational belief that having RMS one extra level
>> removed from our technical community would bring about anything
>> resembling a solution to the very undesirable and unjust gender
>> imbalance you've correctly identified?
>>
>>
>> The action you propose, besides the absence of effect in making our
>> community actually more welcoming, because he's already absent, would
>> send the opposite of a welcoming signal to people with controversial or
>> impopular opinions, to people at a certain spot in the neurodiversity
>> spectrum, and to many others who oppose this sort of mob rule.
>>
>>
>> How about we set out to take individual and collective actions that
>> actually address the problem *in* our community?  We don't need anyone's
>> approval to call out sexist acts, nor to invite and train people with an
>> interest in compiler technology, nor to maintain a welcoming atmosphere.
>>
>> A regime of terror to maintain a false appearance of a welcoming
>> atmosphere won't get us there.
>>
>> If we undertake such actions, individually or collecetively, you might
>> be surprised (but I won't be) that he, even absent from the community,
>> would support these actions, which is the very opposite of the picture
>> you paint.
>>
>> Our taking effective action on our own would help show what the real
>> issues and intents are, and it would tell apart those who are really
>> interested in solving the gender imbalance and the social injustices
>> causing it, like you and me, from those who are abusing that flag as a
>> trojan horse to serve nefarious purposes, as suggested and illustrated
>> in https://ultralux97.medium.com/stallman-must-be-removed-a3061b09fb22

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

The socialist collective angry bullshit will go on rising from the dead.
Richard Stallman executed a truly extraordinary feat that has never been
accomplished by anyone before.

---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Sunday, March 28, 2021 at 2:27 PM
> From: "Óscar Fuentes" <ofv@wanadoo.es>
> To: gcc@gcc.gnu.org
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> This was meant to be sent by private e-mail. I'm sorry it was sent to
> the list by mistake, it was not my intention to stir this debate.
> 
> I invite everyone to keep discussing this topic in a cold-headed way.
> Specially, I'll like to see the base problem (lack of diversity)
> addresed, instead of its hypothetical cause (and even more hypothetical
> solution.) Let's see if, for once, instead of grand symbolic gestures
> that solve nothing the problem is attacked with effective and sustained
> measures.
> 
> Sorry again for my intrusion on the list.
> 
> Óscar Fuentes <ofv@wanadoo.es> writes:
> 
> > We on the West are on the brink of entering into a new cycle of social
> > madness, fueled by Postmodern nonsense.
> >
> > Thank you for being brave enough to confront the self-righteous mob, and
> > thank you for doing it with such equanimity and eloquence.
> >
> > Alexandre Oliva via Gcc <gcc@gcc.gnu.org> writes:
> >
> >> Nathan,
> >>
> >> I think you identify an important problem of gender imbalance in our
> >> community.  It is quite likely that finding ways to make our community
> >> more welcoming to demographic groups that are currently less present
> >> than in the distribution in the global population could reduce this
> >> imbalance.
> >>
> >> However, your diagnosis as to the supposed cause of the problem makes no
> >> sense to me.  You said yourself that Stallman has not participated in
> >> our community for decades.  Much as I know, his very hands-off influence
> >> in the SC has been mostly limited to licensing and strategic issues,
> >> e.g. the GPLv3 and Runtime Exception relicensing, to ensure copyleft
> >> defenses were in place to avoid abuse of such features as plugins.
> >>
> >>
> >> It may be very convenient to paint a boogey-man and expel it because
> >> that became fashionable.  But sacrificing a goat or a lamb does not
> >> expiate our own sins, and expelling someone who hasn't even been present
> >> in the community can't be expected to make any real difference to that
> >> matter; it would rather make us seem *less* welcoming and more
> >> intolerant, and suggest other motivations for the move.
> >>
> >>
> >> Let's be real and honest, when was the last time anyone in the GCC
> >> community was called out for sexist behavior?  When was there even
> >> conversation about it, and about how sexist behavior is not acceptable
> >> and not to be accepted among participants in the GCC community?  What
> >> was our latest collective action to promote e.g. gender equity within
> >> the community?
> >>
> >> If we were to shift our collective blame over this very real and
> >> undesirable problem to someone who has any direct authority over the
> >> project, why not suggesting expelling e.g. the entire Steering Committee
> >> for its evident failure to address the problem?  (I don't think it's a
> >> good idea, but that would be the first thing to try if we were to blame
> >> "management"/"leadership" rather than ourselves for it)
> >>
> >> What could support any rational belief that having RMS one extra level
> >> removed from our technical community would bring about anything
> >> resembling a solution to the very undesirable and unjust gender
> >> imbalance you've correctly identified?
> >>
> >>
> >> The action you propose, besides the absence of effect in making our
> >> community actually more welcoming, because he's already absent, would
> >> send the opposite of a welcoming signal to people with controversial or
> >> impopular opinions, to people at a certain spot in the neurodiversity
> >> spectrum, and to many others who oppose this sort of mob rule.
> >>
> >>
> >> How about we set out to take individual and collective actions that
> >> actually address the problem *in* our community?  We don't need anyone's
> >> approval to call out sexist acts, nor to invite and train people with an
> >> interest in compiler technology, nor to maintain a welcoming atmosphere.
> >>
> >> A regime of terror to maintain a false appearance of a welcoming
> >> atmosphere won't get us there.
> >>
> >> If we undertake such actions, individually or collecetively, you might
> >> be surprised (but I won't be) that he, even absent from the community,
> >> would support these actions, which is the very opposite of the picture
> >> you paint.
> >>
> >> Our taking effective action on our own would help show what the real
> >> issues and intents are, and it would tell apart those who are really
> >> interested in solving the gender imbalance and the social injustices
> >> causing it, like you and me, from those who are abusing that flag as a
> >> trojan horse to serve nefarious purposes, as suggested and illustrated
> >> in https://ultralux97.medium.com/stallman-must-be-removed-a3061b09fb22
> 
>

Re: Remove RMS from the GCC Steering Committee

[Mark Wielaard]

Alexandre,

Making our community more welcoming is indeed a process. And some
steps will just be symbolic. But I don't believe removing RMS from
(perceived) leadership positions in the GNU project and from the FSF
is just symbolic. And even for a symbolic step it is a powerful
one. It shows we don't tolerate harassment in our project. And I do
hope it doesn't end with that step. We also have to decide whether we
still want to be associated with the FSF. Hopefully the FSF takes
their responsibility and replaces the whole board to show we can start
with a clean slate.

One issue is that as long as GCC is associated with RMS and the FSF
others who could help us won't because the FSF is that toxic now:
https://www.outreachy.org/blog/2021-03-23/fsf-participation-barred/
And they are far from the only Free Software project who has said
something similar.

We are not talking about some single recent incident, but about
decades of problematic behavior. At the last face-to-face GNU Tools
Cauldron, everybody I talked to about it had some story about being
harassed by RMS, had witnessed such harassment or heard from or knew
someone who had been.

For years people have tried to help him see how his actions and words
might hurt others, even if they are completely logically correct to
himself. And obviously that is sometimes hard, nobody is perfect, but
hopefully we get a little better every time. But this never happened.
And it really needs to stop.

RMS actively undermines those who try to make our community a little
bit more welcoming. Violating anti-harassment policies of
conferences. Even those from the FSF by claiming to be above those
policies because of his leadership position or using his position to
tell staff they cannot enforce such policies against others. Because
he is against enforcing any anti-harassment policy some GNU
mailinglist is currently being used to organize a doxing campaign
(publishing photos, address and calls to report to the local police
station to get her house raided and arrested) for simply saying the
same things we are discussing here now.

I witnessed something similar recently when we had setup the
mailinglist to discuss improving governance of the GNU project. When a
female GNU (GCC) volunteer spoke up she got attacked and harassed. We
told the harassers that was totally unacceptable and blocked them from
sending more emails to the list. RMS arranged for those people to get
unblocked to continue their hate campaign on the public GNU list so
they could "defend him and the GNU project". That was followed by a
torrent of hate to the list making any discussion impossible and
making women feel like they were specifically targeted. He still
hasn't learned that his words and actions are dog whistles for
misogynists, transphobics and racists. This really has to stop.

You link to a parody of a request of tens of Free Software foundation
projects and thousands of Free Software hackers who are calling for
the removal of the entire Board of the Free Software Foundation and
for Richard M. Stallman to be removed from all leadership positions,
including the GNU Project. For similar reasons that people here are
now calling for RMS to be removed from the GCC steering committee.

The real letter is here: https://rms-open-letter.github.io/

Sometimes satire is a way to deal with difficult problems, but I don't
think that is appropriate here and I hope people take these issues
seriously, because I think they are.

Mark

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Sun, 28 Mar 2021, 13:50 Mark Wielaard, <mark@klomp.org> wrote:

> RMS actively undermines those who try to make our community a little
> bit more welcoming. Violating anti-harassment policies of
> conferences. Even those from the FSF by claiming to be above those
> policies because of his leadership position or using his position to
> tell staff they cannot enforce such policies against others. Because
> he is against enforcing any anti-harassment policy some GNU
> mailinglist is currently being used to organize a doxing campaign
> (publishing photos, address and calls to report to the local police
> station to get her house raided and arrested) for simply saying the
> same things we are discussing here now.
>
> I witnessed something similar recently when we had setup the
> mailinglist to discuss improving governance of the GNU project. When a
> female GNU (GCC) volunteer spoke up she got attacked and harassed. We
> told the harassers that was totally unacceptable and blocked them from
> sending more emails to the list. RMS arranged for those people to get
> unblocked to continue their hate campaign on the public GNU list so
> they could "defend him and the GNU project". That was followed by a
> torrent of hate to the list making any discussion impossible and
> making women feel like they were specifically targeted. He still
> hasn't learned that his words and actions are dog whistles for
> misogynists, transphobics and racists. This really has to stop.
>

We even have a GNU maintainer* with no link to GCC sending abusive emails
in this thread, because he feels such harassment is acceptable.

* He is listed as maintainer on gnu.org despite the project having no
public release and an empty repo. It looks like vapourware that only exists
in his head, but he's still a proud "GNU maintainer". If that's who GNU
welcomes, count me out.

Re: Remove RMS from the GCC Steering Committee

[JeanHeyd Meneide]

Dear GCC Community,

    Hi. My name is JeanHeyd Meneide, my online moniker is "ThePhD"
(not an actual Doctor. Yet!). I spend a lot of my time hacking on C
and C++. Some of the things I've done include:

- Contributing (mostly) a <span> Implementation [1]
- Doing a GSoC for GCC and writing up about fixes for vector<bool> and
other data structures that can be helpful [2] (a lot of these
optimizations were rolled into libstdc++'s normal vector<bool> by
François Dumont, thank you!!)
- Implementing part of my own proposal's [[nodiscard("should have a
reason")]] [3]
- Macros for identifying literal and wide literal encoding, to aid in
code portability and pre-emptively solving a user concern while
preparing for a new C++ proposal that allows identifying the execution
and wide execution character sets deployed by the compiler [4]

     I'm also helping to solve the intmax_t problems in C and C++ so
we can have wider integer types beyond "long long" blessed by
numeric_limits.[5]

     I am also, recently, the ISO/IEC JTC1 SC22 WG14 - Programming
Languages, C: Project Editor. I do not speak for ISO/IEC, the C
Committee, or my National Body here; this e-mail is sent in a person
capacity, but my affiliations should be known (not that they are
hidden with a cursory search, either).

    Asides from many other things, last and most importantly I am a
GCC advocate, a libstdc++ contributor, and an individual who spent an
exorbitant and extraordinary amount of my free time contributing to
these projects and the wider ecosystems in the hope that C, C++, Rust,
and related Systems Programming languages would continue to flourish
under the leadership done by the people here. By the time I was going
to finish my education, the goal was to ramp up these contributions
10-fold. There is much room for improvements in fundamental C and C++
architecture and library, leading me on a long, long journey, to where
I am today.

     I am exactly one of the "future contributors" referenced in the
e-mails by Wakely, Rodgers, Wielaard, Poyarekar, and others here, even
if they were not explicitly thinking of me. Or, I would be:

On Sun, Mar 28, 2021 Mark Wielaard <mark@klomp.org> wrote:
>
> ...
>
> I witnessed something similar recently when we had setup the
> mailinglist to discuss improving governance of the GNU project. When a
> female GNU (GCC) volunteer spoke up she got attacked and harassed. We
> told the harassers that was totally unacceptable and blocked them from
> sending more emails to the list. RMS arranged for those people to get
> unblocked to continue their hate campaign on the public GNU list so
> they could "defend him and the GNU project". That was followed by a
> torrent of hate to the list making any discussion impossible and
> making women feel like they were specifically targeted. He still
> hasn't learned that his words and actions are dog whistles for
> misogynists, transphobics and racists. This really has to stop.
>
> ...

     This is unacceptable. The only reason I was told - as early as
yesterday, by Free Software advocates, to my socially distanced face -
that Stallman was still here is because he was powerless and had no
effect on the project. That it was run by the caring,
community-oriented stewardship of the "real volunteers" doing the
"actual work".

     That is not what this e-mail reveals.

     Further digging into Stallman's own words and behavior also
reveals that he continues to flex this influence throughout the
project (and in other places), showing up (generally unsolicited) into
places to do this kind of gross and extreme harassment and engaging in
canceling our own hardworking contributors that actually write code
and do work. This is not a person who is just here for "historical
reasons" and who has "no power"; this is an active, perpetual threat
to hardworking and contributing members of the Free Software movement.

     I refuse to spend my free time supporting a single bigot and an
entire globe's worth of toxic enthusiasts who actively support his
behavior while letting people like him create horrible ecosystems for
other developers. At the start of this conversation, I was much like
Nathan; I wanted an explanation. Having reviewed the facts of the
situation, I can now unequivocally say that an explanation is not even
close to enough.

      I will never, ever contribute another line of code, another
proposal implementation[6], another optimization, or another
new/better library implementation to GCC and all of its affiliated
projects, including the compilers, glibc, libstdc++, the potential
upcoming Rust implementation, and more until this problem is not
"address", but *fixed*. If you never fix it, I will never return.

Wish you and your community all the best in sorting this out,
JeanHeyd Meneide

[#]: References -
https://gist.github.com/ThePhD/bcfad83f01e6a641c3fda5cfc013a72d

Re: Remove RMS from the GCC Steering Committee

[Mark Wielaard]

Hi,

On Sun, Mar 28, 2021 at 10:33:15AM -0400, JeanHeyd Meneide wrote:
>      This is unacceptable. The only reason I was told - as early as
> yesterday, by Free Software advocates, to my socially distanced face -
> that Stallman was still here is because he was powerless and had no
> effect on the project. That it was run by the caring,
> community-oriented stewardship of the "real volunteers" doing the
> "actual work".

I do not think those people were lying or trying to deceive you. This
is what we hope the actual situation is. But...

>      Further digging into Stallman's own words and behavior also
> reveals that he continues to flex this influence throughout the
> project (and in other places), showing up (generally unsolicited) into
> places to do this kind of gross and extreme harassment and engaging in
> canceling our own hardworking contributors that actually write code
> and do work. This is not a person who is just here for "historical
> reasons" and who has "no power"; this is an active, perpetual threat
> to hardworking and contributing members of the Free Software movement.

He does indeed show up randomly claiming authority even if the GNU
community has told him no. And it is important to say upfront he has
no authority and that his attempts to cancel the work of hardworking
GNU contributors is unwelcome. IMHO for the GCC community this means
to be explicit he doesn't have any authority and he shouldn't be on
the GCC steering committee.

>       I will never, ever contribute another line of code, another
> proposal implementation[6], another optimization, or another
> new/better library implementation to GCC and all of its affiliated
> projects, including the compilers, glibc, libstdc++, the potential
> upcoming Rust implementation, and more until this problem is not
> "address", but *fixed*. If you never fix it, I will never return.
> 
> Wish you and your community all the best in sorting this out,

Thanks. I do hope we can finally fix this and welcome you back.

Cheers,

Mark

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Monday, March 29, 2021 at 6:13 AM
> From: "Mark Wielaard" <mark@klomp.org>
> To: "JeanHeyd Meneide" <phdofthehouse@gmail.com>
> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> Hi,
> 
> On Sun, Mar 28, 2021 at 10:33:15AM -0400, JeanHeyd Meneide wrote:
> >      This is unacceptable. The only reason I was told - as early as
> > yesterday, by Free Software advocates, to my socially distanced face -
> > that Stallman was still here is because he was powerless and had no
> > effect on the project. That it was run by the caring,
> > community-oriented stewardship of the "real volunteers" doing the
> > "actual work".
> 
> I do not think those people were lying or trying to deceive you. This
> is what we hope the actual situation is. But...
> 
> >      Further digging into Stallman's own words and behavior also
> > reveals that he continues to flex this influence throughout the
> > project (and in other places), showing up (generally unsolicited) into
> > places to do this kind of gross and extreme harassment and engaging in
> > canceling our own hardworking contributors that actually write code
> > and do work. This is not a person who is just here for "historical
> > reasons" and who has "no power"; this is an active, perpetual threat
> > to hardworking and contributing members of the Free Software movement.
> 
> He does indeed show up randomly claiming authority even if the GNU
> community has told him no. And it is important to say upfront he has
> no authority and that his attempts to cancel the work of hardworking
> GNU contributors is unwelcome. IMHO for the GCC community this means
> to be explicit he doesn't have any authority and he shouldn't be on
> the GCC steering committee.
> 
> >       I will never, ever contribute another line of code, another
> > proposal implementation[6], another optimization, or another
> > new/better library implementation to GCC and all of its affiliated
> > projects, including the compilers, glibc, libstdc++, the potential
> > upcoming Rust implementation, and more until this problem is not
> > "address", but *fixed*. If you never fix it, I will never return.
> > 
> > Wish you and your community all the best in sorting this out,
> 
> Thanks. I do hope we can finally fix this and welcome you back.

The attacks against Richard Stallman do not stem from any of his actual
statements. Instead, his statements have been given a subversive context
that fits into your narrative that wishes to smear him, followed a demand
that your interpretation of his words be considered canon — even though
evidence to the contrary  summarily disproves your position.

Stallman’s work and advocacy speaks for itself; and this holds true for anyone
in the field of technology, where a person’s work is judged by a system of 
meritocracy. 

Linus Torvalds was also famously criticized by those who took offense to his
no-nonsense attitude and firm speech. Did the quality of the Linux kernel 
suffer? Was being unoffensive a requirement as maintainer? The answer is
NO.

Stallman has never been accused of doing physical harm to anyone, and therefore
any assumptions about the harmful nature or context of his words should not be
conflated with his professional capacity to hold a leadership role within the FSF,
the very organization that he founded.



> Cheers,
> 
> Mark
>

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

You showed your colours with your first few posts, don't try to pretend you
are anything but a zealot and a nasty troll.

Come back when you've contributed more to the GNU project than attacking
those you see as its enemies. The people you are attacking have done more
for Free Software than you ever will.



On Sun, 28 Mar 2021, 19:43 Christopher Dimech via Gcc, <gcc@gcc.gnu.org>
wrote:

>
>
> ---------------------
> Christopher Dimech
> General Administrator - Naiad Informatics - GNU Project (Geocomputation)
> - Geophysical Simulation
> - Geological Subsurface Mapping
> - Disaster Preparedness and Mitigation
> - Natural Resource Exploration and Production
> - Free Software Advocacy
>
>
> > Sent: Monday, March 29, 2021 at 6:13 AM
> > From: "Mark Wielaard" <mark@klomp.org>
> > To: "JeanHeyd Meneide" <phdofthehouse@gmail.com>
> > Cc: "GCC Development" <gcc@gcc.gnu.org>, "Nathan Sidwell" <
> nathan@acm.org>
> > Subject: Re: Remove RMS from the GCC Steering Committee
> >
> > Hi,
> >
> > On Sun, Mar 28, 2021 at 10:33:15AM -0400, JeanHeyd Meneide wrote:
> > >      This is unacceptable. The only reason I was told - as early as
> > > yesterday, by Free Software advocates, to my socially distanced face -
> > > that Stallman was still here is because he was powerless and had no
> > > effect on the project. That it was run by the caring,
> > > community-oriented stewardship of the "real volunteers" doing the
> > > "actual work".
> >
> > I do not think those people were lying or trying to deceive you. This
> > is what we hope the actual situation is. But...
> >
> > >      Further digging into Stallman's own words and behavior also
> > > reveals that he continues to flex this influence throughout the
> > > project (and in other places), showing up (generally unsolicited) into
> > > places to do this kind of gross and extreme harassment and engaging in
> > > canceling our own hardworking contributors that actually write code
> > > and do work. This is not a person who is just here for "historical
> > > reasons" and who has "no power"; this is an active, perpetual threat
> > > to hardworking and contributing members of the Free Software movement.
> >
> > He does indeed show up randomly claiming authority even if the GNU
> > community has told him no. And it is important to say upfront he has
> > no authority and that his attempts to cancel the work of hardworking
> > GNU contributors is unwelcome. IMHO for the GCC community this means
> > to be explicit he doesn't have any authority and he shouldn't be on
> > the GCC steering committee.
> >
> > >       I will never, ever contribute another line of code, another
> > > proposal implementation[6], another optimization, or another
> > > new/better library implementation to GCC and all of its affiliated
> > > projects, including the compilers, glibc, libstdc++, the potential
> > > upcoming Rust implementation, and more until this problem is not
> > > "address", but *fixed*. If you never fix it, I will never return.
> > >
> > > Wish you and your community all the best in sorting this out,
> >
> > Thanks. I do hope we can finally fix this and welcome you back.
>
> The attacks against Richard Stallman do not stem from any of his actual
> statements. Instead, his statements have been given a subversive context
> that fits into your narrative that wishes to smear him, followed a demand
> that your interpretation of his words be considered canon — even though
> evidence to the contrary  summarily disproves your position.
>
> Stallman’s work and advocacy speaks for itself; and this holds true for
> anyone
> in the field of technology, where a person’s work is judged by a system of
> meritocracy.
>
> Linus Torvalds was also famously criticized by those who took offense to
> his
> no-nonsense attitude and firm speech. Did the quality of the Linux kernel
> suffer? Was being unoffensive a requirement as maintainer? The answer is
> NO.
>
> Stallman has never been accused of doing physical harm to anyone, and
> therefore
> any assumptions about the harmful nature or context of his words should
> not be
> conflated with his professional capacity to hold a leadership role within
> the FSF,
> the very organization that he founded.
>
>
>
> > Cheers,
> >
> > Mark
> >
>

Re: Remove RMS from the GCC Steering Committee

[Joseph Myers]

On Sun, 28 Mar 2021, Mark Wielaard wrote:

> He does indeed show up randomly claiming authority even if the GNU
> community has told him no. And it is important to say upfront he has
> no authority and that his attempts to cancel the work of hardworking
> GNU contributors is unwelcome. IMHO for the GCC community this means
> to be explicit he doesn't have any authority and he shouldn't be on
> the GCC steering committee.

For example, consider the October 2019 discussion on libc-alpha of 
removing the abort "joke" from the glibc manual.  We rejected RMS's claims 
of authority to say that the joke should be kept, or kept indefinitely 
until various general points could be decided, and removed it from the 
manual anyway without waiting for conclusions on all those general points.

RMS only has authority over decisions taken about individual GNU packages 
where the people developing those packages let him have that authority and 
make or refrain from making changes based on what he says.  We should not 
give him such authority by treating his views as having some significance 
not given to such views expressed by other people; changes he suggests can 
be considered, and accepted or rejected, on their merits.  And the abort 
joke case illustrates that in fact he is not given such authority, when 
package developers are confident to stand up to claims he makes of 
authority, and provides an example that can speed up the rejection of any 
such assertion of authority to micromanage things that might be made in 
future.

I agree with the conclusion of Nathan's original message, that RMS behaves 
in a toxic way, it is harmful to have him listed as being in a leadership 
role that might suggest what he does is acceptable within the project, and 
he should not be on the SC.  This is based on the longstanding, 
well-documented patterns of how he has misbehaved towards women, *not* on 
the opinions he has expressed on other subjects, *not* on his choices 
regarding the use of language, *not* on his attempts to insist on language 
being used in particular ways, and *not* on where or when he has chosen to 
express such views.

For the same reasons, I think it is harmful for him to be Chief GNUisance 
(but as above, I think GNU packages should not give a Chief GNUisance 
authority to micromanage decisions, beyond ensuring GNU packages follow 
basic GNU free software principles and cooperate with each other and with 
their development communities), harmful for him to be on the FSF board, 
and harmful for him to be seen as leader of the free software movement.  
(For the last point, I don't think the free software movement needs a 
single leader; it needs many people advocating free software, and 
discussing issues related to free software, from diverse perspectives.  
RMS's ideas that form the foundation of the free software movement are 
still of fundamental importance today.  But other people can now build 
better on those ideas in today's context.)

RMS does not, in fact, contribute usefully to the SC.  Any time he 
suggests some feature for GCC, whether a good or a bad idea, that could be 
done just as well on the public mailing list (which would be a better 
place to find someone possibly interested in implementing a feature, and 
to discuss a feature's merits, in any case) without being an SC member.  
He's sufficiently far removed from toolchain development that he's not 
good at making reasonable suggestions for toolchain changes in any case.

We can consider individual proposals or patches from anyone on their 
merits.  We can have leaders who are accepted as leaders because 
contributors can see their relevant expertise that gives them legitimacy 
as leaders, and can see a good basis for decisions they make as leaders.  
But longstanding patterns of bad conduct by a leader, even when formally 
unrelated to the project, can reach the point where considering that 
person a leader is harmful to the project.  I think the ways RMS has 
behaved have long since reached the point where it is harmful for him to 
be considered a leader for GCC or GNU, and that's sufficient to stop 
considering him a leader (even if he were sufficiently involved to be able 
to contribute much more usefully on a technical level).

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Tuesday, March 30, 2021 at 12:20 PM
> From: "Joseph Myers" <joseph@codesourcery.com>
> To: "Mark Wielaard" <mark@klomp.org>
> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> On Sun, 28 Mar 2021, Mark Wielaard wrote:
>
> > He does indeed show up randomly claiming authority even if the GNU
> > community has told him no. And it is important to say upfront he has
> > no authority and that his attempts to cancel the work of hardworking
> > GNU contributors is unwelcome. IMHO for the GCC community this means
> > to be explicit he doesn't have any authority and he shouldn't be on
> > the GCC steering committee.
>
> For example, consider the October 2019 discussion on libc-alpha of
> removing the abort "joke" from the glibc manual.  We rejected RMS's claims
> of authority to say that the joke should be kept, or kept indefinitely
> until various general points could be decided, and removed it from the
> manual anyway without waiting for conclusions on all those general points.
>
> RMS only has authority over decisions taken about individual GNU packages
> where the people developing those packages let him have that authority and
> make or refrain from making changes based on what he says.  We should not
> give him such authority by treating his views as having some significance
> not given to such views expressed by other people; changes he suggests can
> be considered, and accepted or rejected, on their merits.  And the abort
> joke case illustrates that in fact he is not given such authority, when
> package developers are confident to stand up to claims he makes of
> authority, and provides an example that can speed up the rejection of any
> such assertion of authority to micromanage things that might be made in
> future.
>
> I agree with the conclusion of Nathan's original message, that RMS behaves
> in a toxic way, it is harmful to have him listed as being in a leadership
> role that might suggest what he does is acceptable within the project, and
> he should not be on the SC.

Insofar as Stallman is the foundation of all authority, He exercises that foundation because He is the founder of His own work.  He is the foundation upon which all other authority stands or falls. We use the term foundation with respect to the imagery of a building - houses and commercial buildings are erected upon a foundation.

To say that Stallman defended Epstein for comments he made about his former
teacher are from an oceanic distance.  The person who really had ties with
Epstein was Bill Gates, who, instructed Bill Gates to donate $2 million to
MIT.

Stallman simply did not take into account the era of diminishing freedom
(not only in the digital world). Nowadays, with the left (communist) thought
police, who are always on the lookout for any subject to fire their cannons
on, free speech could be gone. If an opinion expressed goes against the prevailing inquisition of the time, the subject and the person is in hot waters.

Well, screw the inquisition.   Seems like World War I has just begun and martial
law has been declared, and this is reason enough, it seems, to expel the firebrand
without much ado, so he can eventually end up in concentration camps in Egypt.

> This is based on the longstanding,
> well-documented patterns of how he has misbehaved towards women, *not* on
> the opinions he has expressed on other subjects, *not* on his choices
> regarding the use of language, *not* on his attempts to insist on language
> being used in particular ways, and *not* on where or when he has chosen to
> express such views.
>
> For the same reasons, I think it is harmful for him to be Chief GNUisance
> (but as above, I think GNU packages should not give a Chief GNUisance
> authority to micromanage decisions, beyond ensuring GNU packages follow
> basic GNU free software principles and cooperate with each other and with
> their development communities), harmful for him to be on the FSF board,
> and harmful for him to be seen as leader of the free software movement.
> (For the last point, I don't think the free software movement needs a
> single leader; it needs many people advocating free software, and
> discussing issues related to free software, from diverse perspectives.
> RMS's ideas that form the foundation of the free software movement are
> still of fundamental importance today.  But other people can now build
> better on those ideas in today's context.)
>
> RMS does not, in fact, contribute usefully to the SC.  Any time he
> suggests some feature for GCC, whether a good or a bad idea, that could be
> done just as well on the public mailing list (which would be a better
> place to find someone possibly interested in implementing a feature, and
> to discuss a feature's merits, in any case) without being an SC member.
> He's sufficiently far removed from toolchain development that he's not
> good at making reasonable suggestions for toolchain changes in any case.
>
> We can consider individual proposals or patches from anyone on their
> merits.  We can have leaders who are accepted as leaders because
> contributors can see their relevant expertise that gives them legitimacy
> as leaders, and can see a good basis for decisions they make as leaders.
> But longstanding patterns of bad conduct by a leader, even when formally
> unrelated to the project, can reach the point where considering that
> person a leader is harmful to the project.  I think the ways RMS has
> behaved have long since reached the point where it is harmful for him to
> be considered a leader for GCC or GNU, and that's sufficient to stop
> considering him a leader (even if he were sufficiently involved to be able
> to contribute much more usefully on a technical level).
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
>

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Tue, 30 Mar 2021, 02:34 Christopher Dimech via Gcc, <gcc@gcc.gnu.org>
wrote:

>
>
>
>
> Insofar as Stallman is the foundation of all authority, He exercises that
> foundation because He is the founder of His own work.  He is the foundation
> upon which all other authority stands or falls. We use the term foundation
> with respect to the imagery of a building - houses and commercial buildings
> are erected upon a foundation.
>


Read the Four Freedoms at gnu.org. Nothing in the definitions of free
software requires us to obey the founder. You are a cultist who understands
nothing about free software and contributes nothing to it either.

Re: Remove RMS from the GCC Steering Committee

[Alexandre Oliva]

Joseph,

On Mar 29, 2021, Joseph Myers <joseph@codesourcery.com> wrote:

> This is based on the longstanding, 
> well-documented patterns of how he has misbehaved towards women,

I have a great deal of respect for your attention to detail.

I can hardly believe you would make such a claim without having actually
looked into available evidence and cross-checked it.

Yet your claim is either (a) misleading or (b) conflicting with findings
by others who did so.

(a) is a distinct possibility, since many people may legitimately claim
RMS has been rude or harsh towards themselves, regardless of gender, and
that can be exaggerated into misbehavior, and made misleading by
phrasing it as if it was directed to any specific demographics.

(b) would surprise me, given how extensively evidence has been looked
into by myself and others.  I request that, if you found anything that
holds up to your high standards of evidence-checking, you submit it to
the voting members of the FSF, so that we can look into it and take
appropriate action.

Thanks in advance,

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: Remove RMS from the GCC Steering Committee

[Mark Wielaard]

Hi Alexandre,

On Mon, 2021-03-29 at 23:08 -0300, Alexandre Oliva via Gcc wrote:
> I request that, if you found anything that holds up to your high
> standards of evidence-checking, you submit it to the voting members
> of the FSF, so that we can look into it and take appropriate action.

If you are still a (voting) board member of the FSF I request that you
and the rest of the remaining old (voting) board members resign. It is
not that you are a bad person. But it is time for a fresh start of the
FSF. The current board has ignored these issues for too long. And I
know you count RMS as your friend. That makes it naturally hard for you
to see the evidence presented unbiased. And that is not a character
flaw. We all want to stick with our friends, that is only natural. But
it might also mean that we just don't want to see, or explain away, bad
things people tell us what our friends do. In which case it is better
to simply step aside.

Various FSF board members already left, or promised to leave, to make
way for a new generation of leaders, please take inspiration from them,
they are also fiercely dedicated to Free Software and believe it is
time for a fresh start.

Thanks,

Mark

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

The methods used to put a leash on Torvalds and Assange and the methods used
to put one on Stallman are too similar to ignore.

It hasn’t stopped there either, it is now being wielded as a way to yoke all
developers of mainstream software (whether mainstream and non-free, or mainstream
and under a free license) into indentured servants of projects that have been
taken over by corporate donors who then force even original authors to do things
the way the monopoly wanted, or get out.


---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Monday, March 29, 2021 at 12:47 AM
> From: "Mark Wielaard" <mark@klomp.org>
> To: "GCC Development" <gcc@gcc.gnu.org>
> Cc: "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> Alexandre,
> 
> Making our community more welcoming is indeed a process. And some
> steps will just be symbolic. But I don't believe removing RMS from
> (perceived) leadership positions in the GNU project and from the FSF
> is just symbolic. And even for a symbolic step it is a powerful
> one. It shows we don't tolerate harassment in our project. And I do
> hope it doesn't end with that step. We also have to decide whether we
> still want to be associated with the FSF. Hopefully the FSF takes
> their responsibility and replaces the whole board to show we can start
> with a clean slate.
> 
> One issue is that as long as GCC is associated with RMS and the FSF
> others who could help us won't because the FSF is that toxic now:
> https://www.outreachy.org/blog/2021-03-23/fsf-participation-barred/
> And they are far from the only Free Software project who has said
> something similar.
> 
> We are not talking about some single recent incident, but about
> decades of problematic behavior. At the last face-to-face GNU Tools
> Cauldron, everybody I talked to about it had some story about being
> harassed by RMS, had witnessed such harassment or heard from or knew
> someone who had been.
> 
> For years people have tried to help him see how his actions and words
> might hurt others, even if they are completely logically correct to
> himself. And obviously that is sometimes hard, nobody is perfect, but
> hopefully we get a little better every time. But this never happened.
> And it really needs to stop.
> 
> RMS actively undermines those who try to make our community a little
> bit more welcoming. Violating anti-harassment policies of
> conferences. Even those from the FSF by claiming to be above those
> policies because of his leadership position or using his position to
> tell staff they cannot enforce such policies against others. Because
> he is against enforcing any anti-harassment policy some GNU
> mailinglist is currently being used to organize a doxing campaign
> (publishing photos, address and calls to report to the local police
> station to get her house raided and arrested) for simply saying the
> same things we are discussing here now.
> 
> I witnessed something similar recently when we had setup the
> mailinglist to discuss improving governance of the GNU project. When a
> female GNU (GCC) volunteer spoke up she got attacked and harassed. We
> told the harassers that was totally unacceptable and blocked them from
> sending more emails to the list. RMS arranged for those people to get
> unblocked to continue their hate campaign on the public GNU list so
> they could "defend him and the GNU project". That was followed by a
> torrent of hate to the list making any discussion impossible and
> making women feel like they were specifically targeted. He still
> hasn't learned that his words and actions are dog whistles for
> misogynists, transphobics and racists. This really has to stop.
> 
> You link to a parody of a request of tens of Free Software foundation
> projects and thousands of Free Software hackers who are calling for
> the removal of the entire Board of the Free Software Foundation and
> for Richard M. Stallman to be removed from all leadership positions,
> including the GNU Project. For similar reasons that people here are
> now calling for RMS to be removed from the GCC steering committee.
> 
> The real letter is here: https://rms-open-letter.github.io/
> 
> Sometimes satire is a way to deal with difficult problems, but I don't
> think that is appropriate here and I hope people take these issues
> seriously, because I think they are.
> 
> Mark
>

Re: Remove RMS from the GCC Steering Committee

[Alexandre Oliva]

On Mar 28, 2021, Mark Wielaard <mark@klomp.org> wrote:

> It shows we don't tolerate harassment in our project.

It shows we will favor and engage in harassment against a certain
demographic group, while pretending or believing it will somehow
make for a welcoming atmosphere.

> everybody I talked to about it had some story about being
> harassed by RMS, had witnessed such harassment or heard from or knew
> someone who had been.

... which, even if true, still requires quite a lot of twisting and
forcing and breaking to make it fit the sexism narrative presented as
the motivating factor.

And this is the problem with most of the witchhunting in place.  There
are plenty of allegations circulating all over the Internet, and most of
them fit either or both of two patterns: actual evidence twisted and
forced to fit a false narrative, or repeated hearsay, most likely
fabricated or exaggerated, without a traceable ultimate source.

Which is not to say that there aren't exceptions, the first-hand
narratives.  Those invariably fit in either of two patterns: they look
like smoking gun evidence of very wrongdoing, but they are disputed by
other who were just as much there and are just as trustworthy, or they
paint the known picture of person who has well-known flaws and is indeed
frequently difficult to deal with, but those facts don't help construct
the false boogeyman narrative.

Of course conclusions may be different once one starts picking evidence
that is favorable to make one's case, and disregarding that which
opposes evidence.  Most people would agree that this is not the way to
go to find truth, be it for science or for justice.

> he is against enforcing any anti-harassment policy some GNU
> mailinglist is currently being used to organize a doxing campaign

Doxing and harassment are not welcome, and that post has already been
solved, with his support and before you brought it up, FWIW.

Harassment has been tolerated before, which made this decision a little
more difficult, because the target of an earlier and ongoing harassment
campaign was someone in a position of power in the GNU project itself.
My understanding is that there was a decision to not silence that
discussion, although some moderators had engaged in suppression of
dissenting positions to the (still) ongoing harassment.  As anyone who
studied history can predict, authoritarian positions tend to suppress or
attempt to suppress dissent, while freedom-respecting ones endure it.

If that was a trial run of the sort of leadership that was trying to
replace Richard's, I'd much rather keep the devil we know.  That alleged
witch may have some warts indeed, but they're not quite as ugly as the
prosecutors/judges/executioners's.


> You link to a parody of a request of tens of Free Software foundation
> projects and thousands of Free Software hackers

If truth finding were a matter of headcount, we might still be forced to
believe we're on a flat planet orbited by a star.  But if we're to use
that measuring stick, petitions calling for the FSF to keep Richard at
the FSF board have been signed by more people, translated to more
languages, despite there being more of them, and hosted on platforms
that are less hostile to software freedom, and not being signed multiple
times by the same few people on behalf of multiple organizations.


> Sometimes satire is a way to deal with difficult problems, but I don't
> think that is appropriate here

How about this one instead?
https://avilarenata.medium.com/stallman-d824724b0083

  RMS’ principled stances cause an uncomfortable cognitive dissonance
  for them. They would rather kill a sacrificial Gnu than admit their
  own shortcomings. It is significant that the letter demanding his
  resignation must be signed using Microsoft’s Github platform, and that
  many organizations taking position are openly accepting money from
  Google and other predatory companies.


Or this one?
https://www.wetheweb.org/post/cancel-we-the-web

  The paradox of Stallman is that while his pointedness and stubbornness
  leads many to dismiss him as a jerk, his stubbornness and
  confrontations are actually rooted in his life-long obsession with
  morality. Though you may disagree, there is ample reason to believe he
  has come to hold his views from a concerted, rigorous, good-faith
  effort to be a voice for good in the world.

  “Stallman… is a hard man to like. He is driven, often impatient. His
  anger can flare at friend as easily as foe. He is uncompromising and
  persistent; patient in both.”
    Lawrence Lessig, Harvard Law Professor, democracy activist

  “Even if I strongly disagree with a position or an idea, an expression
  of an idea, advocacy of an idea, and even if the vast majority of the
  public disagrees with the idea and finds it offensive, that is not a
  justification for suppressing the idea. And it’s not a justification
  for taking away the equal rights of the person who espouses that idea
  including the right to continue holding a tenured position or other
  prominent position for which that person is qualified.”
    Nadine Strossen, Civil Rights Activist, first female President of the ACLU


Maybe this one?
https://medium.com/@whoisylvia/richard-stallman-has-been-vilified-by-those-who-dont-know-him-a3907b25b4c7

  As an active feminist and one who has witnessed much bad behavior
  among tech CEOs over the past 30 years, I think that accusing Richard
  Stallman of not supporting women, gays, or any other minority group is
  false

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: Remove RMS from the GCC Steering Committee

[Soul Studios]

> We are not talking about some single recent incident, but about
> decades of problematic behavior. At the last face-to-face GNU Tools
> Cauldron, everybody I talked to about it had some story about being
> harassed by RMS, had witnessed such harassment or heard from or knew
> someone who had been.

I think I will leave this discussion up to those who have more 
familiarity with the guy than I do. There's no doubt that some of the 
stuff Stallman has written creeps me the hell out, and I think it was 
more the tone of the OP I objected to.
Giving twitter as reference points doesn't really help matters, but it 
appears as though the problems are more offline than on.

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

This is quite similar to James Madison and John Jay, two of the founding
father of the United States Bill of Rights, which enshrined guarantees of
personal freedoms and rights within the American Constitution.

Many companies rely on their founder to be the chief salesperson.  This is
difficult as the company grows, but the founder is uniquely suited to convince
others about free software in this case.

Certainly not Nathan Sidwell, Deb Nicholson, or Neil McGovern.  Or the others.
If people think that the Jeffrey Epstein problems are going to be resolved by
going after Stallman, they are highly misguided.  Money and power often buy what
they shouldn't.

> Sent: Monday, March 29, 2021 at 11:21 AM
> From: "Soul Studios" <matt@soulstudios.co.nz>
> To: "Mark Wielaard" <mark@klomp.org>, "GCC Development" <gcc@gcc.gnu.org>
> Cc: "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> > We are not talking about some single recent incident, but about
> > decades of problematic behavior. At the last face-to-face GNU Tools
> > Cauldron, everybody I talked to about it had some story about being
> > harassed by RMS, had witnessed such harassment or heard from or knew
> > someone who had been.
>
> I think I will leave this discussion up to those who have more
> familiarity with the guy than I do.

Have worked with Stallman and never experienced any stories that
are being perpetuated in discussions.

> There's no doubt that some of the
> stuff Stallman has written creeps me the hell out, and I think it was
> more the tone of the OP I objected to.

Yes, there are things that people can disagree with him about personal views.
Which crimes has he committed exactly?  And under which jurisdiction?  I have
to work with a lot of people that I could not particularly like on a personal
level.  I cannot see how people expect that others stay out of politics because
they have some acrimony against them!

> Giving twitter as reference points doesn't really help matters, but it
> appears as though the problems are more offline than on.
>

Re: Remove RMS from the GCC Steering Committee

[Richard Kenner]

> I think I will leave this discussion up to those who have more 
> familiarity with the guy than I do. There's no doubt that some of the 
> stuff Stallman has written creeps me the hell out, and I think it was 
> more the tone of the OP I objected to.

I mostly want to stay out of this and will leave much of this discussion to
others (though I have met RMS personally on a number of occaisions), but I
want to mostly say that I agree with Jeff that it's important that this
discussion stay civil.

I believe that to a large extent, the discussion here is reflective of a
much larger discussion in society of to what extent, if at all, an entity
associated with an person must or should take action based on things that
that person does while not associated with that entity.

I think all of us understand that, on the one extreme, there are some
things so eggregious that entities must take action and on the other, we
don't want companies taking actions against employees that express
unpopular political positions or are members of marginalized minorities.
There's the famous Supreme Court Justice who said "I can't define
pornography, but I know it when I see it", but I think it's worse here: I
suspect that many more of us would agree on whether a particular piece of
media is pornography or not than would agree on whether a particular
behavior does or doesn't cross the line in terms of the obligations of an
entity associated with that person.

Re: Remove RMS from the GCC Steering Committee

[Soul Studios]

On 30/03/2021 1:18 am, Richard Kenner wrote:
>> I think I will leave this discussion up to those who have more
>> familiarity with the guy than I do. There's no doubt that some of the
>> stuff Stallman has written creeps me the hell out, and I think it was
>> more the tone of the OP I objected to.
> 
> I mostly want to stay out of this and will leave much of this discussion to
> others (though I have met RMS personally on a number of occaisions), but I
> want to mostly say that I agree with Jeff that it's important that this
> discussion stay civil.
> 
> I believe that to a large extent, the discussion here is reflective of a
> much larger discussion in society of to what extent, if at all, an entity
> associated with an person must or should take action based on things that
> that person does while not associated with that entity.

It's worth noting that when RMS was kicked from FSF, there was a 
2k-strong petition in favour, and a 3.5k-strong petition against. So 
clearly there is a discussion to be had, but as long as the left-wing 
(through self-rightiousness and threats of exclusion/withdrawal) and the 
right-wing (through belligerance and abuse/hostility) are trying 
actively to shut down discussion, that will not take place.

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

Here is something close to the fundamental issue: Believing in private life,
that people are entitled to their own associations and opinions (even bad ones!),
and entitled to make their own mistakes, too — and that, barring some direct
connection to work life or extraordinary circumstance, that none of this is
the concern of the little platoons of finks lurking in the community, 
particularly when driven by facebook lackeys muzzling everyday journalists
who go against the grain.  We see this not only here but also to medical
information dealing with coronavirus and vaccines.

---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Tuesday, March 30, 2021 at 9:41 AM
> From: "Soul Studios" <matt@soulstudios.co.nz>
> To: "Richard Kenner" <kenner@vlsi1.ultra.nyu.edu>
> Cc: gcc@gcc.gnu.org, mark@klomp.org, nathan@acm.org
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> 
> On 30/03/2021 1:18 am, Richard Kenner wrote:
> >> I think I will leave this discussion up to those who have more
> >> familiarity with the guy than I do. There's no doubt that some of the
> >> stuff Stallman has written creeps me the hell out, and I think it was
> >> more the tone of the OP I objected to.
> > 
> > I mostly want to stay out of this and will leave much of this discussion to
> > others (though I have met RMS personally on a number of occaisions), but I
> > want to mostly say that I agree with Jeff that it's important that this
> > discussion stay civil.
> > 
> > I believe that to a large extent, the discussion here is reflective of a
> > much larger discussion in society of to what extent, if at all, an entity
> > associated with an person must or should take action based on things that
> > that person does while not associated with that entity.
> 
> It's worth noting that when RMS was kicked from FSF, there was a 
> 2k-strong petition in favour, and a 3.5k-strong petition against. So 
> clearly there is a discussion to be had, but as long as the left-wing 
> (through self-rightiousness and threats of exclusion/withdrawal) and the 
> right-wing (through belligerance and abuse/hostility) are trying 
> actively to shut down discussion, that will not take place.
>

Re: Remove RMS from the GCC Steering Committee

[Ian Lance Taylor]

On Mon, Mar 29, 2021 at 4:33 PM Christopher Dimech via Gcc
<gcc@gcc.gnu.org> wrote:
>
> Here is something close to the fundamental issue: Believing in private life,
> that people are entitled to their own associations and opinions (even bad ones!),
> and entitled to make their own mistakes, too — and that, barring some direct
> connection to work life or extraordinary circumstance, that none of this is
> the concern of the little platoons of finks lurking in the community,
> particularly when driven by facebook lackeys muzzling everyday journalists
> who go against the grain.  We see this not only here but also to medical
> information dealing with coronavirus and vaccines.

Please work to avoid using terms like "finks" or "lackeys" when
describing members of the GCC community.  Please be respectful of
other people's opinions.  Thanks.

The question here is not whether RMS is permitted to contribute to
GCC.  I have not seen anybody arguing against that.  The question is
whether the GCC community should put him in a declared leadership
position.  For a leadership position, which serves as an example for
the community and to some extent demonstrates the values shared by the
community, I think it is reasonable that there is a decreased
expectation of privacy.

Ian

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Tuesday, March 30, 2021 at 12:09 PM
> From: "Ian Lance Taylor" <iant@google.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Soul Studios" <matt@soulstudios.co.nz>, "GCC Development" <gcc@gcc.gnu.org>, "Mark Wielaard" <mark@klomp.org>, "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> On Mon, Mar 29, 2021 at 4:33 PM Christopher Dimech via Gcc
> <gcc@gcc.gnu.org> wrote:
> >
> > Here is something close to the fundamental issue: Believing in private life,
> > that people are entitled to their own associations and opinions (even bad ones!),
> > and entitled to make their own mistakes, too — and that, barring some direct
> > connection to work life or extraordinary circumstance, that none of this is
> > the concern of the little platoons of finks lurking in the community,
> > particularly when driven by facebook lackeys muzzling everyday journalists
> > who go against the grain.  We see this not only here but also to medical
> > information dealing with coronavirus and vaccines.
> 
> Please work to avoid using terms like "finks" or "lackeys" when
> describing members of the GCC community.  Please be respectful of
> other people's opinions.  Thanks.
> 
> The question here is not whether RMS is permitted to contribute to
> GCC.  I have not seen anybody arguing against that.  The question is
> whether the GCC community should put him in a declared leadership
> position.  For a leadership position, which serves as an example for
> the community and to some extent demonstrates the values shared by the
> community, I think it is reasonable that there is a decreased
> expectation of privacy.

It is an unrealistic expectation.  I could understand such attitudes towards 
Harvey Weinstein and the like.  But now the scalp-hunting has started to target
ordinary and often obscure people, and the offenses in question have nothing
to do with bigotry — it is simply having the unfashionable view of a public
controversy, or being somehow associated, however lightly with that controversy.

You might say that the fullness of Thomas Jefferson’s legacy should be
acknowledged, but he did a bit more with his life than own slaves, just
as the Reverend Martin Luther King Jr. did more with his time on earth
than cheat on his wife and Mohandas Gandhi did more than write racist
tracts about black Africans.  We remember those men, and celebrate them,
for other things.
 
> Ian
>

Re: Remove RMS from the GCC Steering Committee

[Thomas Rodgers]

On 2021-03-29 17:39, Christopher Dimech via Gcc wrote:


> You might say that the fullness of Thomas Jefferson's legacy should be
> acknowledged, but he did a bit more with his life than own slaves, just
> as the Reverend Martin Luther King Jr. did more with his time on earth
> than cheat on his wife and Mohandas Gandhi did more than write racist
> tracts about black Africans.  We remember those men, and celebrate 
> them,
> for other things.

This is irrelevant to the discussion as to whether RMS should be member 
of GCC SC and whether or not the SC should make a public statement 
regarding the matter, one way or the other. The individuals you cite are 
all long dead, their entire history and legacy can be and is evaluated 
as much in the context of the time in which they lived as it is in the 
time in which we live now, with all the changes in social norms and 
standards that that entails. Stallman will no doubt be judged in a 
similar manner by history; founding the Free Software movement - good, 
the impact of his abusive and misogynistic behavior which (at best) 
belongs to another time - probably not so good.

The question is, in this time, right now, is that specific last bit 
there. Is that the legacy that the GCC project and it's community of 
contributors (and by contributors, I mean those that actively currently 
do so) by continued association, wants for itself?

I fully support the idea that the Steering Committee ought to make a 
definitive statement in that regard, one way or the other. Active 
contributors can then make whatever decisions they deem necessary based 
on that information.

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Tuesday, March 30, 2021 at 1:30 PM
> From: "Thomas Rodgers" <rodgert@appliantology.com>
> To: "Ian Lance Taylor" <iant@google.com>, "GCC Development" <gcc@gcc.gnu.org>, "Mark Wielaard" <mark@klomp.org>, "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> On 2021-03-29 17:39, Christopher Dimech via Gcc wrote:
>
>
> > You might say that the fullness of Thomas Jefferson's legacy should be
> > acknowledged, but he did a bit more with his life than own slaves, just
> > as the Reverend Martin Luther King Jr. did more with his time on earth
> > than cheat on his wife and Mohandas Gandhi did more than write racist
> > tracts about black Africans.  We remember those men, and celebrate
> > them,
> > for other things.
>
> This is irrelevant to the discussion as to whether RMS should be member
> of GCC SC and whether or not the SC should make a public statement
> regarding the matter, one way or the other. The individuals you cite are
> all long dead, their entire history and legacy can be and is evaluated
> as much in the context of the time in which they lived as it is in the
> time in which we live now, with all the changes in social norms and
> standards that that entails. Stallman will no doubt be judged in a
> similar manner by history; founding the Free Software movement - good,
> the impact of his abusive and misogynistic behavior which (at best)
> belongs to another time - probably not so good.

I followed an interview he had with Dr. Diane Hamilton, and one cannot say
he was prejudiced against her.  I have had my own problems with women in
higher up positions that expect they can act to any level of irresponsibility
as some men have done.  I thus consider women simply as people.

> The question is, in this time, right now, is that specific last bit
> there. Is that the legacy that the GCC project and it's community of
> contributors (and by contributors, I mean those that actively currently
> do so) by continued association, wants for itself?
>
> I fully support the idea that the Steering Committee ought to make a
> definitive statement in that regard, one way or the other. Active
> contributors can then make whatever decisions they deem necessary based
> on that information.
>

Re: Remove RMS from the GCC Steering Committee

[Alfred M. Szmidt]

A good reason why Richard should be on the SC is to that he does
demonstrates the values of the GNU project, that of the free software
movement and the FSF.  GCC is a important project, and having the head
of the GNU project involved -- even if mostly uninvolved in daily
topics, is a ultimately a good thing.

Re: Remove RMS from the GCC Steering Committee

[Richard Kenner]

> For a leadership position, which serves as an example for
> the community and to some extent demonstrates the values shared by the
> community, I think it is reasonable that there is a decreased
> expectation of privacy.

.. and libel and defamation laws in the US reflect that, for example.

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Tuesday, March 30, 2021 at 11:55 PM
> From: "Richard Kenner" <kenner@vlsi1.ultra.nyu.edu>
> To: dimech@gmx.com
> Cc: gcc@gcc.gnu.org, mark@klomp.org, matt@soulstudios.co.nz, nathan@acm.org
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> > Here is something close to the fundamental issue: Believing in
> > private life, that people are entitled to their own associations and
> > opinions (even bad ones!), and entitled to make their own mistakes,
> > too and that, barring some direct connection to work life or
> > extraordinary circumstance, that none of this is the concern of the
> > little platoons of finks lurking in the community,
>
> But I think that's exactly the question: when does something have a "direct
> connection to work life"?  Remember back in 2007 when US airlines were asking
> their pilots not to wear their uniforms to Unemployment offices because
> they were concerned about negative effect on their companies?

It is somewhat more complicated because his position con be recognised by
various people living in various countries, and thus does not fall into
one jurisdiction.  It seems to me that the situation is quite similar
to international law, where treaties requires all ratifying countries.
This can be extremely difficult.  Because Stallman is the founder, it
is in his prerogative to claim authority over the project.  I have been
a proponent over a transition and discussed this with him.  There could
have been possibilities for this to happen.  But in the climate that has
been created, he won't find the right conditions for a transition to occur.

Many had the chance to work with him but screwed it up.  People got to
understand this.

Christopher

Re: Remove RMS from the GCC Steering Committee

[Mark Wielaard]

Hi Richard,

On Mon, 2021-03-29 at 08:18 -0400, Richard Kenner via Gcc wrote:
> I mostly want to stay out of this and will leave much of this discussion to
> others (though I have met RMS personally on a number of occaisions), but I
> want to mostly say that I agree with Jeff that it's important that this
> discussion stay civil.
> 
> I believe that to a large extent, the discussion here is reflective of a
> much larger discussion in society of to what extent, if at all, an entity
> associated with an person must or should take action based on things that
> that person does while not associated with that entity.

I respect that you want stay out of the discussion, but I think that to
present this as some larger societal issue which is somewhat academic
is wrong. People are talking about behavior that affects our
community. 

Even if it is "just" in some other community or speech addressed to
others it sents a message to those others to avoid the Free Software
community, GNU and GCC because it tolerates unkind behavior and
harassment.

And it does happen in our own community. There have been various
examples given in this thread alone. And I hate to point to others,
because I know these people, who worked closely with RMS, will get
harassed to "proof" their allegations or will be told that since they
were not physically attacked it doesn't count as harassment.

It is also at Free Software conferences (organized by the FSF):

https://wwahammy.com/on-safety-at-libreplanet/

   We write to you as former speakers and keynoters at LibrePlanet. We
   are concerned that the Code of Conduct for the event is not applied
   evenly, and in particular that Officers and Board Members seem to be
   exempt. This creates an intimidating and hostile environment for
   attendees, speakers and potential future participants who hear that
   unchecked harassment is allowed at the event.

It is also in the GNU project and at the FSF:

https://nitter.cc/paulnivin/status/1374499598853545986

   I worked at the FSF for 3 years and volunteered for over 6 years -
   that ended in 2004. I witnessed misogyny, sexual objectification,
   and abuse  carried out by RMS. I banded together with my coworkers,
   formed a union, negotiated a contract, and was elected shop steward.

https://nitter.cc/georgialyle/status/1374504389155508232

   I worked at the FSF from 2015-2018 & was shop steward for a while. I
   recall having a months (MONTHS) long conversation with ED John
   Sullivan about why racist & sexist 'hacker humor' from the 90s
   needed to be  removed from gnu.org. rms didn't get why it was
   harmful.

https://nitter.cc/baconandcoconut/status/1374803434344488967

   Checking in as another former staff person (2006 - 2010) who started
   the Women in Free Software Caucus and maintained a GNU project for
   over a decade. I tried "calling in" or educating for years, but the
   community RMS inspires is sexist, completely toxic and impervious to
   change.

This is not just incidents, it is a pattern where RMS is not facing any
consequences because he feels our common rules of decency and
respecting each other don't apply to him.

What is even worse is that when people try to discuss such issues he
encourages his cult of personality to attack those who try to tell
their stories (as we are already seeing on this list by comments from
people not even associated with GNU or GCC). I earlier talked about
when we had an open discussion about GNU governance issues and a female
GCC hacker spoke up. Once he had arranged "new moderators" for the
mailing-list his exact words were:

   The new moderators have now allowed people to defend the GNU Project
   and to defend me personally.  If you would like to do these things,
   please do not hold back.

The resulting torrent of misogynistic and racist posts were truly
shocking. He turns a community into a toxic and hostile place when
people question his authority by implying such people must be the enemy
of Free Software or GNU and that they must be stopped.

Cheers,

Mark

Re: Remove RMS from the GCC Steering Committee

[Richard Kenner]

> I respect that you want stay out of the discussion, but I think that to
> present this as some larger societal issue which is somewhat academic
> is wrong. 

Sorry, I didn't mean to say or imply that.  What I meant to say is
that the very specific discussion we're having in this forum *mirrors*
the similar discussion that society is having in that the same issues
that are being discussed here are also being discussed there.

> And I hate to point to others, because I know these people, who
> worked closely with RMS, will get harassed to "proof" their
> allegations or will be told that since they were not physically
> attacked it doesn't count as harassment.

This is exactly what I mean by the need to draw a line.  At what point
does somebody's behavior rise to the level where it's necessary to
take action?  In other words, I think the question is less in understanding
what RMS's behavior has been (I suspect most people would agree on that),
but what the appropriate consequences of that behavior should be.

Re: Remove RMS from the GCC Steering Committee

[Martin Liška]

On 3/26/21 9:02 PM, Nathan Sidwell wrote:
> Dear members of the GCC Steering Committee (SC),  I ask you to remove Richard Stallman (RMS)

I do fully support Nathan's request.

Martin

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

More rats for the wood pile. 

---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Sunday, March 28, 2021 at 8:49 AM
> From: "Martin Liška" <mliska@suse.cz>
> To: "Nathan Sidwell" <nathan@acm.org>, "GCC Development" <gcc@gcc.gnu.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> On 3/26/21 9:02 PM, Nathan Sidwell wrote:
> > Dear members of the GCC Steering Committee (SC),  I ask you to remove Richard Stallman (RMS)
> 
> I do fully support Nathan's request.
> 
> Martin
>

Re: Remove RMS from the GCC Steering Committee

[Jeff Law]

On 3/27/2021 2:49 PM, Martin Liška wrote:
> On 3/26/21 9:02 PM, Nathan Sidwell wrote:
>> Dear members of the GCC Steering Committee (SC),  I ask you to remove 
>> Richard Stallman (RMS)
>
> I do fully support Nathan's request.

Speaking strictly for myself, not as a representative of the steering 
committee or Tachyum, I also fully support Nathan's request.


jeff

Re: Remove RMS from the GCC Steering Committee

[Martin Jambor]

Hi,

On Fri, Mar 26 2021, Nathan Sidwell wrote:
>
> Dear members of the GCC Steering Committee (SC),  I ask you to remove Richard 
> Stallman (RMS) from the SC, or, should you chose not to do so, make a clear 
> statement as to why he remains.
>

I wholeheartedly agree with Nathan.

In a few weeks I will have to ask selected GSoC students to sign away
their copyright to FSF and it will be very hard for me to make that
request - and doubly so if any of the students is female.  It is true
that RMS has not directly interacted with us for a long time and so
removing him from the committee may amount only to a gesture, but it
would be a powerful and very helpful gesture in this regard.  And IMHO
not just in this regard.

Thank you,

Martin

Re: Remove RMS from the GCC Steering Committee

[Jeff Law]

Setting aside whether or not RMS should be associated with the GCC 
project for a bit, I'm particularly concerned about the tone of some of 
the messages on this thread.  People can and will have differences, and 
that is fine.  But the discussion needs to stay civil.

To those who have crossed the line (no, I'm not going to call them out 
by name) -- please tone things done.  We have a long history here of not 
banning individuals from posting and I don't want to see this discussion 
escalate to the point where we're forced to take what I would consider 
drastic measures.

To those on the receiving end, I'm terribly sorry that some people can't 
disagree in a civil manner and I hope their behavior does not discourage 
you from continuing to contribute to GCC.

Jeff

Re: Remove RMS from the GCC Steering Committee

[Richard Biener]

On Fri, Mar 26, 2021 at 9:03 PM Nathan Sidwell <nathan@acm.org> wrote:
>
> [double sigh, attaching a pdf causes it to be blocked, and I guess the number of
> URLs is also triggering a spam trap for the follow up.  I have removed many of
> the URLS from this, you'll have to use your google-fu for sources.  I emailed
> several members of the SC, and don't want to bomb them with yet a third copy. ]
>
> Dear members of the GCC Steering Committee (SC),  I ask you to remove Richard
> Stallman (RMS) from the SC, or, should you chose not to do so, make a clear
> statement as to why he remains.

As far as I know the GCC Steering Committee (SC) acts as the "GNU maintainer" of
GCC with respect to how the GNU project is set up.  That likely makes it a
representative of the "GCC project" even though the SC rarely presents itself as
such.

I've never been asked to endorse or vote members of the SC, instead it seems to
have "self-appointed" itself in the beginning and when moving back under the
GNU umbrella likely the FSF "appointed" the original set of members as the GNU
maintainer.  I know some members voluntarily leaved but I have no idea about the
process of new members entering the SC - apart from suggesting the SC is
self-appointed (but GNU processes likely require the GNU project
leaders consent).

So this whole story points at a dysfunctional set up of the
representation of the GCC
project.  I suppose GNU (sub-)projects are not supposed to represent themselves.

I would not consider voting RMS onto the SC at this point, in fact I'd
not re-elect him.
I would even ask him to resign from this position.

But being inclusive also means being inclusive to people with
different opinions,
so I welcome technical contribution to GCC by RMS.  If RMS acts contrary to
(unwritten) code of conducts inside the GCC community then appropriate sanctions
should apply.

I do think that the request at hand puts specific pressure on the SC
members that
is unwarranted - you ask for them to respond but they are likely powerless as to
the actual request.  In fact were I on the SC I would suggest to all
of my fellow SC
members to resign and re-organize how GCC wants to be represented.  That would
effectively break the communication channel between GCC and the GNU
Project [the FSF]
but at this point it might be the important signal to send.

Richard.

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Mon, 29 Mar 2021, 11:13 Richard Biener via Gcc, <gcc@gcc.gnu.org> wrote:

>
> I do think that the request at hand puts specific pressure on the SC
> members that
> is unwarranted - you ask for them to respond but they are likely powerless
> as to
> the actual request.


I don't think they are powerless, but it doesn't necessarily matter.


  In fact were I on the SC I would suggest to all
> of my fellow SC
> members to resign and re-organize how GCC wants to be represented.  That
> would
> effectively break the communication channel between GCC and the GNU
> Project [the FSF]
> but at this point it might be the important signal to send.
>


I've been asking myself what benefit GCC gets from being linked to GNU and
all I can think of is the DNS records for gcc.gnu.org.

The downside is the link is that a vocal minority in the GNU community make
it a toxic and hostile place. Anybody who criticises RMS or questions his
authority is treated as an enemy who must be stopped. Ironically, those
rabid supporters of the cult of GNU might be what destroys the FSF as a
meaningful force for good.

I no longer see value in assigning my copyright to the FSF.

>

Re: Remove RMS from the GCC Steering Committee

[Didier Kryn]

Le 30/03/2021 à 10:25, Jonathan Wakely via Gcc a écrit :
> I've been asking myself what benefit GCC gets from being linked to GNU and
> all I can think of is the DNS records for gcc.gnu.org.

    Can you remind the meaning of GCC. Isn't it "*GNU* Compiler
Collection" ?

    If this is still true, it doesn't seem appropriate to "break the
communication channel" as you said in a previous mail. Or maybe you
might suggest a new name for the project (~:

--     Didier

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Tue, 30 Mar 2021 at 10:48, Didier Kryn wrote:
>
> Le 30/03/2021 à 10:25, Jonathan Wakely via Gcc a écrit :
> > I've been asking myself what benefit GCC gets from being linked to GNU and
> > all I can think of is the DNS records for gcc.gnu.org.
>
>     Can you remind the meaning of GCC. Isn't it "*GNU* Compiler
> Collection" ?
>
>     If this is still true, it doesn't seem appropriate to "break the
> communication channel" as you said in a previous mail. Or maybe you
> might suggest a new name for the project (~:

Sure, I have a few in mind.

Re: Remove RMS from the GCC Steering Committee

[Didier Kryn]

Le 30/03/2021 à 11:47, Didier Kryn a écrit :

Sorry it wasn't Jonathan Wakely but Richard Biener

> Le 30/03/2021 à 10:25, Jonathan Wakely via Gcc a écrit :
>> I've been asking myself what benefit GCC gets from being linked to GNU and
>> all I can think of is the DNS records for gcc.gnu.org.
>     Can you remind the meaning of GCC. Isn't it "*GNU* Compiler
> Collection" ?
>
>     If this is still true, it doesn't seem appropriate to "break the
> communication channel" as you said in a previous mail. Or maybe you
> might suggest a new name for the project (~:
>
> --     Didier
>
>

Re: Remove RMS from the GCC Steering Committee

[Andrew Haley]

On 3/30/21 10:47 AM, Didier Kryn wrote:
> Le 30/03/2021 à 10:25, Jonathan Wakely via Gcc a écrit :
>> I've been asking myself what benefit GCC gets from being linked to GNU and
>> all I can think of is the DNS records for gcc.gnu.org.
> 
>     Can you remind the meaning of GCC. Isn't it "*GNU* Compiler
> Collection" ?

It's been renamed at least once already, from "GNU C Compiler."

>     If this is still true, it doesn't seem appropriate to "break the
> communication channel" as you said in a previous mail. Or maybe you
> might suggest a new name for the project (~:

We could just rename it to "GCC", in much the same way that Acorn Risc
Machine became Advanced Risc Machines, then just "Arm". But I'd much
prefer that the FSF got its house in order.

-- 
Andrew Haley  (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Tue, 30 Mar 2021 at 11:14, Andrew Haley wrote:
>
> On 3/30/21 10:47 AM, Didier Kryn wrote:
> > Le 30/03/2021 à 10:25, Jonathan Wakely via Gcc a écrit :
> >> I've been asking myself what benefit GCC gets from being linked to GNU and
> >> all I can think of is the DNS records for gcc.gnu.org.
> >
> >     Can you remind the meaning of GCC. Isn't it "*GNU* Compiler
> > Collection" ?
>
> It's been renamed at least once already, from "GNU C Compiler."
>
> >     If this is still true, it doesn't seem appropriate to "break the
> > communication channel" as you said in a previous mail. Or maybe you
> > might suggest a new name for the project (~:
>
> We could just rename it to "GCC", in much the same way that Acorn Risc
> Machine became Advanced Risc Machines, then just "Arm". But I'd much
> prefer that the FSF got its house in order.

whynotboth.jpg

Re: Remove RMS from the GCC Steering Committee

[Andrew Haley]

On 3/30/21 11:34 AM, Jonathan Wakely wrote:
> On Tue, 30 Mar 2021 at 11:14, Andrew Haley wrote:

>> We could just rename it to "GCC", in much the same way that Acorn Risc
>> Machine became Advanced Risc Machines, then just "Arm". But I'd much
>> prefer that the FSF got its house in order.
> 
> whynotboth.jpg

I dunno, I don't want to see the FSF become the Parler of free software
foundations.

-- 
Andrew Haley  (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Tue, 30 Mar 2021 at 12:13, Andrew Haley wrote:
>
> On 3/30/21 11:34 AM, Jonathan Wakely wrote:
> > On Tue, 30 Mar 2021 at 11:14, Andrew Haley wrote:
>
> >> We could just rename it to "GCC", in much the same way that Acorn Risc
> >> Machine became Advanced Risc Machines, then just "Arm". But I'd much
> >> prefer that the FSF got its house in order.
> >
> > whynotboth.jpg
>
> I dunno, I don't want to see the FSF become the Parler of free software
> foundations.

I don't think GCC's continued involvement in the GNU Project will stop
that from happening.

Re: Remove RMS from the GCC Steering Committee

[Pankaj Jangid]

Not quoting anyone here. As a long time user of GCC, I am just worried
about the project. Hence my few comments and reasons for being part of
this movement called free-software.

RMS paid a visit to our premise in year 2000 or may be 2001. The
institute where I started working as a Visiting Software Engineer in the
year 2000. After a few years he came to IIT Bombay. I travelled a long
distance just to listen him again. I knew. The speech would be same, the
cause would be same but still I went.

[I am not sure if I am allowed to write here or not. Though I have
contributed to Emacs, but I have never contributed source code to
GCC. And some people have repeatedly made me feel that this long thread
is exclusively for those who have committed source code lines in GCC.]

I don’t even know what is the qualification of the existing Steering
Committee (SC). I use GCC, because there is a cause associated with
it. Since, last five years I have been reading articles about
superiority of a competing compiler technology - LLVM. But the original
concerns of RMS are clearly visible. Apple keeps the important
optimizations to itself. And many other software giants are also doing
it. Fair enough. They stick to their ideology. They release the code
only when it is longer a threat to their competitive advantage.

I have seriously started looking into Rust when I read about resumption
of work on ‘gccrs’. Such is the effect of this movement on me.

Coming to diversity. I have never seen people travelling 12000 miles to
convince people to join a cause. I am not talking about the
sponsored/luxurious conferences. I am talking about sleeping in a
sleeping-bag for weeks and sharing home-cooked meals with fellow
free-software activists in the remotest part of the world. Don’t get me
wrong. I would certainly like someone who has done more than this for
diversity. I am speaking this from experience. And I don’t have the said
privileges.

My only request to the remaining members of the SC is that - do take a
wise decision. And there is no need to overwhelmed
yourself. Organization, cause, and here the project, is bigger than the
people. People may come and go, people may saying anything. The project
should continue to be lazer focused, and serve the society.

-- 
Regards,
Pankaj Jangid

Re: Remove RMS from the GCC Steering Committee

[Giacomo Tesio]

Hi Nathan and hello everybody,

On Fri, 26 Mar 2021 16:02:30 -0400 Nathan Sidwell wrote:

> The USA is not the world and the SC is not the US government.  For
> those in the USA, the (inapplicable) first amendment provides 5
> rights, including showing an unwelcome guest the door. [...]
>
> If we fail to do so, it will continue to be harder and harder to
> attract new talent to GCC development.

I do not know if I qualify to speak here because I'm Italian and
I ported GCC 9.2.0 to Jehanne (a Plan 9 fork, see
http://jehanne.io/2021/01/06/gcc_on_jehanne.html), but due to the
pandemic I wasn't able to align it with the new developments and
contribute the port upstream. Also, I have no idea if you would be
interested in running GCC on a Plan 9 fork and thus accept my
contribution.


Yet, after a careful read of this thread I realized that I might
be considered the kind of "new talent" Nathan is talking about.

So here is my perspective on this topic, "in the hope it helps but
without any warranty". :-D


I do not share many of Stallman's opinions (we are VERY different), but
when I write free software and contribute to a free software community,
what I want is long term assurances about one and only one topic: that
the software will stay free as in freedom, as a common good for the
whole humanity.

As of today, GPLv3 is the legal tool that best suit this goal.
I don't think it's perfect in this regards, but that's another story.


As an Italian I'm having a hard time trying to follow your reasoning
about Stallman being a problem to attract new talents.

I could understand such statement if he had committed actual crimes,
was legally persecuted, processed and condemned like Reiser.

But while I try, I cannot really understand why you think that his name
in the Steering Committee would drive away people from contributing GCC 


I ported GCC to Plan 9 because I want a free compiler suite for my OS.

Porting CLANG would have been easier (to some extent) BUT my choice was
political and Stallman in the Steering Committee is a long term
warranty that GCC development will not steer away from the Free
Software conception that I know, betraying my trust.


My impression is that you are, in absolute good faith, projecting your
own culture (quite US-centric, as far as I can deduce by this thread)
to the whole world.


I do not really know if the removing Stallman from the Steering
Committee would attract more US people in GCC development. Or if it
would attract more US people that now prefer to work in LLVM only
because of they feel somehow bad working with Stallman in the SC.


But I can assure you that, as Pankaj Jangid said before me, many many
people are attracted to GCC, as users and developers, BECAUSE of
Stallman presence, because they know that something like this
https://medium.com/@giacomo_59737/what-i-wish-i-knew-before-contributing-to-open-source-dd63acd20696
will not happen to them.


World wide, people do not LIKE Stallman, but we TRUST him on this.
Just like the GPLv3, RMS is not perfect, but it does ONE THING well.


So, since you care about demographics, please consider that.

Removing RMS you might attract more of certain US demographics,
but you will certainly alienate a lot of people world wide that
do not align your political values (despite respecting them a lot!)
and do not think that a compiler suite can fix US systemic issues
anyway.


As for me, I would NOT trust GCC (or FSF) in the long term, had
you to distance Stallman, because I've already seen with my eyes 
what happen when people do not have anything to loose to betray your
trust, and Stallman has all to lose by betraying Free Software. 


Maybe I'm not the "new talent" you are looking for.

But please, do not turn GCC into a US-centric project.



Giacomo

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Wednesday, March 31, 2021 at 1:16 AM
> From: "Giacomo Tesio" <giacomo@tesio.it>
> To: "Nathan Sidwell" <nathan@acm.org>
> Cc: "GCC Development" <gcc@gcc.gnu.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> Hi Nathan and hello everybody,
>
> On Fri, 26 Mar 2021 16:02:30 -0400 Nathan Sidwell wrote:
>
> > The USA is not the world and the SC is not the US government.  For
> > those in the USA, the (inapplicable) first amendment provides 5
> > rights, including showing an unwelcome guest the door. [...]
> >
> > If we fail to do so, it will continue to be harder and harder to
> > attract new talent to GCC development.
>
> I do not know if I qualify to speak here because I'm Italian and
> I ported GCC 9.2.0 to Jehanne (a Plan 9 fork, see
> http://jehanne.io/2021/01/06/gcc_on_jehanne.html), but due to the
> pandemic I wasn't able to align it with the new developments and
> contribute the port upstream. Also, I have no idea if you would be
> interested in running GCC on a Plan 9 fork and thus accept my
> contribution.
>
>
> Yet, after a careful read of this thread I realized that I might
> be considered the kind of "new talent" Nathan is talking about.
>
> So here is my perspective on this topic, "in the hope it helps but
> without any warranty". :-D
>
>
> I do not share many of Stallman's opinions (we are VERY different), but
> when I write free software and contribute to a free software community,
> what I want is long term assurances about one and only one topic: that
> the software will stay free as in freedom, as a common good for the
> whole humanity.
>
> As of today, GPLv3 is the legal tool that best suit this goal.
> I don't think it's perfect in this regards, but that's another story.
>
>
> As an Italian I'm having a hard time trying to follow your reasoning
> about Stallman being a problem to attract new talents.
>
> I could understand such statement if he had committed actual crimes,
> was legally persecuted, processed and condemned like Reiser.
>
> But while I try, I cannot really understand why you think that his name
> in the Steering Committee would drive away people from contributing GCC
>
>
> I ported GCC to Plan 9 because I want a free compiler suite for my OS.
>
> Porting CLANG would have been easier (to some extent) BUT my choice was
> political and Stallman in the Steering Committee is a long term
> warranty that GCC development will not steer away from the Free
> Software conception that I know, betraying my trust.
>
>
> My impression is that you are, in absolute good faith, projecting your
> own culture (quite US-centric, as far as I can deduce by this thread)
> to the whole world.

Correct.  Very good evaluation.

> I do not really know if the removing Stallman from the Steering
> Committee would attract more US people in GCC development. Or if it
> would attract more US people that now prefer to work in LLVM only
> because of they feel somehow bad working with Stallman in the SC.
>
>
> But I can assure you that, as Pankaj Jangid said before me, many many
> people are attracted to GCC, as users and developers, BECAUSE of
> Stallman presence, because they know that something like this
> https://medium.com/@giacomo_59737/what-i-wish-i-knew-before-contributing-to-open-source-dd63acd20696
> will not happen to them.
>
>
> World wide, people do not LIKE Stallman, but we TRUST him on this.
> Just like the GPLv3, RMS is not perfect, but it does ONE THING well.
>
>
> So, since you care about demographics, please consider that.
>
> Removing RMS you might attract more of certain US demographics,
> but you will certainly alienate a lot of people world wide that
> do not align your political values (despite respecting them a lot!)
> and do not think that a compiler suite can fix US systemic issues
> anyway.
>
>
> As for me, I would NOT trust GCC (or FSF) in the long term, had
> you to distance Stallman, because I've already seen with my eyes
> what happen when people do not have anything to loose to betray your
> trust, and Stallman has all to lose by betraying Free Software.
>
>
> Maybe I'm not the "new talent" you are looking for.

The Gnu Project looks for all kind of talent.

> But please, do not turn GCC into a US-centric project.


> Giacomo

Re: Remove RMS from the GCC Steering Committee

[Martin Jambor]

Dear Giacomo,

On Tue, Mar 30 2021, Giacomo Tesio wrote:
> Hi Nathan and hello everybody,
>
> On Fri, 26 Mar 2021 16:02:30 -0400 Nathan Sidwell wrote:
>
>> The USA is not the world and the SC is not the US government.  For
>> those in the USA, the (inapplicable) first amendment provides 5
>> rights, including showing an unwelcome guest the door. [...]
>>
>> If we fail to do so, it will continue to be harder and harder to
>> attract new talent to GCC development.
>
> I do not know if I qualify to speak here because I'm Italian and
> I ported GCC 9.2.0 to Jehanne (a Plan 9 fork, see
> http://jehanne.io/2021/01/06/gcc_on_jehanne.html), but due to the
> pandemic I wasn't able to align it with the new developments and
> contribute the port upstream. Also, I have no idea if you would be
> interested in running GCC on a Plan 9 fork and thus accept my
> contribution.
>
>
> Yet, after a careful read of this thread I realized that I might
> be considered the kind of "new talent" Nathan is talking about.
>
> So here is my perspective on this topic, "in the hope it helps but
> without any warranty". :-D
>
>
> I do not share many of Stallman's opinions (we are VERY different), but
> when I write free software and contribute to a free software community,
> what I want is long term assurances about one and only one topic: that
> the software will stay free as in freedom, as a common good for the
> whole humanity.
>
> As of today, GPLv3 is the legal tool that best suit this goal.
> I don't think it's perfect in this regards, but that's another story.

Nobody suggested that GCC would be relicensed and certainly not to a
non-free license.  If you decide to contribute your port upstream, it
will be safe with us, regardless of who will or will not be on the
steering committee or running the FSF.  Just read the copyright
assignment text that you have singed or would need to sign to contribute
and look for FSF obligations as the license holder there.

> As an Italian I'm having a hard time trying to follow your reasoning
> about Stallman being a problem to attract new talents.

I do not believe that being European or Italian has anything to do with
it. I am European, I understand and agree with everything Nathan wrote
and apparently I am not the only one.

The ability to see and stand up to consistent wrongdoing is universal
and every human of every nationality posses it.  Unfortunately, all
people are also able to close their eyes and ears and ignore mistreatment
when they are not the victims and when their friend or their favorite
public figure is the perpetrator.  There is absolutely nothing American
or European about either.

Sincerely,

Martin

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Wednesday, March 31, 2021 at 4:50 AM
> From: "Martin Jambor" <mjambor@suse.cz>
> To: "Giacomo Tesio" <giacomo@tesio.it>
> Cc: "GCC Development" <gcc@gcc.gnu.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> Dear Giacomo,
> 
> On Tue, Mar 30 2021, Giacomo Tesio wrote:
> > Hi Nathan and hello everybody,
> >
> > On Fri, 26 Mar 2021 16:02:30 -0400 Nathan Sidwell wrote:
> >
> >> The USA is not the world and the SC is not the US government.  For
> >> those in the USA, the (inapplicable) first amendment provides 5
> >> rights, including showing an unwelcome guest the door. [...]
> >>
> >> If we fail to do so, it will continue to be harder and harder to
> >> attract new talent to GCC development.
> >
> > I do not know if I qualify to speak here because I'm Italian and
> > I ported GCC 9.2.0 to Jehanne (a Plan 9 fork, see
> > http://jehanne.io/2021/01/06/gcc_on_jehanne.html), but due to the
> > pandemic I wasn't able to align it with the new developments and
> > contribute the port upstream. Also, I have no idea if you would be
> > interested in running GCC on a Plan 9 fork and thus accept my
> > contribution.
> >
> >
> > Yet, after a careful read of this thread I realized that I might
> > be considered the kind of "new talent" Nathan is talking about.
> >
> > So here is my perspective on this topic, "in the hope it helps but
> > without any warranty". :-D
> >
> >
> > I do not share many of Stallman's opinions (we are VERY different), but
> > when I write free software and contribute to a free software community,
> > what I want is long term assurances about one and only one topic: that
> > the software will stay free as in freedom, as a common good for the
> > whole humanity.
> >
> > As of today, GPLv3 is the legal tool that best suit this goal.
> > I don't think it's perfect in this regards, but that's another story.
> 
> Nobody suggested that GCC would be relicensed and certainly not to a
> non-free license.  If you decide to contribute your port upstream, it
> will be safe with us, regardless of who will or will not be on the
> steering committee or running the FSF.  Just read the copyright
> assignment text that you have singed or would need to sign to contribute
> and look for FSF obligations as the license holder there.
> 
> > As an Italian I'm having a hard time trying to follow your reasoning
> > about Stallman being a problem to attract new talents.
> 
> I do not believe that being European or Italian has anything to do with
> it. I am European, I understand and agree with everything Nathan wrote
> and apparently I am not the only one.
> 
> The ability to see and stand up to consistent wrongdoing is universal
> and every human of every nationality posses it.  Unfortunately, all
> people are also able to close their eyes and ears and ignore mistreatment
> when they are not the victims and when their friend or their favorite
> public figure is the perpetrator.  There is absolutely nothing American
> or European about either.

Young socialists have been getting organized on colleges campuses 
with these extreme ideas not only in the United States.  France, for
instance has been harbouring a socialist model we should all dread.

France was once a role model for what big government can do for its
people. But it has become an embarrassing example since “The Gilets
Jaunes” took to the streets to demonstrate against the insane amount
of taxes they pay. These guys aren’t upper class. They are the people
who had supported the policies that are inevitable when you have the
government providing so many services and involved so deeply in so much
of the economy.

All those people in America who currently fall for the socialism soup
that that Ocasio-Cortez and Sanders are selling need to realize that if
their dream came to pass, they, not the rich – not the bankers and politicians
– will be ones suffering the most from the high taxes, high unemployment, and
slow growth that go hand in hand with the level of public spending they want.

> Sincerely,
> 
> Martin
>

Re: Remove RMS from the GCC Steering Committee

[Gabriel Ravier]

On 3/30/21 7:10 PM, Christopher Dimech via Gcc wrote:
>> Sent: Wednesday, March 31, 2021 at 4:50 AM
>> From: "Martin Jambor" <mjambor@suse.cz>
>> To: "Giacomo Tesio" <giacomo@tesio.it>
>> Cc: "GCC Development" <gcc@gcc.gnu.org>
>> Subject: Re: Remove RMS from the GCC Steering Committee
>>
>> Dear Giacomo,
>>
>> On Tue, Mar 30 2021, Giacomo Tesio wrote:
>>> Hi Nathan and hello everybody,
>>>
>>> On Fri, 26 Mar 2021 16:02:30 -0400 Nathan Sidwell wrote:
>>>
>>>> The USA is not the world and the SC is not the US government.  For
>>>> those in the USA, the (inapplicable) first amendment provides 5
>>>> rights, including showing an unwelcome guest the door. [...]
>>>>
>>>> If we fail to do so, it will continue to be harder and harder to
>>>> attract new talent to GCC development.
>>> I do not know if I qualify to speak here because I'm Italian and
>>> I ported GCC 9.2.0 to Jehanne (a Plan 9 fork, see
>>> http://jehanne.io/2021/01/06/gcc_on_jehanne.html), but due to the
>>> pandemic I wasn't able to align it with the new developments and
>>> contribute the port upstream. Also, I have no idea if you would be
>>> interested in running GCC on a Plan 9 fork and thus accept my
>>> contribution.
>>>
>>>
>>> Yet, after a careful read of this thread I realized that I might
>>> be considered the kind of "new talent" Nathan is talking about.
>>>
>>> So here is my perspective on this topic, "in the hope it helps but
>>> without any warranty". :-D
>>>
>>>
>>> I do not share many of Stallman's opinions (we are VERY different), but
>>> when I write free software and contribute to a free software community,
>>> what I want is long term assurances about one and only one topic: that
>>> the software will stay free as in freedom, as a common good for the
>>> whole humanity.
>>>
>>> As of today, GPLv3 is the legal tool that best suit this goal.
>>> I don't think it's perfect in this regards, but that's another story.
>> Nobody suggested that GCC would be relicensed and certainly not to a
>> non-free license.  If you decide to contribute your port upstream, it
>> will be safe with us, regardless of who will or will not be on the
>> steering committee or running the FSF.  Just read the copyright
>> assignment text that you have singed or would need to sign to contribute
>> and look for FSF obligations as the license holder there.
>>
>>> As an Italian I'm having a hard time trying to follow your reasoning
>>> about Stallman being a problem to attract new talents.
>> I do not believe that being European or Italian has anything to do with
>> it. I am European, I understand and agree with everything Nathan wrote
>> and apparently I am not the only one.
>>
>> The ability to see and stand up to consistent wrongdoing is universal
>> and every human of every nationality posses it.  Unfortunately, all
>> people are also able to close their eyes and ears and ignore mistreatment
>> when they are not the victims and when their friend or their favorite
>> public figure is the perpetrator.  There is absolutely nothing American
>> or European about either.
> Young socialists have been getting organized on colleges campuses
> with these extreme ideas not only in the United States.  France, for
> instance has been harbouring a socialist model we should all dread.
>
> France was once a role model for what big government can do for its
> people. But it has become an embarrassing example since “The Gilets
> Jaunes” took to the streets to demonstrate against the insane amount
> of taxes they pay. These guys aren’t upper class. They are the people
> who had supported the policies that are inevitable when you have the
> government providing so many services and involved so deeply in so much
> of the economy.
>
> All those people in America who currently fall for the socialism soup
> that that Ocasio-Cortez and Sanders are selling need to realize that if
> their dream came to pass, they, not the rich – not the bankers and politicians
> – will be ones suffering the most from the high taxes, high unemployment, and
> slow growth that go hand in hand with the level of public spending they want.
I fail to see how this has anything to do with the message you're 
answering. Is this what the right-wingers in America are resorting to ? 
Randomly making speeches about the "socialist soup" whenever they 
encounter something they can't find a good answer to ?
>> Sincerely,
>>
>> Martin
>>

Re: Remove RMS from the GCC Steering Committee

[Ian Lance Taylor]

I encourage everyone to please try to keep this discussion focused on GCC.

If there is a message that is completely unrelated to GCC, I encourage
not responding, or responding off-list.

Thanks.

Ian

Re: Remove RMS from the GCC Steering Committee

[Markus Böck]

Hello Giacomo and everyone else!

As a neighbour to your north (Austria), and another potential
newcomer, I would also like to point out that I do not believe the
views given by Nathan and others in support of him are very
US-centric. At least I would hope that most countries are in pursuit
or see value in having an inclusive environment where no one has to
feel treated unfairly due to either their gender, race or other
things. For what it's worth, Nathan may have simply picked the USA as
an example due familiarity. We don't know that.
As far as I am aware many of the people who have been participating in
this thread are also not from the USA.

I am also of the opinion that legally wrong does not equal morally
wrong. RMS does not have to have committed a crime for the developers
of GCC, the SC or whoever, to feel like he is not representing their
values as a member of the SC well.

Best regards
Markus

On Tue, Mar 30, 2021 at 3:20 PM Giacomo Tesio <giacomo@tesio.it> wrote:
>
> Hi Nathan and hello everybody,
>
> On Fri, 26 Mar 2021 16:02:30 -0400 Nathan Sidwell wrote:
>
> > The USA is not the world and the SC is not the US government.  For
> > those in the USA, the (inapplicable) first amendment provides 5
> > rights, including showing an unwelcome guest the door. [...]
> >
> > If we fail to do so, it will continue to be harder and harder to
> > attract new talent to GCC development.
>
> I do not know if I qualify to speak here because I'm Italian and
> I ported GCC 9.2.0 to Jehanne (a Plan 9 fork, see
> http://jehanne.io/2021/01/06/gcc_on_jehanne.html), but due to the
> pandemic I wasn't able to align it with the new developments and
> contribute the port upstream. Also, I have no idea if you would be
> interested in running GCC on a Plan 9 fork and thus accept my
> contribution.
>
>
> Yet, after a careful read of this thread I realized that I might
> be considered the kind of "new talent" Nathan is talking about.
>
> So here is my perspective on this topic, "in the hope it helps but
> without any warranty". :-D
>
>
> I do not share many of Stallman's opinions (we are VERY different), but
> when I write free software and contribute to a free software community,
> what I want is long term assurances about one and only one topic: that
> the software will stay free as in freedom, as a common good for the
> whole humanity.
>
> As of today, GPLv3 is the legal tool that best suit this goal.
> I don't think it's perfect in this regards, but that's another story.
>
>
> As an Italian I'm having a hard time trying to follow your reasoning
> about Stallman being a problem to attract new talents.
>
> I could understand such statement if he had committed actual crimes,
> was legally persecuted, processed and condemned like Reiser.
>
> But while I try, I cannot really understand why you think that his name
> in the Steering Committee would drive away people from contributing GCC
>
>
> I ported GCC to Plan 9 because I want a free compiler suite for my OS.
>
> Porting CLANG would have been easier (to some extent) BUT my choice was
> political and Stallman in the Steering Committee is a long term
> warranty that GCC development will not steer away from the Free
> Software conception that I know, betraying my trust.
>
>
> My impression is that you are, in absolute good faith, projecting your
> own culture (quite US-centric, as far as I can deduce by this thread)
> to the whole world.
>
>
> I do not really know if the removing Stallman from the Steering
> Committee would attract more US people in GCC development. Or if it
> would attract more US people that now prefer to work in LLVM only
> because of they feel somehow bad working with Stallman in the SC.
>
>
> But I can assure you that, as Pankaj Jangid said before me, many many
> people are attracted to GCC, as users and developers, BECAUSE of
> Stallman presence, because they know that something like this
> https://medium.com/@giacomo_59737/what-i-wish-i-knew-before-contributing-to-open-source-dd63acd20696
> will not happen to them.
>
>
> World wide, people do not LIKE Stallman, but we TRUST him on this.
> Just like the GPLv3, RMS is not perfect, but it does ONE THING well.
>
>
> So, since you care about demographics, please consider that.
>
> Removing RMS you might attract more of certain US demographics,
> but you will certainly alienate a lot of people world wide that
> do not align your political values (despite respecting them a lot!)
> and do not think that a compiler suite can fix US systemic issues
> anyway.
>
>
> As for me, I would NOT trust GCC (or FSF) in the long term, had
> you to distance Stallman, because I've already seen with my eyes
> what happen when people do not have anything to loose to betray your
> trust, and Stallman has all to lose by betraying Free Software.
>
>
> Maybe I'm not the "new talent" you are looking for.
>
> But please, do not turn GCC into a US-centric project.
>
>
>
> Giacomo

Re: Remove RMS from the GCC Steering Committee

[JeanHeyd Meneide]

Dear Giacomo,

     I want to reply specifically to you because you, like me, are a
new contributor, and I have a few questions and a few points that I
think are salient in this discussion.

> As an Italian I'm having a hard time trying to follow your reasoning
> about Stallman being a problem to attract new talents.
>
> I could understand such statement if he had committed actual crimes,
> was legally persecuted, processed and condemned like Reiser.
>
> But while I try, I cannot really understand why you think that his name
> in the Steering Committee would drive away people from contributing GCC

     The first is that I don't want to get into the conversation about
how the FSF handles Stallman. Other than them having my Copyright
assignment (something I also need to take a look at), the FSF does not
write the code. GCC's contributors, like you and me, do. My biggest
problem with Stallman right now is not about whether or not he likes
US-ians or if he's a good person:

     My problem is Dr. Richard M. Stallman stands credibly and
factually accused of Doxxing and GCC contributor/participant and
knowingly manipulating the project for his own personal reasons.

     When I say this, I want to be clear: when Mark sent his e-mail I
followed up with multiple GCC contributors to determine how factual
his claim actually was. Multiple people have independently
corroborated that Stallman did what Mark said, and worse, and their
quotes of Stallman's words line up word-for-word. In fact, what
Stallman did was worse than what Mark described, and has happened
multiple times before. Stallman is willing to attack and engage in
cancel culture of his own contributors. What his reasons are, I don't
know and I do not want to know: my bottom line here is that Stallman
is a danger to GCC contributors and is harmful to them.

     I make no argument based on my ethnicity, skin color, which side
of the globe I come from. Dr. Stallman's demonstrated behavior is that
he can - and WILL, and HAS - shown up into places where he has very
little to offer technically and utterly derailed or otherwise harmed
individuals or peoples **and their code contributions**.

     So, it boils down to this for me: either GCC is a place where all
contributions are welcome, or GCC is a place of hypocrisy, where
contributions are welcome except when Stallman (or someone else in a
position of power) lobbies a non-technical, non-factual argument
against you and jumps from their high tower to slam down on
rank-and-file contributors and participants. You cannot have it both
ways.

      That is why I switched from "wait and see" to "absolutely not".
I am not going to wait for the day somebody high up enough on the GCC
ladder doesn't like me enough to decide that he's going to
shoulder-slam my contributions with non-technical claptrap, nor am I
going to recommend other people to this project if anyone can do that
to them. Which brings me to another important point...

> I do not really know if the removing Stallman from the Steering
> Committee would attract more US people in GCC development. Or if it
> would attract more US people that now prefer to work in LLVM only
> because of they feel somehow bad working with Stallman in the SC.
>
>
> But I can assure you that, as Pankaj Jangid said before me, many many
> people are attracted to GCC, as users and developers, BECAUSE of
> Stallman presence, because they know that something like this
> https://medium.com/@giacomo_59737/what-i-wish-i-knew-before-contributing-to-open-source-dd63acd20696
> will not happen to them.
>
>
> World wide, people do not LIKE Stallman, but we TRUST him on this.
> Just like the GPLv3, RMS is not perfect, but it does ONE THING well.

     You state it here and many others say it throughout the thread
that Stallman is the only reason they contribute to GCC, or similar
Free Software projects. This deeply concerns me, because the
underlying implication is if that Stallman were to disappear, right
this second, all of you would be gone. Yet, on the other hand, we say
that this is the "Free Software MOVEMENT". A movement cannot be
destroyed because one person disappears; if that is the case, it is
not a movement, but a ring of personality around an individual. Either
this is a Free Software Movement, or this is Stallman's Free Software
Shindig. I contribute to GCC because I expect that when Stallman is
gone and I am Stallman's age, there will still be a Free Software
Movement. Stewarded by the FSF or the CNCF or the {insert gathering of
like-minded OSS contributors and enthusiasts and hard workers here}.

     Is this not the case for you and others?

     If Stallman is the only thing holding this movement together, I
would like to know this now so I can invest my time in an actual
movement elsewhere, independently of whether or not he remains on the
Steering Committee. (I still believe he has no place to have a
position of power on the Steering Committee, and instead should just
be a normal contributor, like everyone else, because he has proven he
is irresponsible and dangerous with such power.)

Sincerely,
JeanHeyd

Re: Remove RMS from the GCC Steering Committee

[Joseph Myers]

On Tue, 30 Mar 2021, JeanHeyd Meneide via Gcc wrote:

>      So, it boils down to this for me: either GCC is a place where all
> contributions are welcome, or GCC is a place of hypocrisy, where
> contributions are welcome except when Stallman (or someone else in a
> position of power) lobbies a non-technical, non-factual argument
> against you and jumps from their high tower to slam down on
> rank-and-file contributors and participants. You cannot have it both
> ways.

All contributions are welcome.  One of the key functions of the SC is 
actually saying no to RMS.

Central FSF or GNU project infrastructure is not used in developing GCC; 
gcc.gnu.org is entirely independent of central FSF or GNU infrastructure 
such as savannah.  So RMS has no control over policies applied to GCC 
mailing lists, and any influence he might apply to the moderation of lists 
hosted on lists.gnu.org does not apply here.  (Although GCC releases are 
uploaded to ftp.gnu.org, which is central GNU infrastructure, they are 
also available at https://gcc.gnu.org/pub/gcc/releases/ .)  He has an 
ordinary restricted user account on gcc.gnu.org giving the same access to 
push commits as most committers; he does not have shell or administrative 
access.

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Wednesday, March 31, 2021 at 5:45 AM
> From: "Joseph Myers" <joseph@codesourcery.com>
> To: "JeanHeyd Meneide" <phdofthehouse@gmail.com>
> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> On Tue, 30 Mar 2021, JeanHeyd Meneide via Gcc wrote:
> 
> >      So, it boils down to this for me: either GCC is a place where all
> > contributions are welcome, or GCC is a place of hypocrisy, where
> > contributions are welcome except when Stallman (or someone else in a
> > position of power) lobbies a non-technical, non-factual argument
> > against you and jumps from their high tower to slam down on
> > rank-and-file contributors and participants. You cannot have it both
> > ways.
> 
> All contributions are welcome.  One of the key functions of the SC is 
> actually saying no to RMS.
> 
> Central FSF or GNU project infrastructure is not used in developing GCC; 
> gcc.gnu.org is entirely independent of central FSF or GNU infrastructure 
> such as savannah.  So RMS has no control over policies applied to GCC 
> mailing lists, and any influence he might apply to the moderation of lists 
> hosted on lists.gnu.org does not apply here.  (Although GCC releases are 
> uploaded to ftp.gnu.org, which is central GNU infrastructure, they are 
> also available at https://gcc.gnu.org/pub/gcc/releases/ .)  He has an 
> ordinary restricted user account on gcc.gnu.org giving the same access to 
> push commits as most committers; he does not have shell or administrative 
> access.

People are inflating the power or control he actually has.  I have to say
that at no time has Stallman dictated on any of my work.  Unlike the animosity
that has been demonstrated by Ludovic Courtès in October 2019, by sending
a message disguised to look like an official Gnu Directive to Gnu Maintainers.
A fashionable tool for excommunicating those he find problematic due to their
pesky different points of view.   
 
> -- 
> Joseph S. Myers
> joseph@codesourcery.com
>

Re: Remove RMS from the GCC Steering Committee

[Andrew Sutton]

Are you still responding to me? Your response reads like a thinly veiled
threat. Angry friends on a jihad? Sounds serious.

On Tue, Mar 30, 2021, 7:14 PM Christopher Dimech <dimech@gmx.com> wrote:

>
> I have some friends in this movement who have been getting rather angry
> recently.  There is a lot of anger in the world,
> in fact, in politics.  Our political movement is not the only one
> suffering from anger at the moment.  But some of my angry
> friends, have come to the conclusion that they’re on a jihad for free
> software.
>
> That way won’t work. If a campaign of coercive compliance is carried just
> a moment too far, willingness to use free
> software among rational people will decline to a point which is dangerous
> to freedom.
>
> ---------------------
> Christopher Dimech
> General Administrator - Naiad Informatics - GNU Project (Geocomputation)
> - Geophysical Simulation
> - Geological Subsurface Mapping
> - Disaster Preparedness and Mitigation
> - Natural Resource Exploration and Production
> - Free Software Advocacy
>
>
> *Sent:* Wednesday, March 31, 2021 at 9:55 AM
> *From:* "Andrew Sutton" <asutton.list@gmail.com>
> *To:* "Christopher Dimech" <dimech@gmx.com>
> *Cc:* "Joseph Myers" <joseph@codesourcery.com>, "GCC Development" <
> gcc@gcc.gnu.org>, "Nathan Sidwell" <nathan@acm.org>
> *Subject:* Re: Remove RMS from the GCC Steering Committee
> Sorry for the confusion, but was this response directed to me? It seems
> entirely unrelated to what I wrote.
>
> On Tue, Mar 30, 2021, 5:35 PM Christopher Dimech <dimech@gmx.com> wrote:
>
>>
>> Seriously.  When you want something to happen within society, it is
>> complex.  Just
>> because you want to push something - an ideology - you chant about it
>> every day,
>> does not mean things will go your way.
>>
>> Perhaps you can start donating money to Antifa!
>>
>>
>>
>>
>>
>> *Sent:* Wednesday, March 31, 2021 at 9:09 AM
>> *From:* "Andrew Sutton" <asutton.list@gmail.com>
>> *To:* "Christopher Dimech" <dimech@gmx.com>
>> *Cc:* "Joseph Myers" <joseph@codesourcery.com>, "GCC Development" <
>> gcc@gcc.gnu.org>, "Nathan Sidwell" <nathan@acm.org>
>> *Subject:* Re: Remove RMS from the GCC Steering Committee
>> I guess I'll add my two cents. It seems everyone else is...
>>
>> I'm not a maintainer or frequent contributor, but I did implement
>> concepts for C++, and I'd like to continue contributing, time permitting.
>> My company (as in, I own it) also does some work on GCC, implementing new
>> and experimental features like contracts, which we intend to upstream,
>> pending review. Some modules-related stuff too (I hope).
>>
>> Maybe my response is a little different because I'm writing as a business
>> owner and not a contributor.
>>
>> </bona-fides>
>>
>> I understand that RMS is not actually on the steering committee and not
>> an active contributor, and the SC web page should be updated to reflect
>> that if it hasn't already.
>>
>> I agree with Nathan.
>>
>> The SC needs to be forward-looking --- you can't steer effectively if
>> you're always looking in the rear-view mirror. My understanding is that GCC
>> put RMS behind it a long time ago. And for the better.
>>
>> Part of the SC's job is (or should be) considering recruitment and
>> retention for this community, including corporate participation. This idea
>> that we have to somehow revere a person who has managed to make himself
>> controversial for reasons entirely unrelated to his ideology on free
>> software actively works against both of those goals.
>>
>> Undeniably so. If RMS were actually in the SC, I would have serious
>> reservations about committing my employees time to this community. His
>> documented behavior readily violates my company's code of conduct. At best,
>> I'd risk burn out employees in a toxic environment. At worst, I could end
>> up as a defendant in a sexual harassment case. And this 100% not hyperbole.
>>
>> (Thanks to everyone who makes GCC a good community to participate in.)
>>
>> I think it's perfectly reasonable for GCC to acknowledge RMS' past
>> contributions, both ideological and code-wise, but it's time to move on.
>> Nothing good comes from lionizing a man who purportedly asked teenage girls
>> to eat candy out of his hand.
>>
>>
>>
>> On Tue, Mar 30, 2021, 2:14 PM Christopher Dimech via Gcc <gcc@gcc.gnu.org>
>> wrote:
>>
>>>
>>> > Sent: Wednesday, March 31, 2021 at 5:45 AM
>>> > From: "Joseph Myers" <joseph@codesourcery.com>
>>> > To: "JeanHeyd Meneide" <phdofthehouse@gmail.com>
>>> > Cc: "GCC Development" <gcc@gcc.gnu.org>, "Nathan Sidwell" <
>>> nathan@acm.org>
>>> > Subject: Re: Remove RMS from the GCC Steering Committee
>>> >
>>> > On Tue, 30 Mar 2021, JeanHeyd Meneide via Gcc wrote:
>>> >
>>> > >      So, it boils down to this for me: either GCC is a place where
>>> all
>>> > > contributions are welcome, or GCC is a place of hypocrisy, where
>>> > > contributions are welcome except when Stallman (or someone else in a
>>> > > position of power) lobbies a non-technical, non-factual argument
>>> > > against you and jumps from their high tower to slam down on
>>> > > rank-and-file contributors and participants. You cannot have it both
>>> > > ways.
>>> >
>>> > All contributions are welcome.  One of the key functions of the SC is
>>> > actually saying no to RMS.
>>> >
>>> > Central FSF or GNU project infrastructure is not used in developing
>>> GCC;
>>> > gcc.gnu.org is entirely independent of central FSF or GNU
>>> infrastructure
>>> > such as savannah.  So RMS has no control over policies applied to GCC
>>> > mailing lists, and any influence he might apply to the moderation of
>>> lists
>>> > hosted on lists.gnu.org does not apply here.  (Although GCC releases
>>> are
>>> > uploaded to ftp.gnu.org, which is central GNU infrastructure, they are
>>> > also available at https://gcc.gnu.org/pub/gcc/releases/ .)  He has an
>>> > ordinary restricted user account on gcc.gnu.org giving the same
>>> access to
>>> > push commits as most committers; he does not have shell or
>>> administrative
>>> > access.
>>>
>>> People are inflating the power or control he actually has.  I have to say
>>> that at no time has Stallman dictated on any of my work.  Unlike the
>>> animosity
>>> that has been demonstrated by Ludovic Courtès in October 2019, by sending
>>> a message disguised to look like an official Gnu Directive to Gnu
>>> Maintainers.
>>> A fashionable tool for excommunicating those he find problematic due to
>>> their
>>> pesky different points of view.
>>>
>>> > --
>>> > Joseph S. Myers
>>> > joseph@codesourcery.com
>>> >
>>
>>

Re: Remove RMS from the GCC Steering Committee

[JeanHeyd Meneide]

Dear Giacomo,

     Apologies, a correction here. I should have more carefully read
it, but this paragraph:

>      My problem is Dr. Richard M. Stallman stands credibly and
> factually accused of Doxxing and GCC contributor/participant and
> knowingly manipulating the project for his own personal reasons.

     This should be "RMS explicitly sanctioned, encouraged, and
blessed the Doxxing of an individual". Apologies, he did not do the
doxxing himself; this was a fat finger on my part. Please take that
into account; the rest is accurate.

Sincerely,
JeanHeyd

Re: Remove RMS from the GCC Steering Committee

[Giacomo Tesio]

Hi everybody, thanks for your feedbacks.

I've to say I'm a bit confused, but maybe we have different sources and
experience so we have different perspective on the matter.

Let's start with something I want to clarify:

On Tue, 30 Mar 2021 13:07:07 -0400 JeanHeyd Meneide wrote:

>  You state it here and many others say it throughout the thread
> that Stallman is the only reason they contribute to GCC, or similar
> Free Software projects. This deeply concerns me

I'm sorry, but apperently I was not clear.

I do NOT follow RMS as a prophet or something. He does NOT "lead" me.
We do not agree on several relevant political issues (even some
important one related to Free Software!) and I find statements like
https://stallman.org/notes/2016-jul-oct.html#31_October_2016_(Down's_syndrome)
plain disgusting.

So I'm NOT, in any way, a RMS fanboy.

That being said (and for full disclosure), I also consider his return to
the FSF fair, because the shitstorm that caused his resign two years
ago was built on top of a severe misrepresentation of his words, as
described here https://jorgemorais.gitlab.io/justice-for-rms/ and
admitted also by the people arguing against his return (see the
various edits at https://rms-open-letter.github.io/appendix ).


But I'd want Stallman in GCC's SC for a totally different reason:

On Tue, 30 Mar 2021 18:50:52 +0200 Martin Jambor wrote:

> Nobody suggested that GCC would be relicensed and certainly not to a
> non-free license.  If you decide to contribute your port upstream, it
> will be safe with us, regardless of who will or will not be on the
> steering committee

When I joined the Harvey project they were all fun and welcoming.
When I asked how and where to write my copyright statement, I was
answered by the seasoned and well known Google's engineer that a few
years later completely removed my name from the project without
removing the contributions.

Harvey is copylefted too (GPLv2) and as you know, this sort of
behaviour would trigger GPL termination, but Harvey is part of
Software Freedom Conservancy and the violation of my copyright
likely occurred during the working hours of the above engineer.

So they were the good guys and the most powerful guys, together.
I had no hope in a US court (and I'm Italian and... let say "not rich").


They taught me a valuable lesson, though.

In the long run, even the good guys betray your trust if they have a
reason to and they think they can get away with that.


Stallman cannot betray Free Software AND get away with it.

So to me (and to many others) Stallman is a sort of a living warranty.

Unless, obviously, you have reasons that I ignore to not trust him on
his loyalty to the Free Software vision and movement. Do you have any?

For example when I read

On Tue, 30 Mar 2021 17:45:24 +0000 Joseph Myers wrote:
> One of the key functions of the SC is actually saying no to RMS.

My bad experiences with Google and SFC makes me ask: "about what?"


So if you (all) have good reason to think that RMS could betray
Free Software, well... THAT would be a good argument to put on the
table!


But note that to many of us, GCC is not just a great compiler suite!
More importantly, it's a Free Software compiler suite.

This means that its core value, its main "selling point", is not how
cool it is, but how it is designed, developed and distributed to
maximise software freedom.

IOW, I can imagine scenarios where some features should NOT be
introduced to reach this political goal which is MORE important
than the technical goal of compiler suite

To this aim, I'd prefer to see RMS in the GCC's SC.
Because to me GCC is not just "open source", it's not just matter of
seeing the source: it's Free Software, it should be designed and
developed TO maximize software freedom!

That's a fundamental difference that still stay between Free Software
and Open Source.


On Tue, 30 Mar 2021 18:56:02 +0200 Markus Böck wrote:

> At least I would hope that most countries are in pursuit
> or see value in having an inclusive environment where no one has to
> feel treated unfairly due to either their gender, race or other
> things.

I want to clarify that I hope this too. Really. 
And in fact thousands of people of very different races and genders
worldwide expressed their support for RMS and FSF by signing
https://rms-support-letter.github.io/
Some of them are my close friends, but I will not, obviously, doxe them.

However you can find very variegate people arguing on the web for RMS
from all of genders and races. Just a few valuable examples are 
Leah Rowe https://mobile.twitter.com/n4of7/status/1374844604101591047 and
Mary Kate Fain https://mobile.twitter.com/mkay_fain/status/1374766567544737793


On Tue, 30 Mar 2021 18:56:02 +0200 Markus Böck wrote:

> I am also of the opinion that legally wrong does not equal morally
> wrong. RMS does not have to have committed a crime for the developers
> of GCC, the SC or whoever, to feel like he is not representing their
> values as a member of the SC well.

This is the point, I think.

__In the context of software development__ RMS actually REPRESENT me.

And many other. We do not have to LIKE him.

But we trust HIM, on this regards.


Giacomo


Post Scripta

On Tue, 30 Mar 2021 18:50:52 +0200 Martin Jambor wrote:

> Unfortunately, all people are also able to close their eyes and ears
> and ignore mistreatment when they are not the victims and when their
> friend or their favorite public figure is the perpetrator.

Martin, what you imply here, is an insult I do not deserve.

I do NOT ignore injustice or mistreatments whenever I see them and I
fight them strongly through nonviolence. ALWAYS. 

But in Italy we have a legal principle called "Presumption of innocence".
It's a principle sadly abused by criminals, but it stands
because otherwise, the same criminals would abuse Law (and Power)
against the weakest.


On Tue, 30 Mar 2021 14:09:26 -0400 JeanHeyd Meneide wrote:

> >      My problem is Dr. Richard M. Stallman stands credibly and
> > factually accused of Doxxing and GCC contributor/participant and
> > knowingly manipulating the project for his own personal reasons.  
> 
> This should be "RMS explicitly sanctioned, encouraged, and
> blessed the Doxxing of an individual". Apologies, he did not do the
> doxxing himself; this was a fat finger on my part. 

Thanks for the clarification. I was quite surprised actually, because
I didn't read such accuse among the others in the rms-open-letter.

Did it happen on a public mailing list I can read?
Or maybe in a public forum? Or something that has been published
somewhere?

Don't get me wrong but I saw so much slanders and lies about Stallman
in the last two years that I prefer to double check primary sources to
form an opinion. 

Re: Remove RMS from the GCC Steering Committee

[Joseph Myers]

On Tue, 30 Mar 2021, Giacomo Tesio wrote:

> That being said (and for full disclosure), I also consider his return to
> the FSF fair, because the shitstorm that caused his resign two years
> ago was built on top of a severe misrepresentation of his words, as
> described here https://jorgemorais.gitlab.io/justice-for-rms/ and
> admitted also by the people arguing against his return (see the
> various edits at https://rms-open-letter.github.io/appendix ).

I explicitly stated in my comments that my agreement with Nathan's 
conclusion is *not* based on the views RMS has expressed, whether on that 
occasion or on any other.

> But I'd want Stallman in GCC's SC for a totally different reason:
> 
> On Tue, 30 Mar 2021 18:50:52 +0200 Martin Jambor wrote:
> 
> > Nobody suggested that GCC would be relicensed and certainly not to a
> > non-free license.  If you decide to contribute your port upstream, it
> > will be safe with us, regardless of who will or will not be on the
> > steering committee

The GCC SC doesn't have the power to relicense GCC; that lies with the 
FSF.  We can correct clear licensing mistakes where the underlying 
licensing policy is already established (e.g. if someone forgets to put 
the runtime exception in a file in a target library) and there are certain 
cases with delegated relicensing powers (e.g. copying documentation for 
target hooks between GFDL and GPL files).  But in general relicensing 
depends on the FSF and that doesn't depend on who is on the SC.

(The original owner of code who assigned it to the FSF can also license 
copies of the code they contributed (not anyone else's changes to that 
code) under different licenses if they so wish, in accordance with the 
terms of the standard assignment agreements.  The standard assignment 
agreements also prevent the FSF from distributing the code under 
proprietary terms.)

> On Tue, 30 Mar 2021 17:45:24 +0000 Joseph Myers wrote:
> > One of the key functions of the SC is actually saying no to RMS.
> 
> My bad experiences with Google and SFC makes me ask: "about what?"

Any time he comes up with an idea, technical or otherwise, that doesn't 
make sense (he's too far removed from actually following GCC development 
or use to be able to judge that effectively himself).  If an idea makes 
sense, of course we'll let him know that we'll consider patches.  (It's 
only likely to be in very routine cases that someone on the SC just makes 
the requested change themselves, e.g. if he points out somewhere in the 
GCC documentation saying "Linux" that should be "GNU/Linux" in accordance 
with GNU conventions.)

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: Remove RMS from the GCC Steering Committee

[Martin Jambor]

Dear Giacomo,

On Tue, Mar 30 2021, Giacomo Tesio wrote:
> On Tue, 30 Mar 2021 18:50:52 +0200 Martin Jambor wrote:
>
>> Unfortunately, all people are also able to close their eyes and ears
>> and ignore mistreatment when they are not the victims and when their
>> friend or their favorite public figure is the perpetrator.
>
> Martin, what you imply here, is an insult I do not deserve.

I am sorry.  I wanted to underline that the questions discussed here are
not cultural or somehow defined geographically.

> I do NOT ignore injustice or mistreatments whenever I see them and I
> fight them strongly through nonviolence. ALWAYS. 

Always?  OK, then you are clearly a much better person than I am.

> But in Italy we have a legal principle called "Presumption of innocence".

Nevertheless, I am convinced that all the many accusations are clear,
consistent and most of them are beyond any doubt (a lot of it is on
RMS's own blog).  They easily clear the bar for legitimate reasons why
he should not be an official representative of GCC.

I do not understand people which keep doubting the "evidence" or
describe it as hearsay, the only explanation I can think of is that they
simply do not wish to not accept the facts.  If you are certain that
this is not your case (no "proof" or explanation necessary) then please
accept my apologies.

Martin

Re: Remove RMS from the GCC Steering Committee

[Giacomo Tesio]

Hi Martin,

On Wed, 31 Mar 2021 10:53:20 +0200 Martin Jambor wrote:

> Dear Giacomo,
> 
> On Tue, Mar 30 2021, Giacomo Tesio wrote:
> > On Tue, 30 Mar 2021 18:50:52 +0200 Martin Jambor wrote:
> >  
> >> Unfortunately, all people are also able to close their eyes and
> >> ears and ignore mistreatment when they are not the victims and
> >> when their friend or their favorite public figure is the
> >> perpetrator.  
> >
> > Martin, what you imply here, is an insult I do not deserve.  
> 
> I am sorry.

No problem, apology accepted! ;-)

> I wanted to underline that the questions discussed here
> are not cultural or somehow defined geographically.

But it IS cultural (and thus storical and geographical): we interpret
any datum according to our existing knowledge and perspectives.

It's happening even now: I write these words trying to express what I
think in my mind and in the very instant you are reading them, you
interpret them according to your current positions and beliefs.


> > But in Italy we have a legal principle called "Presumption of
> > innocence".  
> 
> Nevertheless, I am convinced that all the many accusations are clear,
> consistent and most of them are beyond any doubt (a lot of it is on
> RMS's own blog).

If you consider software as a form of human expression and Free
Software as an obvious extension of Free Speech (that is a complex
human right, probably the most complex as it has to be balanced BY LAW
with all the others, privacy and personal safety above all), I think
you can see how controversial positions on a personal blogs cannot
constitute a valid argument against RMS.

If you marginalize people with controversial (but legal) positions you
select people that only do vague statements that everybody can
interpret as they like.

Ultimately, you select people whose real opinions you do not really
know and that only pretend to defend "Free Software as in Free Speech" 
because they do not practice Free Speech at all.

> They easily clear the bar for legitimate reasons why
> he should not be an official representative of GCC.
>
> I do not understand people which keep doubting the "evidence" or
> describe it as hearsay, the only explanation I can think of is that
> they simply do not wish to not accept the facts.  If you are certain
> that this is not your case (no "proof" or explanation necessary) then
> please accept my apologies.

Again, apologies accepted. :-)


Giacomo

Re: Remove RMS from the GCC Steering Committee

[Mark Wielaard]

Hi Giacomo,

On Tue, Mar 30, 2021 at 11:28:49PM +0200, Giacomo Tesio wrote:
> I've to say I'm a bit confused, but maybe we have different sources and
> experience so we have different perspective on the matter.

Yes, I am pretty sure the perspective changes for people who have had
longer, or more direct, exposure to Richard, while working on GNU or
GCC over the years.
 
> That being said (and for full disclosure), I also consider his return to
> the FSF fair, because the shitstorm that caused his resign two years
> ago was built on top of a severe misrepresentation of his words, as
> described here https://jorgemorais.gitlab.io/justice-for-rms/ and
> admitted also by the people arguing against his return (see the
> various edits at https://rms-open-letter.github.io/appendix ).

So this for example depends on whether you believe this is the one and
only incident that can easily be explained away or if it is a decades
long pattern of behavior where people finally had enough. See for
example this blog that links and lists various other past events
https://www.harihareswara.net/sumana/2021/03/26/0

You are referencing the recent open letter which isn't really what
people are discussing here. Although many probably sympathize with
calling for the removal of the entire Board of the Free Software
Foundation and calling for Richard M. Stallman to be removed from all
leadership positions, including the GNU Project

You can disagree with the specific way that was worded and still come
to the same conclusion. See for example https://www.arp242.net/rms.html

> On Tue, 30 Mar 2021 18:50:52 +0200 Martin Jambor wrote:
> 
> > Nobody suggested that GCC would be relicensed and certainly not to a
> > non-free license.  If you decide to contribute your port upstream, it
> > will be safe with us, regardless of who will or will not be on the
> > steering committee
> 
> When I joined the Harvey project they were all fun and welcoming.
> When I asked how and where to write my copyright statement, I was
> answered by the seasoned and well known Google's engineer that a few
> years later completely removed my name from the project without
> removing the contributions.
> 
> Harvey is copylefted too (GPLv2) and as you know, this sort of
> behaviour would trigger GPL termination, but Harvey is part of
> Software Freedom Conservancy and the violation of my copyright
> likely occurred during the working hours of the above engineer.
> 
> So they were the good guys and the most powerful guys, together.
> I had no hope in a US court (and I'm Italian and... let say "not rich").
> 
> 
> They taught me a valuable lesson, though.
> 
> In the long run, even the good guys betray your trust if they have a
> reason to and they think they can get away with that.

I looked a bit at that issue you filed and how they handled your
request to remove your code from the project. And I must say I don't
really understand what you believe they did wrong, they seemed to have
acknowledged and corrected their mistake and then removed all the code
you wanted to have removed. There is some disagreement over whether a
mass change of function declarations is copyrightable or not. But I
happen to agree with them that if there is only one way to do it, then
having someone else do the same transformation is a correct way to
resolve this. I am not sure I understand your goal in this particular
case. Sorry.

To make this copyright issue somewhat relevant to GCC. GCC doesn't
currently contain individual copyright statements and most of the code
is currently assigned to the FSF. So the above mistake won't happen
when contributing to GCC, but mostly because of the technicality that
you sign away your copyright up front.

> This means that its core value, its main "selling point", is not how
> cool it is, but how it is designed, developed and distributed to
> maximise software freedom.
> 
> IOW, I can imagine scenarios where some features should NOT be
> introduced to reach this political goal which is MORE important
> than the technical goal of compiler suite
> 
> To this aim, I'd prefer to see RMS in the GCC's SC.
> Because to me GCC is not just "open source", it's not just matter of
> seeing the source: it's Free Software, it should be designed and
> developed TO maximize software freedom!

But even here RMS is just one voice and his insights are not always
very accurate. His technical knowledge of the code base and of the
community who develops the code is simply not always current. That
doesn't mean he cannot understand the technology, he can, he still is
really smart. But it takes very long (months) to get him up to
speed. Once he understand the issue he often comes to the right
conclusion. But sometimes he doesn't because he doesn't have the full
picture. If he doesn't it might take months again to convince him he
was wrong. Which he will never admit, he will simply say people didn't
inform him about some change in technology or community participation,
when he changes his opinion. Yes, he always wants to maximize software
freedom, and so do many others with him, but his ideas of how to
design and develop code to achieve that aren't always accurate or
effective.

> On Tue, 30 Mar 2021 14:09:26 -0400 JeanHeyd Meneide wrote:
> 
> > >      My problem is Dr. Richard M. Stallman stands credibly and
> > > factually accused of Doxxing and GCC contributor/participant and
> > > knowingly manipulating the project for his own personal reasons.  
> > 
> > This should be "RMS explicitly sanctioned, encouraged, and
> > blessed the Doxxing of an individual". Apologies, he did not do the
> > doxxing himself; this was a fat finger on my part. 
> 
> Thanks for the clarification. I was quite surprised actually, because
> I didn't read such accuse among the others in the rms-open-letter.
> 
> Did it happen on a public mailing list I can read?
> Or maybe in a public forum? Or something that has been published
> somewhere?

I think this is actually two separate incidents of women being
harassed on a public gnu mailinglist for speaking up against Richard's
behavior. One happening about a year ago, another last week. Both by
individuals who were "defending" RMS. Whether to call them doxxing
depends on your definition. I would say the last one clearly was, the
first one might "just" have been "normal" vile, misogynist and racist.

Some of it was on private gnu lists, where people were called
subhumans and nazis. Which was obviously not a healthy environment to
have a discussion. So we asked the FSF Executive Director for a public
place to discuss GNU governance where we could have rules against such
hate speech and he agreed. Sadly when a woman (GCC contributor) spoke
up she got attacked in such a vile way we had to block/moderate some
posts. RMS disagreed with the public discussion and assumed the
moderators were preventing people from voicing certain opinions so
arranged for new moderators to take over the list that he assumed were
loyal to him and then said...

> The new moderators have now allowed people to defend the GNU Project
> and to defend me personally.  If you would like to do these things,
> please do not hold back.

I am not going to link to the public discussion that resulted because
of his call to action. It was truly horrible. I am also not going to
link to the latest doxxing campaign of the other woman because even
though the link to her picture, address and police station have been
removed from the archives what is left is almost equally bad. The
people involved (even if they acted for RMS, they did so in good faith)
don't deserve to be a target even more. And it doesn't help the
healing process to relitigate this incident. It happened, that is
painful enough.

Again, it isn't about this one or two incidents. I am sure someone can
find a way to explained it away by saying people simply misunderstood
his intentions or that no law was broken. But it is about a pattern of
behavior that shows RMS creates a misogynist, racist and transphobic
environment by (hopefully unknowingly) setting the example that others
will then follow and amplify.

Cheers,

Mark

Re: Remove RMS from the GCC Steering Committee

[Richard Biener]

On Wed, Mar 31, 2021 at 1:36 PM Mark Wielaard <mark@klomp.org> wrote:
>
> You are referencing the recent open letter which isn't really what
> people are discussing here. Although many probably sympathize with
> calling for the removal of the entire Board of the Free Software
> Foundation and calling for Richard M. Stallman to be removed from all
> leadership positions, including the GNU Project
>
> You can disagree with the specific way that was worded and still come
> to the same conclusion. See for example https://www.arp242.net/rms.html

Ah, this one is _very_ well written and captures my thoughts when
writing my response to Nathan (but not willing to spend so much time
on this to coherently formulate what I was thinking).

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").

Richard.

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Wed, 31 Mar 2021 at 13:29, Richard Biener 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").

The SC was appointed by the egcs community. They were then blessed as
"the official GNU maintainer" of the GNU project when egcs replaced
gcc as "the compiler for the GNU system", but we don't have to *be* a
GNU project. GNU cannot remove the SC, if they tried we'd just say
we're independent of GNU and then they don't get to have a say.

So no, the SC is not appointed by RMS, except in the same way that the
UK government is "chosen" by the Queen. By convention she appoints a
Prime Minister (the SC) and asks the PM to form a government (the GCC
devs). But in reality her "choice" is the party that won the election.
She is not allowed to choose for herself, or there would be ...
problems. If RMS or GNU tried to "choose" a new maintainer or replace
the SC, there would be ... problems.

Re: Remove RMS from the GCC Steering Committee

[David Edelsohn]

On Wed, Mar 31, 2021 at 8:28 AM Richard Biener via Gcc <gcc@gcc.gnu.org> wrote:
>
> On Wed, Mar 31, 2021 at 1:36 PM Mark Wielaard <mark@klomp.org> wrote:
> >
> > You are referencing the recent open letter which isn't really what
> > people are discussing here. Although many probably sympathize with
> > calling for the removal of the entire Board of the Free Software
> > Foundation and calling for Richard M. Stallman to be removed from all
> > leadership positions, including the GNU Project
> >
> > You can disagree with the specific way that was worded and still come
> > to the same conclusion. See for example https://www.arp242.net/rms.html
>
> Ah, this one is _very_ well written and captures my thoughts when
> writing my response to Nathan (but not willing to spend so much time
> on this to coherently formulate what I was thinking).
>
> 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").

Richard historically has approved nominees to the GCC SC because the
GNU Project considers the SC the official "maintainers" of GCC, but he
has not nominated or suggested any of the members.  I don't remember
him rejecting a proposed nominee.  And many major contributors to GCC
have not wished to be members of the GCC SC whose major purpose is to
be a buffer between the GCC Community and the Free Software
Foundation.

Has the GCC SC micro-managed you or prevented you from doing anything
as Global Reviewer and Release Manager?  Not that I'm aware of.

Has the GCC SC blocked any new port or major feature?  Not that I'm aware of.

Has the GCC SC blocked any qualified maintainer nominations?  Not that
I'm aware of.

Has the GCC SC instructed GCC developers on which features to work?  No.

Has the GCC SC inserted itself or voted on any disagreements?  No.

The reality is that the governance of GCC is extremely open because
it's performed by the developers in the community, not the GCC SC.
And GCC is much less bureaucratic than other, large Open Source
projects.  It doesn't have multiple committees and SIGs.  Everything
is worked out among the developers.  Projects are started by
developers who take the initiative to start a project.

Be careful what you wish for because it may be much worse than the
freedom that you currently enjoy.

Thanks, David

Re: Remove RMS from the GCC Steering Committee

[Richard Biener]

On Wed, Mar 31, 2021 at 2:59 PM David Edelsohn <dje.gcc@gmail.com> wrote:
>
> On Wed, Mar 31, 2021 at 8:28 AM Richard Biener via Gcc <gcc@gcc.gnu.org> wrote:
> >
> > On Wed, Mar 31, 2021 at 1:36 PM Mark Wielaard <mark@klomp.org> wrote:
> > >
> > > You are referencing the recent open letter which isn't really what
> > > people are discussing here. Although many probably sympathize with
> > > calling for the removal of the entire Board of the Free Software
> > > Foundation and calling for Richard M. Stallman to be removed from all
> > > leadership positions, including the GNU Project
> > >
> > > You can disagree with the specific way that was worded and still come
> > > to the same conclusion. See for example https://www.arp242.net/rms.html
> >
> > Ah, this one is _very_ well written and captures my thoughts when
> > writing my response to Nathan (but not willing to spend so much time
> > on this to coherently formulate what I was thinking).
> >
> > 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").
>
> Richard historically has approved nominees to the GCC SC because the
> GNU Project considers the SC the official "maintainers" of GCC, but he
> has not nominated or suggested any of the members.  I don't remember
> him rejecting a proposed nominee.  And many major contributors to GCC
> have not wished to be members of the GCC SC whose major purpose is to
> be a buffer between the GCC Community and the Free Software
> Foundation.
>
> Has the GCC SC micro-managed you or prevented you from doing anything
> as Global Reviewer and Release Manager?  Not that I'm aware of.
>
> Has the GCC SC blocked any new port or major feature?  Not that I'm aware of.
>
> Has the GCC SC blocked any qualified maintainer nominations?  Not that
> I'm aware of.
>
> Has the GCC SC instructed GCC developers on which features to work?  No.
>
> Has the GCC SC inserted itself or voted on any disagreements?  No.

That's all true.  It's still true that since GCC is a GNU project, formally
its maintainers are appointed by RMS (I've just read the official governance
structure document!).  It's also true that the SC is only indirectly reachable,
that we didn't vote on our representatives, or that there's no traces of
its work (assuming it does any).  Just to point to the pieces that
make it "not open".

> The reality is that the governance of GCC is extremely open because
> it's performed by the developers in the community, not the GCC SC.
> And GCC is much less bureaucratic than other, large Open Source
> projects.  It doesn't have multiple committees and SIGs.  Everything
> is worked out among the developers.  Projects are started by
> developers who take the initiative to start a project.
>
> Be careful what you wish for because it may be much worse than the
> freedom that you currently enjoy.

I'm actually enjoying not needing to interact with RMS or the FSF
and indeed the SC appears to handle things well.  But since people
are throwing in ideas to disassociate GCC from GNU I wanted to
point out that GCC needs to think of its own governance structure.

Richard.

>
> Thanks, David

Re: Remove RMS from the GCC Steering Committee

[Mark Wielaard]

Hi Richard,

On Wed, Mar 31, 2021 at 03:21:01PM +0200, Richard Biener via Gcc wrote:
> That's all true.  It's still true that since GCC is a GNU project, formally
> its maintainers are appointed by RMS (I've just read the official governance
> structure document!).

I think this is unfair to the steering committee and misrepresents
what it means to be a GNU project. That "gnu-stucture" document was
written by RMS a couple of months ago and doesn't represent how the
GNU project and its maintainers have worked for years. It seems to
have been a reaction to various GNU maintainers getting together and
discussing how the GNU project should actually be governed and how it
should interact with the FSF as summarized here:
https://gnu.wildebeest.org/blog/mjw/2019/12/27/proposals-for-the-new-gnu-fsf-relationship/

RMS indeed claims to be the "Chief GNUisance" of the GNU project and
that that title somehow makes him the leader of the project and that
he appoints GNU maintainers. But that isn't how things work in
practice. GNU projects (packages) have almost total autonomy and in
general decide themselves who the maintainers are. RMS simply records
their decissions in the maintainer file so the FSF knows who the
volunteers responsible are. In the past when RMS was the FSF president
it was sometimes an advantage to discuss some (legal) issues with him,
but in practice the FSF staff often had more time to actually help.

I am pretty sure that is how the steering committee has worked
too. Yes they involved RMS from time to time to update the FSF records
for the current steering committee members and to have a more direct
line to the FSF when it needed to involve the FSF for legal guidance,
but that was more to make sure the FSF was up to date than to give RMS
any leadership role. I do think Nathan is right that the Steering
Committee should have been more clear about this up front and
especially two years ago when RMS stepped down as president of the
FSF. But that is water under the bridge now and the steering committee
did clarify the relationship.

> It's also true that the SC is only indirectly reachable,
> that we didn't vote on our representatives, or that there's no traces of
> its work (assuming it does any).  Just to point to the pieces that
> make it "not open".
> 
> > The reality is that the governance of GCC is extremely open because
> > it's performed by the developers in the community, not the GCC SC.
> > And GCC is much less bureaucratic than other, large Open Source
> > projects.  It doesn't have multiple committees and SIGs.  Everything
> > is worked out among the developers.  Projects are started by
> > developers who take the initiative to start a project.
> >
> > Be careful what you wish for because it may be much worse than the
> > freedom that you currently enjoy.
> 
> I'm actually enjoying not needing to interact with RMS or the FSF
> and indeed the SC appears to handle things well.  But since people
> are throwing in ideas to disassociate GCC from GNU I wanted to
> point out that GCC needs to think of its own governance structure.

I do think you have a point here. If GCC is going to disassociate
itself from the FSF it needs to find a different fiscal sponsor and
legal guardian for the project and that would be a good time to
re-formalize the GCC Steering Committee setup. But I also think David
is right. Be careful what you wish for :)

Cheers,

Mark

Re: Remove RMS from the GCC Steering Committee

[Florian Weimer]

* David Edelsohn via Gcc:

> Has the GCC SC blocked any new port or major feature?  Not that I'm aware of.

What about the plugin framework?  The libgcc licensing change would
not have happened naturally.  Someone had to step in and delay the
plugin framework feature until the licensing changes were in place.

Re: Remove RMS from the GCC Steering Committee

[David Edelsohn]

On Wed, Mar 31, 2021 at 9:46 AM Florian Weimer <fw@deneb.enyo.de> wrote:
>
> * David Edelsohn via Gcc:
>
> > Has the GCC SC blocked any new port or major feature?  Not that I'm aware of.
>
> What about the plugin framework?  The libgcc licensing change would
> not have happened naturally.  Someone had to step in and delay the
> plugin framework feature until the licensing changes were in place.

I wrote blocked, not delayed.  In order to continue the alignment of
GCC with the FSF, the GCC SC agreed to delay deployment of LTO and
Plugins until a license to allow such features could be implemented.
We didn't feel that a rupture with the FSF would be beneficial.

Because I foresaw the need for such features and the need for the
license to accommodate it, I had been designing and negotiating with
the FSF for an appropriate license exception for years before LTO and
Plugins were proposed.  Richard Stallman, Richard Fontana, Brad Kuhn
and I all worked to resolve the issue.

I and other members of the GCC SC have worked diligently behind the
scenes to ensure that GCC and GNU Toolchain development can proceed as
smoothly and unhindered as possible.  We have prevented or resolved
many conflicts and issues without disturbing the broader community and
allow the community to focus on its important tasks and great progress
for the toolchain itself. I, at least, view that as my role as a
member of the GCC SC.  It's like a good manager: regardless of the
openness, hopefully the GCC community feels that the GCC SC "has their
back", manages the politics, and removes real or potential roadblocks
so that the software engineer can focus on being productive.

Thanks, David

Re: Remove RMS from the GCC Steering Committee

[Richard Biener]

On March 31, 2021 5:23:09 PM GMT+02:00, David Edelsohn <dje.gcc@gmail.com> wrote:
>On Wed, Mar 31, 2021 at 9:46 AM Florian Weimer <fw@deneb.enyo.de>
>wrote:
>>
>> * David Edelsohn via Gcc:
>>
>> > Has the GCC SC blocked any new port or major feature?  Not that I'm
>aware of.
>>
>> What about the plugin framework?  The libgcc licensing change would
>> not have happened naturally.  Someone had to step in and delay the
>> plugin framework feature until the licensing changes were in place.
>
>I wrote blocked, not delayed.  In order to continue the alignment of
>GCC with the FSF, the GCC SC agreed to delay deployment of LTO and
>Plugins until a license to allow such features could be implemented.
>We didn't feel that a rupture with the FSF would be beneficial.
>
>Because I foresaw the need for such features and the need for the
>license to accommodate it, I had been designing and negotiating with
>the FSF for an appropriate license exception for years before LTO and
>Plugins were proposed.  Richard Stallman, Richard Fontana, Brad Kuhn
>and I all worked to resolve the issue.
>
>I and other members of the GCC SC have worked diligently behind the
>scenes to ensure that GCC and GNU Toolchain development can proceed as
>smoothly and unhindered as possible.  We have prevented or resolved
>many conflicts and issues without disturbing the broader community and
>allow the community to focus on its important tasks and great progress
>for the toolchain itself. I, at least, view that as my role as a
>member of the GCC SC.  It's like a good manager: regardless of the
>openness, hopefully the GCC community feels that the GCC SC "has their
>back", manages the politics, and removes real or potential roadblocks
>so that the software engineer can focus on being productive.

Indeed. I believe without the SC doing this GCC would either have disassociated itself from GNU (again) or be of marginal importance today (without those features). 

Richard. 

>
>Thanks, David

Re: Remove RMS from the GCC Steering Committee

[Ian Lance Taylor]

On Wed, Mar 31, 2021 at 5:28 AM Richard Biener via Gcc <gcc@gcc.gnu.org> 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

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Wed, 31 Mar 2021 at 12:36, Mark Wielaard wrote:
> Again, it isn't about this one or two incidents. I am sure someone can
> find a way to explained it away by saying people simply misunderstood
> his intentions or that no law was broken. But it is about a pattern of
> behavior that shows RMS creates a misogynist, racist and transphobic
> environment by (hopefully unknowingly) setting the example that others
> will then follow and amplify.

Probably unintentionally, but he has allowed the GNU Project to become
a nasty cult of personality. The FSF seems to be imploding (with mass
resignations in the past week). I don't think GCC benefits from being
associated with either of them.

Is there any incident where FSF being the copyright holder for GCC has
made a difference? Are there any GPL violations involving GCC code
that were resolved only because all copyright resides with a single
entity, that couldn't have been resolved on behalf of individual
copyright holders?

Are we still worried about BigCorp trying to do a proprietary fork of
GCC? Because BigCorp, OtherCorp etc. have shown that they would prefer
to create a new toolchain from scratch rather than use GNU code. And
if EvilCorp want to make their own proprietary compiler with secret
optimizations, they'll just use LLVM instead of bothering to violate
the GPL. The work done to make it impossible to steal GCC code was a
success: nobody is even interested in stealing it now. There is an
easier option.

Can we break our (already weak) ties to GNU?

GCC association with the FSF

[Mark Wielaard]

Hi,

Lets change the subject now that this is about GCC and the FSF.

On Wed, Mar 31, 2021 at 01:46:29PM +0100, Jonathan Wakely via Gcc wrote:
> Probably unintentionally, but he has allowed the GNU Project to become
> a nasty cult of personality. The FSF seems to be imploding (with mass
> resignations in the past week). I don't think GCC benefits from being
> associated with either of them.

I admit it isn't looking very good and their last announcement is
certainly odd: https://status.fsf.org/notice/3833062

But apparently the board is still meeting this week to discuss and
might provide a better statement about the way out of this. So lets
give them a couple more days before writing them off completely.

> Is there any incident where FSF being the copyright holder for GCC has
> made a difference?

Yes, at least in my experience it has been helpful that the FSF held
copyright of code that had been assigned by various individuals and
companies. It allowed the merger of GNU Classpath and libgcj for
example. There have been various intances where it was helpful that
the FSF could unilatrally adjust the license terms especially when the
original contributor couldn't be found or didn't exist (as company)
anymore.

And it is really helpful that we don't have to ask permission of every
individual contributor to be able to create the GCC manual (because
the GPL code and GFDL text could otherwise not be combined) but that
the FSF can grant an exception to one of the developers to create it.

> Are there any GPL violations involving GCC code
> that were resolved only because all copyright resides with a single
> entity, that couldn't have been resolved on behalf of individual
> copyright holders?

I think it has been very helpful preventing those violations. If you
only have individual copyright holders instead of an organisation with
the means to actually resolve such violations people pay much more
attention to play by the rules. See for example the linux kernel
project. I believe there are so many GPL violations precisely because
almost no individual has the means to take up a case.

> Are we still worried about BigCorp trying to do a proprietary fork of
> GCC? Because BigCorp, OtherCorp etc. have shown that they would prefer
> to create a new toolchain from scratch rather than use GNU code. And
> if EvilCorp want to make their own proprietary compiler with secret
> optimizations, they'll just use LLVM instead of bothering to violate
> the GPL. The work done to make it impossible to steal GCC code was a
> success: nobody is even interested in stealing it now. There is an
> easier option.

I admit that the only way proprietary compiler writers can compete
with GCC is by producing a lax-permissive licensed compiler is an odd
way to win for Free Software. But we should still make sure that GCC
itself makes it so that users can actually get the sources of the
compiler they are using and not just some sources that might or might
not correspond to the binary they are using. Making sure that the code
reaches actual users and not just some corporate hackers to create a
proprietary compiler is what counts IMHO. And using strong copyleft
and having a shared copyright pool of code held by an entity that can
enforce that is still necessary IMHO.

> Can we break our (already weak) ties to GNU?

I hope GCC stays part of GNU, but that we might reconsider whether it
is in the best interest of GNU and GCC as Free Software project to
still be associated with the FSF. The GNU Assembly is having a similar
discussion right now
https://lists.gnu.tools/postorius/lists/assembly.lists.gnu.tools/

Cheers,

Mark

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Wednesday, April 07, 2021 at 10:22 AM
> From: "Mark Wielaard" <mark@klomp.org>
> To: "Jonathan Wakely" <jwakely.gcc@gmail.com>
> Cc: "GCC Development" <gcc@gcc.gnu.org>
> Subject: GCC association with the FSF
>
> Hi,
>
> Lets change the subject now that this is about GCC and the FSF.
>
> On Wed, Mar 31, 2021 at 01:46:29PM +0100, Jonathan Wakely via Gcc wrote:
> > Probably unintentionally, but he has allowed the GNU Project to become
> > a nasty cult of personality. The FSF seems to be imploding (with mass
> > resignations in the past week). I don't think GCC benefits from being
> > associated with either of them.
>
> I admit it isn't looking very good and their last announcement is
> certainly odd: https://status.fsf.org/notice/3833062
>
> But apparently the board is still meeting this week to discuss and
> might provide a better statement about the way out of this. So lets
> give them a couple more days before writing them off completely.
>
> > Is there any incident where FSF being the copyright holder for GCC has
> > made a difference?
>
> Yes, at least in my experience it has been helpful that the FSF held
> copyright of code that had been assigned by various individuals and
> companies. It allowed the merger of GNU Classpath and libgcj for
> example. There have been various intances where it was helpful that
> the FSF could unilatrally adjust the license terms especially when the
> original contributor couldn't be found or didn't exist (as company)
> anymore.
>
> And it is really helpful that we don't have to ask permission of every
> individual contributor to be able to create the GCC manual (because
> the GPL code and GFDL text could otherwise not be combined) but that
> the FSF can grant an exception to one of the developers to create it.

I have been discussing with Richard Stallman how we could get compatibility
between the GFDL and the other licences.

> > Are there any GPL violations involving GCC code
> > that were resolved only because all copyright resides with a single
> > entity, that couldn't have been resolved on behalf of individual
> > copyright holders?
>
> I think it has been very helpful preventing those violations. If you
> only have individual copyright holders instead of an organisation with
> the means to actually resolve such violations people pay much more
> attention to play by the rules. See for example the linux kernel
> project. I believe there are so many GPL violations precisely because
> almost no individual has the means to take up a case.
>
> > Are we still worried about BigCorp trying to do a proprietary fork of
> > GCC? Because BigCorp, OtherCorp etc. have shown that they would prefer
> > to create a new toolchain from scratch rather than use GNU code. And
> > if EvilCorp want to make their own proprietary compiler with secret
> > optimizations, they'll just use LLVM instead of bothering to violate
> > the GPL. The work done to make it impossible to steal GCC code was a
> > success: nobody is even interested in stealing it now. There is an
> > easier option.
>
> I admit that the only way proprietary compiler writers can compete
> with GCC is by producing a lax-permissive licensed compiler is an odd
> way to win for Free Software. But we should still make sure that GCC
> itself makes it so that users can actually get the sources of the
> compiler they are using and not just some sources that might or might
> not correspond to the binary they are using. Making sure that the code
> reaches actual users and not just some corporate hackers to create a
> proprietary compiler is what counts IMHO. And using strong copyleft
> and having a shared copyright pool of code held by an entity that can
> enforce that is still necessary IMHO.
>
> > Can we break our (already weak) ties to GNU?
>
> I hope GCC stays part of GNU, but that we might reconsider whether it
> is in the best interest of GNU and GCC as Free Software project to
> still be associated with the FSF. The GNU Assembly is having a similar
> discussion right now
> https://lists.gnu.tools/postorius/lists/assembly.lists.gnu.tools/
>
> Cheers,
>
> Mark
>

Re: GCC association with the FSF

[David Malcolm]

On Wed, 2021-04-07 at 00:22 +0200, Mark Wielaard wrote:
> Hi,
> 
> Lets change the subject now that this is about GCC and the FSF.
> 
> On Wed, Mar 31, 2021 at 01:46:29PM +0100, Jonathan Wakely via Gcc
> wrote:
> > Probably unintentionally, but he has allowed the GNU Project to
> > become
> > a nasty cult of personality. The FSF seems to be imploding (with
> > mass
> > resignations in the past week). I don't think GCC benefits from
> > being
> > associated with either of them.
> 
> I admit it isn't looking very good and their last announcement is
> certainly odd: https://status.fsf.org/notice/3833062
> 
> But apparently the board is still meeting this week to discuss and
> might provide a better statement about the way out of this. So lets
> give them a couple more days before writing them off completely.
> 
> > Is there any incident where FSF being the copyright holder for GCC
> > has
> > made a difference?
> 
> Yes, at least in my experience it has been helpful that the FSF held
> copyright of code that had been assigned by various individuals and
> companies. It allowed the merger of GNU Classpath and libgcj for
> example. There have been various intances where it was helpful that
> the FSF could unilatrally adjust the license terms especially when
> the
> original contributor couldn't be found or didn't exist (as company)
> anymore.

This benefit arises from having a single entity own the copyright in
the code.  It doesn't necessarily have to be the FSF to gain this
benefit; it just happens that the FSF currently owns the copyright on
the code.

Another, transitional approach might be to find another Free Software
non-profit and for contributors to start assigning copyright on ongoing
work to that other non-profit.  That way there would be only two
copyright holders on the code; if the FSF somehow survives its current
death-spiral then the other nonprofit could assign copyright back to
the FSF;  if it doesn't, well, we've already got bigger problems.

> And it is really helpful that we don't have to ask permission of
> every
> individual contributor to be able to create the GCC manual (because
> the GPL code and GFDL text could otherwise not be combined) but that
> the FSF can grant an exception to one of the developers to create it.

Alternatively, the copyright holder could relicense the documentation
to a license that is explicitly compatible with the GPL, such as the
GPL itself, and not require us to jump through hoops.  (Or we could
start a non-GFDL body of documentation under a different copyright
holder, but I'm not volunteering for that effort).  In case it's not
clear, I think the GFDL is a terrible license, and that it's always a
mistake to use it for software documentation.

> > Are there any GPL violations involving GCC code
> > that were resolved only because all copyright resides with a single
> > entity, that couldn't have been resolved on behalf of individual
> > copyright holders?
> 
> I think it has been very helpful preventing those violations. If you
> only have individual copyright holders instead of an organisation
> with
> the means to actually resolve such violations people pay much more
> attention to play by the rules. See for example the linux kernel
> project. I believe there are so many GPL violations precisely because
> almost no individual has the means to take up a case.

Again, the "single entity" doesn't need to be the FSF.

> > Are we still worried about BigCorp trying to do a proprietary fork
> > of
> > GCC? Because BigCorp, OtherCorp etc. have shown that they would
> > prefer
> > to create a new toolchain from scratch rather than use GNU code.
> > And
> > if EvilCorp want to make their own proprietary compiler with secret
> > optimizations, they'll just use LLVM instead of bothering to
> > violate
> > the GPL. The work done to make it impossible to steal GCC code was
> > a
> > success: nobody is even interested in stealing it now. There is an
> > easier option.
> 
> I admit that the only way proprietary compiler writers can compete
> with GCC is by producing a lax-permissive licensed compiler is an odd
> way to win for Free Software. 
> But we should still make sure that GCC
> itself makes it so that users can actually get the sources of the
> compiler they are using and not just some sources that might or might
> not correspond to the binary they are using. Making sure that the
> code
> reaches actual users and not just some corporate hackers to create a
> proprietary compiler is what counts IMHO. And using strong copyleft
> and having a shared copyright pool of code held by an entity that can
> enforce that is still necessary IMHO.
> 
> > Can we break our (already weak) ties to GNU?

It's not clear to me to what extent "GNU" is a thing that exists.  I
agree with much of Andy Wingo's October 2019 blog post:
http://www.wingolog.org/archives/2019/10/08/thoughts-on-rms-and-gnu


IMHO, "GNU" can mean various things:
- the small family of "g"-prefixed toolchain/low-level projects (gcc,
glibc, gdb) that work together and attend the GNU Tools Cauldron
- anything hosted under the gnu.org domain (including this mailing
list)
- things that have been blessed by RMS with the "GNU" title for
adhering to his own terms of ideological correctness
- an attempt to reimplement what in the 1980s passed for state-of-the-
art
- an idea, or vision, either political, or technological, or some blend
of both
- an expansive definition for whenever RMS wants to claim that other
people's work is somehow "GNU/Linux"
- various other definitions, I'm sure


> I hope GCC stays part of GNU, but that we might reconsider whether it
> is in the best interest of GNU and GCC as Free Software project to
> still be associated with the FSF. The GNU Assembly is having a
> similar
> discussion right now
> https://lists.gnu.tools/postorius/lists/assembly.lists.gnu.tools/

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.

My opinions, not my employer's, as usual.
Dave

Re: GCC association with the FSF

[Jonathan Wakely]

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.

Re: GCC association with the FSF

[Jeff Law]

On 4/7/2021 11:17 AM, 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.

Speaking strictly for myself, that works for me as well and I'd support 
such a proposal.


jeff

Re: GCC association with the FSF

[David Brown]

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 receives.


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.)

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Friday, April 09, 2021 at 3:00 AM
> From: "David Brown" <david@westcontrol.com>
> To: "Jonathan Wakely" <jwakely.gcc@gmail.com>, "David Malcolm" <dmalcolm@redhat.com>
> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Mark Wielaard" <mark@klomp.org>
> 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 receives.

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 Stallman.
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.)
>
>

Re: GCC association with the FSF

[David Brown]

On 08/04/2021 18:43, Christopher Dimech wrote:
> 
>> Sent: Friday, April 09, 2021 at 3:00 AM
>> From: "David Brown" <david@westcontrol.com>
>> To: "Jonathan Wakely" <jwakely.gcc@gmail.com>, "David Malcolm" <dmalcolm@redhat.com>
>> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Mark Wielaard" <mark@klomp.org>
>> Subject: Re: GCC association with the FSF
>>
<snip>
>> 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 receives.
> 
> 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 Stallman.
> At work, I have never encountered any committee that done me any good.
> 

RMS was key to getting GNU and the whole concept of Free Software off
the ground.  He was key to the initial development of several important
pieces of software.  He is no longer key to the development of any
software in a technical sense, nor is he key to the philosophical or
ideological parts of the process.

I don't think that any of Ian, Jonathan, and the others are
indispensable.  But I think all of them together are.  If any one or two
of the key gcc developers left the project, life would go on.  If my
feared scenario occurred and many or all of the current gcc developers
who are employed by major IT and hardware companies had to leave, the
project would be dead.

> 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.

As I said, I am a user.  I don't speak for the main developers of gcc,
or the maintainers of subprojects.  I expect that they do care about the
attitudes of the companies that employ them, at the very least.

> 
> 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.
> 

Stallman can indeed think whatever he likes, in that no one else can
decide his opinions for him.  He cannot /do/ whatever he likes - I
believe (but do not claim to be able to prove) that some of his past
actions would fall foul of laws against sexual harassment.

However, those of us who think differently on such matters - and that
is, I think, the solid majority of people (not just westerns) - will not
want anything to do with a person who holds such opinions and encourages
such attitudes.

Re: GCC association with the FSF

[Alexandre Oliva]

On Apr  8, 2021, David Brown <david@westcontrol.com> wrote:

> I believe (but do not claim to be able to prove) that some of his past
> actions would fall foul of laws against sexual harassment.

If you have any evidence whatsoever to support this belief, would you
please report it to the FSF board of directors, copying me?

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: GCC association with the FSF

[Nathan Sidwell]

On 4/11/21 5:23 PM, Alexandre Oliva via Gcc wrote:
> On Apr  8, 2021, David Brown <david@westcontrol.com> wrote:
> 
>> I believe (but do not claim to be able to prove) that some of his past
>> actions would fall foul of laws against sexual harassment.
> 
> If you have any evidence whatsoever to support this belief, would you
> please report it to the FSF board of directors, copying me?

Nice bit of deflection there.  I see what you're doing.

nathan

-- 
Nathan Sidwell

Re: GCC association with the FSF

[Gabriel Ravier]

On 4/8/21 6:43 PM, Christopher Dimech via Gcc wrote:
>> Sent: Friday, April 09, 2021 at 3:00 AM
>> From: "David Brown" <david@westcontrol.com>
>> To: "Jonathan Wakely" <jwakely.gcc@gmail.com>, "David Malcolm" <dmalcolm@redhat.com>
>> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Mark Wielaard" <mark@klomp.org>
>> 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 receives.
> 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 Stallman.
> At work, I have never encountered any committee that done me any good.

RMS is not indispensible because he does not contribute to GCC and 
doesn't bring much to it, and otherwise takes more away from it. If you 
were to remove all of Ian, Jonathan, Joseph and Nathan you would be 
removing ~13% of active contribution to GCC (counting in commits). If 
you also remove all the major contributors that are from corporations 
(counting a major contributor as someone with 10 or more commits), 
you're removing ~63% of active contribution. If you also remove the 
major organizations contributing to GCC, like Adacore and the GDC 
project, you're removing ~18% more of active contribution, meaning 
you're left with 19% of active contribution. While I do not doubt that 
all of the contributors that would remain are talented individuals, GCC 
would undoubtedly, in the best case, heavily suffer from the loss of 3 
to 4 fifths of active contribution and become much less appealing as a 
compiler, and in the worst case simply die out. While each of the 
individuals forming any of those groups aren't indispensable, as a 
group, they certainly are indispensible to GCC unless you think GCC can 
really survive with 3/5 times less contributions to it.


> 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.)
>>
>>
-- 
_________________________
Gabriel RAVIER
First year student at Epitech
+33 6 36 46 16 43
gabriel.ravier@epitech.eu
11 Quai Finkwiller
67000 STRASBOURG

Re: GCC association with the FSF

[Pankaj Jangid]

Gabriel Ravier via Gcc <gcc@gcc.gnu.org> writes:

> RMS is not indispensible because he does not contribute to GCC and
> doesn't bring much to it, and otherwise takes more away from it. If
> you were to remove all of Ian, Jonathan, Joseph and Nathan you would
> be removing ~13% of active contribution to GCC (counting in
> commits). If you also remove all the major contributors that are from
> corporations (counting a major contributor as someone with 10 or more
> commits), you're removing ~63% of active contribution. If you also
> remove the major organizations contributing to GCC, like Adacore and
> the GDC project, you're removing ~18% more of active contribution,
> meaning you're left with 19% of active contribution. While I do not
> doubt that all of the contributors that would remain are talented
> individuals, GCC would undoubtedly, in the best case, heavily suffer
> from the loss of 3 to 4 fifths of active contribution and become much
> less appealing as a compiler, and in the worst case simply die
> out. While each of the individuals forming any of those groups aren't
> indispensable, as a group, they certainly are indispensible to GCC
> unless you think GCC can really survive with 3/5 times less
> contributions to it.

What is this man? Are you trying to compute the probability of survival
a project? You forgot to count me. I am one of the users of GCC. If
there are no users then the project is dead; however heavyweight the
maintainers are. 

And let me also tell you the truth. I have looked at the list of
maintainers and the steering committee for the first time, when this
thread was started. My reason for sticking to GCC is FSF and associated
cause. Not the above list of people. Those who are not connected with
the cause have already started migrating to the competing tools.

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Friday, April 09, 2021 at 11:48 PM
> From: "Pankaj Jangid" <pankaj@codeisgreat.org>
> To: gcc@gcc.gnu.org
> Subject: Re: GCC association with the FSF
>
> Gabriel Ravier via Gcc <gcc@gcc.gnu.org> writes:
>
> > RMS is not indispensible because he does not contribute to GCC and
> > doesn't bring much to it, and otherwise takes more away from it. If
> > you were to remove all of Ian, Jonathan, Joseph and Nathan you would
> > be removing ~13% of active contribution to GCC (counting in
> > commits). If you also remove all the major contributors that are from
> > corporations (counting a major contributor as someone with 10 or more
> > commits), you're removing ~63% of active contribution. If you also
> > remove the major organizations contributing to GCC, like Adacore and
> > the GDC project, you're removing ~18% more of active contribution,
> > meaning you're left with 19% of active contribution. While I do not
> > doubt that all of the contributors that would remain are talented
> > individuals, GCC would undoubtedly, in the best case, heavily suffer
> > from the loss of 3 to 4 fifths of active contribution and become much
> > less appealing as a compiler, and in the worst case simply die
> > out. While each of the individuals forming any of those groups aren't
> > indispensable, as a group, they certainly are indispensible to GCC
> > unless you think GCC can really survive with 3/5 times less
> > contributions to it.
>
> What is this man? Are you trying to compute the probability of survival
> a project? You forgot to count me. I am one of the users of GCC. If
> there are no users then the project is dead; however heavyweight the
> maintainers are.
>
> And let me also tell you the truth. I have looked at the list of
> maintainers and the steering committee for the first time, when this
> thread was started. My reason for sticking to GCC is FSF and associated
> cause. Not the above list of people. Those who are not connected with
> the cause have already started migrating to the competing tools.

RMS made the GNU System without the cohort of active contributions listed.
This means that great things can be accomplished when people is focused
on what they do.  I am sure help will come from other sources if the tools
are valuable enough.

Re: GCC association with the FSF

[Gabriel Ravier]

On 4/9/21 1:48 PM, Pankaj Jangid wrote:
> Gabriel Ravier via Gcc <gcc@gcc.gnu.org> writes:
>
>> RMS is not indispensible because he does not contribute to GCC and
>> doesn't bring much to it, and otherwise takes more away from it. If
>> you were to remove all of Ian, Jonathan, Joseph and Nathan you would
>> be removing ~13% of active contribution to GCC (counting in
>> commits). If you also remove all the major contributors that are from
>> corporations (counting a major contributor as someone with 10 or more
>> commits), you're removing ~63% of active contribution. If you also
>> remove the major organizations contributing to GCC, like Adacore and
>> the GDC project, you're removing ~18% more of active contribution,
>> meaning you're left with 19% of active contribution. While I do not
>> doubt that all of the contributors that would remain are talented
>> individuals, GCC would undoubtedly, in the best case, heavily suffer
>> from the loss of 3 to 4 fifths of active contribution and become much
>> less appealing as a compiler, and in the worst case simply die
>> out. While each of the individuals forming any of those groups aren't
>> indispensable, as a group, they certainly are indispensible to GCC
>> unless you think GCC can really survive with 3/5 times less
>> contributions to it.
> What is this man? Are you trying to compute the probability of survival
> a project? You forgot to count me. I am one of the users of GCC. If
> there are no users then the project is dead; however heavyweight the
> maintainers are.
>
> And let me also tell you the truth. I have looked at the list of
> maintainers and the steering committee for the first time, when this
> thread was started. My reason for sticking to GCC is FSF and associated
> cause. Not the above list of people. Those who are not connected with
> the cause have already started migrating to the competing tools.
>

If you have an enormous exodus of maintainers that takes away 4 fifths 
of maintainers, then there is a very high probability that the project 
will simply die by essentially all measures except for such asinine ones 
as "there is still at least 1 user of it" (under which, say, Version 6 
UNIX is not dead as there are still computers running it and people 
using it), as a GCC with much less people maintaining it would, over 
time, become very unattractive as a tool for actually making programs, 
as progress on developing it would become very slow. It would, for 
example, lose any C++ users that want to use anything beyond C++17 or 
the partial support for C++20 that GCC has right now.

While I am not saying that the amount of maintainers is directly tied to 
the survival of a project, I would certainly say that a project with 
near to no maintainers without which it cannot compete with competing 
projects (for example, Clang) /will/ die off.

The only ones that would remain would be those that would use GCC 
despite its enormous shortcomings for the single and only reason that it 
is licensed under the GPL, and those would be rather rare compared to 
the amount of people that use GCC right now. I am not saying that they 
are just a few dozen people or something like that, but GCC would become 
a shadow of its former self without any other support.

I would say that under those circumstances GCC would become about as 
popular as Turbo C or other antiquated tools like it, and I would 
certainly hope one would consider Turbo C to be a dead compiler, despite 
the fact that it still has at least 1 active user. While I don't think 
this outcome is likely, it would become likely if every single 
corporation and organization involved in the development of GCC suddenly 
retracted support for it. Do you really think GCC could remain 
competitive compared to compilers like Clang or MSVC if development on 
it was 5 times as slow, and if distributions like Fedora and Ubuntu 
started to migrate to LLVM, or even maybe straight up removed GCC from 
their repositories ?

PS: Of course, this is completely implausible, and it is almost certain 
that this will never happen, but you're implying that GCC can perfectly 
survive without any support from corporations: I am simply telling you 
what would happen if all those corporations actually stopped to support it

Re: GCC association with the FSF

[Pankaj Jangid]

Gabriel Ravier via Gcc <gcc@gcc.gnu.org> writes:

>> What is this man? Are you trying to compute the probability of survival
>> a project? You forgot to count me. I am one of the users of GCC. If
>> there are no users then the project is dead; however heavyweight the
>> maintainers are.
>>
>> And let me also tell you the truth. I have looked at the list of
>> maintainers and the steering committee for the first time, when this
>> thread was started. My reason for sticking to GCC is FSF and associated
>> cause. Not the above list of people. Those who are not connected with
>> the cause have already started migrating to the competing tools.
>>
> While I am not saying that the amount of maintainers is directly tied
> to the survival of a project, I would certainly say that a project
> with near to no maintainers without which it cannot compete with
> competing projects (for example, Clang) /will/ die off.

I have never said that the project will survive without maintainers. I
just asked you to count me as well. Success of the project also depends
on how widely it is used. And you need to look at the reasons why people
are using it.

> The only ones that would remain would be those that would use GCC
> despite its enormous shortcomings for the single and only reason that
> it is licensed under the GPL, and those would be rather rare compared
> to the amount of people that use GCC right now. I am not saying that
> they are just a few dozen people or something like that, but GCC would
> become a shadow of its former self without any other support.

People who care for “Copyleft” were already rare. But people joined;
despite the shortcomings people used “Libre” tools. Something must have
triggered them to participate as users, as developers. What could be
that?

> I would say that under those circumstances GCC would become about as
> popular as Turbo C or other antiquated tools like it, and I would
> certainly hope one would consider Turbo C to be a dead compiler,
> despite the fact that it still has at least 1 active user.

> While I don't think this outcome is likely, it would become likely if
> every single corporation and organization involved in the development
> of GCC suddenly retracted support for it. Do you really think GCC
> could remain competitive compared to compilers like Clang or MSVC if
> development on it was 5 times as slow, and if distributions like
> Fedora and Ubuntu started to migrate to LLVM, or even maybe straight
> up removed GCC from their repositories ?

> PS: Of course, this is completely implausible, and it is almost
> certain that this will never happen, but you're implying that GCC can
> perfectly survive without any support from corporations: I am simply
> telling you what would happen if all those corporations actually
> stopped to support it

I never said that corporations are not important. But it is not
charity. It is the benefit that they got out of GCC. After LLVM, this
will also be a big challenge.

Let us watch the funding trends in the coming years. I will emphasize on
getting those people onboard who are associated with the cause. And when
I say this, I talk about both sides of the spectrum - the developers as
well as the users. With the right set of emotionally connected community
of people, you can do wonders.

Anyway, I am not against your view that maintainers are important. They
certainly are.

Re: GCC association with the FSF

[David Brown]

On 10/04/2021 14:58, Pankaj Jangid wrote:
> 
> I have never said that the project will survive without maintainers. I
> just asked you to count me as well. Success of the project also depends
> on how widely it is used. And you need to look at the reasons why people
> are using it.
> 

I think it is useful to consider why people use gcc - I agree that
without users, there would be no project.

So why /do/ people use it?  I suspect that one of the biggest reason is
"it's the only compiler that will do the job".  For a lot of important
software, such as Linux kernel, it is gcc or nothing.  Another big
reason is that gcc comes with their system, which is commonly the case
for Linux systems.  In the embedded development world (where I work),
the normal practice for getting a toolchain for a microcontroller is to
download an IDE and toolchain from the manufacturer - and these days it
is more often gcc than not.  You use gcc because that is the standard,
not from choice.

For those that actively /choose/ gcc, why do they do so?  I'd guess
being convenient, well-known and free (as in beer) come a lot higher
than the details of the licence, or the difference between "free
software" and "open source software".  (For me, a major reason is that
the same compiler supports a wide range of targets.  That, and that gcc
is technically a better compiler for my needs than any alternatives.)

I suspect that only a very small (but not zero) proportion of gcc users
care that the project is part of GNU and under the FSF.  I suspect that
a larger proportion would start caring if they felt (rightly or wrongly)
that at the top of the hierarchy was a misogynist who patronises and
sexually harasses women.

(As always, this is just my opinion.)

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Sunday, April 11, 2021 at 4:34 AM
> From: "David Brown" <david.brown@hesbynett.no>
> To: "Pankaj Jangid" <pankaj@codeisgreat.org>, gcc@gcc.gnu.org
> Subject: Re: GCC association with the FSF
>
> On 10/04/2021 14:58, Pankaj Jangid wrote:
> >
> > I have never said that the project will survive without maintainers. I
> > just asked you to count me as well. Success of the project also depends
> > on how widely it is used. And you need to look at the reasons why people
> > are using it.
> >
>
> I think it is useful to consider why people use gcc - I agree that
> without users, there would be no project.
>
> So why /do/ people use it?  I suspect that one of the biggest reason is
> "it's the only compiler that will do the job".  For a lot of important
> software, such as Linux kernel, it is gcc or nothing.  Another big
> reason is that gcc comes with their system, which is commonly the case
> for Linux systems.  In the embedded development world (where I work),
> the normal practice for getting a toolchain for a microcontroller is to
> download an IDE and toolchain from the manufacturer - and these days it
> is more often gcc than not.  You use gcc because that is the standard,
> not from choice.
>
> For those that actively /choose/ gcc, why do they do so?  I'd guess
> being convenient, well-known and free (as in beer) come a lot higher
> than the details of the licence, or the difference between "free
> software" and "open source software".  (For me, a major reason is that
> the same compiler supports a wide range of targets.  That, and that gcc
> is technically a better compiler for my needs than any alternatives.)
>
> I suspect that only a very small (but not zero) proportion of gcc users
> care that the project is part of GNU and under the FSF.  I suspect that
> a larger proportion would start caring if they felt (rightly or wrongly)
> that at the top of the hierarchy was a misogynist who patronises and
> sexually harasses women.
>
> (As always, this is just my opinion.)

I use it because I can do the numerical computations for a given task.
Because it is free software I can work unhindered.  RMS could have been
anybody with any type of personality, I would still use it.  It is not
about any qualms about the behaviour of the people who worked on it.
I could also continue the work even after I change employment status
or stop working with particular groups.

But I have to say that there was tremendous progress during the
first eight years of the Gnu Project, and cost practically nothing.
But the advance since then has not been very great.  Another problem
is that there are not many people working on applications.  In mathematics,
for instance, I did not find people currently in the hacking community who
could contribute much.  Additionally, the work is too advanced even for
mathematicians working at undergraduate level.  Those working at graduate
level customarily restrict the code, because principal investigators
customarily compete with their peers by trampling on others and acting nasty.

In a lot of ways, the free software community works better.  Provided, people
are able to keep their interactions within reason, rather than putting too many
demands on each other.  The original hacking spirit has been eroding through
the years, particularly post-2008.

People should start organising things with RMS, if they want to see how good
then really are in making things better.   Rather than limiting themselves
with hacking,  people should try to organise things together with governmental
bodies in various countries.  Organisers will quickly figure out the real
difficulties that come up, and learn from their mistakes to do a better job.

Remembering my first year, I thought I did my homework and done a great job.
In the end I found out that I blew it.  I was frustrated, completely frustrated.

I had to correct my mistakes.  The next few years, I started to introspect and
emphasise in order to correct my mistakes.  I am still making mistakes and it is difficult.

Regards

Re: GCC association with the FSF

[Pankaj Jangid]

David Brown <david.brown@hesbynett.no> writes:

> So why /do/ people use it?  I suspect that one of the biggest reason is
> "it's the only compiler that will do the job".  For a lot of important
> software, such as Linux kernel, it is gcc or nothing.  Another big
> reason is that gcc comes with their system, which is commonly the case
> for Linux systems.  In the embedded development world (where I work),
> the normal practice for getting a toolchain for a microcontroller is to
> download an IDE and toolchain from the manufacturer - and these days it
> is more often gcc than not.  You use gcc because that is the standard,
> not from choice.
>
> For those that actively /choose/ gcc, why do they do so?  I'd guess
> being convenient, well-known and free (as in beer) come a lot higher
> than the details of the licence, or the difference between "free
> software" and "open source software".  (For me, a major reason is that
> the same compiler supports a wide range of targets.  That, and that gcc
> is technically a better compiler for my needs than any alternatives.)

To summarize, following are the reasons:

1. It compiles complex projects like Linux kernel[1].
2. It comes bundled with system
3. Bundled with IDE toolchains for embedded programming
4. Free (as in beer)
5. Supports wide range of targets
6. GCC is technically better compiler for specific needs

I agree with all of the things. And I agree that a minority of the GCC
users and developers care about “Free Software” (as in freedom). What I
want to emphasize is that, once LLVM catches up on the above 6 points,
it will be only those who care about “freedom” that will stick to the
project.

[Ref]
1. https://www.kernel.org/doc/html/latest/kbuild/llvm.html

Re: GCC association with the FSF

[Giacomo Tesio]

No, David, 

On April 8, 2021 3:00:57 PM UTC, David Brown <david@westcontrol.com> wrote:

>  (And yes, I mean FOSS here, not just free software.)

you are not talking about Free Software, but Open Source.

FOSS, as a term, has been very successful to spread confusion.


> his attitudes and behaviour are not acceptable by
> modern standards and are discouraging to developers and users in the
> FOSS community.

In fact, I'm actively looking for alternatives to GCC (and LLVM) because I cannot trust a 
GCC anymore and I cannot review each and every change.

I won't contribute my port and in general will suggest people to look for alternatives.


But that's not a problem for you, because you do not actually care about real developers 
and users, just about the US corporations you effectively mentioned and now control 
several GNU projects:

> someone in the public relations
> department at IBM, Google, Facebook, ARM, or other big supporters of
> the project will get the impression ...

As you explained, GCC itself is completelly  controlled by few US corporations with 
strong and long term ties with the US DoD.

For sure, it's a big software. And a big threat to everybody outside the US.


Thanks for coming out.


Giacomo

Re: GCC association with the FSF

[Thomas Rodgers]

On 2021-04-08 10:22, Giacomo Tesio wrote:

> No, David,
> 
> On April 8, 2021 3:00:57 PM UTC, David Brown <david@westcontrol.com> 
> wrote:
> 
>> (And yes, I mean FOSS here, not just free software.)
> 
> you are not talking about Free Software, but Open Source.
> 
> FOSS, as a term, has been very successful to spread confusion.
> 
>> his attitudes and behaviour are not acceptable by
>> modern standards and are discouraging to developers and users in the
>> FOSS community.
> 
> In fact, I'm actively looking for alternatives to GCC (and LLVM) 
> because I cannot trust a
> GCC anymore and I cannot review each and every change.
> 
> I won't contribute my port and in general will suggest people to look 
> for alternatives.
> 

I've had some luck with the compiler offerings from Intel and Microsoft 
and I understand IBM has a compiler, and of course there's Nvidia's 
offerings (formerly PGI).

> But that's not a problem for you, because you do not actually care 
> about real developers
> and users, just about the US corporations you effectively mentioned and 
> now control
> several GNU projects:
> 
>> someone in the public relations
>> department at IBM, Google, Facebook, ARM, or other big supporters of
>> the project will get the impression ...
> 
> As you explained, GCC itself is completelly  controlled by few US 
> corporations with
> strong and long term ties with the US DoD.
> 
> For sure, it's a big software. And a big threat to everybody outside 
> the US.
> 
> Thanks for coming out.
> 
> Giacomo

Re: GCC association with the FSF

[David Brown]

On 08/04/2021 19:22, Giacomo Tesio wrote:
> No, David, 
> 
> On April 8, 2021 3:00:57 PM UTC, David Brown <david@westcontrol.com> wrote:
> 
>>  (And yes, I mean FOSS here, not just free software.)
> 
> you are not talking about Free Software, but Open Source.
> 
> FOSS, as a term, has been very successful to spread confusion.
> 

You have snipped the context.  Let me repeat it:

"""
... no one can
be in doubt that [RMS's] 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.)
"""

For most people that have enough interest in software to be aware of the
concepts of free and/or open source software, lump them together.  That
applies to users and developers.  To the majority of gcc users, they do
not care whether the project refers to itself as "free software" or
"open source software".  They often care that it is easily available at
zero cost (though some pay for it - I and my company have, at times,
bought gcc packages), and they like the fact that all the source code is
available even if they don't look at the source themselves.

But whoever you blame for spreading confusion, or for artificially
creating distinctions that rarely matter (this viewpoint has its
supporters too), the fact remains that the mix-up is real.  In almost
all circumstances, to almost all people, it is all "FOSS".  And the GNU
project, along with Linux, LibreOffice (or still OpenOffice, in most
people's minds), Firefox, and a few other big projects are viewed
together as a group and the opposite of "big company" software such as
MS Windows and Office, Apple software, and Adobe Photoshop (to take some
well-known examples).  The attitudes of GNU leaders have an influence on
all of this, as do other public leader figures such as Linus Torvalds.
Their influence (for good or bad) extends well outside the direct
hierarchy of their official positions within their projects.

> 
>> his attitudes and behaviour are not acceptable by
>> modern standards and are discouraging to developers and users in the
>> FOSS community.
> 
> In fact, I'm actively looking for alternatives to GCC (and LLVM) because I cannot trust a 
> GCC anymore and I cannot review each and every change.
> 

That is your choice, obviously.  I don't agree with your points
expressed in this list so far, but you make your own decisions here.
Call me naïve, but I trust the maintainers of gcc to make good technical
decisions and make changes that improve the compiler suite.

I do think it is entirely possible that - for example - Facebook will
pay an employee to add features to gcc with the specific aim of
improving the efficiency of the code Facebook uses.  I think that would
be entirely reasonable, and I would be quite happy with it - either the
changes will coincidentally improve that is useful to me, or it will do
it no harm.  I think it is /implausible/ that any company would exert an
influence over gcc in order to make it worse for competitors or other
users.  This is an open source project (in addition to being free
software) - it is hard to make hidden changes when all changes are
reviewed and visible to many people.  I don't believe in conspiracy
theories - they require the cooperation of too many people who would
disagree and make a noise.

(Mistakes happen, and attacks from outside occasionally happen in open
source projects, but that's another matter.)

> I won't contribute my port and in general will suggest people to look for alternatives.
> 
> 
> But that's not a problem for you, because you do not actually care about real developers 
> and users, just about the US corporations you effectively mentioned and now control 
> several GNU projects:

No, I have no particular interest in any companies (other than loyalty
to my own company).  I am not an American, nor do I live in America - I
am Scottish and live in Norway.  Not that that matters here.

And yes, I care about the gcc developers and their ability and freedom
to work as they want on the project.  I care about potential new
developers too - and I do not want to see them reject the idea of
working for gcc (or any other project) because they perceive a foul
atmosphere of bullying, sexual harassment or misogyny.  Nor would I want
anyone to avoid contributing to gcc because of perceived bias for or
against any particular country, culture, religion, or any other aspect
of life that has no relevance for code development.

And yes, I care about users - I am one, having used gcc for some 25
years on perhaps a dozen different targets.

I don't think any corporations control any GNU projects (with which I am
familiar) in the sense of deciding what goes into them, who works on
them, what direction they should take, or anything of that sort.  But a
big development project takes resources - it costs a lot of money.  This
usually comes from corporations that have an interest in the project's
success - companies that are big users, or re-sell the software.  This
can take effect in different ways - for gcc, this is done by employing
people and letting them work on gcc.  (As far as I understand it, the
individuals usually make their own choices as to what they will work
on.)  Alternative arrangements include for companies to pay sponsorship
and that money is used to employee developers directly in the project -
that model is certainly used on some projects.  However it is done, if
there is a dramatic situation and a major resource supply stops
suddenly, it is very bad for the project.

> 
>> someone in the public relations
>> department at IBM, Google, Facebook, ARM, or other big supporters of
>> the project will get the impression ...
> 
> As you explained, GCC itself is completelly  controlled by few US corporations with 
> strong and long term ties with the US DoD.

I did not "explain" that at all.  You are free to belief this if you
want (you have already said as much), but please do not imagine for an
instant that I have agreed with or supported that view.

I also do not see in any sense how you can conclude that these companies
have "strong and long term ties" with the US DoD.  They are not weapons
suppliers or military suppliers.  The US DoD, just as every country's
DoD, buys whatever computers, chips, software and services it feels make
sense for its needs.  And these companies sell to whatever customers
want their goods and services, subject to any national or internation
trade restrictions.

I am at a loss to understand how such conspiracy theories are relevant
in the discussion about whether or not it would be best for the gcc
project to be independent of the FSF and GNU.

> 
> For sure, it's a big software. And a big threat to everybody outside the US.
> 

You do realise that Italy is a member of NATO - one of the founding
members?  Like Norway, you are part of a military alliance with the USA.
 If you view the US DoD as a threat, you must also view your own
country's DoD as a threat.

But again, you are connecting dots to form a picture that does not
exist, and assigning undue relevance to thin and indirect relationships.
 David Malcolm (to pick one gcc developer) works for Red Hat, which is
owned by IBM, which has supplied computers to the US DoD.  By no
realistic stretch of the imagination does that mean David's
contributions to gcc are controlled by the US DoD.

> 
> Thanks for coming out.
> 

I am truly sorry that you have got such a twisted impression and
misunderstanding of what I wrote, and apparently also what others here
have written.  I hope you can learn to trust other people more and take
their word at face value, instead of seeing conspiracies and hidden
meanings behind everything.

David


> 
> Giacomo
> 

Re: GCC association with the FSF

[Alfred M. Szmidt]

   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.

Then it would not longer be GCC.  It would be something different.
The whole point of GCC is to provide a free software compiler for the
GNU system and systems based on GNU, and not to be pragmatic at the
cost of software freedom.  Commercial interessts are often at odds
with software freedom as well.  This is one of the many reasons why
the GNU project is entierly volunteer based.

But I'd hope that we can avoid words like "fanaticism", "childish",
"cultish" simply because of disagreement in philosophies or continuing
to spread obvious misunderstandings of what someone wrote, it is not
constructive and only causes unnsesescary agitation.

Re: GCC association with the FSF

[David Brown]

On 11/04/2021 15:39, Alfred M. Szmidt wrote:
>    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.
> 
> Then it would not longer be GCC.  It would be something different.
> The whole point of GCC is to provide a free software compiler for the
> GNU system and systems based on GNU, and not to be pragmatic at the
> cost of software freedom.  Commercial interessts are often at odds
> with software freedom as well.  This is one of the many reasons why
> the GNU project is entierly volunteer based.
> 

It is decades since gcc has been /just/ a free compiler for the GNU
system.  That is still an important role, of course, but the compiler's
use has vastly outgrown that area.  The same applies to most of the GNU
projects.

And while I agree that commercial interests are /sometimes/ at odds with
free software, they are also essential for it - GNU would never have
existed without commercial software, and most or all of its projects
would have languished without commercial interest.  (Look, for example,
at the Hurd project - it is absolutely critical to the concept of having
a complete software system using only free software, but it is of almost
no commercial interest to anyone.  And thus it has had negligible
progress.)

Like it or not, money is essential to the way the world works, and
commercial interests are unavoidable.  You can make them work for you
while keeping the values and ideals you hold dear (such as by having
volunteers for development, with contributions and leadership
appointments being personal, while letting a commercial organisation pay
your wages).  Commercial interests are generally only a problem if you
let them be a problem.

> But I'd hope that we can avoid words like "fanaticism", "childish",
> "cultish" simply because of disagreement in philosophies or continuing
> to spread obvious misunderstandings of what someone wrote, it is not
> constructive and only causes unnsesescary agitation.
> 

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Monday, April 12, 2021 at 2:03 AM
> From: "David Brown" <david@westcontrol.com>
> To: "Alfred M. Szmidt" <ams@gnu.org>, gcc@gcc.gnu.org
> Subject: Re: GCC association with the FSF
>
> On 11/04/2021 15:39, Alfred M. Szmidt wrote:
> >    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.
> >
> > Then it would not longer be GCC.  It would be something different.
> > The whole point of GCC is to provide a free software compiler for the
> > GNU system and systems based on GNU, and not to be pragmatic at the
> > cost of software freedom.  Commercial interessts are often at odds
> > with software freedom as well.  This is one of the many reasons why
> > the GNU project is entierly volunteer based.
> >
>
> It is decades since gcc has been /just/ a free compiler for the GNU
> system.  That is still an important role, of course, but the compiler's
> use has vastly outgrown that area.  The same applies to most of the GNU
> projects.
>
> And while I agree that commercial interests are /sometimes/ at odds with
> free software, they are also essential for it - GNU would never have
> existed without commercial software, and most or all of its projects
> would have languished without commercial interest.

Commercial interests are not at odds, provided some rules are followed

> (Look, for example,
> at the Hurd project - it is absolutely critical to the concept of having
> a complete software system using only free software, but it is of almost
> no commercial interest to anyone.  And thus it has had negligible
> progress.)
>
> Like it or not, money is essential to the way the world works, and
> commercial interests are unavoidable.  You can make them work for you
> while keeping the values and ideals you hold dear (such as by having
> volunteers for development, with contributions and leadership
> appointments being personal, while letting a commercial organisation pay
> your wages).  Commercial interests are generally only a problem if you
> let them be a problem.

As aspirations grow, money is an enabling process.  A tool created to simplify transactions.  And things are evolving so that transactions become digital,
where money in the traditional sense does not exist.  The problem is when money
becomes a goal by itself.

To be successful, we need the cooperation of many forces present in our
surroundings, including our employers or people who do business with us.

> > But I'd hope that we can avoid words like "fanaticism", "childish",
> > "cultish" simply because of disagreement in philosophies or continuing
> > to spread obvious misunderstandings of what someone wrote, it is not
> > constructive and only causes unnsesescary agitation.

Re: GCC association with the FSF

[Richard Kenner]

> Then it would not longer be GCC.  It would be something different.
> The whole point of GCC is to provide a free software compiler for the
> GNU system and systems based on GNU, and not to be pragmatic at the
> cost of software freedom.

Certainly that was its initial intent, but I'd argue that at this
point, the main value of GCC to the Free Software movement is that its
extensive use outside of the GNU system makes people aware of the
movement and of the quality of its software.

> Commercial interessts are often at odds with software freedom as
> well.  This is one of the many reasons why the GNU project is
> entierly volunteer based.

Although that's true, I strongly suspect that the majority of actual
work done on GCC is commercially funded.

> But I'd hope that we can avoid words like "fanaticism", "childish",
> "cultish" simply because of disagreement in philosophies or continuing
> to spread obvious misunderstandings of what someone wrote, it is not
> constructive and only causes unnsesescary agitation.

Agreed!

Re: GCC association with the FSF

[Mark Wielaard]

Hi David,

On Wed, Apr 07, 2021 at 10:04:21AM -0400, David Malcolm wrote:
> On Wed, 2021-04-07 at 00:22 +0200, Mark Wielaard wrote:
> > I admit it isn't looking very good and their last announcement is
> > certainly odd: https://status.fsf.org/notice/3833062
> > 
> > But apparently the board is still meeting this week to discuss and
> > might provide a better statement about the way out of this. So lets
> > give them a couple more days before writing them off completely.
> > 
> > > Is there any incident where FSF being the copyright holder for GCC
> > > has
> > > made a difference?
> > 
> > Yes, at least in my experience it has been helpful that the FSF held
> > copyright of code that had been assigned by various individuals and
> > companies. It allowed the merger of GNU Classpath and libgcj for
> > example. There have been various intances where it was helpful that
> > the FSF could unilatrally adjust the license terms especially when
> > the
> > original contributor couldn't be found or didn't exist (as company)
> > anymore.
> 
> This benefit arises from having a single entity own the copyright in
> the code.  It doesn't necessarily have to be the FSF to gain this
> benefit; it just happens that the FSF currently owns the copyright on
> the code.

Yes, I admit that it doesn't have to be the FSF specifically. But
having a shared copyright pool held by one legal entity has benefits.

> Another, transitional approach might be to find another Free Software
> non-profit and for contributors to start assigning copyright on ongoing
> work to that other non-profit.  That way there would be only two
> copyright holders on the code; if the FSF somehow survives its current
> death-spiral then the other nonprofit could assign copyright back to
> the FSF;  if it doesn't, well, we've already got bigger problems.

Yes, having all new copyrights pooled together so we have just two
copyright holders would provide most of the same benefits. And makes
it easier to deal with the legacy FSF copyrights since there would be
just one legal entity having to deal with them instead of each
individual copyright holder on their own.

If it has to come to this then we could take a look at what the
Conservancy already does for aggregating copyright for their member
projects, the Linux kernel and Debian project:
https://sfconservancy.org/copyleft-compliance/

I like their idea of having a counsel of developers that gets involved
in any action taken on behave of the collective:
https://sfconservancy.org/docs/blank_linux-enforcement-agreement.pdf

> > And it is really helpful that we don't have to ask permission of
> > every
> > individual contributor to be able to create the GCC manual (because
> > the GPL code and GFDL text could otherwise not be combined) but that
> > the FSF can grant an exception to one of the developers to create it.
> 
> Alternatively, the copyright holder could relicense the documentation
> to a license that is explicitly compatible with the GPL, such as the
> GPL itself, and not require us to jump through hoops.  (Or we could
> start a non-GFDL body of documentation under a different copyright
> holder, but I'm not volunteering for that effort).  In case it's not
> clear, I think the GFDL is a terrible license, and that it's always a
> mistake to use it for software documentation.

Yes, I am not clear on why this (relicensing the documentation under
the GPL) hasn't been done yet. Is this something the Steering
Committee could start a discussion on with the FSF?

> > > Are there any GPL violations involving GCC code
> > > that were resolved only because all copyright resides with a single
> > > entity, that couldn't have been resolved on behalf of individual
> > > copyright holders?
> > 
> > I think it has been very helpful preventing those violations. If you
> > only have individual copyright holders instead of an organisation
> > with
> > the means to actually resolve such violations people pay much more
> > attention to play by the rules. See for example the linux kernel
> > project. I believe there are so many GPL violations precisely because
> > almost no individual has the means to take up a case.
> 
> Again, the "single entity" doesn't need to be the FSF.

It doesn't, but it would be convenient if it was possible.  We have to
see what the board does to win the confidence of use GNU hackers back.
They still have to answer the questions we sent them about the GNU/FSF
relationship:
https://gnu.wildebeest.org/blog/mjw/2019/12/27/proposals-for-the-new-gnu-fsf-relationship/
Maybe if the whole board is replaced we can finally have that conversation.

> It's not clear to me to what extent "GNU" is a thing that exists.  I
> agree with much of Andy Wingo's October 2019 blog post:
> http://www.wingolog.org/archives/2019/10/08/thoughts-on-rms-and-gnu
> 
> IMHO, "GNU" can mean various things:
> - the small family of "g"-prefixed toolchain/low-level projects (gcc,
> glibc, gdb) that work together and attend the GNU Tools Cauldron
> - anything hosted under the gnu.org domain (including this mailing
> list)
> - things that have been blessed by RMS with the "GNU" title for
> adhering to his own terms of ideological correctness
> - an attempt to reimplement what in the 1980s passed for state-of-the-
> art
> - an idea, or vision, either political, or technological, or some blend
> of both
> - an expansive definition for whenever RMS wants to claim that other
> people's work is somehow "GNU/Linux"
> - various other definitions, I'm sure

To me GNU is people wanting to create a software system that respects
users freedom according to the GNU Social Contract:
https://wiki.gnu.tools/gnu:social-contract

> > I hope GCC stays part of GNU, but that we might reconsider whether it
> > is in the best interest of GNU and GCC as Free Software project to
> > still be associated with the FSF. The GNU Assembly is having a
> > similar
> > discussion right now
> > https://lists.gnu.tools/postorius/lists/assembly.lists.gnu.tools/
> 
> 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.

Agreed,

Mark

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Friday, April 09, 2021 at 7:48 AM
> From: "Mark Wielaard" <mark@klomp.org>
> To: "David Malcolm" <dmalcolm@redhat.com>
> Cc: "GCC Development" <gcc@gcc.gnu.org>
> Subject: Re: GCC association with the FSF
>
> Hi David,
>
> On Wed, Apr 07, 2021 at 10:04:21AM -0400, David Malcolm wrote:
> > On Wed, 2021-04-07 at 00:22 +0200, Mark Wielaard wrote:
> > > I admit it isn't looking very good and their last announcement is
> > > certainly odd: https://status.fsf.org/notice/3833062
> > >
> > > But apparently the board is still meeting this week to discuss and
> > > might provide a better statement about the way out of this. So lets
> > > give them a couple more days before writing them off completely.
> > >
> > > > Is there any incident where FSF being the copyright holder for GCC
> > > > has
> > > > made a difference?
> > >
> > > Yes, at least in my experience it has been helpful that the FSF held
> > > copyright of code that had been assigned by various individuals and
> > > companies. It allowed the merger of GNU Classpath and libgcj for
> > > example. There have been various intances where it was helpful that
> > > the FSF could unilatrally adjust the license terms especially when
> > > the
> > > original contributor couldn't be found or didn't exist (as company)
> > > anymore.
> >
> > This benefit arises from having a single entity own the copyright in
> > the code.  It doesn't necessarily have to be the FSF to gain this
> > benefit; it just happens that the FSF currently owns the copyright on
> > the code.
>
> Yes, I admit that it doesn't have to be the FSF specifically. But
> having a shared copyright pool held by one legal entity has benefits.
>
> > Another, transitional approach might be to find another Free Software
> > non-profit and for contributors to start assigning copyright on ongoing
> > work to that other non-profit.  That way there would be only two
> > copyright holders on the code; if the FSF somehow survives its current
> > death-spiral then the other nonprofit could assign copyright back to
> > the FSF;  if it doesn't, well, we've already got bigger problems.
>
> Yes, having all new copyrights pooled together so we have just two
> copyright holders would provide most of the same benefits. And makes
> it easier to deal with the legacy FSF copyrights since there would be
> just one legal entity having to deal with them instead of each
> individual copyright holder on their own.
>
> If it has to come to this then we could take a look at what the
> Conservancy already does for aggregating copyright for their member
> projects, the Linux kernel and Debian project:
> https://sfconservancy.org/copyleft-compliance/
>
> I like their idea of having a counsel of developers that gets involved
> in any action taken on behave of the collective:
> https://sfconservancy.org/docs/blank_linux-enforcement-agreement.pdf
>
> > > And it is really helpful that we don't have to ask permission of
> > > every
> > > individual contributor to be able to create the GCC manual (because
> > > the GPL code and GFDL text could otherwise not be combined) but that
> > > the FSF can grant an exception to one of the developers to create it.
> >
> > Alternatively, the copyright holder could relicense the documentation
> > to a license that is explicitly compatible with the GPL, such as the
> > GPL itself, and not require us to jump through hoops.  (Or we could
> > start a non-GFDL body of documentation under a different copyright
> > holder, but I'm not volunteering for that effort).  In case it's not
> > clear, I think the GFDL is a terrible license, and that it's always a
> > mistake to use it for software documentation.
>
> Yes, I am not clear on why this (relicensing the documentation under
> the GPL) hasn't been done yet. Is this something the Steering
> Committee could start a discussion on with the FSF?
>
> > > > Are there any GPL violations involving GCC code
> > > > that were resolved only because all copyright resides with a single
> > > > entity, that couldn't have been resolved on behalf of individual
> > > > copyright holders?
> > >
> > > I think it has been very helpful preventing those violations. If you
> > > only have individual copyright holders instead of an organisation
> > > with
> > > the means to actually resolve such violations people pay much more
> > > attention to play by the rules. See for example the linux kernel
> > > project. I believe there are so many GPL violations precisely because
> > > almost no individual has the means to take up a case.
> >
> > Again, the "single entity" doesn't need to be the FSF.
>
> It doesn't, but it would be convenient if it was possible.  We have to
> see what the board does to win the confidence of use GNU hackers back.
> They still have to answer the questions we sent them about the GNU/FSF
> relationship:
> https://gnu.wildebeest.org/blog/mjw/2019/12/27/proposals-for-the-new-gnu-fsf-relationship/
> Maybe if the whole board is replaced we can finally have that conversation.
>
> > It's not clear to me to what extent "GNU" is a thing that exists.  I
> > agree with much of Andy Wingo's October 2019 blog post:
> > http://www.wingolog.org/archives/2019/10/08/thoughts-on-rms-and-gnu
> >
> > IMHO, "GNU" can mean various things:
> > - the small family of "g"-prefixed toolchain/low-level projects (gcc,
> > glibc, gdb) that work together and attend the GNU Tools Cauldron
> > - anything hosted under the gnu.org domain (including this mailing
> > list)
> > - things that have been blessed by RMS with the "GNU" title for
> > adhering to his own terms of ideological correctness
> > - an attempt to reimplement what in the 1980s passed for state-of-the-
> > art
> > - an idea, or vision, either political, or technological, or some blend
> > of both
> > - an expansive definition for whenever RMS wants to claim that other
> > people's work is somehow "GNU/Linux"
> > - various other definitions, I'm sure
>
> To me GNU is people wanting to create a software system that respects
> users freedom according to the GNU Social Contract:
> https://wiki.gnu.tools/gnu:social-contract

Gnu is a project started by Richard Stallman with the aim of making
a software system that respects the freedom of its users.  We don't know
what will happen after.  Someone else might start a new project and use
Gnu tools.  You can only have a claim on things one starts, and Gnu
is not something you started.

There could be many boards that get set up through the years, but nobody can
guarantee how things turn out to be.  At Stanford, a study revealed that 87%
believed they were better than their peers.  It is- evident than many in the
community that have ganged up against Richard think they can do better.  But
they won't!

> > > I hope GCC stays part of GNU, but that we might reconsider whether it
> > > is in the best interest of GNU and GCC as Free Software project to
> > > still be associated with the FSF. The GNU Assembly is having a
> > > similar
> > > discussion right now
> > > https://lists.gnu.tools/postorius/lists/assembly.lists.gnu.tools/
> >
> > 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.

Richard is not self-appointed.  But he decided to make the Gnu Project public.
You are entitled to compete with him and see where you get.

Because he is on the board, he set himself up for some pretty uncomfortable
meetings.  Now we are starting to see the trend where his input could
either be ignored or worse.

Mark, go concentrate on something new, in which there are a myriad of things
you actually can control.  Even without Stallman, it does not mean that
you can then run roughshod over others, because there are many of us
who will not sit around for your convenience.

> Agreed,
>
> Mark
>

Re: GCC association with the FSF

[Alfred M. Szmidt]

These discussions are slightly off topic for gcc@, I'd suggest they
are moved to gnu-misc-discuss@ or some other more suitable list.

   To me GNU is people wanting to create a software system that respects
   users freedom according to the GNU Social Contract:
   https://wiki.gnu.tools/gnu:social-contract

This is your own personal web site, and does not describe the GNU
project nor host any documents related to it.  The GNU project doesn't
have a "social contract", nor does it require anyone to sign or agree
to such a document to contribute, or take on the task of being a GNU
maintainer.  If you want to read about what the GNU project is, how it
runs, and other such interesting tid bits: http://www.gnu.org

Re: GCC association with the FSF

[Paul Koning]

> On Apr 9, 2021, at 2:27 AM, Alfred M. Szmidt via Gcc <gcc@gcc.gnu.org> wrote:
> 
> These discussions are slightly off topic for gcc@, I'd suggest they
> are moved to gnu-misc-discuss@ or some other more suitable list.

More than "slightly", in my view.  I'm close to putting this thread into my "send straight to trash" mail rule.  The alternative would be to unsubscribe gcc, which it would be nice to avoid.

	paul

Re: GCC association with the FSF

[Jonathan Wakely]

On Fri, 9 Apr 2021 at 07:30, Alfred M. Szmidt wrote:
>
> These discussions are slightly off topic for gcc@, I'd suggest they
> are moved to gnu-misc-discuss@ or some other more suitable list.

That list is precisely the toxic cesspit that makes me want to have
nothing more to do with GNU, ever.

My current expectation is that after the GCC 11 release my
contributions to GCC will be pushed to a Git repo somewhere other than
gcc.gnu.org and I will not be assigning copyright to FSF. I'm done
with this cult and those who think they have any influence on GCC,
just because of a historical association with GNU.

Re: GCC association with the FSF

[Richard Sandiford]

[ Like many others who have posted to this thread, I've contributed
  to GCC at various times as a hobby and at other times as a paid
  employee.  Here I'm speaking as a personal contributor, not on
  behalf of my current employer. ]

I think it's misleading to talk about GCC “leaving” or “disassociating
itself” from the FSF or from the GNU project.  No-one can force the FSF or
the GNU project to drop GCC (and I don't think anyone's trying to make it
do that).  I think what we're really talking about is whether there should
be a fork.  In some ways that would be like egcs, although perhaps this time
it would be a clean break, without intending the fork to “rejoin” GNU later.

If the fork takes the current gcc.gnu.org infrastructure with it,
the GNU project would have to maintain its version of GCC elsewhere.
But that would be a minor barrier at most.  The likelihood is that there
would be two versions of GCC, which for want of better terms I'll call
“FSF GCC” and “new GCC”.  If FSF GCC does continue as a project in any
meaningful sense, new GCC would be able to cherry-pick useful contributions
from FSF GCC.  Cherry-picking in the opposite direction would also be
technically and legally possible, but would presumably be rejected on
principle by whoever the new FSF GCC maintainers turn out to be (not least
because “new GCC” commits would not be FSF copyright).

This should also satisfy those who believe that only an FSF-copyright
GCC is trustworthy.  People who only trust the FSF can contribute to
and use “FSF GCC” and ignore “new GCC”.

So I think the question becomes: how many GCC developers and organisations
are willing to agree to follow the fork rather than stick with FSF GCC?
Does anyone have any suggestions for a good procedure for testing the
level of support?  I don't think this mailing list is it.

(It's ironic that the process of answering that question shows how
misplaced a lot of the comments about the SC were.  GCC is fundamentally
a developer/contributor-led project, so even an important decision like
this will be made by developers/contributors rather than the SC.)

FWIW, again speaking personally, I would be in favour of joining a fork.[*]

Mark Wielaard <mark@klomp.org> writes:
> On Wed, Apr 07, 2021 at 10:04:21AM -0400, David Malcolm wrote:
> > Another, transitional approach might be to find another Free Software
> > non-profit and for contributors to start assigning copyright on ongoing
> > work to that other non-profit.  That way there would be only two
> > copyright holders on the code; if the FSF somehow survives its current
> > death-spiral then the other nonprofit could assign copyright back to
> > the FSF;  if it doesn't, well, we've already got bigger problems.
>
> Yes, having all new copyrights pooled together so we have just two
> copyright holders would provide most of the same benefits. And makes
> it easier to deal with the legacy FSF copyrights since there would be
> just one legal entity having to deal with them instead of each
> individual copyright holder on their own.

It sounds like it could be the worst of both worlds in some ways though.
There would no longer be a single entity that could relicense the code,
if that became necessary for any reason, yet we would still require all
contributors to go through the off-putting process of assigning copyright.

I think it would be better to have voluntary aggregation of copyright
(for those in a position to offer it) while also allowing contributors
to retain copyright if they prefer.  If enough regular contributors
agree to pool copyright then that should be enough.

> If it has to come to this then we could take a look at what the
> Conservancy already does for aggregating copyright for their member
> projects, the Linux kernel and Debian project:
> https://sfconservancy.org/copyleft-compliance/
>
> I like their idea of having a counsel of developers that gets involved
> in any action taken on behave of the collective:
> https://sfconservancy.org/docs/blank_linux-enforcement-agreement.pdf

I'm not familiar with this system, but yeah, I agree that it looks on the
face of it like a good approach, provided that it's strictly voluntary.

Thanks,
Richard


[*] Not that anyone should care or is likely to care, but for the record,
    my reasons are:

    The FSF and the GNU project have had a key historical role in developing
    and promoting free software as a concept.  But history is one thing and
    the future is another.  Due to the success of the early advocacy work,
    free software now exists as a principle independently of the FSF and
    the GNU project.  And the FSF has provided copyleft licenses that have
    stood the test of time.  So like others have said, the question for
    the future is: do we as contributors gain anything by having any new
    work we do be owned by the FSF and associated with the GNU project?

    I think the recent developments, as well as the messages in this
    email thread that supposedly give reasons for sticking with GNU,
    have shown what a tarnished brand the GNU project has become.
    Like others have said, it's hard to escape the feeling that it's as
    much about the cult of the founder as it is about the principle of
    free software.  And I think the thread has also shown that even
    people very familiar with the FSF and GNU project fundamentally
    misunderstand how GCC development currently works and how closely
    tied to the GNU project current GCC development really is.  I think
    a fork would help to clarify the situation.

    There's undeniably a close tie between GCC and sibling projects in
    the “GNU toolchain”: glibc, binutils and gdb.  But those GNU projects
    are all in the sourceware.org stable and could in principle fork at
    the same time.  In the 20+ years I've been working on the project,
    there has been at most a very loose link between GCC and other parts
    of the GNU project besides those three.

    So having the name “GNU” attached to GCC development in the last 20
    years or so has felt a bit like having the Union flag in the upper
    left corner of the Australian flag.  It reflects an important part
    of the project's history, but it's not necessarily an important part
    of what the project is today.  Life working on a GCC fork should be
    very much like the status quo, just without the increasingly toxic
    association.

Re: GCC association with the FSF

[Jonathan Wakely]

On Sun, 11 Apr 2021, 15:26 Richard Sandiford via Gcc, <gcc@gcc.gnu.org>
wrote:

>
>
> I think it's misleading to talk about GCC “leaving” or “disassociating
> itself” from the FSF or from the GNU project.  No-one can force the FSF or
> the GNU project to drop GCC (and I don't think anyone's trying to make it
> do that).  I think what we're really talking about is whether there should
> be a fork.


There doesn't *have* to be a fork. If GCC walked away from GNU, the GNU
system could continue to use GCC with no actual input to it, just like it
uses the Linux kernel (except for a statistically insignificant number of
GNU/Hurd systems). I have no objection to the FSF using my GCC work (they
are free to do so, like all users are, thanks to the excellent GPL). But I
no longer want to be required to give them the copyright or ownership of
that work.

But for various reasons being passive consumers of a non-FSF GCC probably
wouldn't be popular, so a fork may be for the best.



>
> FWIW, again speaking personally, I would be in favour of joining a fork.[*]
>

Glad to hear it :-)

I will be forking, alone if necessary, but I've already been told by a few
people I won't be alone.

Re: GCC association with the FSF

[David Brown]

On 11/04/2021 17:06, Jonathan Wakely via Gcc wrote:
> On Sun, 11 Apr 2021, 15:26 Richard Sandiford via Gcc, <gcc@gcc.gnu.org>

>>
>> FWIW, again speaking personally, I would be in favour of joining a fork.[*]
>>
> 
> Glad to hear it :-)
> 
> I will be forking, alone if necessary, but I've already been told by a few
> people I won't be alone.
> 

The big problem with a fork, rather than an amiable split (where FSF/GNU
accepts that gcc wants to be a separate project) is the name.  If the
FSF keep their own "gcc" project, then calling the new fork "gcc" as
well would cause confusion.  And calling it something else would also
confuse people - many would use the FSF gcc because of its name, not
realising that there is a better fork.  You can see that in the
OpenOffice / LibreOffice split - I think a large proportion of people
downloading OpenOffice do so without realising that LibreOffice exists
and is way ahead of it on features.

A fork may be unavoidable in the end, but a more diplomatic change of
structure would have many advantages if it can be achieved.

Re: GCC association with the FSF

[Jonathan Wakely]

On Sun, 11 Apr 2021, 16:56 David Brown, wrote:

>
> The big problem with a fork, rather than an amiable split (where FSF/GNU
> accepts that gcc wants to be a separate project) is the name.  If the
> FSF keep their own "gcc" project, then calling the new fork "gcc" as
> well would cause confusion.


Packagers for Linux distros and BSD ports collections (and similar like
MinGW distros) are unlikely to be confused for long.

The GNU project can have the "GNU C Compiler" name, as far as I'm
concerned. The "GNU Compiler Collection" name dates from the time when EGCS
replaced the original GCC so I would argue that the FSF couldn't claim
ownership of a new twist on it like "GCC Compiler Collection".

And Apple already got away with shipping clang as the "gcc" and "g++"
executables (albeit causing much confusion) so even if the project changed
name, the shipped products wouldn't need to.

Your point is valid, but I've been thinking about the practicalities a lot.
I still think losing the gcc.gnu.org DNS records would be the biggest
drawback.


  And calling it something else would also
> confuse people - many would use the FSF gcc because of its name, not
> realising that there is a better fork.  You can see that in the
> OpenOffice / LibreOffice split - I think a large proportion of people
> downloading OpenOffice do so without realising that LibreOffice exists
> and is way ahead of it on features.
>

Only a small minority download GCC (we don't provide binaries for a start,
so most people use the binary package from their OS, or a semi-automated
build like portage or MacPorts).

So I'm not terribly concerned about that problem.


> A fork may be unavoidable in the end, but a more diplomatic change of
> structure would have many advantages if it can be achieved.
>

I would be very happy if the FSF took that view and let us walk away. If
not, I don't think it's a huge problem.

Re: GCC association with the FSF

[Richard Biener]

On Sun, Apr 11, 2021 at 7:22 PM Jonathan Wakely via Gcc <gcc@gcc.gnu.org> wrote:
>
> On Sun, 11 Apr 2021, 16:56 David Brown, wrote:
>
> >
> > The big problem with a fork, rather than an amiable split (where FSF/GNU
> > accepts that gcc wants to be a separate project) is the name.  If the
> > FSF keep their own "gcc" project, then calling the new fork "gcc" as
> > well would cause confusion.
>
>
> Packagers for Linux distros and BSD ports collections (and similar like
> MinGW distros) are unlikely to be confused for long.
>
> The GNU project can have the "GNU C Compiler" name, as far as I'm
> concerned. The "GNU Compiler Collection" name dates from the time when EGCS
> replaced the original GCC so I would argue that the FSF couldn't claim
> ownership of a new twist on it like "GCC Compiler Collection".
>
> And Apple already got away with shipping clang as the "gcc" and "g++"
> executables (albeit causing much confusion) so even if the project changed
> name, the shipped products wouldn't need to.
>
> Your point is valid, but I've been thinking about the practicalities a lot.
> I still think losing the gcc.gnu.org DNS records would be the biggest
> drawback.
>
>
>   And calling it something else would also
> > confuse people - many would use the FSF gcc because of its name, not
> > realising that there is a better fork.  You can see that in the
> > OpenOffice / LibreOffice split - I think a large proportion of people
> > downloading OpenOffice do so without realising that LibreOffice exists
> > and is way ahead of it on features.
> >
>
> Only a small minority download GCC (we don't provide binaries for a start,
> so most people use the binary package from their OS, or a semi-automated
> build like portage or MacPorts).
>
> So I'm not terribly concerned about that problem.
>
>
> > A fork may be unavoidable in the end, but a more diplomatic change of
> > structure would have many advantages if it can be achieved.
> >
>
> I would be very happy if the FSF took that view and let us walk away. If
> not, I don't think it's a huge problem.

Please people take a step back and let things cool down.  While GCC
might have little benefit from being associated with the FSF or GNU
(I haven't made up my own mind on this yet) the benefits from
disassociating itself from the FSF (or GNU) has just as many
(little) benefits on its own as it has (possible) downsides.

Certainly this whole discussion makes neither the GCC nor the
FSF/GNU side appear in any positive way.

Please concentrate on the important things, we're supposed to get a
release of GCC 11 out of the door.

Thanks,
Richard.

Re: GCC association with the FSF

[Thomas Koenig]

On 12.04.21 11:32, Richard Biener via Gcc wrote:

> Please concentrate on the important things, we're supposed to get a
> release of GCC 11 out of the door.

Amen.

Re: GCC association with the FSF

[Nathan Sidwell]

On 4/12/21 5:32 AM, Richard Biener via Gcc wrote:

> 
> Please concentrate on the important things, we're supposed to get a
> release of GCC 11 out of the door.

Then it is important this is resolved.

nathan

-- 
Nathan Sidwell

Re: GCC association with the FSF

[Richard Biener]

On Mon, Apr 12, 2021 at 11:24 PM Nathan Sidwell <nathan@acm.org> wrote:
>
> On 4/12/21 5:32 AM, Richard Biener via Gcc wrote:
>
> >
> > Please concentrate on the important things, we're supposed to get a
> > release of GCC 11 out of the door.
>
> Then it is important this is resolved.

Maybe - but it is very apparent that the current "discussion" will lead nowhere.

Richard.

> nathan
>
> --
> Nathan Sidwell

Re: GCC association with the FSF

[Jeff Law]

On 4/13/2021 12:01 AM, Richard Biener via Gcc wrote:
> On Mon, Apr 12, 2021 at 11:24 PM Nathan Sidwell <nathan@acm.org> wrote:
>> On 4/12/21 5:32 AM, Richard Biener via Gcc wrote:
>>
>>> Please concentrate on the important things, we're supposed to get a
>>> release of GCC 11 out of the door.
>> Then it is important this is resolved.
> Maybe - but it is very apparent that the current "discussion" will lead nowhere.

I would disagree with that Richi.  While there are elements in this 
discussion that are unhelpful, the overall question about GCC 
association with the FSF and GNU is a good one to be working through.


An EGCS-like split like we had in the late 90s is, IMHO, a definite 
possibility here and judging the mood of the GCC development community 
is vital to guiding decisions we need to make as a project.

Jeff





.  Without strong support from the development community splits like 
that aren't likely to be successful.  And to be clear, what *I* will be 
looking at is how those doing the real work respond, not the ramblings 
of folks who

Re: GCC association with the FSF

[Thomas Koenig]

On 13.04.21 16:40, Jeff Law via Gcc wrote:
> An EGCS-like split like we had in the late 90s is, IMHO, a definite 
> possibility here

Such a move would, in all probability, leave both parts of the split
GCC with too few developers to compete against LLVM, thus rendering
GCC irrelevant and ruining an important project for free software.

(I don't like the idea, for the record).

Re: GCC association with the FSF

[Jeff Law]

On 4/13/2021 10:52 AM, Thomas Koenig wrote:
> On 13.04.21 16:40, Jeff Law via Gcc wrote:
>> An EGCS-like split like we had in the late 90s is, IMHO, a definite 
>> possibility here
>
> Such a move would, in all probability, leave both parts of the split
> GCC with too few developers to compete against LLVM, thus rendering
> GCC irrelevant and ruining an important project for free software.
>
> (I don't like the idea, for the record).

I'm not sure there'll be that much of a community split.  Based on what 
I've seen *so far* it'd be less of a split than we had with EGCS.  But 
that's precisely why I want folks to chime in, particularly those doing 
the day-to-date development work -- I want to see what the likely impact 
on the development community would be rather than going with just what 
*I* want.


jeff

Re: GCC association with the FSF

[Thomas Koenig]

On 13.04.21 19:19, Jeff Law via Gcc wrote:
> I'm not sure there'll be that much of a community split.  Based on what 
> I've seen *so far* it'd be less of a split than we had with EGCS.  But 
> that's precisely why I want folks to chime in, particularly those doing 
> the day-to-date development work -- I want to see what the likely impact 
> on the development community would be rather than going with just what 
> *I* want.

If such a split were to occur, it would probably cost you gfortran.
We're in a precarious situation as is.

So, goodbye to SPEC for both branches in the medium term.

Re: GCC association with the FSF

[Jeff Law]

On 4/13/2021 11:32 AM, Thomas Koenig via Gcc wrote:
>
> On 13.04.21 19:19, Jeff Law via Gcc wrote:
>> I'm not sure there'll be that much of a community split.  Based on 
>> what I've seen *so far* it'd be less of a split than we had with 
>> EGCS.  But that's precisely why I want folks to chime in, 
>> particularly those doing the day-to-date development work -- I want 
>> to see what the likely impact on the development community would be 
>> rather than going with just what *I* want.
>
> If such a split were to occur, it would probably cost you gfortran.
> We're in a precarious situation as is.

Hmm, I'm not following gfortran closely.  Is there a reason to believe 
that the gfortran developers would split across the two projects?  If 
so, that's a significant issue.  If you've got a pointer to a 
discussion, I'm happy to take it and read up on things.


>
> So, goodbye to SPEC for both branches in the medium term.

That depends, of course.


Jeff

Re: GCC association with the FSF

[Thomas Koenig]

On 14.04.21 01:41, Jeff Law wrote:
> 
> On 4/13/2021 11:32 AM, Thomas Koenig via Gcc wrote:
>>
>> On 13.04.21 19:19, Jeff Law via Gcc wrote:
>>> I'm not sure there'll be that much of a community split.  Based on 
>>> what I've seen *so far* it'd be less of a split than we had with 
>>> EGCS.  But that's precisely why I want folks to chime in, 
>>> particularly those doing the day-to-date development work -- I want 
>>> to see what the likely impact on the development community would be 
>>> rather than going with just what *I* want.
>>
>> If such a split were to occur, it would probably cost you gfortran.
>> We're in a precarious situation as is.
> 
> Hmm, I'm not following gfortran closely.  Is there a reason to believe 
> that the gfortran developers would split across the two projects? 

There is no discussion at the moment. Most people on the fortran
mailing list do not follow gcc.  I know of at least two contributors
(myself incluced) who would in all probability stop contributing
in that case.  But then again, I'm only the currently active contributor
with the longest service history (since 2005), so my contribution
may not matter much.

You can, of course, raise the issue on the gfortran mailing list.
This will poison it with the same discussion that has poisoned the gcc
mailing list.  There is an even chance that this will lead people
to stop contributing already.

> If 
> so, that's a significant issue.  If you've got a pointer to a 
> discussion, I'm happy to take it and read up on things.

Well, just raise the issue.  I will, in that case, I will certainly
add my opinion.

Re: GCC association with the FSF

[Jonathan Wakely]

On Wed, 14 Apr 2021 at 08:46, Thomas Koenig via Gcc <gcc@gcc.gnu.org> wrote:
> There is no discussion at the moment. Most people on the fortran
> mailing list do not follow gcc.  I know of at least two contributors
> (myself incluced) who would in all probability stop contributing
> in that case.

Do you mind if I ask why?

(I totally understand that you'd rather not have this topic spill over
onto the gfortran list, so I'm only asking why you'd stop contributing
if there were two active forks of GCC, not anybody else).

Re: GCC association with the FSF

[Thomas Koenig]

On 14.04.21 09:57, Jonathan Wakely wrote:
> On Wed, 14 Apr 2021 at 08:46, Thomas Koenig via Gcc <gcc@gcc.gnu.org> wrote:
>> There is no discussion at the moment. Most people on the fortran
>> mailing list do not follow gcc.  I know of at least two contributors
>> (myself incluced) who would in all probability stop contributing
>> in that case.
> 
> Do you mind if I ask why?
> 
> (I totally understand that you'd rather not have this topic spill over
> onto the gfortran list, so I'm only asking why you'd stop contributing
> if there were two active forks of GCC, not anybody else).

Because I am not willing to donate my time and effort for a doomed
project, and if that split happens, I consider gfortran doomed
for good.

Let's look at

- All gfortran developers stay on the FSF branch.
   Bug fixing goes on as usual, the other branch picks up whatever
   it wants.  This I could see as working, sort
   of.  If the FSF and the other branch diverge in their middle
   end interface, or if the other branch decides not to port something,
   this is bit rot that the maintainers of the other branch
   would have to deal with.  So, gfortran bitrots on the new
   branch, basically.  The question then is if the FSF branch
   will still be the relevant one the future.  If not, gfortran
   will then die a lingering death.

- gfortran developers try to work on both branches, or have
   one primary branch and one other branch.  Dealing with two
   versions is far too much for our resources, we can hardly
   keep up with one.  This is a recipe for disaster, and
   I will not spend my volunteer time on this.

- Some gfortran developers decide to move to the other branch,
   cross-porting fixes if necessary.  This will also lead
   to fewer resources of a project that has already too few,
   and is not sustainable.

- All gfortran developers move to the new branch.  This will not
   happen, I can guarantee you that.

- Somebody decides that hiring a couple of professional programmers
   working full-time keeping the project alive on both sides.
   That has not happened in decades (gfortran has always been
   mostly volunteer-driven), and I consider that extremely
   unlikely.

So, let me modify my statement: It only makes sense for me to
continue working on gfortran if the branch fails.  In that case,
the maxim usually employed by pharmaceutical R&D applies:
"Fail early, fail cheap", and the cheapest way to fail is
never to start.

Re: GCC association with the FSF

[Jonathan Wakely]

N.B. Jeff is no longer @redhat.com so I've changed the CC

On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de> wrote:
> - All gfortran developers move to the new branch.  This will not
>    happen, I can guarantee you that.

This is the part I'm curious about (the rest is obvious, it follows
from there being finite resources and the nature of any fork). But I'm
not going to press for reasons.

Re: GCC association with the FSF

[Richard Biener]

On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc <gcc@gcc.gnu.org> wrote:
>N.B. Jeff is no longer @redhat.com so I've changed the CC
>
>On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
>wrote:
>> - All gfortran developers move to the new branch.  This will not
>>    happen, I can guarantee you that.
>
>This is the part I'm curious about (the rest is obvious, it follows
>from there being finite resources and the nature of any fork). But I'm
>not going to press for reasons.

Note the only viable fork will be on the current hosting (which isn't FSF controlled) with the downside of eventually losing the gcc.gnu.org DNS and thus a need to "switch" to a sourceware.org name. 

Given there would be actual work involved on the FSF side to keep a "fork" with the exact same setup (and thus transparent with existing setups) I don't see it keeping live (but I see somebody populating savannah with sources). 

Richard. 

Richard. 

Re: GCC association with the FSF

[Jeff Law]

On 4/14/2021 6:08 AM, Richard Biener via Gcc wrote:
> On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc <gcc@gcc.gnu.org> wrote:
>> N.B. Jeff is no longer @redhat.com so I've changed the CC
>>
>> On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
>> wrote:
>>> - All gfortran developers move to the new branch.  This will not
>>>     happen, I can guarantee you that.
>> This is the part I'm curious about (the rest is obvious, it follows
> >from there being finite resources and the nature of any fork). But I'm
>> not going to press for reasons.
> Note the only viable fork will be on the current hosting (which isn't FSF controlled) with the downside of eventually losing the gcc.gnu.org DNS and thus a need to "switch" to a sourceware.org name.
I strongly suspect you're right here.  Ultimately if one fork reaches 
critical mass, then it survives and the other dies.  That's a function 
of the developer community.   Right now I don't see the nightmare 
scenario of both forks being viable playing out -- however I'm more 
concerned now than I was before due Thomas's comments.


>
> Given there would be actual work involved on the FSF side to keep a "fork" with the exact same setup (and thus transparent with existing setups) I don't see it keeping live (but I see somebody populating savannah with sources).

Absolutely.  I could even see a small community continuing to push the 
FSF fork for a while until it becomes abundantly clear that only one 
fork is long term viable.  That's what happened with EGCS -- the 
majority of the developer community went with the EGCS fork with a small 
community staying on the FSF fork.  Eventually it became clear that EGCS 
had much broader developer support and the FSF fork ultimately withered 
away.


Jeff

Re: GCC association with the FSF

[Toon Moene]

On 4/14/21 6:18 PM, Jeff Law via Gcc wrote:

> On 4/14/2021 6:08 AM, Richard Biener via Gcc wrote:

>> On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc 
>> <gcc@gcc.gnu.org> wrote:

>>> N.B. Jeff is no longer @redhat.com so I've changed the CC

>>> On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
>>> wrote:

>>>> - All gfortran developers move to the new branch.  This will not
>>>>     happen, I can guarantee you that.

>>> This is the part I'm curious about (the rest is obvious, it follows
>> >from there being finite resources and the nature of any fork). But I'm
>>> not going to press for reasons.

>> Note the only viable fork will be on the current hosting (which isn't 
>> FSF controlled) with the downside of eventually losing the gcc.gnu.org 
>> DNS and thus a need to "switch" to a sourceware.org name.

> I strongly suspect you're right here.  Ultimately if one fork reaches 
> critical mass, then it survives and the other dies.  That's a function 
> of the developer community.   Right now I don't see the nightmare 
> scenario of both forks being viable playing out -- however I'm more 
> concerned now than I was before due Thomas's comments.

When plans for the EGCS were underway, and the (then) Fortran supporters 
were into the plans, it scared the hell out of me, because it was 
completely unclear to me where it would end.

But in the end: I am a supporter of Free Software, not a organization, 
or a person, but *developers* who support Free Software.

That's what got me to go for the fork of EGCS - and I have not been 
disappointed.

-- 
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Thursday, April 15, 2021 at 4:35 AM
> From: "Toon Moene" <toon@moene.org>
> To: "Jeff Law" <jeffreyalaw@gmail.com>, "Richard Biener" <richard.guenther@gmail.com>, "Jonathan Wakely" <jwakely.gcc@gmail.com>, "Jonathan Wakely via Gcc" <gcc@gcc.gnu.org>, "Thomas Koenig" <tkoenig@netcologne.de>
> Subject: Re: GCC association with the FSF
>
> On 4/14/21 6:18 PM, Jeff Law via Gcc wrote:
> 
> > On 4/14/2021 6:08 AM, Richard Biener via Gcc wrote:
> 
> >> On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc 
> >> <gcc@gcc.gnu.org> wrote:
> 
> >>> N.B. Jeff is no longer @redhat.com so I've changed the CC
> 
> >>> On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
> >>> wrote:
> 
> >>>> - All gfortran developers move to the new branch.  This will not
> >>>>     happen, I can guarantee you that.
> 
> >>> This is the part I'm curious about (the rest is obvious, it follows
> >> >from there being finite resources and the nature of any fork). But I'm
> >>> not going to press for reasons.
> 
> >> Note the only viable fork will be on the current hosting (which isn't 
> >> FSF controlled) with the downside of eventually losing the gcc.gnu.org 
> >> DNS and thus a need to "switch" to a sourceware.org name.
> 
> > I strongly suspect you're right here.  Ultimately if one fork reaches 
> > critical mass, then it survives and the other dies.  That's a function 
> > of the developer community.   Right now I don't see the nightmare 
> > scenario of both forks being viable playing out -- however I'm more 
> > concerned now than I was before due Thomas's comments.
> 
> When plans for the EGCS were underway, and the (then) Fortran supporters 
> were into the plans, it scared the hell out of me, because it was 
> completely unclear to me where it would end.
> 
> But in the end: I am a supporter of Free Software, not a organization, 
> or a person, but *developers* who support Free Software.
> 
> That's what got me to go for the fork of EGCS - and I have not been 
> disappointed.
> 
> -- 
> Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
> Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands

The two projects once again united because multiple forks are proved to be
inefficient and unwieldy.   As long as the license terms for free software
are met and there is compatibility, I am pleased. 

Re: GCC association with the FSF

[Jeff Law]

On 4/14/2021 10:55 AM, Christopher Dimech wrote:
>> Sent: Thursday, April 15, 2021 at 4:35 AM
>> From: "Toon Moene" <toon@moene.org>
>> To: "Jeff Law" <jeffreyalaw@gmail.com>, "Richard Biener" <richard.guenther@gmail.com>, "Jonathan Wakely" <jwakely.gcc@gmail.com>, "Jonathan Wakely via Gcc" <gcc@gcc.gnu.org>, "Thomas Koenig" <tkoenig@netcologne.de>
>> Subject: Re: GCC association with the FSF
>>
>> On 4/14/21 6:18 PM, Jeff Law via Gcc wrote:
>>
>>> On 4/14/2021 6:08 AM, Richard Biener via Gcc wrote:
>>>> On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc
>>>> <gcc@gcc.gnu.org> wrote:
>>>>> N.B. Jeff is no longer @redhat.com so I've changed the CC
>>>>> On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
>>>>> wrote:
>>>>>> - All gfortran developers move to the new branch.  This will not
>>>>>>      happen, I can guarantee you that.
>>>>> This is the part I'm curious about (the rest is obvious, it follows
>>>> >from there being finite resources and the nature of any fork). But I'm
>>>>> not going to press for reasons.
>>>> Note the only viable fork will be on the current hosting (which isn't
>>>> FSF controlled) with the downside of eventually losing the gcc.gnu.org
>>>> DNS and thus a need to "switch" to a sourceware.org name.
>>> I strongly suspect you're right here.  Ultimately if one fork reaches
>>> critical mass, then it survives and the other dies.  That's a function
>>> of the developer community.   Right now I don't see the nightmare
>>> scenario of both forks being viable playing out -- however I'm more
>>> concerned now than I was before due Thomas's comments.
>> When plans for the EGCS were underway, and the (then) Fortran supporters
>> were into the plans, it scared the hell out of me, because it was
>> completely unclear to me where it would end.
>>
>> But in the end: I am a supporter of Free Software, not a organization,
>> or a person, but *developers* who support Free Software.
>>
>> That's what got me to go for the fork of EGCS - and I have not been
>> disappointed.
>>
>> -- 
>> Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
>> Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
> The two projects once again united because multiple forks are proved to be
> inefficient and unwieldy.   As long as the license terms for free software
> are met and there is compatibility, I am pleased.

Umm, no.  The projects re-united because the FSF fork wasn't viable and 
we structured EGCS so that if it was successful it could supplant the 
FSF fork.  Toon, myself and others were part of that process.


jeff

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Thursday, April 15, 2021 at 5:42 AM
> From: "Jeff Law" <jeffreyalaw@gmail.com>
> To: "Christopher Dimech" <dimech@gmx.com>, "Toon Moene" <toon@moene.org>
> Cc: "Richard Biener" <richard.guenther@gmail.com>, "Jonathan Wakely" <jwakely.gcc@gmail.com>, "Jonathan Wakely via Gcc" <gcc@gcc.gnu.org>, "Thomas Koenig" <tkoenig@netcologne.de>
> Subject: Re: GCC association with the FSF
>
> 
> On 4/14/2021 10:55 AM, Christopher Dimech wrote:
> >> Sent: Thursday, April 15, 2021 at 4:35 AM
> >> From: "Toon Moene" <toon@moene.org>
> >> To: "Jeff Law" <jeffreyalaw@gmail.com>, "Richard Biener" <richard.guenther@gmail.com>, "Jonathan Wakely" <jwakely.gcc@gmail.com>, "Jonathan Wakely via Gcc" <gcc@gcc.gnu.org>, "Thomas Koenig" <tkoenig@netcologne.de>
> >> Subject: Re: GCC association with the FSF
> >>
> >> On 4/14/21 6:18 PM, Jeff Law via Gcc wrote:
> >>
> >>> On 4/14/2021 6:08 AM, Richard Biener via Gcc wrote:
> >>>> On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc
> >>>> <gcc@gcc.gnu.org> wrote:
> >>>>> N.B. Jeff is no longer @redhat.com so I've changed the CC
> >>>>> On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
> >>>>> wrote:
> >>>>>> - All gfortran developers move to the new branch.  This will not
> >>>>>>      happen, I can guarantee you that.
> >>>>> This is the part I'm curious about (the rest is obvious, it follows
> >>>> >from there being finite resources and the nature of any fork). But I'm
> >>>>> not going to press for reasons.
> >>>> Note the only viable fork will be on the current hosting (which isn't
> >>>> FSF controlled) with the downside of eventually losing the gcc.gnu.org
> >>>> DNS and thus a need to "switch" to a sourceware.org name.
> >>> I strongly suspect you're right here.  Ultimately if one fork reaches
> >>> critical mass, then it survives and the other dies.  That's a function
> >>> of the developer community.   Right now I don't see the nightmare
> >>> scenario of both forks being viable playing out -- however I'm more
> >>> concerned now than I was before due Thomas's comments.
> >> When plans for the EGCS were underway, and the (then) Fortran supporters
> >> were into the plans, it scared the hell out of me, because it was
> >> completely unclear to me where it would end.
> >>
> >> But in the end: I am a supporter of Free Software, not a organization,
> >> or a person, but *developers* who support Free Software.
> >>
> >> That's what got me to go for the fork of EGCS - and I have not been
> >> disappointed.
> >>
> >> -- 
> >> Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
> >> Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
> > The two projects once again united because multiple forks are proved to be
> > inefficient and unwieldy.   As long as the license terms for free software
> > are met and there is compatibility, I am pleased.
> 
> Umm, no.  The projects re-united because the FSF fork wasn't viable and 
> we structured EGCS so that if it was successful it could supplant the 
> FSF fork.  Toon, myself and others were part of that process.

Would you consider the current situation as separate still?  It seems that
some coordination is needed, irrespective of disagreement, if there is to
be a future in all this.

Had asked Thomas Koenig for details which I could follow very clearly.
He talked sense to me. 
 
> jeff
> 
>

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Thursday, April 15, 2021 at 4:18 AM
> From: "Jeff Law via Gcc" <gcc@gcc.gnu.org>
> To: "Richard Biener" <richard.guenther@gmail.com>, "Jonathan Wakely" <jwakely.gcc@gmail.com>, "Jonathan Wakely via Gcc" <gcc@gcc.gnu.org>, "Thomas Koenig" <tkoenig@netcologne.de>
> Subject: Re: GCC association with the FSF
>
> 
> On 4/14/2021 6:08 AM, Richard Biener via Gcc wrote:
> > On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc <gcc@gcc.gnu.org> wrote:
> >> N.B. Jeff is no longer @redhat.com so I've changed the CC
> >>
> >> On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
> >> wrote:
> >>> - All gfortran developers move to the new branch.  This will not
> >>>     happen, I can guarantee you that.
> >> This is the part I'm curious about (the rest is obvious, it follows
> > >from there being finite resources and the nature of any fork). But I'm
> >> not going to press for reasons.

> > Note the only viable fork will be on the current hosting (which isn't FSF controlled) with the downside of eventually losing the gcc.gnu.org DNS and thus a need to "switch" to a sourceware.org name.

It is likely that gcc.gnu.org would not be available.

> I strongly suspect you're right here.  Ultimately if one fork reaches 
> critical mass, then it survives and the other dies.  That's a function 
> of the developer community.   Right now I don't see the nightmare 
> scenario of both forks being viable playing out -- however I'm more 
> concerned now than I was before due Thomas's comments.

> Given there would be actual work involved on the FSF side to keep a "fork" with the exact same setup (and thus transparent with existing setups) I don't see it keeping live (but I see somebody populating savannah with sources).
> 
> Absolutely.  I could even see a small community continuing to push the 
> FSF fork for a while until it becomes abundantly clear that only one 
> fork is long term viable.  That's what happened with EGCS -- the 
> majority of the developer community went with the EGCS fork with a small 
> community staying on the FSF fork.  Eventually it became clear that EGCS 
> had much broader developer support and the FSF fork ultimately withered 
> away.

The issue would then be of compatibility.  Free Software is that which, by
definition, may be forked from the original development team without prior
permission, without violating copyright law.  Gcc would continue as a Gnu 
Project nonetheless.  Technically, gcc is not a fork.   
 
> Jeff
> 
> 
>

Re: GCC association with the FSF

[Jason Merrill]

On Wed, Apr 14, 2021 at 8:08 AM Richard Biener via Gcc <gcc@gcc.gnu.org> wrote:
> On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc <gcc@gcc.gnu.org> wrote:
> >N.B. Jeff is no longer @redhat.com so I've changed the CC
> >On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
> >wrote:
> >> - All gfortran developers move to the new branch.  This will not
> >>    happen, I can guarantee you that.
> >
> >This is the part I'm curious about (the rest is obvious, it follows
> >from there being finite resources and the nature of any fork). But I'm
> >not going to press for reasons.
>
> Note the only viable fork will be on the current hosting (which isn't FSF controlled) with the downside of eventually losing the gcc.gnu.org DNS and thus a need to "switch" to a sourceware.org name.

It seems wrong to call such a scenario a fork.  If someone wanted to
fork GCC they are free to do so, but changing the relationship with
GNU/FSF is not a fork, as there would continue to be one primary
source repository.

Jason

Re: GCC association with the FSF

[Richard Biener]

On April 15, 2021 6:02:50 PM GMT+02:00, Jason Merrill <jason@redhat.com> wrote:
>On Wed, Apr 14, 2021 at 8:08 AM Richard Biener via Gcc
><gcc@gcc.gnu.org> wrote:
>> On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc
><gcc@gcc.gnu.org> wrote:
>> >N.B. Jeff is no longer @redhat.com so I've changed the CC
>> >On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
>> >wrote:
>> >> - All gfortran developers move to the new branch.  This will not
>> >>    happen, I can guarantee you that.
>> >
>> >This is the part I'm curious about (the rest is obvious, it follows
>> >from there being finite resources and the nature of any fork). But
>I'm
>> >not going to press for reasons.
>>
>> Note the only viable fork will be on the current hosting (which isn't
>FSF controlled) with the downside of eventually losing the gcc.gnu.org
>DNS and thus a need to "switch" to a sourceware.org name.
>
>It seems wrong to call such a scenario a fork.  If someone wanted to
>fork GCC they are free to do so, but changing the relationship with
>GNU/FSF is not a fork, as there would continue to be one primary
>source repository.

True. That's definitely better communication. 

Richard. 

>Jason

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Friday, April 16, 2021 at 4:24 AM
> From: "Richard Biener via Gcc" <gcc@gcc.gnu.org>
> To: "Jason Merrill" <jason@redhat.com>
> Cc: "Thomas Koenig" <tkoenig@netcologne.de>, "gcc mailing list" <gcc@gcc.gnu.org>
> Subject: Re: GCC association with the FSF
>
> On April 15, 2021 6:02:50 PM GMT+02:00, Jason Merrill <jason@redhat.com> wrote:
> >On Wed, Apr 14, 2021 at 8:08 AM Richard Biener via Gcc
> ><gcc@gcc.gnu.org> wrote:
> >> On April 14, 2021 12:19:16 PM GMT+02:00, Jonathan Wakely via Gcc
> ><gcc@gcc.gnu.org> wrote:
> >> >N.B. Jeff is no longer @redhat.com so I've changed the CC
> >> >On Wed, 14 Apr 2021 at 11:03, Thomas Koenig <tkoenig@netcologne.de>
> >> >wrote:
> >> >> - All gfortran developers move to the new branch.  This will not
> >> >>    happen, I can guarantee you that.
> >> >
> >> >This is the part I'm curious about (the rest is obvious, it follows
> >> >from there being finite resources and the nature of any fork). But
> >I'm
> >> >not going to press for reasons.
> >>
> >> Note the only viable fork will be on the current hosting (which isn't
> >FSF controlled) with the downside of eventually losing the gcc.gnu.org
> >DNS and thus a need to "switch" to a sourceware.org name.
> >
> >It seems wrong to call such a scenario a fork.  If someone wanted to
> >fork GCC they are free to do so, but changing the relationship with
> >GNU/FSF is not a fork, as there would continue to be one primary
> >source repository.

Correct, but whatever happens, the association with RMS will remain.
Thusly the impasse is not going away.  A fork would work, but then
the secessionists' intention is to carry on with the Gcc tag, because
of its respected position in the world of science and technology.


> True. That's definitely better communication.
>
> Richard.
>
> >Jason
>
>

Re: GCC association with the FSF

[Alfred M. Szmidt]

   [...]  That "gnu-stucture" document was written by RMS a couple of
   months ago and doesn't represent how the GNU project and its
   maintainers have worked for years.

It reflects the same message that has been sent to new GNU maintainers
for the decades. The GNU structure and organization document
(https://www.gnu.org/gnu/gnu-structure.en.html) is basically a
reflection of that, and how we have been doing things for decades.

You can raise any issues you think do not reflect on the lists, or
with the GNU Advisory Committee.

   RMS indeed claims to be the "Chief GNUisance" of the GNU project and
   that that title somehow makes him the leader of the project and that
   he appoints GNU maintainers.

That is true, RMS appoints which projects become GNU projects or not,
and who maintains them.  And as maintainers we have a lot of freedom, as
can be seen here, and elsewhere.  

   The GNU Assembly is having a similar
   discussion right now

It should be noted that this group is not associated with the GNU
project, or represents it in anyway, despite pretending to.

Re: GCC association with the FSF

[David Malcolm]

On Wed, 2021-04-07 at 10:51 -0400, Alfred M. Szmidt via Gcc wrote:
>    [...]  That "gnu-stucture" document was written by RMS a couple of
>    months ago and doesn't represent how the GNU project and its
>    maintainers have worked for years.
> 
> It reflects the same message that has been sent to new GNU
> maintainers
> for the decades. The GNU structure and organization document
> (https://www.gnu.org/gnu/gnu-structure.en.html) is basically a
> reflection of that, and how we have been doing things for decades.

"We've always done it this way" is not necessarily a good defence of an
existing practice.

> You can raise any issues you think do not reflect on the lists, or
> with the GNU Advisory Committee.
> 
>    RMS indeed claims to be the "Chief GNUisance" of the GNU project
> and
>    that that title somehow makes him the leader of the project and
> that
>    he appoints GNU maintainers.
> 
> That is true, RMS appoints which projects become GNU projects or not,
> and who maintains them.  And as maintainers we have a lot of freedom,
> as
> can be seen here, and elsewhere.  

What you're describing sounds like a dictatorship to me.

> 
>    The GNU Assembly is having a similar
>    discussion right now
> 
> It should be noted that this group is not associated with the GNU
> project, or represents it in anyway, despite pretending to.

I don't think you get to speak for who is or is not a member of the GNU
project.  As far as I know, "GNU" isn't trademarked.

My opinions, not my employer's, as usual
Dave

Re: GCC association with the FSF

[John Darrington]

On Wed, Apr 07, 2021 at 11:15:14AM -0400, David Malcolm via Gcc wrote:

     > It reflects the same message that has been sent to new GNU
     > maintainers
     > for the decades. The GNU structure and organization document
     > (https://www.gnu.org/gnu/gnu-structure.en.html) is basically a
     > reflection of that, and how we have been doing things for decades.
     
     "We've always done it this way" is not necessarily a good defence of an
     existing practice.

You are right.  The GNU Structure document doesn't claim to be. It just
documents the way things are.
     
     > That is true, RMS appoints which projects become GNU projects or not,
     > and who maintains them.  And as maintainers we have a lot of freedom,
     > as
     > can be seen here, and elsewhere.  
     
     What you're describing sounds like a dictatorship to me.

???? I cannot see how you reach that conclusion.

     
     
     I don't think you get to speak for who is or is not a member of the GNU
     project.  As far as I know, "GNU" isn't trademarked.
     

It certainly used to be, unless those guys at the FSF have let it lapse again.

J'

Re: GCC association with the FSF

[Jonathan Wakely]

On Wed, 7 Apr 2021 at 17:28, John Darrington wrote:
>
> On Wed, Apr 07, 2021 at 11:15:14AM -0400, David Malcolm via Gcc wrote:
>      I don't think you get to speak for who is or is not a member of the GNU
>      project.  As far as I know, "GNU" isn't trademarked.
>
>
> It certainly used to be, unless those guys at the FSF have let it lapse again.

The footnote at
https://mikegerwitz.com/2012/10/trademarks-in-free-software#fn1 gives
details.

Re: GCC association with the FSF

[David Malcolm]

On Wed, 2021-04-07 at 18:24 +0200, John Darrington wrote:
> On Wed, Apr 07, 2021 at 11:15:14AM -0400, David Malcolm via Gcc
> wrote:
> 
>      > It reflects the same message that has been sent to new GNU
>      > maintainers
>      > for the decades. The GNU structure and organization document
>      > (https://www.gnu.org/gnu/gnu-structure.en.html) is basically a
>      > reflection of that, and how we have been doing things for
> decades.
>      
>      "We've always done it this way" is not necessarily a good
> defence of an
>      existing practice.
> 
> You are right.  The GNU Structure document doesn't claim to be. It
> just
> documents the way things are.
>      
>      > That is true, RMS appoints which projects become GNU projects
> or not,
>      > and who maintains them.  And as maintainers we have a lot of
> freedom,
>      > as
>      > can be seen here, and elsewhere.  
>      
>      What you're describing sounds like a dictatorship to me.
> 
> ???? I cannot see how you reach that conclusion.

Having one guy at the top from whom all power flows.

What's the process for replacing the guy at the top, if he's become a
liability to the project?  What would a healthy structure look like?

My opinions, not my employer's, as usual
Dave

Re: GCC association with the FSF

[John Darrington]

On Wed, Apr 07, 2021 at 06:34:12PM -0400, David Malcolm wrote:
     >      
     >      What you're describing sounds like a dictatorship to me.
     > 
     > ???? I cannot see how you reach that conclusion.
     
     Having one guy at the top from whom all power flows.

Power does not "flow" from RMS.  Since you have used a political analogy:
I think it is more akin to a constitutional monarchy.
     
     What's the process for replacing the guy at the top, if he's become a
     liability to the project?  What would a healthy structure look like?

Many countries have a single person as head of state with no formally
defined process for replacing him or her.   Most of those countries are not
usually descibed as "dictatorships".

Further, history has shown,  in cases where that head of state has been
forcibly removed (eg France, Russia). the regime that replaced them turned
out to be composed of murderous powermongers concerned with nobody's interest
but their own.   I for one, will not sit back and let that heppen to GNU.

J'

Re: GCC association with the FSF

[Richard Kenner]

>      Having one guy at the top from whom all power flows.
> 
> Power does not "flow" from RMS.  Since you have used a political analogy:
> I think it is more akin to a constitutional monarchy.

I think it's like the Queen of England.  As a British person I used to
know said: "The Queen of England has the power to veto anything passed by
the Parliament in any Commonwealth country until she actually does it; at
that point she'll lose that power".

I see it as the same here: if RMS tried to exert an inappropriate
level of control over some GNU project, it would soon be made clear that
that something he can't do.

Re: GCC association with the FSF

[John Darrington]

On Thu, Apr 08, 2021 at 07:56:14AM -0400, Richard Kenner wrote:
     >      Having one guy at the top from whom all power flows.
     > 
     > Power does not "flow" from RMS.  Since you have used a political analogy:
     > I think it is more akin to a constitutional monarchy.
     
     I think it's like the Queen of England.  As a British person I used to
     know said: "The Queen of England has the power to veto anything passed by
     the Parliament in any Commonwealth country until she actually does it; at
     that point she'll lose that power".

In 1975 she dismissed the prime minister of Australia, yet nearly 50 years
later she is still the head of state.
     
     I see it as the same here: if RMS tried to exert an inappropriate
     level of control over some GNU project, it would soon be made clear that
     that something he can't do.

Generally I agree.  Such draconian measures like dismissal of people has to
be done tactfully, only occasionally and only when there is very good cause.
So far as I'm aware, her majesty has done it only once; rms has done it only
twice.

J'

Re: GCC association with the FSF

[David Malcolm]

On Thu, 2021-04-08 at 08:45 +0200, John Darrington wrote:
> On Wed, Apr 07, 2021 at 06:34:12PM -0400, David Malcolm wrote:
>      >      
>      >      What you're describing sounds like a dictatorship to me.
>      > 
>      > ???? I cannot see how you reach that conclusion.
>      
>      Having one guy at the top from whom all power flows.
> 
> Power does not "flow" from RMS.  Since you have used a political
> analogy:
> I think it is more akin to a constitutional monarchy.

I grew up in the UK, and am most familiar with the situation there; I
don't have experience of the Australian system.

>      
>      What's the process for replacing the guy at the top, if he's
> become a
>      liability to the project?  What would a healthy structure look
> like?
> 
> Many countries have a single person as head of state with no formally
> defined process for replacing him or her.   Most of those countries
> are not
> usually descibed as "dictatorships".

It depends on whether the head of state is a mere figurehead, or is
actually in charge.  In the UK, the Queen is nominally in charge of
"her government", but that mostly amounts to merely rubberstamping the
election result, albeit with some limited "soft power" in terms of
gravitas.  I think it remains to be seen if the monarchy will survive
her passing (if indeed the UK is still in its current form at that
point, but that's a whole other can of worms).

> Further, history has shown,  in cases where that head of state has
> been
> forcibly removed (eg France, Russia). the regime that replaced them
> turned
> out to be composed of murderous powermongers concerned with nobody's
> interest
> but their own. 

If we're continuing the political analogy, a counterexample might be
the United States.

>   I for one, will not sit back and let that heppen to GNU.

I think it's important to distinguish between the figurative and
literal here.

No one is literally calling for anyone's head.

Some of us don't want RMS in a leadership position in a project we're
associated with (be it the FSF or GNU, and thus, GCC).

My opinions, not my employer's, as usual.
Dave

Re: GCC association with the FSF

[John Darrington]

On Thu, Apr 08, 2021 at 10:54:25AM -0400, David Malcolm wrote:
     
     I think it's important to distinguish between the figurative and
     literal here.
     
     No one is literally calling for anyone's head.


Nobody has explicitly done so.  However in the last 2 or 3 years there
has been a growing campaign of hatred.  The people feeding that
campaign are unhappy with things that RMS and others have said.
However they have taken it further than that.  These people seek
eliminate *anyone* who holds certain opinions - they don't care how
they get eliminated - so long as they go.  What's more, they cite
numerous putative moralistic justifications to give an air of
legitmacy to that hatred.  

Once such hatefulness becomes accepted, people DON'T any longer make that
literal--figurative distinction.
     
     Some of us don't want RMS in a leadership position in a project we're
     associated with (be it the FSF or GNU, and thus, GCC).

RMS was the first person to be involved in GNU and GCC.  Others became
involved later (under his leadership).  Their contribution was and
continues to be welcome.  They are also free to stop contributing any
time they wish to do so.

     
     My opinions, not my employer's, as usual.

Then why do you write this from your employer's email?  That is like
writing it on the company letterhead.  I suggest that when speaking
for yourself you use your own email.

J'

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Friday, April 09, 2021 at 6:21 AM
> From: "John Darrington" <john@darrington.wattle.id.au>
> To: "David Malcolm" <dmalcolm@redhat.com>
> Cc: gcc@gnu.org, "Alfred M. Szmidt" <ams@gnu.org>, "Mark Wielaard" <mark@klomp.org>
> Subject: Re: GCC association with the FSF
>
> On Thu, Apr 08, 2021 at 10:54:25AM -0400, David Malcolm wrote:
>
>      I think it's important to distinguish between the figurative and
>      literal here.
>
>      No one is literally calling for anyone's head.
>
>
> Nobody has explicitly done so.  However in the last 2 or 3 years there
> has been a growing campaign of hatred.  The people feeding that
> campaign are unhappy with things that RMS and others have said.
> However they have taken it further than that.  These people seek
> eliminate *anyone* who holds certain opinions - they don't care how
> they get eliminated - so long as they go.  What's more, they cite
> numerous putative moralistic justifications to give an air of
> legitmacy to that hatred.
>
> Once such hatefulness becomes accepted, people DON'T any longer make that
> literal--figurative distinction.
>
>      Some of us don't want RMS in a leadership position in a project we're
>      associated with (be it the FSF or GNU, and thus, GCC).
>
> RMS was the first person to be involved in GNU and GCC.  Others became
> involved later (under his leadership).  Their contribution was and
> continues to be welcome.  They are also free to stop contributing any
> time they wish to do so.
>
>
>      My opinions, not my employer's, as usual.
>
> Then why do you write this from your employer's email?  That is like
> writing it on the company letterhead.  I suggest that when speaking
> for yourself you use your own email.

Fair points John.

> J'
>

Re: GCC association with the FSF

[David Malcolm]

On Thu, 2021-04-08 at 20:21 +0200, John Darrington wrote:
> On Thu, Apr 08, 2021 at 10:54:25AM -0400, David Malcolm wrote:     

[...]

>      Some of us don't want RMS in a leadership position in a project
> we're
>      associated with (be it the FSF or GNU, and thus, GCC).
> 
> RMS was the first person to be involved in GNU and GCC.  Others
> became
> involved later (under his leadership).  Their contribution was and
> continues to be welcome.  They are also free to stop contributing any
> time they wish to do so.

I intend to continue contributing to GCC (and to Free Software in
general), but RMS is not my leader.

>      
>      My opinions, not my employer's, as usual.
> 
> Then why do you write this from your employer's email?

My employer gives me permission.

>   That is like
> writing it on the company letterhead.

I disagree.

>   I suggest that when speaking
> for yourself you use your own email.

Given the reaction that some have faced for questioning RMS, I'd prefer
to keep that address private.

As before, these are my opinions, not my employer's.

Dave

Re: GCC association with the FSF

[John Darrington]

On Thu, Apr 08, 2021 at 09:35:23PM -0400, David Malcolm wrote:
     
     > RMS was the first person to be involved in GNU and GCC.  Others
     > became
     > involved later (under his leadership).  Their contribution was and
     > continues to be welcome.  They are also free to stop contributing any
     > time they wish to do so.
     
     I intend to continue contributing to GCC (and to Free Software in
     general), but RMS is not my leader.

Nobody is suggesting that RMS should be regarded by everyone or indeed
anyone as "mein Führer".  I think he would be very much concerned if anyone
tried to confer a cult hero status on him.

Sooner or later, if for no reason other than his age, RMS will have to step
down as leader of GNU.   Rather than calling for his head on a block it
would be more constructive to think to the future.  Unfortunately to date,
I have not seen anyone who in my opinion would have the qualities necessary
to take over the role.

     
     > Then why do you write this from your employer's email?
     
     My employer gives me permission.

That's good to know.  My employer on the other hand expressly forbids it.
And I think that is a reasonable prohibition (we're allowed to use their
internet connection for personal use) but not allowed to use the company
name (including email addresses) in personal communication.  Even if they
didn't prohibit this, I wouldn't dream of using my company's email or
letterhead for personal communication.
     
     Given the reaction that some have faced for questioning RMS, I'd prefer
     to keep that address private.

So in other words, you are happy to make contraversial statements, but don't
wish to face the responsibility.  Come on David!  By all means question RMS
(or anyone else) but have the guts to do this under your own identity rather
than duck in and out behind a veil of quasi-anonymity!

I'm glad that you're going to continue to contribute to GCC.

J'

Re: GCC association with the FSF

[David Brown]

On 09/04/2021 08:37, John Darrington wrote:

> 
> Nobody is suggesting that RMS should be regarded by everyone or indeed
> anyone as "mein Führer".  I think he would be very much concerned if anyone
> tried to confer a cult hero status on him.
> 
> Sooner or later, if for no reason other than his age, RMS will have to step
> down as leader of GNU.   Rather than calling for his head on a block it
> would be more constructive to think to the future.  Unfortunately to date,
> I have not seen anyone who in my opinion would have the qualities necessary
> to take over the role.
> 

And I don't think people (at least, not many) are "calling for his
head".  My thought is that he should be encouraged to step down from all
his positions within GNU, FSF, gcc, and any other projects he is
involved with.  Retire now, while he can do so with dignity and without
harm to the free and open source software worlds.

It is only if it is left too late that people will be /forced/ to call
for his head.  You can be very sure that complaints about his behaviour
and attitudes will not diminish - they will grow, and the result will
not be good for RMS, GNU, gcc, users, developers, or anyone else except
the sellers of tabloid newspapers.  I would rather see him leave quietly
now with respect, than be hounded out later and his statues pulled down
- along with the careers and reputations of many who work with him.  (I
am not saying that such a destruction would be correct or appropriate -
I am saying it will happen in the end if the free software community is
not careful.)


(I agree that there are few, if any, people who had the qualities of RMS
to do the job he did.  But IMHO that role is over - we don't need
someone to fill his shoes.)


David Brown

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Friday, April 09, 2021 at 10:37 PM
> From: "David Brown" <david.brown@hesbynett.no>
> To: "John Darrington" <john@darrington.wattle.id.au>, "David Malcolm" <dmalcolm@redhat.com>
> Cc: gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On 09/04/2021 08:37, John Darrington wrote:
> 
> > 
> > Nobody is suggesting that RMS should be regarded by everyone or indeed
> > anyone as "mein Führer".  I think he would be very much concerned if anyone
> > tried to confer a cult hero status on him.
> > 
> > Sooner or later, if for no reason other than his age, RMS will have to step
> > down as leader of GNU.   Rather than calling for his head on a block it
> > would be more constructive to think to the future.  Unfortunately to date,
> > I have not seen anyone who in my opinion would have the qualities necessary
> > to take over the role.
> > 
> 
> And I don't think people (at least, not many) are "calling for his
> head".  My thought is that he should be encouraged to step down from all
> his positions within GNU, FSF, gcc, and any other projects he is
> involved with.  Retire now, while he can do so with dignity and without
> harm to the free and open source software worlds.

David, I oppose your thought that he should be made to step down from ALL
his positions.  That's the fundamental philosophy of China and Russia.
 
> It is only if it is left too late that people will be /forced/ to call
> for his head.  You can be very sure that complaints about his behaviour
> and attitudes will not diminish - they will grow, and the result will
> not be good for RMS, GNU, gcc, users, developers, or anyone else except
> the sellers of tabloid newspapers.  I would rather see him leave quietly
> now with respect, than be hounded out later and his statues pulled down
> - along with the careers and reputations of many who work with him.  (I
> am not saying that such a destruction would be correct or appropriate -
> I am saying it will happen in the end if the free software community is
> not careful.)
 
> (I agree that there are few, if any, people who had the qualities of RMS
> to do the job he did.  But IMHO that role is over - we don't need
> someone to fill his shoes.)
 
I do not see that a person with the qualities of RMS would ask permission for
the job.  I certainly don't! 
 
> David Brown
>

Re: GCC association with the FSF

[David Brown]

On 09/04/2021 16:40, Christopher Dimech wrote:
>> Sent: Friday, April 09, 2021 at 10:37 PM
>> From: "David Brown" <david.brown@hesbynett.no>
>> To: "John Darrington" <john@darrington.wattle.id.au>, "David Malcolm" <dmalcolm@redhat.com>
>> Cc: gcc@gnu.org
>> Subject: Re: GCC association with the FSF
>>
>> On 09/04/2021 08:37, John Darrington wrote:
>>
>>>
>>> Nobody is suggesting that RMS should be regarded by everyone or indeed
>>> anyone as "mein Führer".  I think he would be very much concerned if anyone
>>> tried to confer a cult hero status on him.
>>>
>>> Sooner or later, if for no reason other than his age, RMS will have to step
>>> down as leader of GNU.   Rather than calling for his head on a block it
>>> would be more constructive to think to the future.  Unfortunately to date,
>>> I have not seen anyone who in my opinion would have the qualities necessary
>>> to take over the role.
>>>
>>
>> And I don't think people (at least, not many) are "calling for his
>> head".  My thought is that he should be encouraged to step down from all
>> his positions within GNU, FSF, gcc, and any other projects he is
>> involved with.  Retire now, while he can do so with dignity and without
>> harm to the free and open source software worlds.
> 
> David, I oppose your thought that he should be made to step down from ALL
> his positions.  That's the fundamental philosophy of China and Russia.
>  

Different opinions are fine.  Bringing national or international
politics into the discussion (presumably meant to be as an insult) is
not fine.  This is not a political discussion - please stop trying to
make it one.

>> It is only if it is left too late that people will be /forced/ to call
>> for his head.  You can be very sure that complaints about his behaviour
>> and attitudes will not diminish - they will grow, and the result will
>> not be good for RMS, GNU, gcc, users, developers, or anyone else except
>> the sellers of tabloid newspapers.  I would rather see him leave quietly
>> now with respect, than be hounded out later and his statues pulled down
>> - along with the careers and reputations of many who work with him.  (I
>> am not saying that such a destruction would be correct or appropriate -
>> I am saying it will happen in the end if the free software community is
>> not careful.)
>  
>> (I agree that there are few, if any, people who had the qualities of RMS
>> to do the job he did.  But IMHO that role is over - we don't need
>> someone to fill his shoes.)
>  
> I do not see that a person with the qualities of RMS would ask permission for
> the job.  I certainly don't! 
>  

We (the free software world) does not need a person with the qualities
of RMS any more - that is the point.  There should not be such a
position as "Chief GNUsance".

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Saturday, April 10, 2021 at 5:01 AM
> From: "David Brown" <david.brown@hesbynett.no>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "John Darrington" <john@darrington.wattle.id.au>, "David Malcolm" <dmalcolm@redhat.com>, gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On 09/04/2021 16:40, Christopher Dimech wrote:
> >> Sent: Friday, April 09, 2021 at 10:37 PM
> >> From: "David Brown" <david.brown@hesbynett.no>
> >> To: "John Darrington" <john@darrington.wattle.id.au>, "David Malcolm" <dmalcolm@redhat.com>
> >> Cc: gcc@gnu.org
> >> Subject: Re: GCC association with the FSF
> >>
> >> On 09/04/2021 08:37, John Darrington wrote:
> >>
> >>>
> >>> Nobody is suggesting that RMS should be regarded by everyone or indeed
> >>> anyone as "mein Führer".  I think he would be very much concerned if anyone
> >>> tried to confer a cult hero status on him.
> >>>
> >>> Sooner or later, if for no reason other than his age, RMS will have to step
> >>> down as leader of GNU.   Rather than calling for his head on a block it
> >>> would be more constructive to think to the future.  Unfortunately to date,
> >>> I have not seen anyone who in my opinion would have the qualities necessary
> >>> to take over the role.
> >>>
> >>
> >> And I don't think people (at least, not many) are "calling for his
> >> head".  My thought is that he should be encouraged to step down from all
> >> his positions within GNU, FSF, gcc, and any other projects he is
> >> involved with.  Retire now, while he can do so with dignity and without
> >> harm to the free and open source software worlds.
> > 
> > David, I oppose your thought that he should be made to step down from ALL
> > his positions.  That's the fundamental philosophy of China and Russia.
> >  
> 
> Different opinions are fine.  Bringing national or international
> politics into the discussion (presumably meant to be as an insult) is
> not fine.  This is not a political discussion - please stop trying to
> make it one.

It is an assessment of what you propose.  The removal of people from all
positions is a political statements.  I have no problem with political
discussions and certainly don't take instructions from you, to say the 
least!  What you talk about is exactly what drives Chinese and Russian
officials to suppress anybody who does not conform with their demands.    
The consequences will be the same should you and others get your way
of doing things.

> >> It is only if it is left too late that people will be /forced/ to call
> >> for his head.  You can be very sure that complaints about his behaviour
> >> and attitudes will not diminish - they will grow, and the result will
> >> not be good for RMS, GNU, gcc, users, developers, or anyone else except
> >> the sellers of tabloid newspapers.  I would rather see him leave quietly
> >> now with respect, than be hounded out later and his statues pulled down
> >> - along with the careers and reputations of many who work with him.  (I
> >> am not saying that such a destruction would be correct or appropriate -
> >> I am saying it will happen in the end if the free software community is
> >> not careful.)
> >  
> >> (I agree that there are few, if any, people who had the qualities of RMS
> >> to do the job he did.  But IMHO that role is over - we don't need
> >> someone to fill his shoes.)
> >  
> > I do not see that a person with the qualities of RMS would ask permission for
> > the job.  I certainly don't! 
> >  
> 
> We (the free software world) does not need a person with the qualities
> of RMS any more - that is the point.  There should not be such a
> position as "Chief GNUsance".
 
Secondly,  I cannot clearly see what status you have for making statements
that imply a representation for the free software world!!!

Re: GCC association with the FSF

[Thomas Rodgers]

On 2021-04-09 11:02, Christopher Dimech via Gcc wrote:

[... snip ...]

>> We (the free software world) does not need a person with the qualities
>> of RMS any more - that is the point.  There should not be such a
>> position as "Chief GNUsance".
> Secondly,  I cannot clearly see what status you have for making 
> statements
> that imply a representation for the free software world!!!

I know, right? He's not even got the cred conferred to a maintainer of 
an empty GNU project on Savannah.

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Saturday, April 10, 2021 at 7:37 AM
> From: "Thomas Rodgers" <rodgert@appliantology.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "David Brown" <david.brown@hesbynett.no>, gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On 2021-04-09 11:02, Christopher Dimech via Gcc wrote:
>
> [... snip ...]
>
> >> We (the free software world) does not need a person with the qualities
> >> of RMS any more - that is the point.  There should not be such a
> >> position as "Chief GNUsance".
> > Secondly,  I cannot clearly see what status you have for making
> > statements
> > that imply a representation for the free software world!!!
>
> I know, right? He's not even got the cred conferred to a maintainer of
> an empty GNU project on Savannah.

There is no law that says the highest grossing author on a subject knows
the most about it, writes the best about it, or is even more than mediocre
on the subject at hand.

My mathematical work was entirely kept secret until I resigned my commission
in 2014.  Other forms of credibility exist.

https://www.corrieredimalta.com/coronavirus/la-diffusione-del-covid-19-a-malta-evento-b/

But you seem too ignorant to introspect the likelihood that I could in effect have
many valuable things to say.

Christopher

Re: GCC association with the FSF

[Thomas Rodgers]

On 2021-04-09 14:02, Christopher Dimech wrote:

> But you seem too ignorant to introspect the likelihood that I could in 
> effect have
> many valuable things to say.

On the contrary, I eagerly await each and every one of your missives on 
this topic, hoping for exactly that very
thing to occur.

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Saturday, April 10, 2021 at 9:17 AM
> From: "Thomas Rodgers" <rodgert@appliantology.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "David Brown" <david.brown@hesbynett.no>, gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On 2021-04-09 14:02, Christopher Dimech wrote:
>
> > But you seem too ignorant to introspect the likelihood that I could in
> > effect have
> > many valuable things to say.
>
> On the contrary, I eagerly await each and every one of your missives on
> this topic, hoping for exactly that very
> thing to occur.

I do not see how you and your friends at redhat could really get any value
from it, because being a seeker of truth means refusing to make assumptions
about things that you do not know.  The moment you assume that you know because
of what you believe, your intelligence will sleep.  It is my wish and my blessing
that every human being has their intelligence awake.

Good Night
Christopher

Re: GCC association with the FSF

[Liu Hao]

[-- Attachment #1.1: Type: text/plain, Size: 1192 bytes --]

在 2021/4/10 上午2:02, Christopher Dimech via Gcc 写道:
> 
> It is an assessment of what you propose.  The removal of people from all
> positions is a political statements.  I have no problem with political
> discussions and certainly don't take instructions from you, to say the
> least!  What you talk about is exactly what drives Chinese and Russian
> officials to suppress anybody who does not conform with their demands.
> The consequences will be the same should you and others get your way
> of doing things.
>

Then what's your point? The suppression of somebody is bad? Then what are you attempting to defend? 
The freedom of software, or of discrimination, of insulting, of harassment? No, that is not what I 
would do or expect, and not what you western people would either.

Chairman Mao actually said that 'women prop up half of the sky', which had a great influence on the 
Chinese society and has almost eradicated sexism. It's something I can hardly understand why you 
(singular) still have a very vicious opinion on that.


[I am not meant to participate in the discussion about the history and future of GCC.]



-- 
Best regards,
Liu Hao


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Saturday, April 10, 2021 at 2:53 PM
> From: "Liu Hao" <lh_mouse@126.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> 在 2021/4/10 上午2:02, Christopher Dimech via Gcc 写道:
> > 
> > It is an assessment of what you propose.  The removal of people from all
> > positions is a political statements.  I have no problem with political
> > discussions and certainly don't take instructions from you, to say the
> > least!  What you talk about is exactly what drives Chinese and Russian
> > officials to suppress anybody who does not conform with their demands.
> > The consequences will be the same should you and others get your way
> > of doing things.
> >
> 
> Then what's your point? The suppression of somebody is bad? Then what are you attempting to defend? 
> The freedom of software, or of discrimination, of insulting, of harassment? No, that is not what I 
> would do or expect, and not what you western people would either.

Yes, the suppression of a person like Stallman from everything is bad.  I defend the freedom of thought.
 
> Chairman Mao actually said that 'women prop up half of the sky', which had a great influence on the 
> Chinese society and has almost eradicated sexism. It's something I can hardly understand why you 
> (singular) still have a very vicious opinion on that.

The suppression of a mass murderer by execution, imprisonment or forced famine is
good.  As is good the suppression of the Communist Party of China, for trying to
dominate the people of Hong Kong, Nepal, and Taiwan.

As well as for lying about coronavirus infection rates amongst people in China. 
 
> [I am not meant to participate in the discussion about the history and future of GCC.]
> 
> 
> 
> -- 
> Best regards,
> Liu Hao
> 
>

Re: GCC association with the FSF

[Bronek Kozicki]

Hello there

As a long time GCC user, who is also a father to teenage children, I would
very much prefer if a person who openly expressed opinions, and also openly
exercised behaviours, which I consider abhorrent, was *not* associated with
the GCC project. It does not matter to me what kind of control that person
exerts on the project, if any. What matters to me is association, even if
indirect one (other than historical).

This aside, I also happen to be one of very many developers in a corporate
setting, able to exert a small amount of pressure to entirely switch my
employer's toolset from GCC to Clang (which we already use for many
projects), if I consider the direction that GCC takes (technical or
otherwise) not favourable to us. For this to happen it would be enough for
GCC to lose only a few of the key contributors, like for example Jonathan
Wakely, Nathan Sidwell, Marek Polacek. It does not have to lose many
contributors at all. In fact, since my employer runs RedHat, we might just
follow the direction that RedHat takes with their developer tools in the
future - given their stance on the matter and the current GCC association,
as well as possible loss of major contributors in GCC, I wouldn't take it
for granted that they will keep supporting GCC forever.

Also, it is not called "cancel culture". It is called "actions have
consequences".

That's all,


B. Kozicki

Re: GCC association with the FSF

[John Darrington]

On Sat, Apr 10, 2021 at 01:50:42PM +0100, Bronek Kozicki via Gcc wrote:
     
     I would
     very much prefer if a person who openly expressed opinions, and also openly
     exercised behaviours, which I consider abhorrent, was *not* associated with
     the GCC project. It does not matter to me what kind of control that person
     exerts on the project, if any. What matters to me is association, even if
     indirect one (other than historical).


I suppose I feel the same.  I would also prefer it if all people involved
with GCC (and all my other interests) did not do or say things which made me
uncomfortable.  I don't however feel that I have the right to call for anyone
to be excluded simply because I'm uncomfortable with that person's words or
deeds (ie. "consider them abhorent"). That would be an utterly dystopian, world.

Of course persons should not use a project's name or infrastructure to make
comments unrelated to the project.  But if that person wishes to make a comment
under his/her own name in an unrelated forum, that is his/her right.  Even if
we consider them abhorrent, we must respect the rights of others.

J'

Re: GCC association with the FSF

[Jonathan Wakely]

On Sat, 10 Apr 2021, 15:38 John Darrington, <john@darrington.wattle.id.au>
wrote:

> On Sat, Apr 10, 2021 at 01:50:42PM +0100, Bronek Kozicki via Gcc wrote:
>
>      I would
>      very much prefer if a person who openly expressed opinions, and also
> openly
>      exercised behaviours, which I consider abhorrent, was *not*
> associated with
>      the GCC project. It does not matter to me what kind of control that
> person
>      exerts on the project, if any. What matters to me is association,
> even if
>      indirect one (other than historical).
>
>
> I suppose I feel the same.  I would also prefer it if all people involved
> with GCC (and all my other interests) did not do or say things which made
> me
> uncomfortable.  I don't however feel that I have the right to call for
> anyone
> to be excluded simply because I'm uncomfortable with that person's words or
> deeds (ie. "consider them abhorent"). That would be an utterly dystopian,
> world.
>

https://en.m.wikipedia.org/wiki/Freedom_of_association

Re: GCC association with the FSF

[Alexandre Oliva]

On Apr 10, 2021, Bronek Kozicki via Gcc <gcc@gcc.gnu.org> wrote:

> It is called "actions have consequences".

FTR, what consequences do you believe would be adequate for such actions
as spreading difamatory rumors about an innocent person?

I ask because some of the people campaigning against RMS have already
disclaimed the false accusations in the hateful letter, but others keep
on resorting to them as if they were true and relevant.


Ironically, those who may have legitimate claims about difficulties in
dealing with RMS and who, for their position in the subproject, might
have to interact with him are not the ones engaging in disrespectful
conversations with users and potential contributors, offering them a far
worse amount of toxicity than anything that could be honestly attributed
to RMS, rather than setting a good example of kind and respectful
dissent for those who've just started participating in our community.


We've already seen that Nathan's frustration with RMS for supposedly
holding up a project he wanted to contribute was misdirected.  People
from neighboring projects, if willing to look honestly into the matters,
would find out that a lot of frustration misdirected at RMS is also
motivated by faulty assumptions.

That, plus the tiresome repeating of unfounded allegations and hearsay
mistaken as evidence, by a few loud individuals, makes for strong cases
of intolerance, witch hunting and scapegoating.

Such unkindness and intolerance do not belong in communities that wish
to be welcoming to contributors and users alike.


Responsibility that might normally be assigned to positions of
authority, and that AFAICT is attributed to Chief GNUisance, is IMHO a
mistake.

Chief GNUisance is not a position of authority over volunteers.  That
would be (-: gnonsense :-) , a deep misunderstanding of the dynamics at
play.  It's rather a position of purpose setting, strategic steering and
policy driving for the project as a whole.  It's not one of policing
contributor's thoughts or behaviors.  That requires authority over
individuals, which Chief GNUisance doesn't have.

If we find undesirable behaviors within our subprojects, we shouldn't
expect Chief GNUisance to send GNU Kindness Police to address it.
There's no such authority, no such power.

We are, rather, free and expected to behave like kind grownups, and
respectfully resolve issues among ourselves, according to policies set
for the project as a whole and for the subproject, if any.  Sort of like
some are trying to do to RMS, just with kindness and respect, and
directing it at someone who's actually engaging in misbehavior among us.


The rationale presented to justify a separation from any organization in
which RMS is involved, on the grounds that a lot of people would find
such a relationship intolerable, is questionable in the face of the
massive support for RMS's return to the FSF board, vs the hate letter
than is such a failure that they now even refuse to apply withdrawals
from undersigners who learned better.

If public image and community alignment were the issue, it would seem
like separation from all things RMS would bring onto us far more
community repproach and distrust than keeping things as they are.

Conversely, such a hate campaign, the false allegations, and the very
vocal and explicit intolerance to symptoms of the neurodiverse condition
of the target do the very opposite of signaling a welcome and safe
space, presented as rationale for these behaviors.

Right now I couldn't honestly recommend GCC as a welcoming or even as a
respectful community, and none of the unwelcoming and intolerant
behavior can be attributed to the favorite scapegoat.

Since some holders of opposing positions haven't been treating each
other kindly or respectfully, and it doesn't seem to me that holders of
any positions have made any progress in convincing holders of different
positions recently, may I suggest that we drop this hateful discussion,
or that participants at least bring the GNU Kind Communication
Guidelines back to mind?

Thanks,

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: GCC association with the FSF

[Jonathan Wakely]

On Sat, 10 Apr 2021, 21:10 Alexandre Oliva via Gcc, <gcc@gcc.gnu.org> wrote:

> On Apr 10, 2021, Bronek Kozicki via Gcc <gcc@gcc.gnu.org> wrote:
>
> > It is called "actions have consequences".
>
> FTR, what consequences do you believe would be adequate for such actions
> as spreading difamatory rumors about an innocent person?
>
> I ask because some of the people campaigning against RMS have already
> disclaimed the false accusations in the hateful letter, but others keep
> on resorting to them as if they were true and relevant.
>

The subject of this thread was *supposed* to have changed to be about GNU
and the FSF and whether it benefits GCC to be linked to them, not about RMS.

The fact that some people insist on seeing that question as another attack
on RMS is not helpful, and is part of the problem with being linked to the
cult of GNU. We can't question whether FSF benefits GCC without being
reminded that RMS started the project, and so he must be involved.

I still can't find where in the four freedoms it says anything about
venerating the project leader.

Re: GCC association with the FSF

[Alfred M. Szmidt]

Please move these off-topic discussions somewhere else, people are
already annoyed and angry as it is -- on both sides!

Re: GCC association with the FSF

[David Brown]

On 09/04/2021 20:02, Christopher Dimech wrote:
> 
>> Sent: Saturday, April 10, 2021 at 5:01 AM
>> From: "David Brown" <david.brown@hesbynett.no>

>>
>> Different opinions are fine.  Bringing national or international
>> politics into the discussion (presumably meant to be as an insult) is
>> not fine.  This is not a political discussion - please stop trying to
>> make it one.
> 
> It is an assessment of what you propose.  The removal of people from all
> positions is a political statements.  I have no problem with political
> discussions and certainly don't take instructions from you, to say the 
> least!  What you talk about is exactly what drives Chinese and Russian
> officials to suppress anybody who does not conform with their demands.    
> The consequences will be the same should you and others get your way
> of doing things.

There is a big difference between suppression or censorship, and wanting
people in leadership positions to be representative of the values of the
group they lead.  RMS can have all the opinions he wants, and act has he
will (until he ends up arrested for it), but if he is to remain a
representative for others (FSF, GNU and/or GCC), then he has a duty to
act appropriately according to the values those organisations think are
important.

I think that you mix up freedom and free reins.  Freedom is not anarchy.
 Being free from sexism, prejudice, bullying, and harassment are as
important as freedom of speech or politics.

>>
>> We (the free software world) does not need a person with the qualities
>> of RMS any more - that is the point.  There should not be such a
>> position as "Chief GNUsance".
>  
> Secondly,  I cannot clearly see what status you have for making statements
> that imply a representation for the free software world!!!
> 

I have said very clearly that I am a user of gcc - not a developer, and
the opinions I express are very much my own.  The does not hinder me
from saying what I think the free software world (developers and users)
want or need.  I have not made any claims or suggestions that I am privy
to the minds of others, or that my opinions and ideas are in any way
more weighty than those of others.

Re: GCC association with the FSF

[Jonathan Wakely]

On Sat, 10 Apr 2021, 13:50 David Brown, <david.brown@hesbynett.no> wrote:

> On 09/04/2021 20:02, Christopher Dimech wrote:
> >
> >> Sent: Saturday, April 10, 2021 at 5:01 AM
> >> From: "David Brown" <david.brown@hesbynett.no>
>
> >>
> >> Different opinions are fine.  Bringing national or international
> >> politics into the discussion (presumably meant to be as an insult) is
> >> not fine.  This is not a political discussion - please stop trying to
> >> make it one.
> >
> > It is an assessment of what you propose.  The removal of people from all
> > positions is a political statements.  I have no problem with political
> > discussions and certainly don't take instructions from you, to say the
> > least!  What you talk about is exactly what drives Chinese and Russian
> > officials to suppress anybody who does not conform with their demands.
>
> > The consequences will be the same should you and others get your way
> > of doing things.
>
> There is a big difference between suppression or censorship, and wanting
> people in leadership positions to be representative of the values of the
> group they lead.  RMS can have all the opinions he wants, and act has he
> will (until he ends up arrested for it), but if he is to remain a
> representative for others (FSF, GNU and/or GCC), then he has a duty to
> act appropriately according to the values those organisations think are
> important.
>
> I think that you mix up freedom and free reins.  Freedom is not anarchy.
>  Being free from sexism, prejudice, bullying, and harassment are as
> important as freedom of speech or politics.
>
> >>
> >> We (the free software world) does not need a person with the qualities
> >> of RMS any more - that is the point.  There should not be such a
> >> position as "Chief GNUsance".
> >
> > Secondly,  I cannot clearly see what status you have for making
> statements
> > that imply a representation for the free software world!!!
> >
>
> I have said very clearly that I am a user of gcc - not a developer, and
> the opinions I express are very much my own.  The does not hinder me
> from saying what I think the free software world (developers and users)
> want or need.  I have not made any claims or suggestions that I am privy
> to the minds of others, or that my opinions and ideas are in any way
> more weighty than those of others.
>

David is a frequent contributor to the mailing lists, helping other users
with their questions about GCC. That's a lot more than can be said for most
of the new posters who have appeared here for the first time recently,
trying to influence how we run the project.

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Sunday, April 11, 2021 at 12:27 AM
> From: "David Brown" <david.brown@hesbynett.no>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "John Darrington" <john@darrington.wattle.id.au>, "David Malcolm" <dmalcolm@redhat.com>, gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On 09/04/2021 20:02, Christopher Dimech wrote:
> > 
> >> Sent: Saturday, April 10, 2021 at 5:01 AM
> >> From: "David Brown" <david.brown@hesbynett.no>
> 
> >>
> >> Different opinions are fine.  Bringing national or international
> >> politics into the discussion (presumably meant to be as an insult) is
> >> not fine.  This is not a political discussion - please stop trying to
> >> make it one.
> > 
> > It is an assessment of what you propose.  The removal of people from all
> > positions is a political statements.  I have no problem with political
> > discussions and certainly don't take instructions from you, to say the 
> > least!  What you talk about is exactly what drives Chinese and Russian
> > officials to suppress anybody who does not conform with their demands.    
> > The consequences will be the same should you and others get your way
> > of doing things.
> 
> There is a big difference between suppression or censorship, and wanting
> people in leadership positions to be representative of the values of the
> group they lead.  RMS can have all the opinions he wants, and act has he
> will (until he ends up arrested for it), but if he is to remain a
> representative for others (FSF, GNU and/or GCC), then he has a duty to
> act appropriately according to the values those organisations think are
> important.

If you look at the history of computing you will find that it was mostly
crooks and people of very mixed kind of qualities.  Not al all saints.
Many of them quite unscrupolous and not very clever.  And still they managed
to do great things. 
  
So it tells a kid: They could do that, why can't you?  That was
certainly what turned me on.  Freedom 0 also says "The freedom to run
a program as you wish, for any purpose".

Should we get our ideas from politicians and bureaucrats; or from Aleksandr
Solzhenitsyn, Fyodor Dostoyevsky, Friedrich Nietzsche, Ernest Hemingway, 
Aldous Huxley, Marie-Henri Beyle, and Emily Jane Brontë?  From the latter
of course!


> I think that you mix up freedom and free reins.  Freedom is not anarchy.
>  Being free from sexism, prejudice, bullying, and harassment are as
> important as freedom of speech or politics.
> 
> >>
> >> We (the free software world) does not need a person with the qualities
> >> of RMS any more - that is the point.  There should not be such a
> >> position as "Chief GNUsance".
> >  
> > Secondly,  I cannot clearly see what status you have for making statements
> > that imply a representation for the free software world!!!
> > 
> 
> I have said very clearly that I am a user of gcc - not a developer, and
> the opinions I express are very much my own.  The does not hinder me
> from saying what I think the free software world (developers and users)
> want or need.  I have not made any claims or suggestions that I am privy
> to the minds of others, or that my opinions and ideas are in any way
> more weighty than those of others.
> 
>

Re: GCC association with the FSF

[Thomas Rodgers]

On 2021-04-09 14:34, Christopher Dimech wrote:

>> On the contrary, I eagerly await each and every one of your missives 
>> on
>> this topic, hoping for exactly that very  thing to occur.

> I do not see how you and your friends at redhat could really get any 
> value
> from it, because being a seeker of truth means refusing to make 
> assumptions
> about things that you do not know. The moment you assume that you know 
> because
> of what you believe, your intelligence will sleep. It is my wish and my 
> blessing
> that every human being has their intelligence awake.

On 2021-04-10 07:49, Christopher Dimech via Gcc wrote:

>> There is a big difference between suppression or censorship, and 
>> wanting
>> people in leadership positions to be representative of the values of 
>> the
>> group they lead.  RMS can have all the opinions he wants, and act has 
>> he
>> will (until he ends up arrested for it), but if he is to remain a
>> representative for others (FSF, GNU and/or GCC), then he has a duty to
>> act appropriately according to the values those organisations think 
>> are
>> important.
> If you look at the history of computing you will find that it was 
> mostly
> crooks and people of very mixed kind of qualities.  Not al all saints.
> Many of them quite unscrupolous and not very clever.  And still they 
> managed
> to do great things.
> 
> So it tells a kid: They could do that, why can't you?  That was
> certainly what turned me on.  Freedom 0 also says "The freedom to run
> a program as you wish, for any purpose".
> 
> Should we get our ideas from politicians and bureaucrats; or from 
> Aleksandr
> Solzhenitsyn, Fyodor Dostoyevsky, Friedrich Nietzsche, Ernest 
> Hemingway,
> Aldous Huxley, Marie-Henri Beyle, and Emily Jane Brontë?  From the 
> latter
> of course!

So, that's a solid 'no' on the likelihood of you contributing anything 
of value
to the discussion of GCC governance then?

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Sunday, April 11, 2021 at 3:17 AM
> From: "Thomas Rodgers" <rodgert@appliantology.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "David Brown" <david.brown@hesbynett.no>, gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On 2021-04-09 14:34, Christopher Dimech wrote:
> 
> >> On the contrary, I eagerly await each and every one of your missives 
> >> on
> >> this topic, hoping for exactly that very  thing to occur.
> 
> > I do not see how you and your friends at redhat could really get any 
> > value
> > from it, because being a seeker of truth means refusing to make 
> > assumptions
> > about things that you do not know. The moment you assume that you know 
> > because
> > of what you believe, your intelligence will sleep. It is my wish and my 
> > blessing
> > that every human being has their intelligence awake.
> 
> On 2021-04-10 07:49, Christopher Dimech via Gcc wrote:
> 
> >> There is a big difference between suppression or censorship, and 
> >> wanting
> >> people in leadership positions to be representative of the values of 
> >> the
> >> group they lead.  RMS can have all the opinions he wants, and act has 
> >> he
> >> will (until he ends up arrested for it), but if he is to remain a
> >> representative for others (FSF, GNU and/or GCC), then he has a duty to
> >> act appropriately according to the values those organisations think 
> >> are
> >> important.
> > If you look at the history of computing you will find that it was 
> > mostly
> > crooks and people of very mixed kind of qualities.  Not al all saints.
> > Many of them quite unscrupolous and not very clever.  And still they 
> > managed
> > to do great things.
> > 
> > So it tells a kid: They could do that, why can't you?  That was
> > certainly what turned me on.  Freedom 0 also says "The freedom to run
> > a program as you wish, for any purpose".
> > 
> > Should we get our ideas from politicians and bureaucrats; or from 
> > Aleksandr
> > Solzhenitsyn, Fyodor Dostoyevsky, Friedrich Nietzsche, Ernest 
> > Hemingway,
> > Aldous Huxley, Marie-Henri Beyle, and Emily Jane Brontë?  From the 
> > latter
> > of course!
> 
> So, that's a solid 'no' on the likelihood of you contributing anything 
> of value
> to the discussion of GCC governance then?

There are many instances when one has to work with people, even though 
one does not personally like them.  I have worked with others in the
Free Software Community that have placed themselves on the opposite side
of the debate.  And have no intention of stopping them working.

I also worked with others, including MEPs in Brussels, etc.  There's no
way out of it.  Eventually, one has to get out of bed and face the world.

Irrespective of the attitudes that we take on what we like, and on what we 
don't like.   I like this person, I don't like this person.  Now with this
person, I will do things willingly.  With this other person, I will do things
unwillingly.   But the reality is that everybody is oscillating between 
a good person and a bad person.  It is important to understand this.

If you create a very pleasant wonderful atmosphere, everybody behaves
wonderfully.  If you create an unpleasant atmosphere, a whole lot of
people act nasty.  That's how it is. 

The moment we think we are good, we are entitled to destroy the bad,
isn't it? 

Regards
Christopher

Re: GCC association with the FSF

[Thomas Rodgers]

On 2021-04-10 08:54, Christopher Dimech wrote:

<...snip...>

> If you create a very pleasant wonderful atmosphere, everybody behaves
> wonderfully.  If you create an unpleasant atmosphere, a whole lot of
> people act nasty.  That's how it is.

This is crux of it really. For many RMS has very much created that 
unpleasant atmosphere full
of people acting nasty, and a few decades on, some people, notably those 
that do significant
amounts of work on a project he may have been part of two decades ago, 
no longer want any kind
of association between their work product and the toxic environment of 
'people acting nasty'
that he (for a multitude of reasons) engenders.

We are done here.

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Sunday, April 11, 2021 at 4:14 AM
> From: "Thomas Rodgers" <rodgert@appliantology.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "David Brown" <david.brown@hesbynett.no>, gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On 2021-04-10 08:54, Christopher Dimech wrote:
>
> <...snip...>
>
> > If you create a very pleasant wonderful atmosphere, everybody behaves
> > wonderfully.  If you create an unpleasant atmosphere, a whole lot of
> > people act nasty.  That's how it is.
>
> This is crux of it really. For many RMS has very much created that
> unpleasant atmosphere full
> of people acting nasty, and a few decades on, some people, notably those
> that do significant
> amounts of work on a project he may have been part of two decades ago,
> no longer want any kind
> of association between their work product and the toxic environment of
> 'people acting nasty'
> that he (for a multitude of reasons) engenders.
>
> We are done here.

Would that not have been the job of the organisers?  Have organised
meetings with Richard, including with governmental bodies and
things progressed decently.  Should people have been wronged, in small
ways or big ones, many countries provide recourse for that.

How it is that many want the Gnu Tag he build.  One can simply continue
the work and have a website or some other way for distribution.  I
frequently do that, make software without the Gnu Association.
Gnu could be better with me, but I left the decision for RMS on whether
he wanted new types of projects that were not port of Gnu at the time.

Re: GCC association with the FSF

[David Malcolm]

On Sat, 2021-04-10 at 08:17 -0700, Thomas Rodgers wrote:
> On 2021-04-09 14:34, Christopher Dimech wrote:
> 
> > > On the contrary, I eagerly await each and every one of your
> > > missives 
> > > on
> > > this topic, hoping for exactly that very  thing to occur.

[...]

> On 2021-04-10 07:49, Christopher Dimech via Gcc wrote:
> 
> > 
> > 
> > Should we get our ideas from politicians and bureaucrats; or from 
> > Aleksandr
> > Solzhenitsyn, Fyodor Dostoyevsky, Friedrich Nietzsche, Ernest 
> > Hemingway,
> > Aldous Huxley, Marie-Henri Beyle, and Emily Jane Brontë?  From the 
> > latter
> > of course!
> 
> So, that's a solid 'no' on the likelihood of you contributing
> anything 
> of value
> to the discussion of GCC governance then?

Thomas, please don't feed the troll.

Hope this is constructive
Dave

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Sunday, April 11, 2021 at 3:59 AM
> From: "David Malcolm" <dmalcolm@redhat.com>
> To: "Thomas Rodgers" <rodgert@appliantology.com>, "Christopher Dimech" <dimech@gmx.com>
> Cc: gcc@gnu.org, "David Brown" <david.brown@hesbynett.no>
> Subject: Re: GCC association with the FSF
>
> On Sat, 2021-04-10 at 08:17 -0700, Thomas Rodgers wrote:
> > On 2021-04-09 14:34, Christopher Dimech wrote:
> > 
> > > > On the contrary, I eagerly await each and every one of your
> > > > missives 
> > > > on
> > > > this topic, hoping for exactly that very  thing to occur.
> 
> [...]
> 
> > On 2021-04-10 07:49, Christopher Dimech via Gcc wrote:
> > 
> > > 
> > > 
> > > Should we get our ideas from politicians and bureaucrats; or from 
> > > Aleksandr
> > > Solzhenitsyn, Fyodor Dostoyevsky, Friedrich Nietzsche, Ernest 
> > > Hemingway,
> > > Aldous Huxley, Marie-Henri Beyle, and Emily Jane Brontë?  From the 
> > > latter
> > > of course!
> > 
> > So, that's a solid 'no' on the likelihood of you contributing
> > anything 
> > of value
> > to the discussion of GCC governance then?
> 
> Thomas, please don't feed the troll.
> Hope this is constructive
 
Yes, it is better.

Regards
Christopher 

Re: GCC association with the FSF

[Richard Kenner]

> So, that's a solid 'no' on the likelihood of you contributing
> anything of value to the discussion of GCC governance then?

I really think that most of the people replying on this thread have a
much more encompassing view of "GCC governance" than actually exists.

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Sunday, April 11, 2021 at 8:10 AM
> From: "Richard Kenner" <kenner@vlsi1.ultra.nyu.edu>
> To: rodgert@appliantology.com
> Cc: david.brown@hesbynett.no, dimech@gmx.com, gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> > So, that's a solid 'no' on the likelihood of you contributing
> > anything of value to the discussion of GCC governance then?
>
> I really think that most of the people replying on this thread have a
> much more encompassing view of "GCC governance" than actually exists.

If the community makes it too hard by demanding too much (which seems to me
that it is bending towards the merely bureaucratic), people would be discouraged
to serve on it.

Years ago I proposed Committee Refreshments and Committee Rotations
for School Governing Bodies in the United Kingdom, which was supported
by the Department for Education and Skills of the UK Government that
existed until 2007.  A strategy that can potentially resolve a lot of
problems within the free software community.

I also suggest the concept of logrolling with laid down safeguards first
applied to legislation by US Congressman David Crockett in about 1835.
This does have benefits in direct democracies.

Regards
Christopher

Re: GCC association with the FSF

[Richard Kenner]

> > > So, that's a solid 'no' on the likelihood of you contributing
> > > anything of value to the discussion of GCC governance then?
> >
> > I really think that most of the people replying on this thread have a
> > much more encompassing view of "GCC governance" than actually exists.
> 
> If the community makes it too hard by demanding too much (which
> seems to me that it is bending towards the merely bureaucratic),
> people would be discouraged to serve on it.

I'm sorry, what is it that you think that the "community" (whatever
that is) is demanding too much of?

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Monday, April 12, 2021 at 1:11 AM
> From: "Richard Kenner" <kenner@vlsi1.ultra.nyu.edu>
> To: dimech@gmx.com
> Cc: david.brown@hesbynett.no, gcc@gnu.org, rodgert@appliantology.com
> Subject: Re: GCC association with the FSF
>
> > > > So, that's a solid 'no' on the likelihood of you contributing
> > > > anything of value to the discussion of GCC governance then?
> > >
> > > I really think that most of the people replying on this thread have a
> > > much more encompassing view of "GCC governance" than actually exists.
> >
> > If the community makes it too hard by demanding too much (which
> > seems to me that it is bending towards the merely bureaucratic),
> > people would be discouraged to serve on it.
>
> I'm sorry, what is it that you think that the "community" (whatever
> that is) is demanding too much of?

Some have been saying that leaders are representatives of the whole
free software users, and if mistakes happen, they would tarnish everybody.
And then a situation similar to this one starts all over again.

I would say that it is the organisers of events that have such responsibility.

Re: GCC association with the FSF

[Gerald Pfeifer]

On Sat, 10 Apr 2021, Richard Kenner via Gcc wrote:
> I really think that most of the people replying on this thread have a
> much more encompassing view of "GCC governance" than actually exists.

There are a number of people arguing here who have contributed little 
to nothing to GCC, whose names even did not trigger memories - unlike 
David M. or Jonathan, for example, or Nathan or Alexandre.

We generally welcome contributions - technical and otherwise.

When it comes to deciding the direction of a project like GCC - technical 
and otherwise - in my mind it primarily should be those actually involved 
and contributing.

(And, for the record, I have no doubt that all of the other contributors
who have spoken up care a lot about free software and the future of GCC
in that context. That does not necessarily require the FSF, though.)

Gerald

Re: GCC association with the FSF

[John Darrington]

On Sun, Apr 11, 2021 at 12:30:41AM +0200, Gerald Pfeifer wrote:

     There are a number of people arguing here who have contributed little 
     to nothing to GCC, whose names even did not trigger memories - unlike 
     David M. or Jonathan, for example, or Nathan or Alexandre.

For myself, I have been a long term user/contributor to GCC albiet hardly in
a major role.   I don't think I've ever posted to this list until a few days
ago, when all of a sudden these messages started popping up in my inbox.  So
either I subscribed to this list many years ago and it has been dormant until
recently or someone subscribed me just recently.
     
     When it comes to deciding the direction of a project like GCC - technical 
     and otherwise - in my mind it primarily should be those actually involved 
     and contributing.
     
I disagree.  The principle by which high level decisions in all GNU projects
have always been made is how it best helps the GNU system as a whole.
Contributors are exactly that.  They offer *contributions* - the very meaning
of the word implies there is no expectation of anything in return.  Obviously
I hope all contributors *do* get some satisfaction and maybe even some tangible
benefit.  But contributions are not to be seen as a means  to gain control of
the project at a high level.

J'

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Monday, April 12, 2021 at 12:05 AM
> From: "John Darrington" <john@darrington.wattle.id.au>
> To: "Gerald Pfeifer" <gerald@pfeifer.com>
> Cc: gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On Sun, Apr 11, 2021 at 12:30:41AM +0200, Gerald Pfeifer wrote:
>
>      There are a number of people arguing here who have contributed little
>      to nothing to GCC, whose names even did not trigger memories - unlike
>      David M. or Jonathan, for example, or Nathan or Alexandre.
>
> For myself, I have been a long term user/contributor to GCC albiet hardly in
> a major role.   I don't think I've ever posted to this list until a few days
> ago, when all of a sudden these messages started popping up in my inbox.  So
> either I subscribed to this list many years ago and it has been dormant until
> recently or someone subscribed me just recently.
>
>      When it comes to deciding the direction of a project like GCC - technical
>      and otherwise - in my mind it primarily should be those actually involved
>      and contributing.
>
> I disagree.  The principle by which high level decisions in all GNU projects
> have always been made is how it best helps the GNU system as a whole.
> Contributors are exactly that.  They offer *contributions* - the very meaning
> of the word implies there is no expectation of anything in return.  Obviously
> I hope all contributors *do* get some satisfaction and maybe even some tangible
> benefit.  But contributions are not to be seen as a means  to gain control of
> the project at a high level.
>
> J'

There are many instances of project maintainers who are not the major
contributors, but are very capable of leading their project.

Many fail to understand the benefits of knowing the role maintainers
play in alleviating or conquering some of the current challenges that
interdisciplinary projects face.  Although I agree that they need to
possess technical experience too.  I see many MBAs trying to parachute
in as a leader without having worked their way up.

Regards
Christopher

Re: GCC association with the FSF

[Richard Kenner]

> The principle by which high level decisions in all GNU projects have
> always been made is how it best helps the GNU system as a whole.
> Contributors are exactly that.  They offer *contributions* - the
> very meaning of the word implies there is no expectation of anything
> in return.  Obviously I hope all contributors *do* get some
> satisfaction and maybe even some tangible benefit.  But
> contributions are not to be seen as a means to gain control of the
> project at a high level.

I agree with most of that, but all *actual* changes to a project are done
by contributors.  If somebody makes a "high level decision" to do a certain
thing to GCC, but no contributor steps up to do that thing, it won't get
done.  Conversely, if some contributor decided to do some thing (e.g., add
an optimization) that nobody made a "high level decision" to do, that
thing *will* get done, since it's unusual to reject such contributions,
assuming they're technically sound.

So I think that the bulk of the "power", from a practical standpoint, is
in the hands of the contributors, not some high-level group.

Re: GCC association with the FSF

[Jonathan Wakely]

On Sun, 11 Apr 2021, 13:31 John Darrington wrote:

>
> For myself, I have been a long term user/contributor to GCC albiet hardly
> in
> a major role.   I don't think I've ever posted to this list until a few
> days
> ago, when all of a sudden these messages started popping up in my inbox.
> So
> either I subscribed to this list many years ago and it has been dormant
> until
> recently or someone subscribed me just recently.
>

I don't know who changed the Cc from gcc@gcc.gnu.org to gcc@gnu.org but I
think they're the same destination.
You can check the archives, the list has been highly active for decades.
Maybe somebody subscribed you to help brigade this list. If you don't want
the mails, the mail headers have unsubscribe instructions, and there's a
form at https://gcc.gnu.org/lists.html

Re: GCC association with the FSF

[Richard Kenner]

> When it comes to deciding the direction of a project like GCC - technical 
> and otherwise - in my mind it primarily should be those actually involved 
> and contributing.

I agree, but I'm not clear if you're claiming that that is or is not
currently the case.  I believe it is.

Re: GCC association with the FSF

[Alexandre Oliva]

On Apr 10, 2021, Gerald Pfeifer <gerald@pfeifer.com> wrote:

> When it comes to deciding the direction of a project like GCC - technical 
> and otherwise - in my mind it primarily should be those actually involved 
> and contributing.

GNU follows the general principle of the Free Software movement, that
freedom for *users* is the priority.  Assigning *higher* importance to
developers' preferences is *not* a position I share.

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: GCC association with the FSF

[Frosku]

On Sun Apr 11, 2021 at 2:23 PM BST, Alexandre Oliva via Gcc wrote:
> On Apr 10, 2021, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> > When it comes to deciding the direction of a project like GCC - technical 
> > and otherwise - in my mind it primarily should be those actually involved 
> > and contributing.
>
> GNU follows the general principle of the Free Software movement, that
> freedom for *users* is the priority. Assigning *higher* importance to
> developers' preferences is *not* a position I share.

I feel like this should be even more evident when dealing with something like
a compiler toolchain. GCC's user is likely to be another free software project's
contributor (as is my case).

Re: GCC association with the FSF

[Richard Kenner]

> I feel like this should be even more evident when dealing with
> something like a compiler toolchain. GCC's user is likely to be
> another free software project's contributor (as is my case).

I suspect that's not true.  It certainly wasn't true when more major
large companies used GCC to compile their products and I doubt it's even
true now when many have switched to other compilers.

Re: GCC association with the FSF

[Richard Kenner]

> > When it comes to deciding the direction of a project like GCC - technical 
> > and otherwise - in my mind it primarily should be those actually involved 
> > and contributing.
> 
> GNU follows the general principle of the Free Software movement, that
> freedom for *users* is the priority.  Assigning *higher* importance to
> developers' preferences is *not* a position I share.

I think there's a difference between philosophy and practicality here.
Sure, the importance of work done by different developers, measured on
the scale of advancing the goals of the Free Software movement, is
different for each.  But what actually advances a project (which can
be viewed as "deciding [its] direction") is what work developers
choose to do, not the importance of each piece of work on that metric.
So I certainly agree with what you said above, but don't think that
changes the reality that it's ultimately what developers choose to
work on that most affects the direction of a project.

Re: GCC association with the FSF

[John Darrington]

On Sun, Apr 11, 2021 at 09:30:48AM -0400, Richard Kenner via Gcc wrote:
     > > When it comes to deciding the direction of a project like GCC - technical 
     > > and otherwise - in my mind it primarily should be those actually involved 
     > > and contributing.
     > 
     > GNU follows the general principle of the Free Software movement, that
     > freedom for *users* is the priority.  Assigning *higher* importance to
     > developers' preferences is *not* a position I share.
     
     I think there's a difference between philosophy and practicality here.
     Sure, the importance of work done by different developers, measured on
     the scale of advancing the goals of the Free Software movement, is
     different for each.  But what actually advances a project (which can
     be viewed as "deciding [its] direction") is what work developers
     choose to do, not the importance of each piece of work on that metric.

I guess my point is that the direction in which a project *does* go is not
always the direction in which it *should* go.  I conceed that the converse
is also true:  Technical experts are very useful for putting the brakes on
Joe Average User's crazy ideas when they are doomed to failure from the outset.

     So I certainly agree with what you said above, but don't think that
     changes the reality that it's ultimately what developers choose to
     work on that most affects the direction of a project.

That indeed is often the reality, but equally as often *not* what is desired.
To give just one small practical example, I'm told (by people who are more
familiar with GCC internals than I) that it is not feasible with today's
GCC to port to backends which have a small number of registers.   This has
meant that whole familys of CPUs work only with proprietary compilers.

J'

Re: GCC association with the FSF

[Richard Kenner]

> I guess my point is that the direction in which a project *does* go is not
> always the direction in which it *should* go.  

I agree.  And depending on people's "political" views, that can either be
an advantage or disadvantage of the free software development model.

> To give just one small practical example, I'm told (by people who are more
> familiar with GCC internals than I) that it is not feasible with today's
> GCC to port to backends which have a small number of registers.

[Finally, a technical discussion in this thread!]

It never really has been.  Maybe it's not even possible now (I don't
know), but if you tried it in the past the results would never have
been very good.  Almost all multi-backend systems operate by having
very large numbers of expressions at all levels, which you gradually
lower to actual registers.  This works quite well if you have enough
registers to hold the high-usage expressions in them, but when you
have high register pressure, the model breaks down completely.
Although the situation may well have gotten worse in recent versions
that I'm not familiar with, I'd say that GCC was probably doing a
*better* job with a small number of registers in more recent versions
than in older ones: "reload" was particularly bad when there was high
register pressure.

When your main constraint is register pressure, in order to get
high-quality results, I think you almost have to change the entire
philosophy of compilation, to the point I think where you have an
almost entirely different compilation chain for such machines.

Re: GCC association with the FSF

[David Brown]

On 11/04/2021 16:37, Richard Kenner via Gcc wrote:
>> I guess my point is that the direction in which a project *does* go is not
>> always the direction in which it *should* go.  
> 
> I agree.  And depending on people's "political" views, that can either be
> an advantage or disadvantage of the free software development model.
> 
>> To give just one small practical example, I'm told (by people who are more
>> familiar with GCC internals than I) that it is not feasible with today's
>> GCC to port to backends which have a small number of registers.
> 
> [Finally, a technical discussion in this thread!]
> 
> It never really has been.  Maybe it's not even possible now (I don't
> know), but if you tried it in the past the results would never have
> been very good.  Almost all multi-backend systems operate by having
> very large numbers of expressions at all levels, which you gradually
> lower to actual registers.  This works quite well if you have enough
> registers to hold the high-usage expressions in them, but when you
> have high register pressure, the model breaks down completely.
> Although the situation may well have gotten worse in recent versions
> that I'm not familiar with, I'd say that GCC was probably doing a
> *better* job with a small number of registers in more recent versions
> than in older ones: "reload" was particularly bad when there was high
> register pressure.
> 
> When your main constraint is register pressure, in order to get
> high-quality results, I think you almost have to change the entire
> philosophy of compilation, to the point I think where you have an
> almost entirely different compilation chain for such machines.
> 

Low register count cpu designs have been out of fashion for quite some
time now (perhaps precisely because they are not a good fit for common
compiler strategies).  They are mostly found in older families, such as
the 8-bit CISC designs in older microcontrollers (8051, PIC, COP8, 6502,
etc.).  And you are absolutely right that you need a different way of
thinking in order to get the best out of such chips - low register count
is only one aspect.  Other issues are few or no flexible pointer
registers, no "SP + offset" addressing modes for efficient parameters or
stack frames, banked ram and code blocks, and multiple separate address
spaces.  Good toolchains for such devices need to work in a very
different way, and typically encompass compilation, assembling and
linking in one "omniscient" build so that variables, parameters, etc.,
can be placed statically in ways that minimise banking and maximise
reuse, based on lifetime analysis of the whole program.

This would be a massively different way of working from how gcc does
things now, and given that such devices are very much on the decline
(when 32-bit ARM microcontrollers can be bought for 30 cents, smaller
and cheaper cpu cores are rarely the right choice for a new design), it
would not make sense to spend the effort supporting them in gcc.  There
is, after all, quite a solid GPL'ed compiler toolchain for such devices
at <http://sdcc.sourceforge.net/>.

Re: GCC association with the FSF

[Ian Lance Taylor]

On Sun, Apr 11, 2021 at 8:04 AM David Brown <david.brown@hesbynett.no> wrote:
>
> On 11/04/2021 16:37, Richard Kenner via Gcc wrote:
> >> I guess my point is that the direction in which a project *does* go is not
> >> always the direction in which it *should* go.
> >
> > I agree.  And depending on people's "political" views, that can either be
> > an advantage or disadvantage of the free software development model.
> >
> >> To give just one small practical example, I'm told (by people who are more
> >> familiar with GCC internals than I) that it is not feasible with today's
> >> GCC to port to backends which have a small number of registers.
> >
> > [Finally, a technical discussion in this thread!]
> >
> > It never really has been.  Maybe it's not even possible now (I don't
> > know), but if you tried it in the past the results would never have
> > been very good.  Almost all multi-backend systems operate by having
> > very large numbers of expressions at all levels, which you gradually
> > lower to actual registers.  This works quite well if you have enough
> > registers to hold the high-usage expressions in them, but when you
> > have high register pressure, the model breaks down completely.
> > Although the situation may well have gotten worse in recent versions
> > that I'm not familiar with, I'd say that GCC was probably doing a
> > *better* job with a small number of registers in more recent versions
> > than in older ones: "reload" was particularly bad when there was high
> > register pressure.
> >
> > When your main constraint is register pressure, in order to get
> > high-quality results, I think you almost have to change the entire
> > philosophy of compilation, to the point I think where you have an
> > almost entirely different compilation chain for such machines.
> >
>
> Low register count cpu designs have been out of fashion for quite some
> time now (perhaps precisely because they are not a good fit for common
> compiler strategies).  They are mostly found in older families, such as
> the 8-bit CISC designs in older microcontrollers (8051, PIC, COP8, 6502,
> etc.).  And you are absolutely right that you need a different way of
> thinking in order to get the best out of such chips - low register count
> is only one aspect.  Other issues are few or no flexible pointer
> registers, no "SP + offset" addressing modes for efficient parameters or
> stack frames, banked ram and code blocks, and multiple separate address
> spaces.  Good toolchains for such devices need to work in a very
> different way, and typically encompass compilation, assembling and
> linking in one "omniscient" build so that variables, parameters, etc.,
> can be placed statically in ways that minimise banking and maximise
> reuse, based on lifetime analysis of the whole program.
>
> This would be a massively different way of working from how gcc does
> things now, and given that such devices are very much on the decline
> (when 32-bit ARM microcontrollers can be bought for 30 cents, smaller
> and cheaper cpu cores are rarely the right choice for a new design), it
> would not make sense to spend the effort supporting them in gcc.  There
> is, after all, quite a solid GPL'ed compiler toolchain for such devices
> at <http://sdcc.sourceforge.net/>.

I think it depends on your goals.  In the past I've ported GCC to a
Harvard architecture system with six registers.  I agree that the code
quality was not the highest possible.  But the port worked fine, and
for this process performance was not an issue.  (As you suggest, I
tend to think that for most people who choose a processor with a small
number of registers, performance is not an issue.  Where performance
matters a lot, spend the money for a real processor, or at least use a
RISC/V.)

Ian

Re: GCC association with the FSF

[Jonathan Wakely]

On Sun, 11 Apr 2021, 14:59 Alexandre Oliva via Gcc, <gcc@gcc.gnu.org> wrote:

> On Apr 10, 2021, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> > When it comes to deciding the direction of a project like GCC -
> technical
> > and otherwise - in my mind it primarily should be those actually
> involved
> > and contributing.
>
> GNU follows the general principle of the Free Software movement, that
> freedom for *users* is the priority.  Assigning *higher* importance to
> developers' preferences is *not* a position I share.
>


Freedom for users is provided by the licences of the GCC code. Any
particular form of leadership or veneration of the project founder is not
required for that be true. Unless maybe I'm still misreading the four
freedoms, or maybe they are not a proper description of the principles.
Maybe the four freedoms need to be corrected to add this implicit
requirement that association with a particular group is necessary. Could
you look into that please, Alex?

Re: GCC association with the FSF

[Alexandre Oliva]

Jonathan,

It's very offensive for you to misattribute a disagreeing position as
veneration.

I could name many reasons for me to disagree with yours, including
justice, truth, honesty, tolerance, freedom of speech and unity of the
movement.

If anything, it's threatening to abandon a project over false
allegations about a person, on occasion of that person rejoining the
board of an organization that was founded and has always supported the
project who's still led by that person, that makes the issue personal
and based on blind faith, though in the opposite sense of veneration.

If you find any offense in the previous paragraph, you understand
exactly why I feel offended by your retort, so please try to take that
into account in your attempts to participate in a kind debate.

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: GCC association with the FSF

[Jonathan Wakely]

On Sun, 11 Apr 2021, 19:28 Alexandre Oliva, <oliva@gnu.org> wrote:

> Jonathan,
>
> It's very offensive for you to misattribute a disagreeing position as
> veneration.
>

There have been many posts over the past two weeks suggesting that without
RMS to guide us, GCC will become a pawn of the NSA, or that nobody has any
authority to decide on the future of GNU projects except RMS (a view also
stated on GNU mailing lists by moderators of those very lists), or other
silly claims that are based on little but veneration. They're not really
based on anything about GCC, just "y u no like RMS?"





> I could name many reasons for me to disagree with yours, including
> justice, truth, honesty, tolerance, freedom of speech and unity of the
> movement.
>
> If anything, it's threatening to abandon a project over false
> allegations about a person, on occasion of that person rejoining the
> board of an organization that was founded and has always supported the
> project who's still led by that person, that makes the issue personal
> and based on blind faith, though in the opposite sense of veneration.
>

Oh I have other reasons to consider the FSF a dead end too.


> If you find any offense in the previous paragraph, you understand
> exactly why I feel offended by your retort, so please try to take that
> into account in your attempts to participate in a kind debate.
>

Kind debate. Right.

Maybe somebody from the GNU project or the FSF could tell one of their GNU
Maintainers (apparently part of the governance structure of the GNU
project) to stop calling people mad, or rats, or to stop endless off-topic
trolling about communism. There is no kind debate when every other post is
an attack from a troll.

Your own emails are always carefully considered (and carefully skate around
the actual issues people raised) but most of the other voices objecting to
the requests to make changes to GCC are coming from outsiders who are only
too happy to insult GCC devs and derail any "debate".

Re: GCC association with the FSF

[Alexandre Oliva]

On Apr 11, 2021, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:

> There have been many posts over the past two weeks [...] based on
> little but veneration.

> Your own emails are always carefully considered

Thanks for confirming it.

Now, you were responding to me, not to the other posters.


As usual among RMS critics (see?, I've made an effort to resist the
unkindness of de-venerators), he, and apparently now me too, are somehow
held responsible for actions of others, just because they seem to
support some position you disagree with.  That's not right.

I wouldn't say people who undersigned a hate letter full of lies have
lied themselves.  Those who have been misled did not lie, even if the
words they honestly believed in were false, whatever it was that got
them to believe them.

Similarly, people who support a position you disagree with are not pawns
in an army of brainless creatures guided by your favorite monster.  They
are independent individuals with very different beliefs and motivations
who, for their own reasons, formulated their own theories as to why
people have fallen for such lies, or used them as levers to promote
actions where other not-so-shocking truths failed before.

Remember how much hate RMS got in glibc land for something I did?  I
said I did it out of my own volition, I explained my why I did it, but
people wouldn't believe he had nothing to do with it!  That's what I'm
talking about.  It's the same undeserved hatred that he got from Nathan
for his assumption that delays had something to do with RMS's
interference.  Even when he explicitly disapproves actions by misguided
supporters, he still gets hate over their actions.

Does that sound reasonable to you?

As in, do you agree to be held responsible for any speech or action by
anyone who happens to be favorable to the libstdc++ fork you are
proposing right now?


I didn't think so.

I hereby invoke the golden rule.


>> If you find any offense in the previous paragraph, you understand
>> exactly why I feel offended by your retort, so please try to take that
>> into account in your attempts to participate in a kind debate.

> Kind debate. Right.

You were addressing me, and I responded to that.

Have *I* been unkind in the debate I'm carrying out with you?

If you wish to lump me together with everyone else to whom you attribute
the same position that I hold, do you acknowledge that I'd be entitled
to hold you to a similar standard, and lump you with the shills and
liars behind a hate letter that failed a decapitation attack, but may
have partially succeeded at a divide-and-conquer attack on our movement?


> the requests to make changes to GCC are coming from outsiders who are only
> too happy to insult GCC devs and derail any "debate".

Some of the voices in favor of making changes have also come from
outsiders to GCC.

Did I miss your objections to their contributing their outsiders'
thoughts, or to their unkindness?

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: GCC association with the FSF

[Adhemerval Zanella]

> Il giorno 11 apr 2021, alle ore 17:45, Alexandre Oliva via Gcc <gcc@gcc.gnu.org> ha scritto:
> 
> Remember how much hate RMS got in glibc land for something I did?  I
> said I did it out of my own volition, I explained my why I did it, but
> people wouldn't believe he had nothing to do with it! 

It was clear to me and others glibc maintainers that it was *you* who bypass the consensus to *not* reinstate the “joke”. And there was no hate (at least not from my side) only *disappointment* that you used your status to do it even though most of senior developers and maintainers said explicitly you shouldn’t do it.

Re: GCC association with the FSF

[Alexandre Oliva]

On Apr 11, 2021, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:

> It was clear to me and others glibc maintainers that it was *you* who
> bypass the consensus to *not* reinstate the “joke”.

I think you wrote it backwards: what I did was to revert the commit that
the person who put it in agreed shouldn't have been made at that point,
so that the debate about whether or not to install the patch could be
carried out without the fait accompli.  To my surprise, it stopped.

Then, a year or so later, when most of the GNU policies that incided on
that matter had already been discussed and approved, and they suggested
(at least to me) that the conclusion was likely that the patch was in
line with them, some other situation came up that reminded people of the
patch, it was discussed under the heat of the unrelated situation (which
I also found inappropriate), but it got applied AFAICT in accordance
with GNU and GLIBC policies.

> maintainers said explicitly you shouldn’t do it.

I do not see nor recall any such responses or reactions to my offer to
revert the patch in case the installer wouldn't do it, except the
installer saying they wouldn't do the reversal.  Eventually I did it.
After the fact, some said I shouldn't have done it.


That's my recollection of the events.

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: GCC association with the FSF

[Adhemerval Zanella]

On Sun, Apr 11, 2021 at 8:06 PM Alexandre Oliva <oliva@gnu.org> wrote:
>
> On Apr 11, 2021, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
>
> > It was clear to me and others glibc maintainers that it was *you* who
> > bypass the consensus to *not* reinstate the “joke”.
>
> I think you wrote it backwards: what I did was to revert the commit that
> the person who put it in agreed shouldn't have been made at that point,
> so that the debate about whether or not to install the patch could be
> carried out without the fait accompli.  To my surprise, it stopped.
>
> Then, a year or so later, when most of the GNU policies that incided on
> that matter had already been discussed and approved, and they suggested
> (at least to me) that the conclusion was likely that the patch was in
> line with them, some other situation came up that reminded people of the
> patch, it was discussed under the heat of the unrelated situation (which
> I also found inappropriate), but it got applied AFAICT in accordance
> with GNU and GLIBC policies.

RMS briefly stated that he did not want the change to be applied, we
considered his
input back then but we decided to remove the joke *regardless* of what
he thought
about the subject. And you used this to state the change had no consensus to
reinstate it in a way that we haven't done in the project for a couple
of years and which
caused a lot of disarray. The problem was not that you did it, but how
you did it.

You then spent a lot of days trying to convince other glibc
maintainers about your
actions to the point that Torvald and Siddhesh were fed up with your rhetoric.

>
> > maintainers said explicitly you shouldn’t do it.
>
> I do not see nor recall any such responses or reactions to my offer to
> revert the patch in case the installer wouldn't do it, except the
> installer saying they wouldn't do the reversal.  Eventually I did it.
> After the fact, some said I shouldn't have done it.
>
>
> That's my recollection of the events.

All the other active maintainers suggested you shouldn't have done that, but you
ignored it anyway. And we did not want to start a potential contention of patch
applying and reversion from that petty discussion.

But this is done and I don't want to dig into this. My point is *we*
glibc maintainers
were fully aware that it was *you* that decided to act in that way and
it was not my
feelings that it was *hate* the dominant response, but rather a lot of
frustration and
disappointment from how you acted.

Re: GCC association with the FSF

[Alexandre Oliva]

On Apr 11, 2021, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:

> All the other active maintainers suggested you shouldn't have done that, but you
> ignored it anyway.

How could I possibly have ignored something that hadn't happened yet?

> *we* glibc maintainers were fully aware that it was *you* that decided
> to act in that way

There have been plenty of insinuations that contradict that assumption
and attempted to somehow blame it on RMS, but whether the record has
been set straight on this point now, or if it was straight already, the
point stands.

As recently as a couple of weeks ago someone referred, in this list, to
RMS's voicing his objection to the removal of one of the many pieces he
wrote for the glibc manual, and then setting out to propose and discuss
policies that incided on the matter, as if those were horrible actions.

That was almost as abhorrent as his asking a GNU developer a question
that he could have answered by just downloading the subproject's source
code and looking for the answer himself!  Oh, the horror!


If that's not hatred, I don't really wish to know what is :-/

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: GCC association with the FSF

[Siddhesh Poyarekar]

On 4/12/21 7:13 AM, Alexandre Oliva via Gcc wrote:
> On Apr 11, 2021, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
> 
>> All the other active maintainers suggested you shouldn't have done that, but you
>> ignored it anyway.
> 
> How could I possibly have ignored something that hadn't happened yet?

There are irreconcilable differences in perceptions over the events that 
unfolded then and your comments and Adhemerval's (that, FWIW, I echo as 
glibc not-a-gnu-maintainer-just-a-contributor) are sufficient to signal 
that.  The discussion of the events itself is irrelevant to this thread 
and this mailing list so I suggest we stop this subthread.

Siddhesh

Re: GCC association with the FSF

[Adhemerval Zanella]

On Sun, Apr 11, 2021 at 10:43 PM Alexandre Oliva <oliva@gnu.org> wrote:
>
> On Apr 11, 2021, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
>
> > All the other active maintainers suggested you shouldn't have done that, but you
> > ignored it anyway.
>
> How could I possibly have ignored something that hadn't happened yet?
>
> > *we* glibc maintainers were fully aware that it was *you* that decided
> > to act in that way
>
> There have been plenty of insinuations that contradict that assumption
> and attempted to somehow blame it on RMS, but whether the record has
> been set straight on this point now, or if it was straight already, the
> point stands.

No, you are insinuating that the glibc community both as maintainer
and contributors
acted in a hateful way regarding the 'joke' removal. Sorry, but this
is not true; there
were messages that might be characterized as such but they did not come from
either of main glibc developers or maintainers.

>
> As recently as a couple of weeks ago someone referred, in this list, to
> RMS's voicing his objection to the removal of one of the many pieces he
> wrote for the glibc manual, and then setting out to propose and discuss
> policies that incided on the matter, as if those were horrible actions.
>
> That was almost as abhorrent as his asking a GNU developer a question
> that he could have answered by just downloading the subproject's source
> code and looking for the answer himself!  Oh, the horror!
>
>
> If that's not hatred, I don't really wish to know what is :-/

The main idea, which I was vocal about and shared with some glibc
developers and
maintainers, was that the "joke" has no place in a technical manual. You might
disagree ideological and politically from this assessment, but this it
is not "hatred" and
this very rhetoric is trying to characterize it as such is what made
me see that discussion
as frustrating and disappointing.

Re: GCC association with the FSF

[Alexandre Oliva]

On Apr 12, 2021, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:

> No, you are insinuating that the glibc community both as maintainer
> and contributors acted in a hateful way regarding the 'joke'
> removal. Sorry, but this is not true;

Easy to say for someone who hasn't been the target of hate, but it's
just that it was there right then, it's *remains* there.  Not exclusive
among glibc maintainers, and certainly not unanimous among them, but
there.  I may even have earned it myself.  But the one that Richard got
over incorrect assumptions that he commanded the reversal, that's just
another false piece of evidence often used to support the hate campaign.

> The main idea, which I was vocal about and shared with some glibc
> developers and maintainers, was that the "joke" has no place in a
> technical manual.

I understand there is consensus about that now, but back then there were
too many unsettled policy issues to make that call consensually among
all relevant parties.

The main disagreement was not over the issue proper, though.  It was
about procedure, and then it was about whose opinions as much as
counted.


It was a really trivial issue, but sufficiently hot-button and
triggering enough underlying issues that it got to be exploited
politically in several ugly ways.

It can't really be understood without looking into broader contexts that
had long been mounting, and that again quite explicit in this list too.


But I hope we can all agree that it was a horrible mess.

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: GCC association with the FSF

[Adhemerval Zanella]

On 12/04/2021 14:52, Alexandre Oliva wrote:
> On Apr 12, 2021, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
> 
>> No, you are insinuating that the glibc community both as maintainer
>> and contributors acted in a hateful way regarding the 'joke'
>> removal. Sorry, but this is not true;
> 
> Easy to say for someone who hasn't been the target of hate, but it's
> just that it was there right then, it's *remains* there.  Not exclusive
> among glibc maintainers, and certainly not unanimous among them, but
> there.  I may even have earned it myself.  But the one that Richard got
> over incorrect assumptions that he commanded the reversal, that's just
> another false piece of evidence often used to support the hate campaign.

There were no "hate" campaign from glibc developers and maintainers,
keep stating it does not make it true.  Since libc-alpha is non moderated
list, there were a lot of unfriendly message from undisclosed or
non-representative people.

What happened is some glibc developers were *really* annoyed in the way
*you* acted, not RMS; and they vocalized it.  And you, instead of work 
toward to create consensus by making some concession (as the currently
we try to run the glibc community), keep arguing to exhaustion that you
acted in the benefit or the project.  

So the aforementioned 'hate' is just because we did not agreed in the
way *you* acted, which caused a lot of distress.

> 
>> The main idea, which I was vocal about and shared with some glibc
>> developers and maintainers, was that the "joke" has no place in a
>> technical manual.
> 
> I understand there is consensus about that now, but back then there were
> too many unsettled policy issues to make that call consensually among
> all relevant parties.
> 
> The main disagreement was not over the issue proper, though.  It was
> about procedure, and then it was about whose opinions as much as
> counted.

No, the disagreement is the way *you* did it. I haven't seen such
contention and disarray you started since I have started to work on the 
project, about a decade ago.

So, please stop put the blame of that episode on the glibc community as 
a whole.

> 
> 
> It was a really trivial issue, but sufficiently hot-button and
> triggering enough underlying issues that it got to be exploited
> politically in several ugly ways.
> 
> It can't really be understood without looking into broader contexts that
> had long been mounting, and that again quite explicit in this list too.
> 
> 
> But I hope we can all agree that it was a horrible mess.
> 

Re: GCC association with the FSF

[John Darrington]

41;344;0cOn Sun, Apr 11, 2021 at 07:30:13PM -0300, Adhemerval Zanella via Gcc wrote:
     
     And there was no hate (at least not from my side) only *disappointment* that you used your status to do it even though most of senior developers and maintainers said explicitly you shouldn’t do it.

In GNU, there are no "senior" (or junior) developers/maintainers.  Maintainers
have some specific responsibilities, with which developers are not emcumbered.
In almost all projects, the maintainers are also developers, but this need not
be the case.  But all maintainers are equal, and all developers are equal.

J'

Re: GCC association with the FSF

[Siddhesh Poyarekar]

On 4/12/21 12:55 PM, John Darrington wrote:
> In GNU, there are no "senior" (or junior) developers/maintainers.  Maintainers
> have some specific responsibilities, with which developers are not emcumbered.
> In almost all projects, the maintainers are also developers, but this need not
> be the case.  But all maintainers are equal, and all developers are equal.

Those are terms we tend to use in the glibc developer community to 
loosely indicate the amount of time and resources individuals have spent 
in the glibc project as developers, testers, release managers, etc.  In 
fact, 'maintainer' in glibc is not the same as 'maintainer' in GNU 
because they're not GNU maintainers.  We call GNU maintainers "FSF 
stewards" in glibc to disambiguate that.

It doesn't matter what these roles are called in GNU because they're not 
the names we use in the glibc community on a day to day basis.  That 
said, we can have a conversation about glibc on the glibc mailing list. 
  The gcc mailing list is not the place for it.  In the interest of 
keeping the thread relevant, this is my last email on this topic on the 
gcc mailing list.

Siddhesh

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Monday, April 12, 2021 at 8:04 AM
> From: "Jonathan Wakely via Gcc" <gcc@gcc.gnu.org>
> To: "Alexandre Oliva" <oliva@gnu.org>
> Cc: gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On Sun, 11 Apr 2021, 19:28 Alexandre Oliva, <oliva@gnu.org> wrote:
>
> > Jonathan,
> >
> > It's very offensive for you to misattribute a disagreeing position as
> > veneration.
> >
>
> There have been many posts over the past two weeks suggesting that without
> RMS to guide us, GCC will become a pawn of the NSA, or that nobody has any
> authority to decide on the future of GNU projects except RMS (a view also
> stated on GNU mailing lists by moderators of those very lists), or other
> silly claims that are based on little but veneration. They're not really
> based on anything about GCC, just "y u no like RMS?"

I have disagreed that GCC will become a pawn of the NSA, or that the only
person to decide is RMS.

> > I could name many reasons for me to disagree with yours, including
> > justice, truth, honesty, tolerance, freedom of speech and unity of the
> > movement.
> >
> > If anything, it's threatening to abandon a project over false
> > allegations about a person, on occasion of that person rejoining the
> > board of an organization that was founded and has always supported the
> > project who's still led by that person, that makes the issue personal
> > and based on blind faith, though in the opposite sense of veneration.
> >
>
> Oh I have other reasons to consider the FSF a dead end too.
>
>
> > If you find any offense in the previous paragraph, you understand
> > exactly why I feel offended by your retort, so please try to take that
> > into account in your attempts to participate in a kind debate.
> >
>
> Kind debate. Right.
>
> Maybe somebody from the GNU project or the FSF could tell one of their GNU
> Maintainers (apparently part of the governance structure of the GNU
> project) to stop calling people mad, or rats, or to stop endless off-topic
> trolling about communism. There is no kind debate when every other post is
> an attack from a troll.

Things can be said directly as customary.  You are certainly willing offending
me in your pursuit.  There have been instances where my post followed a number
of posts, but not on the entire thread.

> Your own emails are always carefully considered (and carefully skate around
> the actual issues people raised) but most of the other voices objecting to
> the requests to make changes to GCC are coming from outsiders who are only
> too happy to insult GCC devs and derail any "debate".

I am not an outsider.  Or have a plan to derail any debate or insult every
developer.  But the debate is in the gcc mailing list to which I was not an
outsider.  Changes can be done, and even if I would not agree with some
aspects, will respect the final choice.  There is no prerogative to praise
developers, including myself.

Re: GCC association with the FSF

[Christopher Dimech]

Things will still remain good for RMS by those willing to help him.  I use
free software every day and will be a long time before Richard exhausts his
entitlement to help from me!!!

> Sent: Saturday, April 10, 2021 at 5:01 AM
> From: "David Brown" <david.brown@hesbynett.no>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "John Darrington" <john@darrington.wattle.id.au>, "David Malcolm" <dmalcolm@redhat.com>, gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
> On 09/04/2021 16:40, Christopher Dimech wrote:
> >> Sent: Friday, April 09, 2021 at 10:37 PM
> >> From: "David Brown" <david.brown@hesbynett.no>
> >> To: "John Darrington" <john@darrington.wattle.id.au>, "David Malcolm" <dmalcolm@redhat.com>
> >> Cc: gcc@gnu.org
> >> Subject: Re: GCC association with the FSF
> >>
> >> On 09/04/2021 08:37, John Darrington wrote:
> >>
> >>>
> >>> Nobody is suggesting that RMS should be regarded by everyone or indeed
> >>> anyone as "mein Führer".  I think he would be very much concerned if anyone
> >>> tried to confer a cult hero status on him.
> >>>
> >>> Sooner or later, if for no reason other than his age, RMS will have to step
> >>> down as leader of GNU.   Rather than calling for his head on a block it
> >>> would be more constructive to think to the future.  Unfortunately to date,
> >>> I have not seen anyone who in my opinion would have the qualities necessary
> >>> to take over the role.
> >>>
> >>
> >> And I don't think people (at least, not many) are "calling for his
> >> head".  My thought is that he should be encouraged to step down from all
> >> his positions within GNU, FSF, gcc, and any other projects he is
> >> involved with.  Retire now, while he can do so with dignity and without
> >> harm to the free and open source software worlds.
> > 
> > David, I oppose your thought that he should be made to step down from ALL
> > his positions.  That's the fundamental philosophy of China and Russia.
> >  
> 
> Different opinions are fine.  Bringing national or international
> politics into the discussion (presumably meant to be as an insult) is
> not fine.  This is not a political discussion - please stop trying to
> make it one.
> 
> >> It is only if it is left too late that people will be /forced/ to call
> >> for his head.  You can be very sure that complaints about his behaviour
> >> and attitudes will not diminish - they will grow, and the result will
> >> not be good for RMS, GNU, gcc, users, developers, or anyone else except
> >> the sellers of tabloid newspapers.  I would rather see him leave quietly
> >> now with respect, than be hounded out later and his statues pulled down
> >> - along with the careers and reputations of many who work with him.  (I
> >> am not saying that such a destruction would be correct or appropriate -
> >> I am saying it will happen in the end if the free software community is
> >> not careful.)
> >  
> >> (I agree that there are few, if any, people who had the qualities of RMS
> >> to do the job he did.  But IMHO that role is over - we don't need
> >> someone to fill his shoes.)
> >  
> > I do not see that a person with the qualities of RMS would ask permission for
> > the job.  I certainly don't! 
> >  
> 
> We (the free software world) does not need a person with the qualities
> of RMS any more - that is the point.  There should not be such a
> position as "Chief GNUsance".
> 
>

Re: GCC association with the FSF

[John Darrington]

On Fri, Apr 09, 2021 at 07:01:07PM +0200, David Brown wrote:
     
     Different opinions are fine.  Bringing national or international
     politics into the discussion (presumably meant to be as an insult) is
     not fine.  This is not a political discussion - please stop trying to
     make it one.

For the record it was David who first brought up the political allegory so
this comment should be directed in his direction.

As for your second point, I find it disappointing but not suprising that
you "presumed" this comment to be an insult.   This is precisely the
thing which has caused so much poisonous discourse in recent years.  Some
people take any opinion they disagree with and look for ways to interpret
it as an insult.   This gives them a lever to claim that anyone who holds
that opinion is a chauvanist, a bigot or worse.   This must stop.

Re: GCC association with the FSF

[Giacomo Tesio]

Hi John,

On April 9, 2021 6:36:31 PM UTC, John Darrington <john@darrington.wattle.id.au> wrote:
> On Fri, Apr 09, 2021 at 07:01:07PM +0200, David Brown wrote:
>      
>      Different opinions are fine.  Bringing national or international
>  politics into the discussion (presumably meant to be as an insult) is
>  not fine.  This is not a political discussion - please stop trying to
>      make it one.
> 
> For the record it was David who first brought up the political

I think David was talking about me: https://gcc.gnu.org/pipermail/gcc/2021-April/235285.html

It was not meant to insult anybody, I was just asking to fix a serious problem in GCC.

Since it's clear that the Steering Committee doesn't want to address it, I'm moving on.


GCC is clearly an US-only project.
A US-corporate one. Totally SFW (in the US).

This is not intended as an insult.
It's just a fact.


Giacomo

Re: GCC association with the FSF

[Ian Lance Taylor]

On Fri, Apr 9, 2021, 1:04 PM Giacomo Tesio <giacomo@tesio.it> wrote:

> Hi John,
>
> On April 9, 2021 6:36:31 PM UTC, John Darrington <
> john@darrington.wattle.id.au> wrote:
> > On Fri, Apr 09, 2021 at 07:01:07PM +0200, David Brown wrote:
> >
> >      Different opinions are fine.  Bringing national or international
> >  politics into the discussion (presumably meant to be as an insult) is
> >  not fine.  This is not a political discussion - please stop trying to
> >      make it one.
> >
> > For the record it was David who first brought up the political
>
> I think David was talking about me:
> https://gcc.gnu.org/pipermail/gcc/2021-April/235285.html
>
> It was not meant to insult anybody, I was just asking to fix a serious
> problem in GCC.
>
> Since it's clear that the Steering Committee doesn't want to address it,
> I'm moving on.
>
>
> GCC is clearly an US-only project.
> A US-corporate one. Totally SFW (in the US).
>
> This is not intended as an insult.
> It's just a fact.
>

Just for the record, for other readers, this is not even remotely true.

Ian

Re: GCC association with the FSF

[Giacomo Tesio]

Just for the record, I was not talking about developers but about the leadership of the project, Ian.

8 out of 13 members of the Steering Committee are from US-corporations.

This is a fact.


Just like the weird relations some of these companies have had with US Government:
https://www.virtualthreat.com/wp-content/uploads/2013/11/nsa-google-cloud-exploitation.jpg

The implications are left as an exercise for the readers. ;-)


Giacomo

On April 9, 2021 9:40:33 PM UTC, Ian Lance Taylor <iant@google.com> wrote:
> On Fri, Apr 9, 2021, 1:04 PM Giacomo Tesio <giacomo@tesio.it> wrote:
> 
> > Hi John,
> >
> > On April 9, 2021 6:36:31 PM UTC, John Darrington <
> > john@darrington.wattle.id.au> wrote:
> > > On Fri, Apr 09, 2021 at 07:01:07PM +0200, David Brown wrote:
> > >
> > >      Different opinions are fine.  Bringing national or
> international
> > >  politics into the discussion (presumably meant to be as an
> insult) is
> > >  not fine.  This is not a political discussion - please stop
> trying to
> > >      make it one.
> > >
> > > For the record it was David who first brought up the political
> >
> > I think David was talking about me:
> > https://gcc.gnu.org/pipermail/gcc/2021-April/235285.html
> >
> > It was not meant to insult anybody, I was just asking to fix a
> serious
> > problem in GCC.
> >
> > Since it's clear that the Steering Committee doesn't want to address
> it,
> > I'm moving on.
> >
> >
> > GCC is clearly an US-only project.
> > A US-corporate one. Totally SFW (in the US).
> >
> > This is not intended as an insult.
> > It's just a fact.
> >
> 
> Just for the record, for other readers, this is not even remotely
> true.
> 
> Ian

Re: GCC association with the FSF

[Jonathan Wakely]

On Fri, 9 Apr 2021, 23:22 Giacomo Tesio, <giacomo@tesio.it> wrote:

> Just for the record, I was not talking about developers but about the
> leadership of the project, Ian.
>
> 8 out of 13 members of the Steering Committee are from US-corporations.
>
> This is a fact.
>
>
> Just like the weird relations some of these companies have had with US
> Government:
>
> https://www.virtualthreat.com/wp-content/uploads/2013/11/nsa-google-cloud-exploitation.jpg
>
> The implications are left as an exercise for the readers. ;-)
>


You are clueless about what the SC actually does, or the control they have
over GCC.

You said you would move on, please do so.

Re: GCC association with the FSF

[Pankaj Jangid]

Jonathan Wakely via Gcc <gcc@gcc.gnu.org> writes:

> You are clueless about what the SC actually does, or the control they
> have over GCC.

I think, it would be great help if someone can document what the SC
does.

Re: GCC association with the FSF

[Jonathan Wakely]

On Sat, 10 Apr 2021, 12:57 Pankaj Jangid, <pankaj@codeisgreat.org> wrote:

> Jonathan Wakely via Gcc <gcc@gcc.gnu.org> writes:
>
> > You are clueless about what the SC actually does, or the control they
> > have over GCC.
>
> I think, it would be great help if someone can document what the SC
> does.
>


https://gcc.gnu.org/steering.html

They make decisions, they don't get to insert NSA backdoors on behalf of
their employers without the rest of the project being aware. The idea that
the SC members have a special ability to sneak such a change in, any more
than any contributor, is just stupid. But I don't think he's seriously
worried about that, he's just a Concern Troll raising nonsense concerns to
derail any useful discussion from happening. The sooner he moves on to a
new compiler he trusts, the better for everybody involved in GCC.

>

Re: GCC association with the FSF

[Thomas Rodgers]

On 2021-04-10 05:35, Jonathan Wakely via Gcc wrote:

> On Sat, 10 Apr 2021, 12:57 Pankaj Jangid, <pankaj@codeisgreat.org> 
> wrote:
> 
> Jonathan Wakely via Gcc <gcc@gcc.gnu.org> writes:
> 
> You are clueless about what the SC actually does, or the control they
> have over GCC.
> I think, it would be great help if someone can document what the SC
> does.

https://gcc.gnu.org/steering.html

They make decisions, they don't get to insert NSA backdoors on behalf of
their employers without the rest of the project being aware. The idea 
that
the SC members have a special ability to sneak such a change in, any 
more
than any contributor, is just stupid. But I don't think he's seriously
worried about that, he's just a Concern Troll raising nonsense concerns 
to
derail any useful discussion from happening. The sooner he moves on to a
new compiler he trusts, the better for everybody involved in GCC.

Him too really, it's important to have trust in your toolchain...

Re: GCC association with the FSF

[Giacomo Tesio]

It's fantastic how inclusive you are, isn't it?  :-D

Indeed you ARE inclusive to those who share your interests, like Nathan.
Just not to everybody else.


But it's quite obvious, after you removed RMS's oversight on SC's decisions.

And now I'm depicted as a "concern troll", because I don't share your opinion.
You can't argue in merit, so you insult me personally.
I'm fine with this: it says a lot about you and nothing about me.


In fact, the mail boxes of the Steering Committee's members are stored on their corporate servers.
And among such corporations are IBM and Google.

And you pretend it's all fine.


Yet I only asked to fix the Steering Committee AFTER the only credible no-profit protecting free software (FSF) was removed.

But I'm a "concern troll", right?


I think everybody can see who is who. ;-)


Giacomo


On April 10, 2021 3:04:22 PM UTC, Thomas Rodgers <rodgert@appliantology.com> wrote:
> On 2021-04-10 05:35, Jonathan Wakely via Gcc wrote:
> 
> > On Sat, 10 Apr 2021, 12:57 Pankaj Jangid, <pankaj@codeisgreat.org> 
> > wrote:
> > 
> > Jonathan Wakely via Gcc <gcc@gcc.gnu.org> writes:
> > 
> > You are clueless about what the SC actually does, or the control
> they
> > have over GCC.
> > I think, it would be great help if someone can document what the SC
> > does.
> 
> https://gcc.gnu.org/steering.html
> 
> They make decisions, they don't get to insert NSA backdoors on behalf
> of
> their employers without the rest of the project being aware. The idea 
> that
> the SC members have a special ability to sneak such a change in, any 
> more
> than any contributor, is just stupid. But I don't think he's seriously
> worried about that, he's just a Concern Troll raising nonsense
> concerns 
> to
> derail any useful discussion from happening. The sooner he moves on to
> a
> new compiler he trusts, the better for everybody involved in GCC.
> 
> Him too really, it's important to have trust in your toolchain...

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Sunday, April 11, 2021 at 4:01 AM
> From: "Giacomo Tesio" <giacomo@tesio.it>
> To: gcc@gcc.gnu.org, "Thomas Rodgers" <rodgert@appliantology.com>, "Jonathan Wakely" <jwakely.gcc@gmail.com>
> Cc: "Pankaj Jangid" <pankaj@codeisgreat.org>
> Subject: Re: GCC association with the FSF
>
> It's fantastic how inclusive you are, isn't it?  :-D
>
> Indeed you ARE inclusive to those who share your interests, like Nathan.
> Just not to everybody else.
>
>
> But it's quite obvious, after you removed RMS's oversight on SC's decisions.
>
> And now I'm depicted as a "concern troll", because I don't share your opinion.
> You can't argue in merit, so you insult me personally.
> I'm fine with this: it says a lot about you and nothing about me.

Welcome to the club, friend. ;)

> In fact, the mail boxes of the Steering Committee's members are stored on their corporate servers.
> And among such corporations are IBM and Google.
>
> And you pretend it's all fine.
>
>
> Yet I only asked to fix the Steering Committee AFTER the only credible no-profit protecting free software (FSF) was removed.
>
> But I'm a "concern troll", right?
>
>
> I think everybody can see who is who. ;-)

It's easier than fixing the world economies for sure.

> Giacomo
>
>
> On April 10, 2021 3:04:22 PM UTC, Thomas Rodgers <rodgert@appliantology.com> wrote:
> > On 2021-04-10 05:35, Jonathan Wakely via Gcc wrote:
> >
> > > On Sat, 10 Apr 2021, 12:57 Pankaj Jangid, <pankaj@codeisgreat.org>
> > > wrote:
> > >
> > > Jonathan Wakely via Gcc <gcc@gcc.gnu.org> writes:
> > >
> > > You are clueless about what the SC actually does, or the control
> > they
> > > have over GCC.
> > > I think, it would be great help if someone can document what the SC
> > > does.
> >
> > https://gcc.gnu.org/steering.html
> >
> > They make decisions, they don't get to insert NSA backdoors on behalf
> > of
> > their employers without the rest of the project being aware. The idea
> > that
> > the SC members have a special ability to sneak such a change in, any
> > more
> > than any contributor, is just stupid. But I don't think he's seriously
> > worried about that, he's just a Concern Troll raising nonsense
> > concerns
> > to
> > derail any useful discussion from happening. The sooner he moves on to
> > a
> > new compiler he trusts, the better for everybody involved in GCC.
> >
> > Him too really, it's important to have trust in your toolchain...
>

Re: GCC association with the FSF

[Thomas Rodgers]

On 2021-04-10 09:01, Giacomo Tesio wrote:

> It's fantastic how inclusive you are, isn't it?  :-D
> 
> Indeed you ARE inclusive to those who share your interests, like 
> Nathan.
> Just not to everybody else.
> 

I share with Nathan an interest in making GCC the best C++ compiler and 
standard library, and like Nathan, I work to help make that the case. It 
is certainly true I don't have a lot of concern for the concerns of 
those, whose only apparent contribution to the discussion is 'oooh evil 
bad bigcorp's subverting mah compiler. I will go away now'.

> Yet I only asked to fix the Steering Committee AFTER the only credible 
> no-profit protecting free software (FSF) was removed.
> 
> But I'm a "concern troll", right?
> 
> I think everybody can see who is who. ;-)
> 

Indeed.

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Sunday, April 11, 2021 at 7:52 AM
> From: "Thomas Rodgers" <rodgert@appliantology.com>
> To: "Giacomo Tesio" <giacomo@tesio.it>
> Cc: gcc@gcc.gnu.org, "Pankaj Jangid" <pankaj@codeisgreat.org>
> Subject: Re: GCC association with the FSF
>
> On 2021-04-10 09:01, Giacomo Tesio wrote:
>
> > It's fantastic how inclusive you are, isn't it?  :-D
> >
> > Indeed you ARE inclusive to those who share your interests, like
> > Nathan.
> > Just not to everybody else.
> >
>
> I share with Nathan an interest in making GCC the best C++ compiler and
> standard library, and like Nathan, I work to help make that the case. It
> is certainly true I don't have a lot of concern for the concerns of
> those, whose only apparent contribution to the discussion is 'oooh evil
> bad bigcorp's subverting mah compiler. I will go away now'.

Companies have serious problems right now.  The internet used to run
as a US Benign Dictatorship, under the assumption that the US was generally
behaving in the world's best interest.  That trust has been lost.  If you are
someone in some country somewhere, and you hear that the NSA is getting a copy
of everything.  And IBM and Google have a Press Release saying that they
have fixed a problem.  Do you believe it?  I sure don't.  And many others don't,
and for good reasons.  I also think that will be a bunch of other countries
that will do way worse than what the United States has done.  If we are against
national means of intelligence, all bets are off.  This is compounded by the fact
that attack in much easier than defense.  I don't think that's what we are trying
to defend against.  We are trying to defend against bulk collection.

But I tend to be optimistic, than humanity as a species tend to solve these problems.
It might take one or a few generations.  We might have some terrible world wars
while we're solving it.  But till now we have managed to have more freedom,
more rights, more liberty, century by century.

People have to understand that companies and governments are not made of magic, that
they are not breaking systems to anywhere near the extent that we thought they were.
This is the most important conclusion that can be taken from Snowden's documents.
The reality in that there are many things we can do to make ourselves much more secure.
I might have some reservations about Nathan and others regarding the RMS debate, but
not that many of them are likely to be consciously injecting malicious code
or introducing vulnerabilities.

If business leaders change the way they look at life, instead of making a whole lot
of money and then contributing to some cause, they can structure their business
in such a way that every customer is in some way a partner with them.

However if companies and governments try to conquer people, they will have to keep
sitting on top of their head, and they will do everything to make the life of business
leaders miserable.

Traditionally, military leaders were the most powerful people.  In the last hundred
years, political leaders were the most powerful.  But now and in the future, economic leaders will be the most powerful.

We have to start working with economic leaders to make a difference in the way they
make decisions, and in the way they conduct their businesses.   This is being done,
but is being done very discreetly because it is something that today cannot be
handled publicly.

> > Yet I only asked to fix the Steering Committee AFTER the only credible
> > no-profit protecting free software (FSF) was removed.
> >
> > But I'm a "concern troll", right?
> >
> > I think everybody can see who is who. ;-)
> >
>
> Indeed.
>

Re: GCC association with the FSF

[Richard Kenner]

> But it's quite obvious, after you removed RMS's oversight on SC's decisions.

The SC is the "GNU maintainer" for GCC.  The GNU project has oversight on
the maintainers of every GNU project, including GCC.  The change to the
web page didn't affect that: RMS still has oversight on the SC's
decisions to some extent, just like he does over all GNU projects.

Re: GCC association with the FSF

[Gerald Pfeifer]

On Sat, 10 Apr 2021, Giacomo Tesio wrote:
> In fact, the mail boxes of the Steering Committee's members are 
> stored on their corporate servers.

You keep making statements which are simply wrong.

None of my GCC-related e-mails touch the servers of my employer,
nor servers under the control of my employer, nor servers running
one of my employer's products.

Membership in the steering committee is personal, not related to
the respective employeers, and transcends employment.

Oh, and FWIW: my employer legally is not even allowed to access 
my work mailbox.

> Yet I only asked to fix the Steering Committee AFTER the only 
> credible no-profit protecting free software (FSF) was removed.

Please stop spreading FUD and insulting steering committee members.

Gerald

Re: GCC association with the FSF

[Ian Lance Taylor]

On Sat, Apr 10, 2021 at 4:36 AM Pankaj Jangid <pankaj@codeisgreat.org> 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).

Ian

Re: GCC association with the FSF

[David Edelsohn]

On Sun, Apr 11, 2021 at 8:40 PM Ian Lance Taylor via Gcc
<gcc@gcc.gnu.org> wrote:
>
> On Sat, Apr 10, 2021 at 4:36 AM Pankaj Jangid <pankaj@codeisgreat.org> 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

Re: GCC association with the FSF

[Chris Punches]

Hello,

I've been reading quietly on how the GCC SC handles this and generally
only lurk here so that I can stay informed on GCC changes.  I am nobody
you would probably care about, but, maybe I will be one day.  No one
ever really knows.

I thought you'd like to know what "nobody" thinks, because, if I am
paying enough attention to know that some here are not, perhaps people
who are not "nobody" will have similar observations.

It is not appropriate to discuss the removal of someone based on
innuendo, provenly false smearing, and other types of political
maneuvering at the behest of corporations desiring the destruction of
the very projects they are sponsoring.

It is not appropriate to even suggest to blackmail sponsor or non-
sponsor organizations by cutting ties with them to force someone that a
couple corporates in your group don't like out of their organization.
 I call on those of you who argued this to restore credibility and
integrity to this discussion.

This kind of thinking has defaced this project.  What are you thinking?
 We don't care about your political views.  We don't care about GCC's
participation in activism-- in fact, many would view it as a marker of
instability of the project.  We care about the stable maintenance of
GCC into perpetuity.

No one who cares about these projects wants these kinds of politics
driving such a technical and fundamental project.  You have been
infected.  Please restore the compasses and carry on.

I salute you,

-C

On Sun, 2021-04-11 at 21:03 -0400, David Edelsohn via Gcc wrote:
> On Sun, Apr 11, 2021 at 8:40 PM Ian Lance Taylor via Gcc
> <gcc@gcc.gnu.org> wrote:
> > On Sat, Apr 10, 2021 at 4:36 AM Pankaj Jangid <
> > pankaj@codeisgreat.org> 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

Re: GCC association with the FSF

[Bronek Kozicki]

On Mon, 12 Apr 2021 at 03:12, Chris Punches via Gcc <gcc@gcc.gnu.org> wrote:

> Hello,
>
> I've been reading quietly on how the GCC SC handles this and generally
> only lurk here so that I can stay informed on GCC changes.  I am nobody
> you would probably care about, but, maybe I will be one day.  No one
> ever really knows.
>
> I thought you'd like to know what "nobody" thinks, because, if I am
> paying enough attention to know that some here are not, perhaps people
> who are not "nobody" will have similar observations.
>
> It is not appropriate to discuss the removal of someone based on
> innuendo, provenly false smearing, and other types of political
> maneuvering at the behest of corporations desiring the destruction of
> the very projects they are sponsoring.
>


The whole controversy is *because* many of the allegations are well
founded. Some of the current SC members in this thread make it sound as if
they were made up, but they never attempted as much as put the first few
points (ones which matter to me the most, as a father) in any doubt from
https://gcc.gnu.org/pipermail/gcc/2021-March/235091.html


B.

Re: GCC association with the FSF

[Bronek Kozicki]

On Mon, 12 Apr 2021 at 11:24, Bronek Kozicki <b.kozicki@gmail.com> wrote:

> On Mon, 12 Apr 2021 at 03:12, Chris Punches via Gcc <gcc@gcc.gnu.org>
> wrote:
>
>> Hello,
>>
>> I've been reading quietly on how the GCC SC handles this and generally
>> only lurk here so that I can stay informed on GCC changes.  I am nobody
>> you would probably care about, but, maybe I will be one day.  No one
>> ever really knows.
>>
>> I thought you'd like to know what "nobody" thinks, because, if I am
>> paying enough attention to know that some here are not, perhaps people
>> who are not "nobody" will have similar observations.
>>
>> It is not appropriate to discuss the removal of someone based on
>> innuendo, provenly false smearing, and other types of political
>> maneuvering at the behest of corporations desiring the destruction of
>> the very projects they are sponsoring.
>>
>
>
> The whole controversy is *because* many of the allegations are well
> founded. Some of the current SC members in this thread make it sound as if
> they were made up, but they never attempted as much as put the first few
> points (ones which matter to me the most, as a father) in any doubt from
> https://gcc.gnu.org/pipermail/gcc/2021-March/235091.html
>


My sincere apologies to SC members, it was pointed out to me privately
(thank you!) that the defenders of the person in question are not actually
in SC.


B.

-- 
Bronek Kozicki     brok@incorrekt.com <brok@spamcop.net>

Re: GCC association with the FSF

[Kalamatee]

On Mon, 12 Apr 2021 at 03:13, Chris Punches via Gcc <gcc@gcc.gnu.org> wrote:

> Hello,
>
> I've been reading quietly on how the GCC SC handles this and generally
> only lurk here so that I can stay informed on GCC changes.  I am nobody
> you would probably care about, but, maybe I will be one day.  No one
> ever really knows.
>
> I thought you'd like to know what "nobody" thinks, because, if I am
> paying enough attention to know that some here are not, perhaps people
> who are not "nobody" will have similar observations.
>
> It is not appropriate to discuss the removal of someone based on
> innuendo, provenly false smearing, and other types of political
> maneuvering at the behest of corporations desiring the destruction of
> the very projects they are sponsoring.
>
> It is not appropriate to even suggest to blackmail sponsor or non-
> sponsor organizations by cutting ties with them to force someone that a
> couple corporates in your group don't like out of their organization.
>  I call on those of you who argued this to restore credibility and
> integrity to this discussion.
>
> This kind of thinking has defaced this project.  What are you thinking?
>  We don't care about your political views.  We don't care about GCC's
> participation in activism-- in fact, many would view it as a marker of
> instability of the project.  We care about the stable maintenance of
> GCC into perpetuity.
>
> No one who cares about these projects wants these kinds of politics
> driving such a technical and fundamental project.  You have been
> infected.  Please restore the compasses and carry on.
>
> I salute you,
>

+1

I find some of the behaviour and and actions of developers afforded
positions of authority in the project highly unprofessional, and
irresponsible. I would seriously question their motives, and why they are
involved in the project at all.


> -C
>
> On Sun, 2021-04-11 at 21:03 -0400, David Edelsohn via Gcc wrote:
> > On Sun, Apr 11, 2021 at 8:40 PM Ian Lance Taylor via Gcc
> > <gcc@gcc.gnu.org> wrote:
> > > On Sat, Apr 10, 2021 at 4:36 AM Pankaj Jangid <
> > > pankaj@codeisgreat.org> 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
>
>

Re: GCC association with the FSF

[Nathan Sidwell]

On 4/11/21 9:34 PM, Chris Punches via Gcc wrote:

> It is not appropriate to discuss the removal of someone based on
> innuendo, provenly false smearing, and other types of political
> maneuvering at the behest of corporations desiring the destruction of
> the very projects they are sponsoring.

Good job that's not what is happening then.

> It is not appropriate to even suggest to blackmail sponsor or non-
> sponsor organizations by cutting ties with them to force someone that a
> couple corporates in your group don't like out of their organization.
>   I call on those of you who argued this to restore credibility and
> integrity to this discussion.

People, and companies can chose to support whatever organizations they desire, 
and they can chose to withdraw such support.  For what ever reasons they may have.

nathan


-- 
Nathan Sidwell

Re: GCC association with the FSF

[Chris Punches]

That will never make it appropriate.

I would encourage you to reflect more carefully on the meaning of the
words you are reading and using.

These arguments are paper thin, and full of lofty rhetoric; none of
them will expand the expectation of anyone here to include integrating
their poltical beliefs into the GCC project roadmap beyond its
technical and licensing goals.

I would encourage anyone reading this to start treating this discussion
as off-topic disruption for the GCC SC.

-C

On Mon, 2021-04-12 at 17:22 -0400, Nathan Sidwell wrote:
> On 4/11/21 9:34 PM, Chris Punches via Gcc wrote:
> 
> > It is not appropriate to discuss the removal of someone based on
> > innuendo, provenly false smearing, and other types of political
> > maneuvering at the behest of corporations desiring the destruction
> > of
> > the very projects they are sponsoring.
> 
> Good job that's not what is happening then.
> 
> > It is not appropriate to even suggest to blackmail sponsor or non-
> > sponsor organizations by cutting ties with them to force someone
> > that a
> > couple corporates in your group don't like out of their
> > organization.
> >   I call on those of you who argued this to restore credibility and
> > integrity to this discussion.
> 
> People, and companies can chose to support whatever organizations
> they desire, 
> and they can chose to withdraw such support.  For what ever reasons
> they may have.
> 
> nathan
> 
> 

Re: GCC association with the FSF

[Daniel (Robin) Smith]

"but muh freedum license reeeee"

"haha quality compiler suite go brrr"

On Mon, Apr 12, 2021, 8:25 PM Chris Punches via Gcc <gcc@gcc.gnu.org> wrote:

> That will never make it appropriate.
>
> I would encourage you to reflect more carefully on the meaning of the
> words you are reading and using.
>
> These arguments are paper thin, and full of lofty rhetoric; none of
> them will expand the expectation of anyone here to include integrating
> their poltical beliefs into the GCC project roadmap beyond its
> technical and licensing goals.
>
> I would encourage anyone reading this to start treating this discussion
> as off-topic disruption for the GCC SC.
>
> -C
>
> On Mon, 2021-04-12 at 17:22 -0400, Nathan Sidwell wrote:
> > On 4/11/21 9:34 PM, Chris Punches via Gcc wrote:
> >
> > > It is not appropriate to discuss the removal of someone based on
> > > innuendo, provenly false smearing, and other types of political
> > > maneuvering at the behest of corporations desiring the destruction
> > > of
> > > the very projects they are sponsoring.
> >
> > Good job that's not what is happening then.
> >
> > > It is not appropriate to even suggest to blackmail sponsor or non-
> > > sponsor organizations by cutting ties with them to force someone
> > > that a
> > > couple corporates in your group don't like out of their
> > > organization.
> > >   I call on those of you who argued this to restore credibility and
> > > integrity to this discussion.
> >
> > People, and companies can chose to support whatever organizations
> > they desire,
> > and they can chose to withdraw such support.  For what ever reasons
> > they may have.
> >
> > nathan
> >
> >
>
>

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Saturday, April 10, 2021 at 10:12 AM
> From: "Giacomo Tesio" <giacomo@tesio.it>
> To: "Ian Lance Taylor" <iant@google.com>
> Cc: "GCC Development" <gcc@gcc.gnu.org>, gcc@gnu.org, "David Brown" <david.brown@hesbynett.no>
> Subject: Re: GCC association with the FSF
>
> Just for the record, I was not talking about developers but about the leadership of the project, Ian.
>
> 8 out of 13 members of the Steering Committee are from US-corporations.
>
> This is a fact.

Many in tech have worked at some point in their lives with large corporations.
This is not wrong it itself because most knowledge is concentrated in highly industrialized countries.  I owe much of my technological experience during
my days working with british, dutch and french intelligence.

It is also well known that governments employ about 10% of the best mathematicians.
Furthermore I cannot see how you can feel secure if the people involved work from
Non-Us Corporations.  There are many countries that are even worse than the US.


> Just like the weird relations some of these companies have had with US Government:
> https://www.virtualthreat.com/wp-content/uploads/2013/11/nsa-google-cloud-exploitation.jpg
>
> The implications are left as an exercise for the readers. ;-)
>
>
> Giacomo
>
> On April 9, 2021 9:40:33 PM UTC, Ian Lance Taylor <iant@google.com> wrote:
> > On Fri, Apr 9, 2021, 1:04 PM Giacomo Tesio <giacomo@tesio.it> wrote:
> >
> > > Hi John,
> > >
> > > On April 9, 2021 6:36:31 PM UTC, John Darrington <
> > > john@darrington.wattle.id.au> wrote:
> > > > On Fri, Apr 09, 2021 at 07:01:07PM +0200, David Brown wrote:
> > > >
> > > >      Different opinions are fine.  Bringing national or
> > international
> > > >  politics into the discussion (presumably meant to be as an
> > insult) is
> > > >  not fine.  This is not a political discussion - please stop
> > trying to
> > > >      make it one.
> > > >
> > > > For the record it was David who first brought up the political
> > >
> > > I think David was talking about me:
> > > https://gcc.gnu.org/pipermail/gcc/2021-April/235285.html
> > >
> > > It was not meant to insult anybody, I was just asking to fix a
> > serious
> > > problem in GCC.
> > >
> > > Since it's clear that the Steering Committee doesn't want to address
> > it,
> > > I'm moving on.
> > >
> > >
> > > GCC is clearly an US-only project.
> > > A US-corporate one. Totally SFW (in the US).
> > >
> > > This is not intended as an insult.
> > > It's just a fact.
> > >
> >
> > Just for the record, for other readers, this is not even remotely
> > true.
> >
> > Ian
>

Re: GCC association with the FSF

[Richard Kenner]

> Just for the record, I was not talking about developers but about
> the leadership of the project, Ian.
> 
> 8 out of 13 members of the Steering Committee are from US-corporations.

I don't think I'd consider the Steering Committee "the leadership of
the project".  In what sense do they "lead" the project?

To me, when you talk about "leading" a software project, you're talking
about deciding what work gets done and when and by whom it gets done.  The
SC has *absolutely zero* influence on any of those things.  All the
"maintainers" they appoint (which is already indirect) do is approve
changes, not make the changes or decide what changes to make.  And their
approval is supposed to be on technical or style grounds.

The people who make the "leadership" decisions (what to work on and when)
are the companies that employ the *developers*, not the SC or the companies
the employ the members of the SC.

Re: GCC association with the FSF

[Gerald Pfeifer]

On Fri, 9 Apr 2021, Giacomo Tesio wrote:
> GCC is clearly an US-only project.

This is simply incorrect.

> A US-corporate one. Totally SFW (in the US).

As is this.

> This is not intended as an insult.
> It's just a fact.

Ex falso quodlibet.

Gerald

Re: GCC association with the FSF

[David Brown]

On 09/04/2021 20:36, John Darrington wrote:
> On Fri, Apr 09, 2021 at 07:01:07PM +0200, David Brown wrote:
>      
>      Different opinions are fine.  Bringing national or international
>      politics into the discussion (presumably meant to be as an insult) is
>      not fine.  This is not a political discussion - please stop trying to
>      make it one.
> 
> For the record it was David who first brought up the political allegory so
> this comment should be directed in his direction.

Fair enough.

> 
> As for your second point, I find it disappointing but not suprising that
> you "presumed" this comment to be an insult.   This is precisely the
> thing which has caused so much poisonous discourse in recent years.  Some
> people take any opinion they disagree with and look for ways to interpret
> it as an insult.   This gives them a lever to claim that anyone who holds
> that opinion is a chauvanist, a bigot or worse.   This must stop.
> 

I did not take the comment as an insult - I merely presumed that when
Christopher says someone is acting like the Russian or Chinese
government, he does not mean it in a good way.  (His later posts make
that entirely clear.)  I simply don't want to see this turn into a
political discussion.

I agree with you entirely that it is not helpful to perceive insults,
prejudice or bigotry - in general, it is important to keep the
discussion polite and try to remain focused.  That is what I wanted to
do by asking Christopher to avoid politics.

Re: GCC association with the FSF

[Christopher Dimech]

> Sent: Sunday, April 11, 2021 at 12:37 AM
> From: "David Brown" <david.brown@hesbynett.no>
> To: "John Darrington" <john@darrington.wattle.id.au>
> Cc: "Christopher Dimech" <dimech@gmx.com>, "David Malcolm" <dmalcolm@redhat.com>, gcc@gnu.org
> Subject: Re: GCC association with the FSF
>
>
>
> On 09/04/2021 20:36, John Darrington wrote:
> > On Fri, Apr 09, 2021 at 07:01:07PM +0200, David Brown wrote:
> >
> >      Different opinions are fine.  Bringing national or international
> >      politics into the discussion (presumably meant to be as an insult) is
> >      not fine.  This is not a political discussion - please stop trying to
> >      make it one.
> >
> > For the record it was David who first brought up the political allegory so
> > this comment should be directed in his direction.
>
> Fair enough.
>
> >
> > As for your second point, I find it disappointing but not suprising that
> > you "presumed" this comment to be an insult.   This is precisely the
> > thing which has caused so much poisonous discourse in recent years.  Some
> > people take any opinion they disagree with and look for ways to interpret
> > it as an insult.   This gives them a lever to claim that anyone who holds
> > that opinion is a chauvanist, a bigot or worse.   This must stop.
> >
>
> I did not take the comment as an insult - I merely presumed that when
> Christopher says someone is acting like the Russian or Chinese
> government, he does not mean it in a good way.  (His later posts make
> that entirely clear.)  I simply don't want to see this turn into a
> political discussion.

It was meant to enlighten you.  Although it has not yet done so, the basic
philosophy of removing people from the community, was the same philosophy
used in Russia and China.

> I agree with you entirely that it is not helpful to perceive insults,
> prejudice or bigotry - in general, it is important to keep the
> discussion polite and try to remain focused.  That is what I wanted to
> do by asking Christopher to avoid politics.

Politics is also my business.  Have heard many discuss "Representations of
values of a group (e.g. of Free Software)", "Marginalisation and removal of
people from all positions in society to undermine the likelihood or making
an impact, rather than being merely spectators but not participants in action".

Re: GCC association with the FSF

[Christopher Dimech]

 
> Sent: Friday, April 09, 2021 at 6:37 PM
> From: "John Darrington" <john@darrington.wattle.id.au>
> To: "David Malcolm" <dmalcolm@redhat.com>
> Cc: gcc@gnu.org, "Alfred M. Szmidt" <ams@gnu.org>, "Mark Wielaard" <mark@klomp.org>
> Subject: Re: GCC association with the FSF
>
> On Thu, Apr 08, 2021 at 09:35:23PM -0400, David Malcolm wrote:
>      
>      > RMS was the first person to be involved in GNU and GCC.  Others
>      > became
>      > involved later (under his leadership).  Their contribution was and
>      > continues to be welcome.  They are also free to stop contributing any
>      > time they wish to do so.
>      
>      I intend to continue contributing to GCC (and to Free Software in
>      general), but RMS is not my leader.

RMS never sent me an Allegiance Oath.
 
> Nobody is suggesting that RMS should be regarded by everyone or indeed
> anyone as "mein Führer".  I think he would be very much concerned if anyone
> tried to confer a cult hero status on him.
> 
> Sooner or later, if for no reason other than his age, RMS will have to step
> down as leader of GNU.   Rather than calling for his head on a block it
> would be more constructive to think to the future.  Unfortunately to date,
> I have not seen anyone who in my opinion would have the qualities necessary
> to take over the role.
> 
>      
>      > Then why do you write this from your employer's email?
>      
>      My employer gives me permission.
> 
> That's good to know.  My employer on the other hand expressly forbids it.
> And I think that is a reasonable prohibition (we're allowed to use their
> internet connection for personal use) but not allowed to use the company
> name (including email addresses) in personal communication.  Even if they
> didn't prohibit this, I wouldn't dream of using my company's email or
> letterhead for personal communication.
>      
>      Given the reaction that some have faced for questioning RMS, I'd prefer
>      to keep that address private.
> 
> So in other words, you are happy to make contraversial statements, but don't
> wish to face the responsibility.  Come on David!  By all means question RMS
> (or anyone else) but have the guts to do this under your own identity rather
> than duck in and out behind a veil of quasi-anonymity!

My address is public.  David, if you did not like my reaction, I would
not say that you hesitated in making disparaging comments.  But am not
against using your freedem of speech to see what is going on.

But tho philosophy that is guiding the utterances against RMS by left wing
totalitarians is the same philosophy of that of Mao Zedong - "Life is shit
and then you die!".
 
> I'm glad that you're going to continue to contribute to GCC.
> 
> J'
>

Re: GCC association with the FSF

[Alfred M. Szmidt]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]

   "We've always done it this way" is not necessarily a good defence of an
   existing practice.

That wasn't the claim, it is how we do it currently, and have been
doing for decades though.  If you have concrete suggestions, please
send them to the GNU Advisory Committee.

   >    The GNU Assembly is having a similar
   >    discussion right now
   > 
   > It should be noted that this group is not associated with the GNU
   > project, or represents it in anyway, despite pretending to.

   I don't think you get to speak for who is or is not a member of the GNU
   project.  As far as I know, "GNU" isn't trademarked.

I said that the group isn't speaking for the GNU project, nor does it
represent it.  If you want to know more, feel free reach out to the
GAC or RMS.

Re: Remove RMS from the GCC Steering Committee

[Giacomo Tesio]

Hi Mark,

I'm a bit in a hurry and do not really want to focus on what happened
in Harvey: to my eyes that story just show you cannot trust people just
because they are nice and well known "open source" contributors, or
because they work for big multinational that "do no evil" or even
join the Good Guys (TM) of Software Freedom Conservancy.

But let me clarify 

On Wed, 31 Mar 2021 13:34:17 +0200 Mark Wielaard wrote:

> I looked a bit at that issue you filed and how they handled your
> request to remove your code from the project. And I must say I don't
> really understand what you believe they did wrong, they seemed to have
> acknowledged and corrected their mistake and then removed all the code
> you wanted to have removed. 

I asked them to `git revert` my changes referencing the issue, so that
the code I reused in my own fork of Plan 9 was safe that nobody could
claim copyright of my work after, say, a change in the version control
system adopted by the project.

Instead they did a `git rebase` over which, I was pretty surprised
actually, they "accidentaly" squashed some of my own commits verbatim
(but without my name) in incredibly large commits.
And you know, they had to git push -f such rebase, breaking all the
existing github forks (while the `git revert` approach would not have
caused any issue to anybody)

> There is some disagreement over whether a
> mass change of function declarations is copyrightable or not.

And implementations. And kernel changes that took a couple of days to
get right (Harvey kernel was pretty unstable back then). And more I did
not remember but I noticed back then: 


> But I happen to agree with them that if there is only one way to do
> it, then having someone else do the same transformation is a correct
> way to resolve this.

Sure!

But first, there were several different ways to do that (several
equivalent typedefs were already in place in u.h, without even
mentioning macros and so on), and more importantly if you actually
redo the same work in the same way because there is a single way
to do that, you do in a dedicated commit with an author that takes
the clear responsibility for change.

Instead my work (or a totally, byte-for-byte equivalent, one) got
squashed into gigantic commits that include several very large commits
of several authors (all mentioned in the commit message... but me).


> To make this copyright issue somewhat relevant to GCC. GCC doesn't
> currently contain individual copyright statements and most of the code
> is currently assigned to the FSF. So the above mistake won't happen
> when contributing to GCC, but mostly because of the technicality that
> you sign away your copyright up front.

Oh sorry, I wasn't clear enough about this.

I'm SURE that this specific issue would not happen on GCC.
Nor on Linux. Nor in several other Free Software and Open Source
communities.

But I think you are missing the valuable lesson that the Harvey team
(some of which actually signed the rms-open-letter) tauht me: I didn't
expected ANYTHING like this to happen. And I didn't expect SFC to not
expell a project doing something like this.

I trusted them both. All of them.


So ultimately I do not expect this specific issue to occur in a
hypothetical GCC lead by a Stallman-less Steering Comittee.

But I DO expect that, in the long run, a Stallman-less Steering
Comittee might do something not aligned with the long-term
interests of Free Software, abusing my trust again.

Maybe not you. Maybe not the CURRENT Steering Committee.

But people, groups and incentives changes.
Stallman does not.


Giacomo

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Wed, 31 Mar 2021 at 14:30, Giacomo Tesio wrote:
> But people, groups and incentives changes.
> Stallman does not.

Well, he's not immortal. Are you really suggesting that his crowning
achievement (the free software movement and copyleft) is actually not
sustainable, and only works if he's watching?

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Thursday, April 01, 2021 at 1:28 AM
> From: "Giacomo Tesio" <giacomo@tesio.it>
> To: "Mark Wielaard" <mark@klomp.org>
> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> Hi Mark,
>
> I'm a bit in a hurry and do not really want to focus on what happened
> in Harvey: to my eyes that story just show you cannot trust people just
> because they are nice and well known "open source" contributors, or
> because they work for big multinational that "do no evil" or even
> join the Good Guys (TM) of Software Freedom Conservancy.
>
> But let me clarify
>
> On Wed, 31 Mar 2021 13:34:17 +0200 Mark Wielaard wrote:
>
> > I looked a bit at that issue you filed and how they handled your
> > request to remove your code from the project. And I must say I don't
> > really understand what you believe they did wrong, they seemed to have
> > acknowledged and corrected their mistake and then removed all the code
> > you wanted to have removed.
>
> I asked them to `git revert` my changes referencing the issue, so that
> the code I reused in my own fork of Plan 9 was safe that nobody could
> claim copyright of my work after, say, a change in the version control
> system adopted by the project.
>
> Instead they did a `git rebase` over which, I was pretty surprised
> actually, they "accidentaly" squashed some of my own commits verbatim
> (but without my name) in incredibly large commits.
> And you know, they had to git push -f such rebase, breaking all the
> existing github forks (while the `git revert` approach would not have
> caused any issue to anybody)
>
> > There is some disagreement over whether a
> > mass change of function declarations is copyrightable or not.
>
> And implementations. And kernel changes that took a couple of days to
> get right (Harvey kernel was pretty unstable back then). And more I did
> not remember but I noticed back then:
>
>
> > But I happen to agree with them that if there is only one way to do
> > it, then having someone else do the same transformation is a correct
> > way to resolve this.
>
> Sure!
>
> But first, there were several different ways to do that (several
> equivalent typedefs were already in place in u.h, without even
> mentioning macros and so on), and more importantly if you actually
> redo the same work in the same way because there is a single way
> to do that, you do in a dedicated commit with an author that takes
> the clear responsibility for change.
>
> Instead my work (or a totally, byte-for-byte equivalent, one) got
> squashed into gigantic commits that include several very large commits
> of several authors (all mentioned in the commit message... but me).
>
>
> > To make this copyright issue somewhat relevant to GCC. GCC doesn't
> > currently contain individual copyright statements and most of the code
> > is currently assigned to the FSF. So the above mistake won't happen
> > when contributing to GCC, but mostly because of the technicality that
> > you sign away your copyright up front.
>
> Oh sorry, I wasn't clear enough about this.
>
> I'm SURE that this specific issue would not happen on GCC.
> Nor on Linux. Nor in several other Free Software and Open Source
> communities.
>
> But I think you are missing the valuable lesson that the Harvey team
> (some of which actually signed the rms-open-letter) tauht me: I didn't
> expected ANYTHING like this to happen. And I didn't expect SFC to not
> expell a project doing something like this.
>
> I trusted them both. All of them.
>
>
> So ultimately I do not expect this specific issue to occur in a
> hypothetical GCC lead by a Stallman-less Steering Comittee.
>
> But I DO expect that, in the long run, a Stallman-less Steering
> Comittee might do something not aligned with the long-term
> interests of Free Software, abusing my trust again.
>
> Maybe not you. Maybe not the CURRENT Steering Committee.
>
> But people, groups and incentives changes.
> Stallman does not.

It is likely that anothep person or group will evolve, which
although not Stallman-Like, work within the free software idea.

After Newton, there were other illustrious people.  Does not mean
everything stops forever after the demise of Richard.

> Giacomo
>

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Wednesday, March 31, 2021 at 11:34 PM
> From: "Mark Wielaard" <mark@klomp.org>
> To: "Giacomo Tesio" <giacomo@tesio.it>
> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> Hi Giacomo,
> 
> On Tue, Mar 30, 2021 at 11:28:49PM +0200, Giacomo Tesio wrote:
> > I've to say I'm a bit confused, but maybe we have different sources and
> > experience so we have different perspective on the matter.
> 
> Yes, I am pretty sure the perspective changes for people who have had
> longer, or more direct, exposure to Richard, while working on GNU or
> GCC over the years.
>  
> > That being said (and for full disclosure), I also consider his return to
> > the FSF fair, because the shitstorm that caused his resign two years
> > ago was built on top of a severe misrepresentation of his words, as
> > described here https://jorgemorais.gitlab.io/justice-for-rms/ and
> > admitted also by the people arguing against his return (see the
> > various edits at https://rms-open-letter.github.io/appendix ).
> 
> So this for example depends on whether you believe this is the one and
> only incident that can easily be explained away or if it is a decades
> long pattern of behavior where people finally had enough. See for
> example this blog that links and lists various other past events
> https://www.harihareswara.net/sumana/2021/03/26/0

In 2017, Marianne Corvellec was discussing GNU Philosophy and his
elaborations were valid.  Having worked with both, I agree with       
Richard stance.

Regarding, the Glibc Controversy, the comment was a criticism about
the United States Federal Censorship Regulations that were being
proposed.  This was the result of Roe vs. Wade that affirmed a woman’s
constitutional right to an abortion.  Opponents of the ruling have
steadfastly refused to accept it, and have tried to overturn it altogether.

I disagree with the conclusions resulting from Roe vs. Wade.  Doing what
you want does not mean you can act at any level of irresponsibility.  People
have to understand this - there are many documented cases where families 
have killed their own daughters.  I am particularly saying this because it
happens more to girls.  Because the parents believe that after they are
their children and if things don't turn out the way they wanted, they 
can kill them.

I personally disagree with Stallman regarding the joke.  But, I do not
fall within the camp that worked to remove it.

As for the "safe spaces" phase, this is about eliminating anything and
everything that could emotionally troubling students. This assumes a high
degree of fragility among western students.  I work as a journalist and
have had colleagues blown to smithereens - foot there, bits of brain there.
I wonder how many of you bitches, have ever been shot or had a bomb blown
up your ass.   

After scrutinising many of the presented arguments for removing Richard
Stallman from public and working life.  

I have to conclude that the drive is another ridiculous and sad story of a 
smear campaign in the media and on social networks.  This includes the big
companies that do a lot of high level work for the government and for big
corporations - e.g. Red Hat subsidiary of IBM, Facebook.  Digging into minor
and fabricated events to somehow attack his credibility.

Peaple have lost the narrative.  I therefore deplore the offensive against 
Richard Stallman and those who support him.  I see a huge opportunity for
journalists to dig into the real story.

> You are referencing the recent open letter which isn't really what
> people are discussing here. Although many probably sympathize with
> calling for the removal of the entire Board of the Free Software
> Foundation and calling for Richard M. Stallman to be removed from all
> leadership positions, including the GNU Project
> 
> You can disagree with the specific way that was worded and still come
> to the same conclusion. See for example https://www.arp242.net/rms.html
> 
> > On Tue, 30 Mar 2021 18:50:52 +0200 Martin Jambor wrote:
> > 
> > > Nobody suggested that GCC would be relicensed and certainly not to a
> > > non-free license.  If you decide to contribute your port upstream, it
> > > will be safe with us, regardless of who will or will not be on the
> > > steering committee
> > 
> > When I joined the Harvey project they were all fun and welcoming.
> > When I asked how and where to write my copyright statement, I was
> > answered by the seasoned and well known Google's engineer that a few
> > years later completely removed my name from the project without
> > removing the contributions.
> > 
> > Harvey is copylefted too (GPLv2) and as you know, this sort of
> > behaviour would trigger GPL termination, but Harvey is part of
> > Software Freedom Conservancy and the violation of my copyright
> > likely occurred during the working hours of the above engineer.
> > 
> > So they were the good guys and the most powerful guys, together.
> > I had no hope in a US court (and I'm Italian and... let say "not rich").
> > 
> > 
> > They taught me a valuable lesson, though.
> > 
> > In the long run, even the good guys betray your trust if they have a
> > reason to and they think they can get away with that.
> 
> I looked a bit at that issue you filed and how they handled your
> request to remove your code from the project. And I must say I don't
> really understand what you believe they did wrong, they seemed to have
> acknowledged and corrected their mistake and then removed all the code
> you wanted to have removed. There is some disagreement over whether a
> mass change of function declarations is copyrightable or not. But I
> happen to agree with them that if there is only one way to do it, then
> having someone else do the same transformation is a correct way to
> resolve this. I am not sure I understand your goal in this particular
> case. Sorry.
> 
> To make this copyright issue somewhat relevant to GCC. GCC doesn't
> currently contain individual copyright statements and most of the code
> is currently assigned to the FSF. So the above mistake won't happen
> when contributing to GCC, but mostly because of the technicality that
> you sign away your copyright up front.
> 
> > This means that its core value, its main "selling point", is not how
> > cool it is, but how it is designed, developed and distributed to
> > maximise software freedom.
> > 
> > IOW, I can imagine scenarios where some features should NOT be
> > introduced to reach this political goal which is MORE important
> > than the technical goal of compiler suite
> > 
> > To this aim, I'd prefer to see RMS in the GCC's SC.
> > Because to me GCC is not just "open source", it's not just matter of
> > seeing the source: it's Free Software, it should be designed and
> > developed TO maximize software freedom!
> 
> But even here RMS is just one voice and his insights are not always
> very accurate. His technical knowledge of the code base and of the
> community who develops the code is simply not always current. That
> doesn't mean he cannot understand the technology, he can, he still is
> really smart. But it takes very long (months) to get him up to
> speed. Once he understand the issue he often comes to the right
> conclusion. But sometimes he doesn't because he doesn't have the full
> picture. If he doesn't it might take months again to convince him he
> was wrong. Which he will never admit, he will simply say people didn't
> inform him about some change in technology or community participation,
> when he changes his opinion. Yes, he always wants to maximize software
> freedom, and so do many others with him, but his ideas of how to
> design and develop code to achieve that aren't always accurate or
> effective.
> 
> > On Tue, 30 Mar 2021 14:09:26 -0400 JeanHeyd Meneide wrote:
> > 
> > > >      My problem is Dr. Richard M. Stallman stands credibly and
> > > > factually accused of Doxxing and GCC contributor/participant and
> > > > knowingly manipulating the project for his own personal reasons.  
> > > 
> > > This should be "RMS explicitly sanctioned, encouraged, and
> > > blessed the Doxxing of an individual". Apologies, he did not do the
> > > doxxing himself; this was a fat finger on my part. 
> > 
> > Thanks for the clarification. I was quite surprised actually, because
> > I didn't read such accuse among the others in the rms-open-letter.
> > 
> > Did it happen on a public mailing list I can read?
> > Or maybe in a public forum? Or something that has been published
> > somewhere?
> 
> I think this is actually two separate incidents of women being
> harassed on a public gnu mailinglist for speaking up against Richard's
> behavior. One happening about a year ago, another last week. Both by
> individuals who were "defending" RMS. Whether to call them doxxing
> depends on your definition. I would say the last one clearly was, the
> first one might "just" have been "normal" vile, misogynist and racist.
> 
> Some of it was on private gnu lists, where people were called
> subhumans and nazis. Which was obviously not a healthy environment to
> have a discussion. So we asked the FSF Executive Director for a public
> place to discuss GNU governance where we could have rules against such
> hate speech and he agreed. Sadly when a woman (GCC contributor) spoke
> up she got attacked in such a vile way we had to block/moderate some
> posts. RMS disagreed with the public discussion and assumed the
> moderators were preventing people from voicing certain opinions so
> arranged for new moderators to take over the list that he assumed were
> loyal to him and then said...
> 
> > The new moderators have now allowed people to defend the GNU Project
> > and to defend me personally.  If you would like to do these things,
> > please do not hold back.
> 
> I am not going to link to the public discussion that resulted because
> of his call to action. It was truly horrible. I am also not going to
> link to the latest doxxing campaign of the other woman because even
> though the link to her picture, address and police station have been
> removed from the archives what is left is almost equally bad. The
> people involved (even if they acted for RMS, they did so in good faith)
> don't deserve to be a target even more. And it doesn't help the
> healing process to relitigate this incident. It happened, that is
> painful enough.
> 
> Again, it isn't about this one or two incidents. I am sure someone can
> find a way to explained it away by saying people simply misunderstood
> his intentions or that no law was broken. But it is about a pattern of
> behavior that shows RMS creates a misogynist, racist and transphobic
> environment by (hopefully unknowingly) setting the example that others
> will then follow and amplify.
> 
> Cheers,
> 
> Mark
>

Re: Remove RMS from the GCC Steering Committee

[Paul Koning]

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?

2. Is there a formal process for receiving claims of infraction of this code, and for adjudicating such claims?

	paul

Re: Remove RMS from the GCC Steering Committee

[Joel Sherrill]

On Wed, Mar 31, 2021 at 9:23 AM Paul Koning via Gcc <gcc@gcc.gnu.org> 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


> 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?

--joel


>
>         paul
>
>

Re: Remove RMS from the GCC Steering Committee

[Ian Lance Taylor]

On Wed, Mar 31, 2021 at 7:44 AM Joel Sherrill <joel@rtems.org> wrote:
>
> On Wed, Mar 31, 2021 at 9:23 AM Paul Koning via Gcc <gcc@gcc.gnu.org> 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

Re: Remove RMS from the GCC Steering Committee

[David Edelsohn]

[I previously sent this from another email account, but it seems to be
lost.  I am sending this on behalf of the GCC Steering Committee.]

In 2012 RMS was added to the GCC Steering Committee web page
based on his role in the GNU Project, though his role as a member
of the Steering Committee has been ambiguous and he was not a member
of the Steering Committee when EGCS became GCC[1].  We no longer feel
that this listing serves the best interests of the GCC developer and
user community.  Therefore, we are removing him from the page.

GCC supports the principles of Free Software and has remained aligned
with the GNU Project since EGCS became GCC, but effectively has continued
to operate as an autonomous project.

The GCC Steering Committee is committed to providing a friendly, safe
and welcoming environment for all, regardless of gender identity and
expression, sexual orientation, disabilities, neurodiversity, physical
appearance, body size, ethnicity, nationality, race, age, religion, or
similar personal characteristics.

- The GCC Steering Committee

[1] https://static.lwn.net/1999/0429/a/gcc.html

Re: Remove RMS from the GCC Steering Committee

[Nathan Sidwell]

On 3/31/21 2:27 PM, David Edelsohn via Gcc wrote:
> [I previously sent this from another email account, but it seems to be
> lost.  I am sending this on behalf of the GCC Steering Committee.]
> 
> In 2012 RMS was added to the GCC Steering Committee web page
> based on his role in the GNU Project, though his role as a member
> of the Steering Committee has been ambiguous and he was not a member
> of the Steering Committee when EGCS became GCC[1].  We no longer feel
> that this listing serves the best interests of the GCC developer and
> user community.  Therefore, we are removing him from the page.
> 
> GCC supports the principles of Free Software and has remained aligned
> with the GNU Project since EGCS became GCC, but effectively has continued
> to operate as an autonomous project.
> 
> The GCC Steering Committee is committed to providing a friendly, safe
> and welcoming environment for all, regardless of gender identity and
> expression, sexual orientation, disabilities, neurodiversity, physical
> appearance, body size, ethnicity, nationality, race, age, religion, or
> similar personal characteristics.
> 
> - The GCC Steering Committee
> 
> [1] https://static.lwn.net/1999/0429/a/gcc.html
> 

You, the SC, have chosen to fix this as a clerical error.  The most 
do-nothing response, other than actually doing nothing.

I am profoundly disappointed that you have not even acknowledged the 
harm RMS has caused.  Using passive voiced 'RMS was added' phrasing. 
You're not explicitly saying that was incorrect, and neither are you 
saying it was correct.   Your language attempts to distance you from 
your choices.

'we no longer feel the listing serves the best interest'.  'Therefore, 
we are removing him from the page FULLSTOP'. Well, at least that's not 
passive voice, but it is a milque-toast response.   You're not removing 
him from the SC, merely removing mention of him from the listing. 
You're not adding words to the website mentioning this historical 
ambiguity/error/misjudgement (you'd say if you were, right?).  You're 
not adding words acknowledging that RMS's involvement has been 
detrimental and repelled contributors.  Nor are you apologizing.  You're 
not owning your mistake.  You just hope the problem will silently go 
away.  The problem will not go away.

/You/ involved RMS in SC discussions.  /You/ treated him as a member 
thereof.  /You/ gave him controlling rights.

You have misled the majority of GCC developers, and the wider community 
by doing so.  If it looks like a duck, walks like a duck, and talks like 
a duck, it's a duck.  (As compiler developers for duck-typed languages, 
you should understand that.)

You involved RMS prior to 2012, and continued to do so after.  Including 
after 2019 when he was no longer at the FSF.  Two instances I personally 
know of:

1) Sometime around 2005? maybe later, I lobbied to change gcc's 
implementation language to C++.  I failed because I'm lazy and learned I 
was arguing against an RMS effective veto.  (I learned this because Mark 
Mitchell informed me that some SC members were also pushing back against 
RMS's opposition to C++.  I was not privy to the actual SC discussion.) 
  If he was not an SC member, why was he even in that private 
conversation?  The public ML would have been more appropriate place for 
non-SC opinions to be voiced.  Just think, we could have transitioned to 
C++ earlier than we did, if it were not for the SC's inclusio of RMS.

2) Last year, I asked for libcody to be added as a subcomponent, with 
its Apachev2 license intact.  AFAICT RMS was involved in that licensing 
discussion, /for which I never received a response/.  He was not at the 
FSF then, so he could not render any FSF licensing opinion.  Why was he 
involved?  If he was not involved, how did he learn of it in order to 
ask me questions about C++ modules?  I only emailed the SC and the 
timing is too coincidental to draw a different conclusion.

Interactions I've had with the SC, beyond maintainer appointment, seem 
to run into RMS.  (In the original email I mentioned a third interaction 
about RMS's position on the SC, which didn't do so, but also was 
decidedly one way.)

You, the SC, do not state that you will not continue to involve RMS in 
discussions, just as you have done for the past 20 years.  You merely 
feel the listing is unfortunate.

Your final paragraph is the corporate BS of hollow men.  Nice words, no 
specific actions.

Richard Biener pointed out dysfunction in the SC.  The case of the 
missing question I asked in 2019 also points to that.  This response 
gives me no confidence that things will materially change.  I call for 
the dissolution of the SC, replacing it with a more open, functional and 
inclusive body (which includes, nothing).

nathan

FWIW, I am surprised that you, the SC, chose to respond only to the 
mailing list, and not CC me, the original complainant, of your decision. 
  Perhaps that seems petty, but it is personally insulting.
-- 
Nathan Sidwell

Re: Remove RMS from the GCC Steering Committee

[Ian Lance Taylor]

On Thu, Apr 1, 2021 at 10:08 AM Nathan Sidwell <nathan@acm.org> wrote:
>
> You, the SC, have chosen to fix this as a clerical error.  The most
> do-nothing response, other than actually doing nothing.
>
> I am profoundly disappointed that you have not even acknowledged the
> harm RMS has caused.  Using passive voiced 'RMS was added' phrasing.
> You're not explicitly saying that was incorrect, and neither are you
> saying it was correct.   Your language attempts to distance you from
> your choices.
>
> 'we no longer feel the listing serves the best interest'.  'Therefore,
> we are removing him from the page FULLSTOP'. Well, at least that's not
> passive voice, but it is a milque-toast response.   You're not removing
> him from the SC, merely removing mention of him from the listing.
> You're not adding words to the website mentioning this historical
> ambiguity/error/misjudgement (you'd say if you were, right?).  You're
> not adding words acknowledging that RMS's involvement has been
> detrimental and repelled contributors.  Nor are you apologizing.  You're
> not owning your mistake.  You just hope the problem will silently go
> away.  The problem will not go away.
>
> /You/ involved RMS in SC discussions.  /You/ treated him as a member
> thereof.  /You/ gave him controlling rights.
>
> You have misled the majority of GCC developers, and the wider community
> by doing so.  If it looks like a duck, walks like a duck, and talks like
> a duck, it's a duck.  (As compiler developers for duck-typed languages,
> you should understand that.)
>
> You involved RMS prior to 2012, and continued to do so after.  Including
> after 2019 when he was no longer at the FSF.  Two instances I personally
> know of:
>
> 1) Sometime around 2005? maybe later, I lobbied to change gcc's
> implementation language to C++.  I failed because I'm lazy and learned I
> was arguing against an RMS effective veto.  (I learned this because Mark
> Mitchell informed me that some SC members were also pushing back against
> RMS's opposition to C++.  I was not privy to the actual SC discussion.)
>   If he was not an SC member, why was he even in that private
> conversation?  The public ML would have been more appropriate place for
> non-SC opinions to be voiced.  Just think, we could have transitioned to
> C++ earlier than we did, if it were not for the SC's inclusio of RMS.
>
> 2) Last year, I asked for libcody to be added as a subcomponent, with
> its Apachev2 license intact.  AFAICT RMS was involved in that licensing
> discussion, /for which I never received a response/.  He was not at the
> FSF then, so he could not render any FSF licensing opinion.  Why was he
> involved?  If he was not involved, how did he learn of it in order to
> ask me questions about C++ modules?  I only emailed the SC and the
> timing is too coincidental to draw a different conclusion.
>
> Interactions I've had with the SC, beyond maintainer appointment, seem
> to run into RMS.  (In the original email I mentioned a third interaction
> about RMS's position on the SC, which didn't do so, but also was
> decidedly one way.)
>
> You, the SC, do not state that you will not continue to involve RMS in
> discussions, just as you have done for the past 20 years.  You merely
> feel the listing is unfortunate.
>
> Your final paragraph is the corporate BS of hollow men.  Nice words, no
> specific actions.
>
> Richard Biener pointed out dysfunction in the SC.  The case of the
> missing question I asked in 2019 also points to that.  This response
> gives me no confidence that things will materially change.  I call for
> the dissolution of the SC, replacing it with a more open, functional and
> inclusive body (which includes, nothing).
>
> nathan
>
> FWIW, I am surprised that you, the SC, chose to respond only to the
> mailing list, and not CC me, the original complainant, of your decision.
>   Perhaps that seems petty, but it is personally insulting.


Nathan, you are clearly angry and frustrated.  I'm sorry about that.

I'm going to give some of my own personal opinions.  I'm not at all
speaking for the committee, and other committee members may disagree.

The steering committee is just a bunch of GCC hackers who originally
self-organized to manage the EGCS fork.  As it says at
https://gcc.gnu.org/steering.html, "committee members were chosen to
represent the interests of communities."  I was not on the steering
committee at the time, but I was somewhat involved with thinking about
who should be, and that statement accurately describes what we were
trying to do.  The intent was to ensure that when decisions were made
that covered the GCC project as a whole, all interested groups would
have a representative.

In practice the steering committee makes few decisions.  Naturally,
members of the committee work to improve GCC in various ways.  That
work almost never involves any sort of steering committee discussion.

I think you want the steering committee to issue a statement about
RMS's behavior.  I think that is approximately as likely as collecting
the GCC maintainers together to issue a statement about RMS's
behavior.  It's not impossible.  But it's not something anybody is
really trying to do.

Speaking for myself, personally, I will say that RMS has harmed
people, and he has to the best of my knowledge never acknowledged that
harm.  As such he should not be in a leadership position of any
organization.  The FSF should not have put RMS back on the board.  And
RMS should not be in a leadership position for GCC in particular.


Going back to the GCC steering committee, you make several accusations
(I think that is a fair word to use here).  Again I'm going to give my
own personal reactions.  I'm telling the truth to the best of my
recollection, but I can't prove what I say.


> /You/ involved RMS in SC discussions.

Yes, we did.  He never actually said anything in any discussion that
he did not start himself, but he was CC'ed.

> /You/ treated him as a member thereof.

Yes, we did.  He never actually voted on anything, and I don't know
what we would have done if he had, but he was treated as a member.

>  /You/ gave him controlling rights.

No, we didn't.  The pattern of his interactions with the steering
committee, which were infrequent, was that he would ask us to do
something, and we would explain why we were not going to do that.


> You have misled the majority of GCC developers, and the wider community
> by doing so.  If it looks like a duck, walks like a duck, and talks like
> a duck, it's a duck.

Sorry, I don't quite understand this one.  It's not clear to me how
the committee misled anyone.


> 1) Sometime around 2005? maybe later, I lobbied to change gcc's
> implementation language to C++.  I failed because I'm lazy and learned I
> was arguing against an RMS effective veto.  (I learned this because Mark
> Mitchell informed me that some SC members were also pushing back against
> RMS's opposition to C++.  I was not privy to the actual SC discussion.)
>   If he was not an SC member, why was he even in that private
> conversation?  The public ML would have been more appropriate place for
> non-SC opinions to be voiced.  Just think, we could have transitioned to
> C++ earlier than we did, if it were not for the SC's inclusio of RMS.

I wasn't on the committee at the time so I don't know what happened.
But honestly, as one of the main people who got GCC to convert to C++,
I don't think it could have happened any earlier.  For several years
at the GCC Summit, later the GNU Cauldron, I asked for a show of hands
for how many GCC developers were willing to convert to C++.  There
were strong and significant objections from numerous maintainers long
after 2005.  Certainly there were significant objections when I made
my presentation at the GCC Summit in 2008.  In 2010 the steering
committee (which I was not on at the time) approved the use of C++ for
GCC.  Even then it took several more years to make the switch.

So, yes, if RMS's concerns were the only reason that the steering
committee did not permit using C++ for GCC In 2005, that was wrong.
He should not have had a veto on GCC internal decisions.  But we
should not extrapolate from that to think that anything would have
happened differently on the technical side.

> 2) Last year, I asked for libcody to be added as a subcomponent, with
> its Apachev2 license intact.  AFAICT RMS was involved in that licensing
> discussion, /for which I never received a response/.  He was not at the
> FSF then, so he could not render any FSF licensing opinion.  Why was he
> involved?  If he was not involved, how did he learn of it in order to
> ask me questions about C++ modules?  I only emailed the SC and the
> timing is too coincidental to draw a different conclusion.

Yes, we definitely dropped the ball on that.  Sorry.  If that ever
happens again I would encourage you to ping.

I checked the mailing list archives.  Jeff and I expressed support for
using libcody.  Nobody else said anything.  Certainly RMS didn't say
anything, and it would have been astonishing if he had.  But, yes, he
was CC'ed.


> Richard Biener pointed out dysfunction in the SC.  The case of the
> missing question I asked in 2019 also points to that.  This response
> gives me no confidence that things will materially change.  I call for
> the dissolution of the SC, replacing it with a more open, functional and
> inclusive body (which includes, nothing).

I'm fine with that in principle.  But it's like everything else with
GCC, and with free software in general: someone has to do the work.
We can't literally replace the SC with nothing, at least not unless we
do a much bigger overhaul of the GCC development process: someone has
to decide who is going to have maintainership rights and
responsibilities for different parts of the compiler.

Again, I'm sorry for the ways in which the steering committee has made
you feel angry and frustrated.

Ian

Re: Remove RMS from the GCC Steering Committee

[Joseph Myers]

On Thu, 1 Apr 2021, Ian Lance Taylor via Gcc wrote:

> > 2) Last year, I asked for libcody to be added as a subcomponent, with
> > its Apachev2 license intact.  AFAICT RMS was involved in that licensing
> > discussion, /for which I never received a response/.  He was not at the
> > FSF then, so he could not render any FSF licensing opinion.  Why was he
> > involved?  If he was not involved, how did he learn of it in order to
> > ask me questions about C++ modules?  I only emailed the SC and the
> > timing is too coincidental to draw a different conclusion.
> 
> Yes, we definitely dropped the ball on that.  Sorry.  If that ever
> happens again I would encourage you to ping.
> 
> I checked the mailing list archives.  Jeff and I expressed support for
> using libcody.  Nobody else said anything.  Certainly RMS didn't say
> anything, and it would have been astonishing if he had.  But, yes, he
> was CC'ed.

And while in that case RMS probably learned of modules and libcody through 
the SC mailing list, in general he has this habit of asking GNU package 
developers random questions related to their packages.

RMS once asked me about the status of fused multiply-add support in glibc.  
I don't know why.  He wasn't asking for any changes or objecting to 
anything the glibc maintainers had done.  I'd hope that future Chief 
GNUisances won't try to get involved in details like that as part of their 
role as Chief GNUisance, because it's clearly outside the scope of such a 
role, and that if interested in such details as an individual free 
software developer (but not directly involved in development of the 
package in question) they will do more research of their own first and 
then approach the usual public mailing lists or other public discussion 
areas rather than individual developers.

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: Remove RMS from the GCC Steering Committee

[Christian Groessler]

On 4/1/21 10:33 PM, Joseph Myers wrote:
> RMS once asked me about the status of fused multiply-add support in glibc.
> I don't know why.  He wasn't asking for any changes or objecting to
> anything the glibc maintainers had done.  I'd hope that future Chief
> GNUisances won't try to get involved in details like that as part of their
> role as Chief GNUisance, because it's clearly outside the scope of such a
> role, and that if interested in such details as an individual free
> software developer (but not directly involved in development of the
> package in question) they will do more research of their own first and
> then approach the usual public mailing lists or other public discussion
> areas rather than individual developers.


So what? He asked you. I don't know why he asked and I don't see a bad 
intent in it.

This bashing is getting ridiculous now...

regards,
chris

Re: Remove RMS from the GCC Steering Committee

[Thomas Koenig]

On 01.04.21 22:33, Joseph Myers wrote:
> And while in that case RMS probably learned of modules and libcody through
> the SC mailing list, in general he has this habit of asking GNU package
> developers random questions related to their packages.

I've been asked a few questions about gfortran by random people, which
I have always tried to answer correctly and courteously, with a copy
to the relevant mailing list.

If RMS had ever done the same (pretty unlikely, Fortran isnt't his
thing), I would have done the same without thinking twice about it.

Re: Remove RMS from the GCC Steering Committee

[Richard Kenner]

> If RMS had ever done the same (pretty unlikely, Fortran isnt't his
> thing), I would have done the same without thinking twice about it.

I agree with that sentiment.  The fact that somebody has a certain
role doesn't necessarily mean that the question is asked with that hat
on: it may be nothing more than curiousity.

Re: Remove RMS from the GCC Steering Committee

[Nathan Sidwell]

Ian,
thank you for taking the time to write this.  I appreciate that you have 
reached out.  I do have a couple of comments though.

On 4/1/21 3:19 PM, Ian Lance Taylor wrote:
> On Thu, Apr 1, 2021 at 10:08 AM Nathan Sidwell <nathan@acm.org> wrote:

> I think you want the steering committee to issue a statement about
> RMS's behavior.  I think that is approximately as likely as collecting
> the GCC maintainers together to issue a statement about RMS's
> behavior.  It's not impossible.  But it's not something anybody is
> really trying to do.

And that speaks volumes.  The one thing we have in the form of structure 
is not trying to do that thing.

> Going back to the GCC steering committee, you make several accusations
> (I think that is a fair word to use here).  Again I'm going to give my
> own personal reactions.  I'm telling the truth to the best of my
> recollection, but I can't prove what I say.

That's understandable.
>>   /You/ gave him controlling rights.
> 
> No, we didn't.  The pattern of his interactions with the steering
> committee, which were infrequent, was that he would ask us to do
> something, and we would explain why we were not going to do that.

The appearance is that the SC did.  Another event that I've now 
remembered concerns powerpc floating point.  My understanding is that 
RMS vetoed something, and an SC member reached out to me, as if the 
personal interactions of another SC member was something I could 
control.  If RMS had no power, that conversation need not have happened.

> Sorry, I don't quite understand this one.  It's not clear to me how
> the committee misled anyone.

by observable behaviour, including the listing on the web page -- who 
other than the SC could tell it was incorrect?  (perhaps you're 
associating intent with 'misled'?  I'm associating 'impact')

You're quite likely right about the timing of the C++ change, but the 
earlier interaction caused damage.

>> 2) Last year, I asked for libcody to be added as a subcomponent, with
>> its Apachev2 license intact.  AFAICT RMS was involved in that licensing
>> discussion, /for which I never received a response/.  He was not at the
>> FSF then, so he could not render any FSF licensing opinion.  Why was he
>> involved?  If he was not involved, how did he learn of it in order to
>> ask me questions about C++ modules?  I only emailed the SC and the
>> timing is too coincidental to draw a different conclusion.
> 
> Yes, we definitely dropped the ball on that.  Sorry.  If that ever
> happens again I would encourage you to ping.
> 
> I checked the mailing list archives.  Jeff and I expressed support for
> using libcody.  Nobody else said anything.  Certainly RMS didn't say
> anything, and it would have been astonishing if he had.  But, yes, he
> was CC'ed.

I've realized what happened was that I very quickly received an email 
saying just 'looks good to me'.  Which didn't read like an SC blessing 
at all.  I thought it was just personal comment.   You're right, I 
should have pinged, but one reason I didn't was because I was concerned 
RMS would veto the whole shebang.  Don't poke the sleeping bear.   Fault 
all round.

nathan
-- 
Nathan Sidwell

Re: Remove RMS from the GCC Steering Committee

[Richard Biener]

On Thu, Apr 1, 2021 at 9:21 PM Ian Lance Taylor via Gcc <gcc@gcc.gnu.org> wrote:
>
> On Thu, Apr 1, 2021 at 10:08 AM Nathan Sidwell <nathan@acm.org> wrote:
> >
> > Richard Biener pointed out dysfunction in the SC.  The case of the
> > missing question I asked in 2019 also points to that.  This response
> > gives me no confidence that things will materially change.  I call for
> > the dissolution of the SC, replacing it with a more open, functional and
> > inclusive body (which includes, nothing).
>
> I'm fine with that in principle.  But it's like everything else with
> GCC, and with free software in general: someone has to do the work.
> We can't literally replace the SC with nothing, at least not unless we
> do a much bigger overhaul of the GCC development process: someone has
> to decide who is going to have maintainership rights and
> responsibilities for different parts of the compiler.

Seeing the word "dysfunction" I don't remember using I want to clarify
the non-openess which I intended to criticize.  The SC is not "open" because:
- it appoints itself (new members, that is) - in fact in theory it
should be appointed
  by the FSF because the SC is the GNU maintainer of GCC
- all requests and discussions are _private_ - the SC does not report to the
  GCC project (it might report to the FSF which it is formally a delegate of)
- you can reach the SC only indirectly (unless you know the secret mailing list
  it operates on) - CC an SC member and hope a request is forwarded

now I understand the SC sees itself as buffer between GCC and the FSF (RMS
in particular) and it thinks we need to be protected from direct engagement.  I
think this is wrong.  I can very well say NO to RMS myself.

I'm actually curious how many of the 13 SC members actively contribute or
whether the "SC show" is a one or two persons game and the "13" is just
to make the SC appear as a big representative group of people.

Thus I request an archive of the SC mailing list be made publically available
and the SC discussion from now on take place in an open forum (you can
choose to moderate everybody so the discussion while carried out in open
is still amongst SC members only).

Richard.

Re: Remove RMS from the GCC Steering Committee

[Matthias Klose]

On 4/6/21 12:27 PM, Richard Biener via Gcc wrote:
> On Thu, Apr 1, 2021 at 9:21 PM Ian Lance Taylor via Gcc <gcc@gcc.gnu.org> wrote:
>>
>> On Thu, Apr 1, 2021 at 10:08 AM Nathan Sidwell <nathan@acm.org> wrote:
>>>
>>> Richard Biener pointed out dysfunction in the SC.  The case of the
>>> missing question I asked in 2019 also points to that.  This response
>>> gives me no confidence that things will materially change.  I call for
>>> the dissolution of the SC, replacing it with a more open, functional and
>>> inclusive body (which includes, nothing).
>>
>> I'm fine with that in principle.  But it's like everything else with
>> GCC, and with free software in general: someone has to do the work.
>> We can't literally replace the SC with nothing, at least not unless we
>> do a much bigger overhaul of the GCC development process: someone has
>> to decide who is going to have maintainership rights and
>> responsibilities for different parts of the compiler.
> 
> Seeing the word "dysfunction" I don't remember using I want to clarify
> the non-openess which I intended to criticize.  The SC is not "open" because:
> - it appoints itself (new members, that is) - in fact in theory it
> should be appointed
>   by the FSF because the SC is the GNU maintainer of GCC
> - all requests and discussions are _private_ - the SC does not report to the
>   GCC project (it might report to the FSF which it is formally a delegate of)
> - you can reach the SC only indirectly (unless you know the secret mailing list
>   it operates on) - CC an SC member and hope a request is forwarded
> 
> now I understand the SC sees itself as buffer between GCC and the FSF (RMS
> in particular) and it thinks we need to be protected from direct engagement.  I
> think this is wrong.  I can very well say NO to RMS myself.
> 
> I'm actually curious how many of the 13 SC members actively contribute or
> whether the "SC show" is a one or two persons game and the "13" is just
> to make the SC appear as a big representative group of people.
> 
> Thus I request an archive of the SC mailing list be made publically available
> and the SC discussion from now on take place in an open forum (you can
> choose to moderate everybody so the discussion while carried out in open
> is still amongst SC members only).

Not sure if a completely open SC list would help, seeing other SC's or tech
boards having a private communication channel as well.  But +1 on a public point
of contact, with a ML archive behind.  Issues are involuntarily dropped, or not
communicated like last year's gm2 contribution which stayed silent for quiet a
while and the SC thought that a resolution had been communicated.

Matthias

Re: Remove RMS from the GCC Steering Committee

[Siddhesh Poyarekar]

On 4/6/21 3:57 PM, Richard Biener via Gcc wrote:
> Seeing the word "dysfunction" I don't remember using I want to clarify
> the non-openess which I intended to criticize.  The SC is not "open" because:
> - it appoints itself (new members, that is) - in fact in theory it
> should be appointed
>    by the FSF because the SC is the GNU maintainer of GCC
> - all requests and discussions are _private_ - the SC does not report to the
>    GCC project (it might report to the FSF which it is formally a delegate of)
> - you can reach the SC only indirectly (unless you know the secret mailing list
>    it operates on) - CC an SC member and hope a request is forwarded
> 
> now I understand the SC sees itself as buffer between GCC and the FSF (RMS
> in particular) and it thinks we need to be protected from direct engagement.  I
> think this is wrong.  I can very well say NO to RMS myself.

FWIW, the glibc FSF stewards are analogous to the SC and pretty much all 
of those points apply to them.  My impression is that it's a symptom of 
governance style of GNU projects (or maybe GNU *toolchain* projects due 
to shared history) and not specifically anything to do with the steering 
committee or the glibc FSF stewards.  Perhaps (and I guess it's more 
hope than knowledge) dissociation from GNU/FSF will make it easier to 
change the nature of the SC/steward governance.

Siddhesh

Re: Remove RMS from the GCC Steering Committee

[Ian Lance Taylor]

On Tue, Apr 6, 2021 at 3:28 AM Richard Biener
<richard.guenther@gmail.com> wrote:
>
> Seeing the word "dysfunction" I don't remember using I want to clarify
> the non-openess which I intended to criticize.  The SC is not "open" because:
> - it appoints itself (new members, that is) - in fact in theory it
> should be appointed
>   by the FSF because the SC is the GNU maintainer of GCC
> - all requests and discussions are _private_ - the SC does not report to the
>   GCC project (it might report to the FSF which it is formally a delegate of)
> - you can reach the SC only indirectly (unless you know the secret mailing list
>   it operates on) - CC an SC member and hope a request is forwarded
>
> now I understand the SC sees itself as buffer between GCC and the FSF (RMS
> in particular) and it thinks we need to be protected from direct engagement.  I
> think this is wrong.  I can very well say NO to RMS myself.
>
> I'm actually curious how many of the 13 SC members actively contribute or
> whether the "SC show" is a one or two persons game and the "13" is just
> to make the SC appear as a big representative group of people.
>
> Thus I request an archive of the SC mailing list be made publically available
> and the SC discussion from now on take place in an open forum (you can
> choose to moderate everybody so the discussion while carried out in open
> is still amongst SC members only).

To a first approximation, the only thing that the SC does is approve
maintainers.  Questions like Nathan's example of libcody are rare.  To
be pedantically clear, by "maintainers" I mean the people listed in
the MAINTAINERS file who have the right to approve and commit changes
to various parts of the compiler.

While most discussion about approving maintainers is pro forma, there
are sometimes discussions as to whether a particular person has the
appropriate knowledge and sense of responsibility for the role.  I
don't think it would be appropriate to require that those discussions
be held publically.  In any case it wouldn't work; if they were
required to be public, SC members would resort to private e-mail for
anything they didn't want to be public.

So perhaps one thing we should be talking about is: can we develop a
mechanism for approving maintainers that does not involve the SC?

For example, I am also involved with the Go language project.  In that
project, any existing maintainer (that is, any person with the right
to commit changes to the repo) can approve any person to be a new
maintainer.  However, all changes require approval from at least two
maintainers, and, of course there are people who take at least a quick
look at every commit after it happens.  The two maintainer rule is
enforced by tooling, as all changes to Go must be made through Gerrit
(https://www.gerritcodereview.com/).  I'm not suggesting that we adopt
this for GCC, just mentioning as an example of a different approach
that does not require anything like the SC.

I'm sure other people on this list can give examples of other
approaches used by other free software projects.

Ian

Re: Remove RMS from the GCC Steering Committee

[David Malcolm]

On Wed, 2021-03-31 at 16:18 +0200, Christopher Dimech via Gcc wrote:

[...snip...]

> As for the "safe spaces" phase, this is about eliminating anything
> and
> everything that could emotionally troubling students. This assumes a
> high
> degree of fragility among western students.  I work as a journalist
> and
> have had colleagues blown to smithereens - foot there, bits of brain
> there.
> I wonder how many of you bitches, have ever been shot or had a bomb
> blown
> up your ass.   

I've been attempting to decide if you're merely trolling us, or if you
genuinely believe the stuff you've been posting to this list.

With your latest missive I'm leaning to the former interpretation, but
if the latter, may I humbly suggest that referring to us as "bitches"
might not be the best way to win people over, and that it's not normal
to have to work in a literal war zone, and that most reasonable people
do not want to work in a figurative war zone.

[...snip...]

Hope this is constructive
Dave

(my opinions only, not my employer's)

Re: Remove RMS from the GCC Steering Committee

[Christopher Dimech]

> Sent: Thursday, April 01, 2021 at 2:56 AM
> From: "David Malcolm" <dmalcolm@redhat.com>
> To: "Christopher Dimech" <dimech@gmx.com>, "Mark Wielaard" <mark@klomp.org>
> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Nathan Sidwell" <nathan@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> On Wed, 2021-03-31 at 16:18 +0200, Christopher Dimech via Gcc wrote:
> 
> [...snip...]
> 
> > As for the "safe spaces" phase, this is about eliminating anything
> > and
> > everything that could emotionally troubling students. This assumes a
> > high
> > degree of fragility among western students.  I work as a journalist
> > and
> > have had colleagues blown to smithereens - foot there, bits of brain
> > there.
> > I wonder how many of you bitches, have ever been shot or had a bomb
> > blown
> > up your ass.   
> 
> I've been attempting to decide if you're merely trolling us, or if you
> genuinely believe the stuff you've been posting to this list.
> 
> With your latest missive I'm leaning to the former interpretation, but
> if the latter, may I humbly suggest that referring to us as "bitches"
> might not be the best way to win people over, and that it's not normal
> to have to work in a literal war zone, and that most reasonable people
> do not want to work in a figurative war zone.
> 
> [...snip...]

I recognise it is not the best way, but the contempt is mainly directed
to those with a history of unjust accusations against Stallman.  
Although one can lean towards your interpretation, it is very easy to verify
my credentials.

https://www.corrieredimalta.com/coronavirus/la-diffusione-del-covid-19-a-malta-evento-b/

https://theshiftnews.com/2019/03/01/university-of-malta-building-fails-to-comply-with-safety-standards/

https://theshiftnews.com/2018/05/09/the-return-to-infantilism/

https://www.islesoftheleft.org/digital-rights-and-blockchain/



> Hope this is constructive
> Dave

Yes, I consider it constructive criticsism. 
 
> (my opinions only, not my employer's)
> 
>

Re: Remove RMS from the GCC Steering Committee

[Alexandre Oliva]

On Mar 30, 2021, JeanHeyd Meneide via Gcc <gcc@gcc.gnu.org> wrote:

>      My problem is Dr. Richard M. Stallman stands credibly and
> factually accused of Doxxing and GCC contributor/participant and
> knowingly manipulating the project for his own personal reasons.

This accusation is outright false, beyond any possible doubt.


A misguided person thought that reciprocating the doxxing against RMS
was a good way to defend him.  It's not.

The message went through because there is no censorship regime in effect.

RMS asked the unacceptable post to be deleted from the archives hosted
in GNU servers as soon as he learned about it.

I did not check whether that was done.  If you have any evidence that it
wasn't, please let me know.


That you got confirmation of a false claim from multiple developers you
talked to should now have you doubting other of their allegations.

If you look into them outside the attacking coalition, you *will* find
them to be built on just as flaky foundations.


-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: Remove RMS from the GCC Steering Committee

[JeanHeyd Meneide]

Dear Alexandre,

    As stated here, shortly after I sent my message
(https://gcc.gnu.org/pipermail/gcc/2021-March/235197.html):

> Apologies, a correction here. I should have more carefully read
> it, but this paragraph:
>
> >      My problem is Dr. Richard M. Stallman stands credibly and
> > factually accused of Doxxing and GCC contributor/participant and
> > knowingly manipulating the project for his own personal reasons.
>
>     This should be "RMS explicitly sanctioned, encouraged, and
> blessed the Doxxing of an individual". Apologies, he did not do the
> doxxing himself; this was a fat finger on my part. Please take that
> into account; the rest is accurate.

      Taking the correction into account, no, the accusation is not
even close to false. What you've presented here is your word ("This
accusation is outright false, beyond any possible doubt."), with a
shortened version of what happened and no evidence, and that does not
match the quoted responses from Stallman and other people who were
present in both the public mailing list discussion and the internal
mailing list. I was given quoted evidence of, after people being told
they were NOT allowed to attack people like this and go this far and
being banned by moderation, RMS taking explicit actions to UNDO that
moderation and explicitly, in the internal mailing list, state
(paraphrased): 'I have put a new moderator in. Have at it.'

     That the same individuals (who Stallman, again, explicitly and
knowingly) unshackled were then banned for continuing to do things
that were against the Community Guidelines and grossly inappropriate
(including the Doxxing). Stallman was not born yesterday, neither were
any of the moderators or contributors involved: Stallman deliberately
overturned moderator decisions and that decision went poorly after he
explicitly signaled to people that they should Go All Out.

     If you (or anyone else) have evidence to the contrary, logs,
screenshots, etc. that counteract what I know and I have already
received, then I would LOVE to be proven wrong and have ABSOLUTELY no
problem walking back every word I said and giving Richard M. Stallman
an apology and respect as well as apologizing to the mailing list for
believing to be led astray. If you feel the exact words should not be
shared publicly, you can e-mail me or message me privately; I have
honored everyone's right to privacy, and I will continue to do so.

     I must be explicitly clear here that the current body of evidence
gives me my current conviction. There is no planet, no galaxy, no
UNIVERSE, where someone who was already banned for going **way**
beyond acceptable behavior, and then brought back with their
punishment undone with the *explicit go-ahead to go forward* and a
*new moderator for that purpose*, would not take that as a signal to
be even nastier. If you are in a Leadership position and your thought
process here was "well, things will go better the second time" after
doing those actions, then you absolutely do not deserve to be in a
Leadership position, and you absolutely should not have stewardship
over me or my contributions. Especially if this is not your first time
on a mailing list and this is not your first time being a leader.

All my best,
JeanHeyd

Re: Remove RMS from the GCC Steering Committee

[Alexandre Oliva]

On Mar 30, 2021, JeanHeyd Meneide <phdofthehouse@gmail.com> wrote:

>       Taking the correction into account

*nod*

> What you've presented here is your word ("This
> accusation is outright false, beyond any possible doubt."),

True, I didn't claim to be offering evidence, and that didn't seem
necessary since all the supporting evidence you'd brought was hearsay.
I can't link to the message that is presumably removed, and I suppose I
could get permission to share the email in which he issued the request,
but please be honest: would you believe it?

> they were NOT allowed to attack people like this and go this far and
> being banned by moderation, RMS taking explicit actions to UNDO that
> moderation and explicitly, in the internal mailing list, state
> (paraphrased): 'I have put a new moderator in. Have at it.'

This description suggests we're not even talking about the same events.
My description was about a doxxing web site/email posted no more than a
week ago.

Your description appears to resemble events of 2019: the illegitimate
censorious moderation that was imposed on a GNU mailing list, against
GNU and mailing list policies, after someone abused their autonomy to
grant moderation privileges to a group that started suppressing views
they disagreed with, while allowing personal attacks they supported to
go through.  List rules were restored and censorship ceased with the
legitimate installation of a larger group of moderators with more
diverse stances, that applied list rules and blocked inappropriate posts
while allowing through civil criticism on all sides.  Richard was
criticized for insisting on enabling the debate to carry on, but he
insisted on the principled stance of free speech, and then some, to
allow for what some perceived as personal attacks against him.


Now, you appear to believe a very different interpretation of these
facts.  I can't imagine that showing public posts will prove anything,
since the difference is in the interpretation and attribution of
motivations and allegiances, rather than on facts.  As law and history
have taught us, proving innocence or honesty are often impossible tasks;
it is the burden of the accuser to offer enough evidence to sustain an
accusation, and all you've brought is hearsay.  Popular, widespread
hateful hearsay, but still hearsay.


> where someone who was already banned

No such thing happened.  That's yet another distortion.

There was an attempt to attach shocking labels to an honest man.

The labels failed to stick, though some people still believe them.

Part of the problem is the reasoning that, if so many people are
parroting the same false allegations, there must be truth to them.

When any one of them is proven wrong, with the great effort required to
overcome preconceptions, the goal post is moved onto all of the others
that appear to remain, because the preconceptions still mistake them for
granted, and the accused remains guilty for having taken multiple shots.
That's not the way civilizations have long carried out justice.

-- 
Alexandre Oliva, happy hacker  https://FSFLA.org/blogs/lxo/
   Free Software Activist         GNU Toolchain Engineer
        Vim, Vi, Voltei pro Emacs -- GNUlius Caesar

Re: Remove RMS from the GCC Steering Committee

[Alfred M. Szmidt]

I ("new moderator") won't recount what happened, it is neither here,
or there, but Mark is presenting a very biased view of what occured,
and also one of the reasons why he no longer is a moderator.  

The claims about doxxing, etc, are entierly untrue and unfounded. 

Re: Remove RMS from the GCC Steering Committee

[JeanHeyd Meneide]

Dear Alfred and Alexandre,

     It seems that neither of you would like to offer any evidence
that counteracts what I have already been given by multiple
individuals. Furthermore,

Alexandre:
> A misguided person thought that reciprocating the doxxing against RMS
> was a good way to defend him.  It's not

Alfred:
> The claims about doxxing, etc, are entierly untrue and unfounded.

Either this happened, or it didn't. Alexandre says that some doxxing,
possibly in retaliation to original doxxing, occurred. Alfred says
everything is unfounded and untrue, point blank, no details. I do not
know which of you to believe, which mix is true, and at this point I
don't think I want to know because it's incredibly clear nobody wants
to be publicly clear about it, even after my offer to have the details
sent to me so I can have an informed opinion and not a piecemeal
understanding.

     Okay, fine.

     I support Nathan's inquiry.

Best of luck,
JeanHeyd

On Wed, Mar 31, 2021 at 3:14 AM Alfred M. Szmidt <ams@gnu.org> wrote:
>
> I ("new moderator") won't recount what happened, it is neither here,
> or there, but Mark is presenting a very biased view of what occured,
> and also one of the reasons why he no longer is a moderator.
>
> The claims about doxxing, etc, are entierly untrue and unfounded.

Remove RMS from the GCC Steering Committee

[Maksim Fomin]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, 26 March 2021 г., 23:02, Nathan Sidwell <nathan@acm.org> wrote:

> I would rather not have to write this email. Like many developers, I just want
> to write code. Right now we’re working towards the GCC 11 release. I thought
> about deferring this email. But there’s never a good time, and bad behaviour
> needs to be addressed in the moment. I have left this for too long already.
>
> I used to think of GCC development as egalitarian, and therefore fair, and, by
> assumption, welcoming. That is not true. I’m a white dude with a British accent.
> /Of course/ I have white male privilege. I used to joke that I fell into every
> job I’ve had (including my doctorate) – that, right there, is white male
> privilege.
>
> Perhaps you discount the benefits of white male privilege. You’re wrong.
>
> You cannot have missed the sparsity of women and people of color in compiler
> engineering (kaporcenter black tech workforce). Maybe you fallaciously put that
> down to imbalances in education (leakytechpipeline) How can we, the GCC
> community, be expected to address that? Representation matters, we’re the problem.

[Left most relevant parts of the letter]

The logic of this letter (and sjw in general) is obviously false.

1. There are no examples where Stallman (or people with similar views) censored project contribution from non-white non-male people.
In recent decades there is inflow of people from different counties and 2020 is definitely more diverse in programming than 2000 or 1980.
This observation (absense of discrimiation) is the first important note which blows the login behind the letter.

2. Because the p1 is hard to refute, the discussion moves from objective things (for example, rejecting some pull request from people of color) toward subjective
things like 'remove Stallman because I am not comfortable with his views/claims'. However, once this arguement is naked from the rest of discussion it becomes obviously weak.
Why the project should remove Stallman because 'some' people are not comfortable? Why sjw consider themselves in the position to judge? What to do with the group of people who supports him?
Finally, 'white priviledge' is only one (although  big) subject of dedates. What happens if other areas of social, political or economical debates are brought to the project? There are plenty of issues which divide people and there is no way to make the project to move of on if for each issue one group of people will demand removing members of comittee because of their views.

3. Most of claims about Stallman are not true (to be more precise - they are deliberately misrepresent what Stallman said to make his views to look immoral).

4. Regarding morality. This letter (like many other sjw creatures) says many words about morality, diversity, but at the end of the day it boils down to removing Stallman from position. As a citizen of post-soviet country I can vividly see that this letter is enterely about politics and looks very similar to communist agenda which likes to hide authoritarian policies behind morality. It is very surprising for people from former Soviet block countries to see western world falling into 'very familiar' but notorious propaganda.

Best regards,
Maxim Fomin

Re: Remove RMS from the GCC Steering Committee

[Richard Kenner]

> 3. Most of claims about Stallman are not true (to be more precise -
> they are deliberately misrepresent what Stallman said to make his
> views to look immoral).

I would like to suggest that this discussion will go better without
making accusations that people are "deliberately" doing something.  In
my opinion, there are many different ways both of interpreting what
somebody writes and in making value judgements on the appropriateness
of saying something in a certain way.

Just because you and somebody else interpret a statement in different
ways or have different moral views of the propriety of saying
something in a certain way doesn't mean that either of you are
"deliberately misrepresting" anything.

Re: Remove RMS from the GCC Steering Committee

[Franz Fehringer]

To me (not being a contributor) this is the best contribution to the 
discussion so far.


Am 30.03.2021 um 17:24 schrieb Maksim Fomin via Gcc:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, 26 March 2021 г., 23:02, Nathan Sidwell <nathan@acm.org> wrote:
>
>> I would rather not have to write this email. Like many developers, I just want
>> to write code. Right now we’re working towards the GCC 11 release. I thought
>> about deferring this email. But there’s never a good time, and bad behaviour
>> needs to be addressed in the moment. I have left this for too long already.
>>
>> I used to think of GCC development as egalitarian, and therefore fair, and, by
>> assumption, welcoming. That is not true. I’m a white dude with a British accent.
>> /Of course/ I have white male privilege. I used to joke that I fell into every
>> job I’ve had (including my doctorate) – that, right there, is white male
>> privilege.
>>
>> Perhaps you discount the benefits of white male privilege. You’re wrong.
>>
>> You cannot have missed the sparsity of women and people of color in compiler
>> engineering (kaporcenter black tech workforce). Maybe you fallaciously put that
>> down to imbalances in education (leakytechpipeline) How can we, the GCC
>> community, be expected to address that? Representation matters, we’re the problem.
> [Left most relevant parts of the letter]
>
> The logic of this letter (and sjw in general) is obviously false.
>
> 1. There are no examples where Stallman (or people with similar views) censored project contribution from non-white non-male people.
> In recent decades there is inflow of people from different counties and 2020 is definitely more diverse in programming than 2000 or 1980.
> This observation (absense of discrimiation) is the first important note which blows the login behind the letter.
>
> 2. Because the p1 is hard to refute, the discussion moves from objective things (for example, rejecting some pull request from people of color) toward subjective
> things like 'remove Stallman because I am not comfortable with his views/claims'. However, once this arguement is naked from the rest of discussion it becomes obviously weak.
> Why the project should remove Stallman because 'some' people are not comfortable? Why sjw consider themselves in the position to judge? What to do with the group of people who supports him?
> Finally, 'white priviledge' is only one (although  big) subject of dedates. What happens if other areas of social, political or economical debates are brought to the project? There are plenty of issues which divide people and there is no way to make the project to move of on if for each issue one group of people will demand removing members of comittee because of their views.
>
> 3. Most of claims about Stallman are not true (to be more precise - they are deliberately misrepresent what Stallman said to make his views to look immoral).
>
> 4. Regarding morality. This letter (like many other sjw creatures) says many words about morality, diversity, but at the end of the day it boils down to removing Stallman from position. As a citizen of post-soviet country I can vividly see that this letter is enterely about politics and looks very similar to communist agenda which likes to hide authoritarian policies behind morality. It is very surprising for people from former Soviet block countries to see western world falling into 'very familiar' but notorious propaganda.
>
> Best regards,
> Maxim Fomin
>
>

Re: Remove RMS from the GCC Steering Committee

[mfriley]

For the record, I am not a GNU contributor--I am only chiming in as a

FOSS sympathizer. I will not pretend to be unbiased, or to have any sort

of personal experience with, or extensive knowledge of, RMS's behavior

apropos of GCC, or any other GNU project.

> (For the last point, I don't think the free software movement needs a
> single leader; it needs many people advocating free software, and
> discussing issues related to free software, from diverse perspectives.
> RMS's ideas that form the foundation of the free software movement are
> still of fundamental importance today.  But other people can now build
> better on those ideas in today's context.)

Perhaps it does not need a *formal* leader, but I am strongly inclined

to believe that guidance in some form or another does matter, and I think

a lot of RMS's supporters (vocal or otherwise) feel similarly. Some have

claimed that RMS has only repelled people from free software, and yet,

in spite of the threat of cancellation, many more people have signed the

letter in support of RMS than the one demanding his removal.

"Leaderless" movements are always feckless because they lack direction.

They start with good intentions, but when anyone can find a soapbox and

claim to speak for everyone else, those good intentions are inevitably

thrown under the bus by people seeking personal clout and pursuing their

own agendas.

Say what you will about RMS, but his unwavering laser focus on free

software advocacy shows a level of integrity that is hard not to respect.

This matters more than ever, because as difficult as it is to address

without sounding like a bitter right-wing hack, cancel culture is real,

and it will come for absolutely *anyone*, regardless of your personal

views. I doubt the majority of people signing the Github open letter

have judged the case against him for themselves, or even care one way

or another: people cancel because they can. Social media causes brain

damage, and this is how that brain damage tends to manifest.

There are people developing scripts and browser extensions to

automatically label or block anyone who signed the open letter in

defense of RMS. Just a few examples:

https://github.com/travisbrown/octocrabby
https://github.com/aaronbassett/rm
s-letter-sigs
https://github.com/sticks-stuff/highlight-RMS-supporters

There are also reports of people whose emails are visible on Github

receiving anonymous demands to remove their signatures from the

support letter, on threat of being reported to their employers.

People like this cannot be reasoned with, nor do they want to listen.

If given the chance, they will style themselves as representative of

FOSS, despite clear evidence that this is not the case. They thrive

on interpersonal conflict, so their input is virtually useless in

addressing any genuine issues plaguing GNU or the FOSS community as

a whole.

This is not directed at any reasoned criticism of RMS. I doubt that

everyone who wants him removed is so bluntly insane. If GNU and the

FSF see it fit, that is entirely their prerogative. But it will do

absolutely nothing to satisfy these people, because they are acting

in bad faith. As others have suggested, I fear that it will only make

things worse.

Re: Remove RMS from the GCC Steering Committee

[Jonathan Wakely]

On Tue, 30 Mar 2021, 08:48 mfriley via Gcc, <gcc@gcc.gnu.org> wrote:

> For the record, I am not a GNU contributor--I am only chiming in as a
>
> FOSS sympathizer. I will not pretend to be unbiased, or to have any sort
>
> of personal experience with, or extensive knowledge of, RMS's behavior
>
> apropos of GCC, or any other GNU project.
>
> > (For the last point, I don't think the free software movement needs a
> > single leader; it needs many people advocating free software, and
> > discussing issues related to free software, from diverse perspectives.
> > RMS's ideas that form the foundation of the free software movement are
> > still of fundamental importance today.  But other people can now build
> > better on those ideas in today's context.)
>
> Perhaps it does not need a *formal* leader, but I am strongly inclined
>
> to believe that guidance in some form or another does matter, and I think
>
> a lot of RMS's supporters (vocal or otherwise) feel similarly. Some have
>
> claimed that RMS has only repelled people from free software, and yet,
>
> in spite of the threat of cancellation, many more people have signed the
>
> letter in support of RMS than the one demanding his removal.
>

We're talking here about whether he should be on the GCC steering
committee, not the FSF board. The GCC community should decide, not
signatories to petitions.



> "Leaderless" movements are always feckless because they lack direction.
>

We're not talking about a movement, were talking about the GCC project. We
have leaders, and a steering committee. RMS does not contribute usefully to
that steering committee.



> They start with good intentions, but when anyone can find a soapbox and
>
> [...]
>

This is not directed at any reasoned criticism of RMS. I doubt that
>
> everyone who wants him removed is so bluntly insane. If GNU and the
>
> FSF see it fit, that is entirely their prerogative. But it will do
>
> absolutely nothing to satisfy these people, because they are acting
>
> in bad faith. As others have suggested, I fear that it will only make
>
> things worse.


Totally irrelevant to his position on the GCC steering committee. If you
want to discuss the broader issues, please do so elsewhere.

Remove RMS from the GCC Steering Committee

[Ville Voutilainen]

Giacomo wrote:
>Stallman cannot betray Free Software AND get away with it.
>So to me (and to many others) Stallman is a sort of a living warranty.

That's fine. He  doesn't need to be in the GCC SC to do that.
He can continue to provide guidance on the spirit of Free Software
without having an SC position, or any official leadership position.
The people in the GCC SC are very reasonable people; I have worked
with some of them, and they will listen to reasonable arguments.
RMS doesn't have veto powers anyway, and doesn't need them.

The proposed removal from the SC doesn't prevent RMS from
giving the aforementioned guidance in any way, nor does it even
make it any more difficult. In fact, that removal shouldn't have
any effect on his ability to give such guidance, nor does it actually
have any effect on what the consequences of his guidance will be.

The warranty you speak of does not boil down to a particular individual
being there in the SC. That's by RMS's own design; the copyright and the license
give you that warranty, not the SC presence of any single person.
And a removal from an SC doesn't equal the removal from the set
of people who can meaningfully contribute. That is certainly, I would
think, not the intent of anyone who has spoken in favor of the removal.

There is certainly a fair amount of heat in this discussion. Whether
the proposed removal has the effects it seeks, I don't know. But
I don't buy the surreptitious suggestions that the proposed removal
somehow spells doom for the continued availability of GCC as Free Software,
or for the spirit of Free Software in general. In my anecdotal case,
it doesn't. I have fairly good reasons to think that it doesn't spell such
doom for quite many other contributors to these projects, some far
more frequently active than me.

I am, Yours Most Sincerely,
Ville Voutilainen
an occasional libstdc++ contributor
a less-frequently occasional g++ contributor