[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Overview of copyright issues
From: |
Reinhold Kainhofer |
Subject: |
Re: Overview of copyright issues |
Date: |
Wed, 9 Sep 2009 22:26:53 +0200 |
User-agent: |
KMail/1.11.4 (Linux/2.6.29-02062906-generic; KDE/4.2.4; i686; ; ) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Mittwoch, 9. September 2009 20:53:21 schrieb Hans Aberg:
> On 9 Sep 2009, at 20:30, Joseph Wakeling wrote:
> > The whole point of this formulation is to give users of the program
> > the
> > option to choose which version of the license they want to be bound by
> > if they redistribute or modify the code, and in particular to make it
> > easy for a project to upgrade the license OR NOT.
>
> You might check with the GNUers if it is the intention.
One intention is also to not retroactively change the license terms and make
somthing legal suddenly illegal. That's called "legal certainty".
> It means that
> sources can be tivoized, even in the face of the new v3.
Sources that could be tivoized (i.e. they were released under GPL 2 and can
thus always be used under the GPL v2) can still be tivoized - that's the
intention of the GPL not to take away rights retroactively.
If you are working with a version, where the license allows tivoization (i.e.
GPL 2), then you should be assured that you can keep doing this (with this
exact version, of course, not necessarily with future versions) in the future.
Your wording would e.g. turn users of the GPL 3 suddenly into license
violators, should the FSF release a new version. (This is a severe legal
problem, since suddenly someone would be in violation, even though neither he
nor the licensor did anything - That might even be struck as invalid by a
court!) If you can legally use some source code today, you need to be sure
that doing the exact same thing will still be legal tomorrow. Everything else
would be Suicide for Open Source!
I'm sure the FSF people thought through the "or later" wording and put that in
for a reason... After all, that's one very fundamental part to prevent future
legal problems.
Cheers,
Reinhold
- --
- ------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFKqA+OTqjEwhXvPN0RApY1AKCULQwo/TaEG3VuVZX6g2/rrBUklQCgqSb7
zxibnf4RIfKBRlKpxsDurkc=
=758Q
-----END PGP SIGNATURE-----
- Overview of copyright issues, Joseph Wakeling, 2009/09/09
- Re: Overview of copyright issues, Hans Aberg, 2009/09/09
- Re: Overview of copyright issues, Joseph Wakeling, 2009/09/09
- Re: Overview of copyright issues, Hans Aberg, 2009/09/09
- Re: Overview of copyright issues,
Reinhold Kainhofer <=
- Re: Overview of copyright issues, Joseph Wakeling, 2009/09/09
- Re: Overview of copyright issues, Hans Aberg, 2009/09/09
- Re: Overview of copyright issues, Joseph Wakeling, 2009/09/09
- Re: Overview of copyright issues, Hans Aberg, 2009/09/09
- Re: Overview of copyright issues, Joseph Wakeling, 2009/09/09
- Re: Overview of copyright issues, Reinhold Kainhofer, 2009/09/09
- Re: Overview of copyright issues, Joseph Wakeling, 2009/09/09
- Re: Overview of copyright issues, Peter Chubb, 2009/09/09
- Re: Overview of copyright issues, Anthony W. Youngman, 2009/09/10
- Re: Overview of copyright issues, Anthony W. Youngman, 2009/09/10