Google Wave

I have a number of Google Wave invites that I'd like to pass along to Drupalists. Send me your e-mail address if you want one. You should get notice from Google within 24 hours if I get your info before I run out of available invites.

Gestern auf einer kleinen aber feinen Veranstaltung bei Google München hab ich den neuest Stand bzg. Wave erfahren. Neben anderen Top-Google-Entwicklern waren nicht nur der Produktmanager des Google Chrome Browsers, sondern v.a. auch die Produktmanagerin (Stephanie Hanson) und der Schöpfer und Chefentwickler von eben GOOGLE WAVE (Lars Rasmussen - suuperwitziger Typ, der auch schon mit seinem Bruder Google Maps erfunden und geschaffen hatte) anwesend, und haben den aktuellen Stand vorgestellt, Feedback eingeholt und Rede und Antwort gestanden.

UPDATE: To all of you who have requested an invitation from me, I want you to know that I have forwarded your invite request to Google. They usually respond to this nomination within a couple of days. If you do not get an invite email from Google by November 24, 2009, let me know. Remember to send me your FULL name with email addy (private or public, I don't care). By the way, I still have a couple of invites, but they're going pretty fast. Let me know if you're up for surfing.

Google Wave has been generating a lot of excitement among Drupal developers and there are very good reasons for this. Back in July 2009 or so a handful of Drupalistas, including myself, were privileged to play in Google's Wave Developer Sandbox. In early October 2009, a public preview server was opened to allow many more developers an opportunity to kick the tires on this new vehicle of communication. Most people checked it out for maybe an hour or so, liked what they saw and then moved on to other business.

I used to think of publishing a new module "Drubot" on behalf of Ethos Technologies at first, but it's still in early stage, and seems here's a better place to discuss and merge. :)
see http://drupal.org/node/580966 for code.
Note that Drubot is not working alone, but with a google wave robot, will give the robot code repo url later. :)

Some descriptions copied here for your convenience:

There are at least two basic types of information objects. One is organic and the other idealistic. By organic I mean a composite of attributes that reflect nature's use of ordered and encoded DNA information to drive organic living and organic growth processes. It is no accident that trees, branches and leaves are so often used to describe ordered relationships. By idealistic, I mean a throwback to the Platonic concept of a pure object that exists in form but is never actualized in practice.

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.

I am at liberty to dispense access to Google Wave Developer's Sandbox to one developer for the purpose of collaborative testing. I prefer to provide this access to someone who is not contractually bound to any employer to create code for the sole benefit of the employer. I will be at the Northern NJ Drupal Group meeting in Ramsey this Thursday evening. If interested in this sandbox access and collaborative testing, please discuss your interest with me at this meeting.

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,

I am primarily a Drupal developer, looking into integration of Drupal and other open source CMS platforms with Google Wave. Basically I am interested in the Wave as a content type similar to a blog, users would have the option to create wave posts on the Drupal site, other users comment, add media, robots, widgets, etc. to the wave.