And … I made a change, actually an addition: each event-related wave needs to have 2 links: to the main event wave and to the event’s registration page.

Below is the wave itself. When you update it here it does update the Googlewave within a Googlewave environment real time.

♦ Major issue with Google API: You can’t click on the links in the Wave within the blog! – Use the real wave within the GoogleWave environment to navigate!♦

Send me your comments/questions!

[wave id="googlewave.com!w+XxNhPBX4C" color="#0950f5" font="Arial, Helvetica, sans-serif" font_size="10" server="https://wave.google.com/wave/"]

Here are some design principals I used to create a Google Wave for this conference.

Structure:

Main Wave:

-         links to the event web site;

-         wave creator info – people can contact me with any suggestions on how to improve this wave;

-         wave etiquette;

-         links to individual speaker waves;

-         links to individual session waves.

Speaker Wave:

-         Speaker Bio;

-         Links to the sessions where this person speaks.

Session Wave:

-         Session Info;

-         Links to Speakers Waves.

Each wave has event specific tag “SocialTech2010”.

Each wave marked as a Public Wave.

Why to use wave for conferences?

Allows all people interested in the conference communicate about the event before, during and after the conference. Communications are managed on per session and per speaker basis. Though I can’t guarantee each speaker will be checking their event wave, some might…

Please share with your experiences running events on Google Wave!