On Sun, May 13, 2012 at 12:23 PM, Gert Doering <g...@greenie.muc.de> wrote: > Hi, > > On Sun, May 13, 2012 at 12:10:48PM +0300, Alon Bar-Lev wrote: >> And, if not split, they these two plugins should integrated within >> build system. > > This is certainly true. > >> The custom make files are not doing any good, but I >> still don't understand the difference between these two and other >> plugins out there. > > They are maintained by the openvpn project, and other plugins are not. > > That difference should be quite obious, no?
This is exactly my point. An healthy community dealing with openvpn need to gather all resources that are acting at that niche. There is no reason why we should not invite these maintainer to be part of the openvpn project, on the contrary, we gain more resources, more professionals. Why should we define the scope of the openvpn project based on the legacy james svn tree? Can't we progress? I would like to see this community growing... all UI/management/plugin developers working under the same roof. It is healthy to the project = more resources. It is healthy to the users = one stop shop, better integration. Alon.
