On Aug 5, 9:02 pm, -TJ <tjra...@gmail.com> wrote: > I completely agree. But what should we do?
Maybe just starting a community site, like on google code, and start saving all the knowledge that may disappear when google shuts down wave at the end of the year. There are many resources and projects started which may become essential for continuing wave. What I think are the priorities: * start a community site for development and resources, * fix quickly any issue with the current protocols - if any - for both server and client, bugs are fixed with time * develop a server, as google didn't released any AFAIK (like http://code.google.com/p/pygowave-server/ can be a good start) * develop client API Clients will born as API get usable. I don't think that having a fully- featured web client is an immediate need. First of all, data sharing and framework pervasiveness is to be developed. Well, I've not much time to work on this, but I'll be glad to help. ~Aki -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
