From: Mark H Weaver <mhw@netris.org>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: Daniel Krueger <keenbug@googlemail.com>,
guile-devel <guile-devel@gnu.org>
Subject: Re: Patches for module/ice-9/occam-channel.scm
Date: Tue, 15 May 2012 18:37:05 -0400 [thread overview]
Message-ID: <878vgtdqb2.fsf@netris.org> (raw)
In-Reply-To: <CA+U71=MdyhKS=oaxuR7sSYrJxSo79z6MemeQCfWxAZYwCEEQrQ@mail.gmail.com> (Noah Lavine's message of "Wed, 9 May 2012 08:06:38 -0400")
Noah Lavine <noah.b.lavine@gmail.com> writes:
> Since these are relatively large changes, you'll also need to do a
> copyright assignment. We assign the copyright on Guile to the Free
> Software Foundation because under US law, the owner of a copyrighted
> work is sometimes the only person with the power to sue over
> violations of copyright. The FSF wants to be able to sue if people
> violate the GPL, so we assign copyright.
I'd just like to add that suing is a last resort and extremely rare,
only done when companies use our software and blatantly refuse to give
their users the rights that are guaranteed to _all_ users by the GPL.
The policy of the FSF regarding GPL violations was explained well by
Eben Moglen: <http://www.geof.net/research/2006/moglen-notes>
When I went to work for Richard Stallman in 1993, he said to me at
the first instruction over enforcing the GPL, "I have a rule. You
must never let a request for damages interfere with a settlement for
compliance." I thought about that for a moment and I decided that
that instruction meant that I could begin every telephone
conversation with a violator of the GPL with magic words: We don't
want money. When I spoke those words, life got simpler. The next
thing I said was, We don't want publicity. The third thing I said
was, We want compliance. We won't settle for anything less than
compliance, and that's all we want. Now I will show you how to make
that ice in the wintertime. And so they gave me compliance. Which
had been defined mutually as ice in the wintertime.
Unfortunately, there are many corporations that will violate the GPL
without remorse unless we have the _ability_ to sue them.
> Please see http://www.gnu.org/licenses/why-assign.html for more
> information, or email assign@gnu.org to fill out a form.
I should also mention that I'm _extremely_ allergic to legalese, and can
literally count on one hand the number of agreements I have signed in
the last decade, but the FSF legalese I was asked to sign was
refreshingly fair and reasonable.
Mark
next prev parent reply other threads:[~2012-05-15 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 12:42 Patches for module/ice-9/occam-channel.scm Daniel Krueger
2012-05-04 2:58 ` Noah Lavine
2012-05-04 3:18 ` Nala Ginrut
2012-05-04 13:17 ` Andrew Gwozdziewycz
2012-05-06 9:33 ` Daniel Krueger
2012-05-09 12:06 ` Noah Lavine
2012-05-15 22:37 ` Mark H Weaver [this message]
2012-05-18 20:14 ` Daniel Krueger
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vgtdqb2.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=keenbug@googlemail.com \
--cc=noah.b.lavine@gmail.com \
/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.
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).