unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: nipponpost@airmail.cc
To: Marcin Borkowski <mbork@mbork.pl>
Cc: bug-gnu-emacs
	<bug-gnu-emacs-bounces+nipponpost=airmail.cc@gnu.org>,
	rms@gnu.org, 38002@debbugs.gnu.org
Subject: bug#38002: Please remove this joke
Date: Fri, 01 Nov 2019 20:30:53 +0000	[thread overview]
Message-ID: <25b7c44fa4a0886a2c977a51c26dc1e0@airmail.cc> (raw)
In-Reply-To: <874kzna7mb.fsf@mbork.pl>

A joke is not a bug: it has /absolutely/ nothing to do with the 
operation of the software; it isn't even /part/ of the software.

What it is, is a makers' mark.
A signature.
A piece of the author.
"This is me, this is part of my personality"

Removing the joke is tantamount to removing a maker's mark.
It's basically white-washing the person from the project
and laundering his code.

Now the code, the project, is attributed to the "maintainers",
their system of society is all that is present,
the personality of the actual creators is gone.

It's just as bad as removing the author from the Authors attribution;
it's even worse: from the names you cannot tell /who/ these people were;
but from their jokes you can catch a glimpse.

All maintainers do is take other peoples work, and make sure it
works on new incompatable systems. They then parade around as if
they wrote the whole thing (see: Guix "maintainers" who are demanding
the ouster of RMS from HIS GNU for example).

It's basically plagiarism, in practice.

I'm an attorney btw, if the Authors are angry about this, and I gain 
information about such (if they're still alive), I'll consider guiding 
them regarding copyright law (US). I doubt they're in my juristiction 
though so I could only show them the way. In europe they could perhaps 
assert moral rights aswell (this becomes complicated, due to all the 
different interpretations there-of). In the USA it's the 35 year 
statutory provision in the Copyright Act that could be used.

Respect the guys that helped you; Stop spitting on them.
These Maintainers are not equal to the original programmers who helped 
you.
It's like saying a touch-up artist is the same as a from-scratch 
painter.

Free Software does NOT exist without the Software; which does not exist 
without the Men who BOTHER to write said software to begin with.

If you lost all female contributors from Free Software: you would still 
have it.
If you lost all male contributors you would not.
And men and women do NOT get along.
One dominates the other.
In Anglo-American societies the woman dominates the man and the man is 
just a beast of burden: caged at the first notice of his master to the 
male-handlers (police).

Pandering to the women will not get anyone "laid"
(Though Pandering to Islam will get you young brides (young girls, not 
adult women) eventually; which is why the European policticians wisely 
do so: it's either Americanism or Islam... so they choose the nicer one 
for themselves)

(Note: if anyone wants to question my credentials regarding programming: 
I have a 25Mbyte code diff I can show you; it's not all of my code; but 
alot of it is, and that's on my latest project I've been working on for 
a decade (foss 3d videogame). I know what motivates me and demotivates 
me, and I see who contributes what in FOSS and who simply controls 
others socially, so I'm not fooled. There is a method to all of this, 
and degrading the men like Americans do was not the method that 
succeeded, but is now what is proposed and has been followed for the 
last few years (which has resulted in a quiet /exodus/ of hackers and 
the domination of /foundations/ and /corporate backers/ instead (as 
intended)))





  parent reply	other threads:[~2019-11-01 20:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 14:29 bug#38002: Please remove this joke Cecilio Pardo
2019-10-31 15:46 ` Stefan Kangas
2019-10-31 16:22   ` Marcin Borkowski
2019-10-31 20:24     ` Robert Pluim
2019-10-31 16:25   ` Lars Ingebrigtsen
2019-10-31 19:24     ` Glenn Morris
2019-10-31 23:12       ` Juanma Barranquero
2019-11-01  0:40         ` nipponpost
2019-11-01 13:15         ` Filipp Gunbin
2019-11-01 14:29           ` Richard Stallman
2019-11-01 15:24             ` nipponpost
2019-11-01 16:23               ` Marcin Borkowski
2019-11-01 20:13                 ` cpardo
2019-11-01 23:13                   ` nipponpost
2019-11-02  8:46                   ` Marcin Borkowski
     [not found]                     ` <237201ce8334abb8f7dfb4612ed9db08@airmail.cc>
2019-11-03 13:21                       ` Richard Stallman
2019-11-01 20:30                 ` nipponpost [this message]
2019-11-02  8:52                   ` Marcin Borkowski
2019-11-01 16:21             ` Lars Ingebrigtsen
2019-11-01 23:25               ` nipponpost
2019-11-02  2:14                 ` Juanma Barranquero
2019-11-02 15:57                   ` nipponpost
2019-11-01  2:22 ` Richard Stallman
2019-11-01 12:55 ` Lars Ingebrigtsen
     [not found] ` <mailman.425.1572711186.13325.bug-gnu-emacs@gnu.org>
2019-11-02 21:06   ` Alan Mackenzie
2019-11-03 16:45     ` bug#38002: Please remove this joke - Informing of legal rights is not a threat - 35 year copyright recovery for non-works-for-hire nipponpost
2019-11-03 17:01       ` bug#38002: Please remove this joke Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25b7c44fa4a0886a2c977a51c26dc1e0@airmail.cc \
    --to=nipponpost@airmail.cc \
    --cc=38002@debbugs.gnu.org \
    --cc=bug-gnu-emacs-bounces+nipponpost=airmail.cc@gnu.org \
    --cc=mbork@mbork.pl \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).