Upayavira, You raise a very interesting point with OpenOffice. I note that there is an openoffice.org Web site to help promote this product. Wave would benefit from a similar branded domain. Wave.org is owned by Google, so as a part of this greater exercise it would help if the appropriate body were to take over that domain, if Google were inclined to do so. That would certainly help to align the marketing of Wave appropriately with other open source platforms.
I can see where this could work out well, and that Apache could provide a suitable framework. The one difference that I'd like to have people consider is that whereas OpenOffice focuses on a specific product, what we're proposing for Wave is a platform that would enable multiple client products to be developed - as well as "demo" apps, presumably for both PC and mobile devices. From that perspective, a hypothetical wave.org might wind up being a hybrid of openoffice.org and linux.org. Linux.org includes links to popular distributions, education and opportunities for Linux partner organizations such as Ubuntu to promote their products and services. So if that sort of thing seemed to fit into the ASF framework, then perhaps that's a good solution. I am not sure how the administration of OpenOffice works within the Apache framework, so if you could forward a link to appropriate information I'd be glad to educate myself. Many thanks, John On Wed, May 29, 2013 at 1:44 PM, Upayavira <[email protected]> wrote: > On Wed, May 29, 2013, at 05:06 PM, John Blossom wrote: > > Michael, > > > > Sounds like we're all starting to sync up on this bit by bit. The > > SMTP/IMAP > > analogy is correct, though with different services, of course. > > > > I am certainly open to who maintains the raw reference client. Given that > > the platforms for that client are not really in Apache's typical line of > > projects, AFAIK, perhaps the API is where we draw the line, but there > > would > > have to be an equivalent body providing similar development and > > maintenance > > services as the Apache server code evolves. It may start one way, then go > > another way, whatever, it's doable either way. Regardless of who develops > > the reference client, clearly testing via the reference client would be > > part of the Apache Wave server release process. The key thing is to > > enable > > client apps to evolve rapidly with the right organizational structure > > focused on client apps commercialization, evangelization and education. > > > > If we can get a little more clarity on feasibility and roles, perhaps we > > can start to move this to a more public realm. I don't think that we're > > quite there yet, but we're a lot closer than we were 24 hours ago. > > John, > > While much of the code that is developed at Apache is developer focused > (e.g. servers, libraries, etc), don't assume that that is a constraint > or anything other than chance. There's no reason why user focused code > (e.g. clients) can't be developed here, it is simply a question of who > is interested in developing such things. > > If OpenOffice can succeed at developing user focused code at Apache, > then the Wave project should be able to also. > > Upayavira >
