Changes between Version 6 and Version 7 of RoadMap
- Timestamp:
- 05/07/10 10:42:00 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RoadMap
v6 v7 46 46 There is also the problem that the new codebase will be competing for users and developers against the old codebase. Non-developers are unlikely to use the new codebase until it provides something the old codebase does not. Attracting developers to work on the new codebase may also be difficult unless somebody (e.g. at the company) bootstraps and leads the development effort. This means the new codebase will be relatively untested for a long time even after it's somewhat functional. To minimize this time period we'd need solid data on how people use OpenVPN (e.g. what features) and focus on developing those. Asking the users directly (e.g. on mailing lists) would help, but the dataset would be relatively small. An automated opt-in system similar to [http://popcon.debian.org/ Debian's popularity contest] would give a larger dataset, but would have to be coupled with a new software release to get widest possible audience. 47 47 48 Incremental approach solves the problem with competing codebases. However, as software architecture is difficult to change afterwards, incremental approach works only on a limited subset of the code. Some of the problematic code may be too tightly integrated to be fixable without invasive changes. However, using the incremental approach whenever possible makes most sense. 48 Incremental approach solves the problem with competing codebases. However, as software architecture is difficult to change afterwards, incremental approach works only on a limited subset of the code. Some of the problematic code may be too tightly integrated to be fixable without invasive changes. However, there are a few good candidates for incremental modularization: 49 50 * Logger 51 * Encryption 52 * Authentication 49 53 50 54 == Generic network stack vs. focus on VPN functionality ==