Michael, Thanks very much for taking the initiative to make your statement. It is for developers themselves to decide this, but I see some of the best talents available beginning to coalesce around the Apache framework, now. I agree that there are many good ideas on the table, and that there will be a competition amongst those ideas for the things that work best and that meet the market's needs. If the Apache framework can manage those ideas and the people behind them effectively and fairly in a way that can accelerate the deliverable of highly functional and supportable Wave components, I am all for it. Wave needs a strong open source management framework to succeed in its goals. While we may debate about the specific tools that are best for managing a rapidly evolving project effectively, I don't think that there's much disagreement about needing not just excellent ideas and skills but a community with guidelines and mentorship that encourage the best efforts.
In some ways this effort is somewhat unique within the Apache framework, which provides opportunities as well as challenges. The example of Apache OpenOffice has been used as a potential model of a user-oriented Apache product platform, and I think that there are many aspects of that project that might serve as a model for Apache Wave marketing. The main difference is that it's well-established technology and a small and specific set of applications. What we're discussing so far as of late is a data model and applications development toolkit that can enable many user interface applications as well as embedded applications, all of which are headed towards like what appears to be a rapid development regimen. Wave is also being reborn in a mobile era that's used to accessing applications in other sorts of channels that maximize their market penetration. So I would hope that the Apache community would be open to considering ways in which the resulting outputs from its Wave project can be marketed in more modern ways. So I am very excited to see the responses surfacing on this thread. I hope that this energy can be channeled towards maximum market impact. I don't want Wave to be just great - I want it to rock the world, top to bottom. All the best, John Blossom On Wed, Jun 12, 2013 at 3:48 PM, Michael MacFadden < michael.macfad...@gmail.com> wrote: > Wavers, > > It has become clear that there a MANY more people are interested in Wave > that we had previously thought. There recent explosion of interest is > fantastic. However, what I am seeing is that the wave community is > splintered and fragmented. There are a lot of people who have been doing > development work on wave related concepts like OT, federation, etc outside > of Apache Wave. Maybe they thought they were not welcome. Maybe they > though the existing code base was headed in the wrong direction. Maybe > they > thought we would not be open to their project ideas. Who knows. Whatever > the reason, there have been many side projects all over the web some how > related to wave. Either inspired by wave, or developed to explore some > alternative to the way wave did something. > > I would like to try to unite these efforts in to one umbrella project. > From > a code base perspective, we can create multiple folders in our repository > were proof of concepts and side projects can exist along side WiaB. If this > drives activity and interest to Apache Wave, then fantastic. Sure we would > love to have 20 people jump in and help us with the current issues directly > in WiaB. If people want to do that, by all means PLEASE HELP. But if that > is not what you are interested in, but you ARE interested in some other > path > forward, please join our community. Please use Apache Wave as your home to > develop Wave technology. Be it OT, Clients, Protocols, what have you. > There is nothing that says the WiaB in its current form has to be the only > product produced by this project. We could have a generic core OT Engine / > API that powers wave. We could have the core server that leverages this > engine. We could have multiple clients, etc. > > I specifically named the project Apache Wave and not Apache Wave in a Box, > because the vision was the eventually this project would become the home of > a whole ecosystem of wave related things. > > If there is one current truth, it is that none of our groups has been > independently successful in developing and distributing a widely used and > adopted OT based collaboration project. I think together we can be more > successful than apart. Yes that means we have to hash things out on the > mailing list occasionally, but I think we are all open to input from > anyone. > If we can create a place for side projects, then perhaps people will be > more > free to bring their ideas and efforts here. > > To that end, I would put a call out to people who are currently working on > related projects to officially joint the Apache Wave community. Contribute > some code, whatever that may be. Help start a proof of concept for an OT > Engine, work on the client server protocol, whatever you want to do, come > do > it here. > > Together we can keep our collective momentum. Become a committer here. We > need you. > > Sincere Regards, > > ~Michael > > >
