From: Craig Milo Rogers <rogers@isi.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Oliver Neukum <oliver@neukum.org>,
Kenneth Lavrsen <kenneth@lavrsen.dk>,
Jesper Juhl <juhl-lkml@dif.dk>, Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] Re: Summarizing the PWC driver questions/answers
Date: Mon, 30 Aug 2004 02:14:13 -0700 [thread overview]
Message-ID: <20040830091413.GA32665@isi.edu> (raw)
In-Reply-To: <1093786799.27934.28.camel@localhost.localdomain>
On 04.08.29, Alan Cox wrote:
> A license was granted, for ever.
This has been discussed before (on this list, I think), and
the answer may surprise you, or maybe not: nothing lasts forever.
I am not a laywer. I haven't looked at the U.K. copyright
laws. I *have* read throught the relevant U.S. laws (a few years
back), and a copyright assignment or license (which I believe is a
broad enough category to include the GPL) *can* be terminated in the
U.S. in certain cases -- that's quite clear. The "recapture" period
(for works created after 1978) is a five-year period that starts 35
years after the license was issued. In that window, the author of
copyrighted code, or the author's heirs or estate, have the option to
revoke the original copyright assignment or license, i.e., in our
case, presumably, revoke the GPL.
There are various details and procedures involved. They must
be followed precisely, or the opportunity to recapture the copyright
may be lost. One important detail is that work-for-hire copyright
assignments may not be recaptured.
So, If you keep track of everyone to whom you, the author,
*directly* distribute a copy of your GPL'd work (and thus assign an
"original" GPL'd license), you might be able to effect a recapture by
notifying everyone on that list. Then again, you might have to notify
everyone who ever received a copy of the GPL'd code, directly from you
or not. The GPL raises certain issues that simply weren't forseen by
the framers of the statutes in question! :-)
Again, I don't have the U.S. Federal Code references at hand.
However, here is an article that explains this issue for composers of
music:
http://www.ascap.com/estates/estatescopyrights.html
Finally, three preemptive comments:
1) This aspect of copyright law is something that all professional
authors should know about. You shouldn't have to relay upon
a lawyer to know your basic legal rights.
2) Linus Torvalds has recently reinforced the notion that the Linux
developers comminuty should behave as honorable gentlebeings, rather
than behave as lawyers. This posting is not meant to gainsay that
statement in any way. Think of knowledge of copyright law as akin to
knowing the terrain of a potential battlefield -- even though the
successful strategist seeks victory without the need for battle
(Sun Tzu, more or less).
3) The U.S. Congress or courts could make further changes to the laws that
affect copyright recapture. Again, nothing is forever.
Craig Milo Rogers
next prev parent reply other threads:[~2004-08-30 9:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 19:54 Summarizing the PWC driver questions/answers Kenneth Lavrsen
2004-08-27 20:14 ` [linux-usb-devel] " David Brownell
2004-08-27 20:22 ` David S. Miller
2004-08-27 20:30 ` David Ford
2004-08-27 21:26 ` Wouter Van Hemel
2004-08-27 22:07 ` [OT] " David Ford
2004-08-27 20:32 ` Zwane Mwaikambo
2004-08-27 21:25 ` Jesper Juhl
[not found] ` <Pine.LNX.4.61.0408272259450.2771@dragon.hygekrogen.localho st>
2004-08-27 22:08 ` Kenneth Lavrsen
2004-08-27 23:01 ` Bernd Petrovitsch
2004-08-27 23:13 ` [linux-usb-devel] " Oliver Neukum
2004-08-29 13:40 ` Alan Cox
2004-08-30 9:14 ` Craig Milo Rogers [this message]
2004-08-31 5:04 ` asterix the gual
2004-08-28 0:22 ` Paul Jakma
2004-08-28 15:55 ` [linux-usb-devel] " michel Xhaard
2004-08-30 12:04 ` Geert Uytterhoeven
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040830091413.GA32665@isi.edu \
--to=rogers@isi.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=juhl-lkml@dif.dk \
--cc=kenneth@lavrsen.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox