Hi, We would like to be able to continue to build/ship OpenVPN with mbed > TLS. We want all contributors to ask if they agree to license change > that adds explicit permission to link with Apache 2 licensed libraries: > > > Special exception for linking OpenVPN with Apache 2 licensed libraries: > > In addition, as a special exception, OpenVPN Inc and contributors > give permission to link the code of this program to libraries with the > "APACHE LICENSE, VERSION 2.0", and distribute linked combination > including the two. You must obey the GNU General Public License in > all respects for all of the code used other than these libraries. If > you modify this file, you may extend this exception to your version of > the file, but you are not obligated to do so. If you do not wish to > do so, delete this exception statement from your version. >
Instead of this exemption I would vote for a change to 'GPL v2 or any later version'. That would keep the license in the spirit by which people like me contributed. Using an existing license that has already been vetted also avoids the need for legal counsel. I do not understand the argument about 'GPLv2 and later...' and embedded devices. Those who are currently embedding based on GPL v2 can continue to do so, those who want/need v3 can do so too. Those who need v3 but also want to lock the firmware on a consumer device may be affected. But that's a choice they make, why would we want to promote that? Some may find this discussion a waste of time but let's not belittle people's contributions. I do care about how my work is licensed. Selva
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
