| Version 2 (modified by , 13 years ago) (diff) |
|---|
Introduction
Historically, there have been many, many client GUIs for OpenVPN. Practically all are work of a one person, and many of them are completely unmaintained. Here's a snapshot (12th May 2011) of native Windows GUIs from our related project list:
- OpenVPN-GUI. Based on old OpenVPN GUI for Windows.
- OpenVPN MI GUI. Based on old OpenVPN GUI for Windows.
- OpenVPN Manager. Latest changes ~4 months old.
- OpenVPN Client Windows. Latest changes ~12 months old.
There are also tons of inactive client GUI projects and probably dozens of in-house client GUI implementations. This fragmentation of development effort hurts both users (who never get to use a really good GUI) and developers (who have to reinvent the wheel over and over again).
OpenVPN project has distributed a Windows GUI with it's Windows installers for years, but core OpenVPN developers have put very little emphasis on developing the GUI; this is understandable, as it's outside the scope of the project. However, bundling an obsolete (released 2005) WindowS GUI gives people the wrong impression of OpenVPN's capabilities and limitations. So, a Windows GUI overhaul is definitely needed.
Here's a list of potential reasons why so many OpenVPN GUIs exist:
- Existing GUI(s) are lacking some special functionality
- Hacking together a customized GUI is relatively easy
- Making a good-quality general purpose GUI requires lots of work
- Working with others necessarily means extra development overhead
- Most GUI projects are small and don't show up anywhere (except our related projects list)
The first step in creating a general purpose GUI is to find out what the GUI should do. Second step would be to merge existing projects together, if feasible.
