[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gNewSense-users] KFV Flow

From: Sam Geeraerts
Subject: Re: [gNewSense-users] KFV Flow
Date: Fri, 11 Apr 2008 20:33:00 +0200
User-agent: Mozilla-Thunderbird (X11/20080110)

Luis Alberto Guzmán García wrote:
El jue, 10-04-2008 a las 20:22 +0200, Sam Geeraerts escribió:
What would you do if he says "oh wait, I actually meant the CDDL"? Technically the GPL would still apply because it cannot be revoked, but in order to not piss off the copyright holder you would remove it.
If in any case any copyright holder try to change from one license to
another then he has to notify to the competente authority and let the
whole Free Software community know that his/her software is not free.

And in that case, it must and should be removed from any distro that
respects their users freedom.

More than just teaching developers to be more explicit, this would
really mean that gNS handles only free software, we can support it up
with the developers (copyright holders) word.

This is the final goal that i attempted to achieve but maybe is too much
trouble :/

Once released as GPL, the code will always be GPL. If the copyright holder doesn't like that, too bad. The only thing he can do is re-release it under another license, but then the GPL version will still be available.

It's nice for gNewSense to have the developer's support, but it's not necessary. If a copyright holder wants to change the license and the discussion about it turns ugly, it could be decided on a case by case basis wether or not to remove the code. Contacting the copyright holder yourself instead of letting them come to you just might give one of them funny ideas, thereby increasing the chance of triggering such a dicussion. You are of course free to do as you like when confronted with such cases. I just don't think it should be a necessary part of the flow.

It's good to have these things cleared up to have a nicely documented verification method. Your flow chart is a considerable contribution to that. I think it will come in handy to clearly represent outcomes of possible future discussions on this list.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]