Wave

As Google suggests, Wave requires a contribution from a broader community outside Google. The Google Wave API is open for all and developers around the world may participate. Having this context we look for building a vibrant forum which will simultaneously have the developers and their end users at the same platform. Budding developers will also get support from the forum in different technical issues. The mission is to have a very supportive community like we have today for different Open Source platforms, e.g. Drupal, phpBB etc.

Hi. I am a Drupal webmaster/project manager/user experience specialist, and am VERY interested in integrating Wave into my client projects right out of the gate. I am also waiting on sandbox access, so haven;t had a chance to play yet. I've expressed interest at the Wave module page in helping however I can - testing, UX review, documentation, whatever I can. I think one of the immediate decisions that needs to be clarified for people like me is: when is it appropriate to recommend that we implement a Wave server vs just using a third-party provider? Is it number of sites the client is managing? is it infrastructure-dependent? Is it branding considerations? I'm sure the answers are yes, yes and yes to some degree, but I think it will be instructive to begin work on some best-practice guidelines to help us Drupal folks know the landscape a little better. I am VERY excited about Wave, and can't wait until we have a module to begin messing with. FUN!!

Another thing - I've started a DrupalWave Twitter account for us to use. I know it's not convenient for long posts but maybe just some of the more announcement-type stuff and smaller issues could be addressed there. I expect that I'm hardly the best candidate for inside information and the latest scoops -- I just want to make sure that we have a voice out there in Twitterland and to contribute any way I can. Having issued that last caveat,