You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
208 lines
11 KiB
208 lines
11 KiB
11 months ago
|
<!DOCTYPE html>
|
||
|
<html lang="en">
|
||
|
<head>
|
||
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||
|
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||
|
|
||
|
<!-- Enable responsiveness on mobile devices-->
|
||
|
<!-- viewport-fit=cover is to support iPhone X rounded corners and notch in landscape-->
|
||
|
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1, viewport-fit=cover">
|
||
|
|
||
|
<title>Julio Biason .Me 4.3</title>
|
||
|
|
||
|
<!-- CSS -->
|
||
|
<link rel="stylesheet" href="https://blog.juliobiason.me/print.css" media="print">
|
||
|
<link rel="stylesheet" href="https://blog.juliobiason.me/poole.css">
|
||
|
<link rel="stylesheet" href="https://blog.juliobiason.me/hyde.css">
|
||
|
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=PT+Sans:400,400italic,700|Abril+Fatface">
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
</head>
|
||
|
|
||
|
<body class=" ">
|
||
|
|
||
|
<div class="sidebar">
|
||
|
<div class="container sidebar-sticky">
|
||
|
<div class="sidebar-about">
|
||
|
|
||
|
<a href="https://blog.juliobiason.me"><h1>Julio Biason .Me 4.3</h1></a>
|
||
|
|
||
|
<p class="lead">Old school dev living in a 2.0 dev world</p>
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
<ul class="sidebar-nav">
|
||
|
|
||
|
|
||
|
<li class="sidebar-nav-item"><a href="/">English</a></li>
|
||
|
|
||
|
<li class="sidebar-nav-item"><a href="/pt">Português</a></li>
|
||
|
|
||
|
<li class="sidebar-nav-item"><a href="/tags">Tags (EN)</a></li>
|
||
|
|
||
|
<li class="sidebar-nav-item"><a href="/pt/tags">Tags (PT)</a></li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
</div>
|
||
|
</div>
|
||
|
|
||
|
|
||
|
<div class="content container">
|
||
|
|
||
|
<div class="post">
|
||
|
<h1 class="post-title">FSF and rms (Again)</h1>
|
||
|
<span class="post-date">
|
||
|
2021-03-29
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/gpl/">#gpl</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/fsf/">#fsf</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/free-software-foundation/">#free software foundation</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/stallman/">#stallman</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/rms/">#rms</a>
|
||
|
|
||
|
</span>
|
||
|
<p>About six months ago, in 2020-09-16<sup class="footnote-reference"><a href="#1">1</a></sup>, Richard Stallman, a.k.a. "rms", <a href="https://www.osnews.com/story/130635/richard-stallman-resigns-from-fsf-mit-after-defending-child-rape/">resigned from
|
||
|
FSF</a>
|
||
|
(the Free Software Foundation, maintainer of the GPL family of licenses) with
|
||
|
not-so-great headlines. A week ago, in 2021-03-22, rms told the world <a href="https://www.zdnet.com/article/richard-m-stallman-returns-to-the-free-software-foundation-board-of-directors/">that he
|
||
|
is back</a>.</p>
|
||
|
<p>And now we have a huge mess. Again.</p>
|
||
|
<span id="continue-reading"></span><h2 id="first-of-all">First of all...</h2>
|
||
|
<p>Let me say this first and foremost: No one is denying the works of rms. No one
|
||
|
is denying that taking a huge undertaking of writing a whole compiler to
|
||
|
produce an open source operating system isn't without merit. All those are
|
||
|
recognizable and show a lot of effort for the greater good.</p>
|
||
|
<h2 id="but-then">But then...</h2>
|
||
|
<p>There are allegations coming from all sides that rms seems to harass people
|
||
|
(mostly women), some people feeling uncomfortable with his words and acting;
|
||
|
and we also have people saying that it is not all that, that there is a
|
||
|
"lynching" going around (I'm not kidding) and general support for him.</p>
|
||
|
<p>"Is he a bad or good person?" is not a question I intent answer here. This is
|
||
|
not the part that annoys me in this whole discussion.</p>
|
||
|
<p>Due his strong opinions and general complains about his presence,
|
||
|
he decided to resign from the FSF, the body responsible for the GPL license and
|
||
|
everything related to it, from keeping it active to helping developers with
|
||
|
legal situations with the license.</p>
|
||
|
<p>(Personally, while the linked article points that his resignation was in part
|
||
|
for the news about people using the "services" of Jeffrey Epstein of young
|
||
|
girls for sex, I've read that rms support for Marvin Minsky, cited in Epstein
|
||
|
list of clients, was not "yeah, sex with kids is alright!" but actually "I
|
||
|
think Minsky was convinced that the girls weren't underage and forced into
|
||
|
sex, so he was unknowingly part of it" -- again, that's my understanding.
|
||
|
And only on that point, just to be clear.)</p>
|
||
|
<p>But, in the end, that's what's pointed as his resignation.</p>
|
||
|
<h2 id="and-then">And then...</h2>
|
||
|
<p>In 2021-03-22, rms appeared in an online event,
|
||
|
<a href="https://libreplanet.org/2021/">LibrePlanet</a> to announce that he's back into
|
||
|
the board of the FSF. There wasn't an official statement about it, it was like
|
||
|
a huge surprise for everyone.</p>
|
||
|
<p>In the follow days, RedHat, FSFE (Free Software Foundation Europe) and a lot
|
||
|
other companies and groups removed their support for the FSF.</p>
|
||
|
<h2 id="but">But...</h2>
|
||
|
<p>The first problem I see with it all is that the FSF, while promoting the
|
||
|
openness of software, by securing a license that allows anyone to have access
|
||
|
to the code, a license that promotes the evolution of code in the open, suddenly took
|
||
|
a closed decision behind closed doors without consulting anyone outside the
|
||
|
board.</p>
|
||
|
<p>It seems weird promoting openness when they are closed in their own decisions.</p>
|
||
|
<h2 id="also">Also...</h2>
|
||
|
<p>The second problem is the content of the announcement.</p>
|
||
|
<p>Again, without ever getting into "he said that" "he didn't said that" matter,
|
||
|
one must recognize what they said that could cause people to revolt.
|
||
|
There wasn't any words about "Look, thinks I said were taken out of
|
||
|
context" or even a "I've chosen words poorly and that hurt people, and I
|
||
|
promise I'll take care of that in the future"<sup class="footnote-reference"><a href="#2">2</a></sup>.</p>
|
||
|
<p>I believe that if there was any mention of that, the current revolt wouldn't be
|
||
|
so strong. Not saying "There wouldn't be any", but less aggressive. Heck, if
|
||
|
there was the acknowledgment that he learnt why there was a revolt in the first
|
||
|
place, this time it would be a lot less painful.</p>
|
||
|
<h2 id="and-finally">And finally...</h2>
|
||
|
<p>The third problem is the current state of free software. No, I don't mean "WE
|
||
|
ARE BEING SWALLOWED BY CORPORATE GREED", although that's partially true, but we
|
||
|
are seeing the use of "kind-of-open-source-but-not-quite" license, a.k.a.
|
||
|
"source available" license, like the
|
||
|
<a href="https://en.wikipedia.org/wiki/Server_Side_Public_License">SSPL</a> being recently
|
||
|
adopted by the Elastic Corporation.</p>
|
||
|
<p>While resources from FSF could be used to dispel any
|
||
|
<a href="https://en.wikipedia.org/wiki/Fear,_uncertainty,_and_doubt">FUD</a> or
|
||
|
misconceptions about GPL licenses, we now focus on "Should he be in the
|
||
|
board?". The board even had to engineer a staff member to <a href="https://www.fsf.org/news/update-on-work-to-improve-governance-at-the-fsf">act as
|
||
|
director</a>
|
||
|
and other measures of openness, when there should be a focus on making sure
|
||
|
"source available" licenses don't spread too much.</p>
|
||
|
<h2 id="in-conclusion">In conclusion...</h2>
|
||
|
<p>I just have one question floating my head right now: Does anyone need to be on
|
||
|
the board to actually help the FSF? Imagine if instead of "I'm back to the
|
||
|
board of FSF", rms announcement actually was "I'm back helping the FSF promote
|
||
|
free software". Sure, some people would complain, but you can see that even
|
||
|
them would think "Yeah, but he's not <em>part</em> of the FSF." And life would move
|
||
|
on, and the FSF could focus on the GPL and other licenses, and helping
|
||
|
companies not get trapped into "source-available license is our only solution"
|
||
|
and so on.</p>
|
||
|
<p>So <em>why</em> in the board? Isn't there any other position where rms can't help the
|
||
|
FSF? I pretty much doubt that, but someone (or someones) decided that wasn't
|
||
|
enough; board or burst.</p>
|
||
|
<p>"Since he's there, just leave him there" as a way to quell the discussion is no
|
||
|
way to deal with this. Unless we see open discussion on why -- and, for morbid
|
||
|
curiosity, who -- rms is back on the board, the whole point of the FSF as
|
||
|
promoters of openness feels shaken to me, personally.</p>
|
||
|
<h2 id="post-script">Post-script</h2>
|
||
|
<p>One of the easiest way to make a project crumble is to have heroes. "If this
|
||
|
person takes a vacation, the system will crash", "The whole success of this
|
||
|
project is due that person" are very <em>bad</em> signs in a project.</p>
|
||
|
<p>For example, when Guido von Rossum decided to resign from his BDFL position,
|
||
|
the whole Python community scrabbled to figure out a way to move along --
|
||
|
mostly 'cause the community put a lot of pressure on him because it thought the
|
||
|
only way to move forward was with Guido at the helm. The Rust community, on the
|
||
|
other hand, focus a lot of taking this image of "This is the project of this
|
||
|
person" by giving small parts to a lot of people: I know there is a person
|
||
|
leading the "better error messages" part, I know there is a person leading the
|
||
|
"async" part (although I'm seeing a movement on the lead of that part), I know there
|
||
|
is person leading the "Rust in Embedded environments" part and so on. If any
|
||
|
one of those resigns, I don't feel like the Rust ecosystem is in danger; it is
|
||
|
only part of it, and a substitute can be found 'cause that person was not "the
|
||
|
hero" of that part.</p>
|
||
|
<p>That need for heroes seems to be part of the problem with FSF: With rms out,
|
||
|
there was no hero in tow to promote the project. Because nobody actually tried
|
||
|
to move out of rms shadow before his resignation, the leadership ended with a
|
||
|
vacuum that nobody filled -- or felt the need to fill. That was the moment to
|
||
|
push small projects, assign several names (maybe a handful of names) into those
|
||
|
projects and show that the FSF found a better way to move. But because they
|
||
|
never tried to innovate, they seems to have get stuck into "finding another
|
||
|
hero" and decided to call the old one back.</p>
|
||
|
<p>Free Software shouldn't be synonymous of rms.</p>
|
||
|
<hr />
|
||
|
<div class="footnote-definition" id="1"><sup class="footnote-definition-label">1</sup>
|
||
|
<p>Well, screw this, I don't want to use the Imperial format for dates and I
|
||
|
don't want to confuse people that use the Imperial format, so let's go with
|
||
|
the ISO format and confuse the world.</p>
|
||
|
</div>
|
||
|
<div class="footnote-definition" id="2"><sup class="footnote-definition-label">2</sup>
|
||
|
<p>That isn't that freaking hard, people! I've been called out for using
|
||
|
"guys", which I responded that I understood what they meant, would take more
|
||
|
care in the future, and thanked for their reply. From that point, instead of
|
||
|
"guys", I use "people" and neutral pronouns. And it doesn't freaking
|
||
|
hurt <strong>at all</strong> (although it is really hard when my native language --
|
||
|
Portuguese -- have only gendered pronouns, but I try).</p>
|
||
|
</div>
|
||
|
|
||
|
</div>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
</body>
|
||
|
|
||
|
</html>
|