Michael, I Thank you very much for the warm welcome. I am hopeful that we can move towards combining the remaining (and emerging) energies focused on Wave such that the Apache platform becomes the focus for maintaining the development aspects of the project as much as possible. The Wave Watchers ( http://www.wavewatchers.org) is a group of Wave enthusiasts, including some developers, self-formed during the Google Wave project, who during that period were avid testers and contributors to all things Wave-oriented and who contributed to defending waves against the incursions of malware bots that some were deploying on Wave. Wave Watchers were a close-knit community then, and remarkably they have remained so for all these years since the end of Google Wave. I think that it is important for everyone in the Wave community to recognize the value of having such people as a part of this effort. Their enthusiasm and relatively high profile in social media platforms like Google+ and Twitter can help Wave to attract the attention of users as the code base begins to support more robust and attractive options using the Wave protocols, APIs, tools and data models. So as important as it is to recognize that Apache's community is extremely valuable at a detailed design and coding level, so must we recognize that those efforts need to be complemented by efforts at a higher level.
I agree wholeheartedly that the "balkanization" of Wave efforts fairly soon after the Apache project was set up has been highly destructive overall to the effort, and that it's important for us to encourage both contributions of code and testing to Apache from existing projects and to establish the importance of federation as a tool that will help the Wave market to grow. Right now Wave is set up in a way that even email is not - you have various platforms claiming Wave benefits but there is no sharing of data to allow users to enable conversations that can use those platforms on common data sets. Even email does that via its various client apps using POP/SMTP, etc. The potential for a highly sophisticated conversational data model with federation of these data conversations is just about ideal for many mobile-first development needs now, so if we can focus resources to build out Wave to make that possible, then I think that Wave will not only survive, it will become something that will be unquestionably powerful. So I intend to gently shepherd development and design resources towards Apache - I don't want any further balkanization of core code - but also make sure that those who want to participate on another level are also encouraged in the venues that will complement and amplify the Apache community's efforts. We have much to learn from all of you and look forward to building one big, beautiful and amazing Wave. All the best, John Blossom email: [email protected] phone: 203.293.8511 google+: https://google.com/+JohnBlossom On Sat, May 25, 2013 at 4:08 PM, Michael MacFadden < [email protected]> wrote: > John / Justin, > > The apache community for wave could use some help to be honest. From my > perspective, we would rather welcome you into our community and have your > input directly into this project rather than have you feel like you need > to go off in your own direction and then merge changes with us. I would > recommend that you, and anyone else you have been coordinating with joint > this mailing list and start discussing the protocol in an open forum. We > can set you up with access to the wiki and other resources. > > I think one of wave's challenges is that a lot of little side projects are > underway, but a larger community is slow to get going. We would welcome > you and your contributors directly into the wave project. > > If you have any questions on how this might work, please feel free to ask. > We would love to have your contributions. > > Regards, > > Michael > > On 5/24/13 11:07 AM, "John Blossom" <[email protected]> wrote: > > >Justin, > > > >Thanks for chiming in, I am working with some folks to come up with an > >updated spec, so I'd like to keep you in the loop, and vice versa. > > > >My coding talents are deprecated, but I am focused on getting Wave back on > >track for long-term success via specifications and product strategy. > > > >All the best, > > > >John Blossom > > > >email: [email protected] > >phone: 203.293.8511 > >google+: https://google.com/+JohnBlossom > > > > > >On Thu, May 23, 2013 at 4:33 PM, Justin Beals > ><[email protected]>wrote: > > > >> Hi all, > >> > >> I've been lurking on this list for a little bit and am really glad to > >>see > >> some activity. I thought I would chime in. I am interested in > >> contributing to the design and documentation tasks that may arise for > >>the > >> Apache Wave project. I have UXD & User experience. > >> > >> My interest in Wave is as a replacement to the typical 'forum' or > >> 'discussion board' we currently use in a lot of our educational > >>solutions. > >> I'm excited to contribute so that I can help Wave become a new part of > >>our > >> online learning strategies. > >> > >> Thanks, > >> Justin Beals > >> VP of Product Solutions > >> HotChalk.com > >> > > >
