Richard Stallman Demands Return Of Abortion Joke To libc Documentation (theregister.co.uk)
An anonymous reader quotes The Register:
Late last month, open-source contributor Raymond Nicholson proposed a change to the manual for glibc, the GNU implementation of the C programming language's standard library, to remove "the abortion joke," which accompanied the explanation of libc's abort() function... The joke, which has been around since the 1990s and is referred to as a censorship joke by those supporting its inclusion, reads as follows:
25.7.4 Aborting a Program... Future Change Warning: Proposed Federal censorship regulations may prohibit us from giving you information about the possibility of calling this function. We would be required to say that this is not an acceptable way of terminating a program.
On April 30, the proposed change was made, removing the passage from the documentation. That didn't sit well with a number of people involved in the glibc project, including the joke's author, none other than Free Software Foundation president and firebrand Richard Stallman, who argued that the removal of the joke qualified as censorship... Carlos O'Donnell, a senior software engineer at Red Hat, recommended avoiding jokes altogether, a position supported by many of those weighing in on the issue. Among those voicing opinions, a majority appears to favor removal.
But in a post to the project mailing list, Stallman wrote "Please do not remove it. GNU is not a purely technical project, so the fact that this is not strictly and grimly technical is not a reason to remove this." He added later that "I exercise my authority over glibc very rarely -- and when I have done so, I have talked with the official maintainers. So rarely that some of you thought that you are entirely autonomous. But that is not the case. On this particular question, I made a decision long ago and stated it where all of you could see it."
The Register reports that "On Monday, the joke was restored by project contributor Alexandre Oliva, having taken Stallman's demand as approval to do so."
25.7.4 Aborting a Program... Future Change Warning: Proposed Federal censorship regulations may prohibit us from giving you information about the possibility of calling this function. We would be required to say that this is not an acceptable way of terminating a program.
On April 30, the proposed change was made, removing the passage from the documentation. That didn't sit well with a number of people involved in the glibc project, including the joke's author, none other than Free Software Foundation president and firebrand Richard Stallman, who argued that the removal of the joke qualified as censorship... Carlos O'Donnell, a senior software engineer at Red Hat, recommended avoiding jokes altogether, a position supported by many of those weighing in on the issue. Among those voicing opinions, a majority appears to favor removal.
But in a post to the project mailing list, Stallman wrote "Please do not remove it. GNU is not a purely technical project, so the fact that this is not strictly and grimly technical is not a reason to remove this." He added later that "I exercise my authority over glibc very rarely -- and when I have done so, I have talked with the official maintainers. So rarely that some of you thought that you are entirely autonomous. But that is not the case. On this particular question, I made a decision long ago and stated it where all of you could see it."
The Register reports that "On Monday, the joke was restored by project contributor Alexandre Oliva, having taken Stallman's demand as approval to do so."
I, personally, thought to the joke was funny enough, albeit off-color. Black humor is still humor, and I personally recommend its persistence if only as a defense against the professionally offended. That being said, I can sympathize a bit with folks who are legitimately offended by something like this (primarily because death as a whole is a subject that requires concern/consideration when talking about it in certain contexts), in contrast to those who are essentially allowing themselves to be offended on behalf of some other entity/group. As a final note, if someone has read this comment, and assumed that they are a target of my labeling as a professional offense taker, some soul-searching is recommended, as that was basically my intention.
There is no XUL, only WebExtensions...
After all, OSS documentation itself is one big joke.
It didn't make me laugh, but I have to admit that I find it a clever way to comment on a political issue: not abortion itself, but rather the way anti-abortion proponents try to exert control on abortion clinics by forcing them to talk-down to their patients as if they were ignorant children.
Get over yourself. You guys need to learn to "get over it" and learn that you have no right to NOT be offended. The "professional" thing is no to release software that is riddled with security holes. I'm still waiting for the "professional" software houses to start doing that.
The workplace is for work, not for crude humor or for politics.
Some of us are old enough to remember a time when Free Software wasn't just about work - when it was something that people did because it was fun.
But it's a pretty good reason for deleting it from technical documentation.
You could also write the word "spam" at the bottom of every single function's documentation, and that wouldn't be funny either. It also wouldn't be censorship if someone removed it.
I usually agree with RMS but this is one of those "who the fuck cares?" things.
Then it gets worse:
OMG, we're having a contest to see who can be the most stupid. I'm almost back to joining RMS in "demanding" it be put back again. "Triggered?" really? Holy shit.
Fuck anyone and everyone who pretends they're unable to handle reading a certain word. The "joke" needs to be put back in, just to piss on the drama queens.
"Believe me!" -- Donald Trump
There are other jokes/easter-eggs in Glibc's documentation. I get a kick out of them every time I run across one.
Should we also go through and strip all of those out? What if I decide that EIEIO is insulting to farmers? Who decides what's a trigger-warning and what isn't?
Should we remove HTTP error 418?
The UNIX/Linux hacker subculture of the 80s and 90s produced a ton of interesting technology, and arguably shaped the internet into what it is today.
I don't want my operating system to be a sterile, soulless entity. I like the in-jokes, the fact that 'fortune' exists, and the recursive acronyms. People have poured their vitality into making tools that are free for the world - the least we can do is let them express a sense of humor if they choose.
UNIX cultureLinux/UNIX is born from a really unique, amazing kind of culture, which
---- I'll take you in a Hunt deathmatch any day.