From: "Andreas Röhler" <email@example.com>
Cc: Richard Stallman <firstname.lastname@example.org>, Bastien <email@example.com>
Subject: Re: Re: What license for Worg?
Date: Fri, 06 Aug 2010 11:25:07 +0200 [thread overview]
Message-ID: <4C5BD4F3.firstname.lastname@example.org> (raw)
Am 04.08.2010 07:36, schrieb Bastien:
> Or we might also consider CC0:
> It looks way more simple to me.
> It also circumvents the problem of people having to sign the FSF papers
> if the Org/Emacs manuals include part of the code they contributed to
> Worg as examples.
> What people think?
that's an interesting proposal, I'm glad seeing you
reflecting the matter.
Please permet first clarifying a little bit: we can't
speek of FSF papers as such, it's very different one.
The FSF disclaimer is perfectly ok IMO and should be
sufficient for any distributor.
The other paper, obliging the author to indemnities
towards the FSF even in cases of false accusations,
stipulating US-courts and US-law as the only
relevant, is a human rights violation.
Bien sure, that hat not been the intention of RMS and
the other developers. Nonetheless, in fact it's not
different from the famous Sarbanes-Oxley Act, which
first time in newer history stipulated US-law for all
the others too.
Copyright assignment is an essay not to defend, but to
attack. It trys software as a weapon. This deplorable
idea we see inside the GPL too BTW, marking a cultural
gab between post-communist Europe and US.
In consideration which was said above, your proposal
probably will not be accepted by FSF, as a non-existing
copyright can't be assigned any more. :-)
CC to RMS.
next prev parent reply other threads:[~2010-08-06 9:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 12:33 What license for Worg? Bastien
2010-08-02 16:59 ` David Maus
2010-08-02 18:50 ` Bernt Hansen
2010-08-03 9:34 ` Ian Barton
2010-08-04 4:26 ` Bastien
2010-08-13 23:32 ` Eric S Fraga
2010-08-03 12:53 ` tycho garen
2010-08-04 4:36 ` Bastien
2010-08-08 21:10 ` tycho garen
2010-08-09 19:36 ` David Maus
2010-08-10 1:35 ` Memnon Anon
2010-08-10 15:41 ` Bastien
2010-08-04 5:36 ` Bastien
2010-08-04 7:14 ` Ian Barton
2010-08-06 8:31 ` Bastien
2010-08-06 9:25 ` Andreas Röhler [this message]
2010-08-04 12:33 ` Sebastian Rose
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).