On Thu, 16 Sep 2004, Matthias Andree wrote:
> On Tue, 14 Sep 2004, James Yonan wrote:
>
> > Therefore, in order for a dual licensing scheme to work, anyone who has ever
> > submitted code to the OpenVPN source code would need to agree to the dual
> > licensing scheme, since their code might now b
On Tue, 14 Sep 2004, James Yonan wrote:
> Therefore, in order for a dual licensing scheme to work, anyone who has ever
> submitted code to the OpenVPN source code would need to agree to the dual
> licensing scheme, since their code might now be potentially licensed under a
> commercial license (in
I all,
I've not yet submit any patches for Openvpn but I would like to write a
little as I will surely provide a patch in few days/weeks.
I totally agree with your vision James. Openvpn main aim is to provide a
free/libre alternative to proprietry SSL VPN. I think the main aim is not
to make of O
Hello James,
> I'd like to invite some discussion on this idea, and I'd especially
> like feedback from past OpenVPN contributors as to whether this is
> something they could agree to.
I didn't submit that much code, but of course I would aggree to dual
licensing.
Honestly,
Thomas
Open Letter to OpenVPN developers and users
---
This message is primarily directed at individuals who have submitted or plan
to submit source code patches to the OpenVPN project.
I've been considering various ways that the OpenVPN project might become
finan
