Hi Alon, > > Current active developers are interested in specific features which > are never complete. > > For example Gert cares about the IPv6 implementation, but did not take > all the routing and tun handling on him self as a whole. > > Adriaan added the PolarSSL support, but did not take all the crypto > interfaces of OpenVPN. > > Heiko took the MSVC build + unicode support, bit did not take the > windows (non-tun none-routing) subsystem. I think having subsystem maintainers would make sense. Current feature-based development will probably work for a few years, but as you say, it can result in problems down the road. That said, there are a few practical obstacles if we take the subsystem maintainer approach:
1) Do the developers have the (extra?) time to commit to the project 2) Do the developers have enough knowledge to take over a subsystem? If not, go to 1). What would the core tasks for subsystem maintainers be, in your view? -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
