The complete list of licences

[kuraga]

Good day!

I see there are two places where licenses are listed:

1. /LICENSE with GPL-2 license,
2. /AUTHORS with references to a lot of others.

The questions:

1. So, where is GPL-2 applied to?
2. Is it a good idea to store the licences in file named /AUTHORS?
3. Let's point license information in the /README.md?

Thanks!

[newhoa]

Thanks for the report!

So I read up a little on this and, if I understand it correctly, it seems both Apache 2.0 and CC-BY-SA-4.0 stuff can be combined with GPL-3 but the resulting release would be GPL-3 licensed.

So effectively the content becomes relicensed.

This theme probably needs to be updated to GPL-3 as it will improve compatibility with other licenses. Most of its content is from elementary which updated to GPL-3 a while back. And at this point I don't think there are any Tango or Gnome icons left here (and I believe the old GNOME and Humanity icons were licensed GPL-2 or later anyway, so a relicense would be fine for that content anyway).

So I'm not totally sure what the right way to list the conent that was originally Apache or Creative Commons would be. If they're relicensed when incorporated with GPL-3, can the original licensing simply be removed (while the Authors and copyright info should remain)?

@ochosi, are you okay with an update to the GPL-3 license? And any comment on the above paragraph?

[kuraga]

@newhoa , thanks!

IMHO we may separate:

1. the original license,
2. the current license,
3. our intended (the future) license.

This issue is about the first and the second.

So, it would be nice:

1. Store the current (and optionally, the original) licence texts in /licences directory.
2. Save the original licences information in /AUTHORS/etc.
3. Make "the table of current licences" in /LICENCE.
4. Add a small paragraph about p.3. in /README.md.

(all files can have different extension).

On relicensing, /LICENCE will become short and /licences will become optional.