On Wed, Apr 17, 2019 at 14:18 Jeremy Huntwork < [email protected]> wrote:
> > Looking a little closer, it looks like contributors to a GPL-based > project maintain copyright on their own contributions. That being > said, the whole point of a license like that is to allow free use and > duplication, provided the license stays with the work. To change the > license, we would need to have permission from contributors whose code > remains, but there's nothing that prevents us from hosting it > somewhere else and even modifying it. Reflecting even further, it does seem like we only halfway set up the license. I implied GPL 2 by adding that alongside the code, but I didn’t explicitly define that anywhere. It seems the copy of the license still has template values. Regardless of whether you move it or not, it would probably make sense to get the legal status under control... If we assume that the code is actually valid GPL'd, then you could change the license if you get consent from those who have contributed to the _current_ code. Or, if that's not possible to do, you could replace those parts of the code with new/different code and then you should be able to place it under a new license. Anyway, just some suggestions. JH
-- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
