Licensing change: Audacious - GPLv3 --> BSD
Matthew Garrett
mjg59 at srcf.ucam.org
Tue Jul 10 02:56:32 UTC 2012
On Mon, Jul 09, 2012 at 10:27:37PM +0200, Michael Schwendt wrote:
> On Mon, 9 Jul 2012 20:52:23 +0100, Matthew Garrett wrote:
> > Revision control or some sort of out-of-band tracking. It's the
> > project's responsibility, not the copyright holder's.
>
> That's hardly feasible and not accurate enough either (if it comes to line
> numbers, changing the RC software, importing from source tarball for a
> forked project, tracking down when lines get removed or replaced, …).
> For any code modification, the committer would need to check whether he's
> about to remove an external person's contribution and then drop that
> person from the list of copyright holders. [insert Impossible Mission
> title music here]
This isn't the copyright holder's problem. This is very much the
responsibility of anyone who wants to change the license afterwards. If
you're not able to keep track of all your copyright holders then
changing the license is something you should only do with the aid of
good lawyers.
--
Matthew Garrett | mjg59 at srcf.ucam.org
More information about the devel
mailing list