-
Notifications
You must be signed in to change notification settings - Fork 31
WiND 2
- New requirements: IPv6, Organize services ( VoIP, DNS, VPN ), monitoring, abstract user authentication (DB, Ldap, OAuth, OpenID)
- New technologies: After 6 years there are more technologies available. Technologies that can provide better and more open/free experience to the end user. (Javascript, CSS3, WebGL, HTML5, OpenStreetMaps?)
- Quality: WiND 2 will be based on the usage experience of WiND 1, giving a great opportunity to fill all the gaps and don't make the same mistakes. Adding test units and test cases will increase the overall quality of the product.
- Flexibility: WiND 1 was made for AWMN but leaving it as open as possible for other WN too. WiND 2 will be made for ANY network in mind. This will be accomplished by adding more configuration levels and modularization.
- Interconnectivity: It would be nice if WiND 2 could connect with other WiND 2 instances to share and fetch common knowledge, like intraWMN vpns, common IP Range pool, common top-level DNS (.wn?) etc.
To achieve better results, the brainstorming must be done from people with the biggest experience on the field.
This can be done be organizing open Internet-based pools where members from networks around the world could publish their ideas. This requires a platform (there are many outhere) and advertisement to all known WN that exist and use or wished to use WiND. This will be done in a fixed time-frame so that the development process can go on and not stuck on the brain storming.
Apart from internet based, there can be physical meetings per network and by the development team itself. However it would be better if the results of these meetings was published on the brainstorming platform.
After we have collected all the ideas, we have to sort them based on criteria like popularity, development cost, etc. Based on this list, we will have to identify all possible existing solutions and either decide to integrate them or replicate them or reinvent them. This involves other project parts, frameworks etc. The process can be time consuming and endless, that's why designing phase will also have a time frame that must obey.
Depending on the quality of the previous steps, this process can be fast and painless. A plan could be made and based on developers experience milestones should be suggested along with a time deadline.