Wavers, Apache is an open community and a do-ocracy. We don't have a hierarchical structure and anyone is welcome to contribute in any way they wish. This is a key principle of being an Apache project.
At the same time we need to start to have focus in several key areas in order to progress. As such I am recommending we for sever committees with focused topics of discussion, specific goals, and plans of action. The committees are not intended to be exclusive in any manor. Discussion will happen on the dev list where everyone is welcome to participate. Rather the point of the committee is to give some focus to a group of developers who agree to help advance particular aspects of Apache Wave. These members would commit to facilitating discussion on certain aspects of wave. I propose we form four committees based on my observation of the wave project. 1. Operational Transformation Research and design of OT algorithms, data models, and concurrency control. 2. Protocols Investigate protocols such as federation, client server, and the underlying mechanisms such as protocol transport and discovery. 3. Development, Build (eg maven) and Release This committee would focus on making wave easier to develop, build, and release. This can include documentation, architecture diagrams, maven, git, etc. this will hopefully help attract developers to the project. 4. Client / Server Architecture This last group would leverage the work of the first three to start to separate the client and server components. The vision would be that the committees would start holding regular discussions and start to document plans and decisions in sections of the wiki. I would like your thoughts on the formation of committees, if we have the right ones identified, and if there is interest in supporting this model. Regards, Michael MacFadden http://www.macfadden.org
