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
