As the Auguste committee is spread out over the different universities this makes face-to-face communication at best, hard. This is exacerbated only further if peoples schedules do not align. With Google Wave we intend to hold our meetings using it and thus allow the minutes to be automatically created and shared. As Google Wave and ourselves are still in infancy. This page should help clarify what Google Wave is and some best practises for its use within Auguste.
Contents |
Google Wave is a realtime online collaboration software by Google. Its primary aim is to enable multiple users to work together and colaborate on documents by way of "conversations". You can imagine to be a bit like a wiki page but on roids, hopefully there will be no roid rage. With each wave (note the lowercase 'w') being equivalent to a conversation and Wave representing the product itself.
Wave Fun Fact No. 1 Google Wave takes its name from Firefly and their universe wide email system wave.
Each conversation, a wave, is made up of distinct conversation threads wavelets. These are the individual topics that can exist in a conversation. Wavelets themselves are made up of blips, outlined in green, and are individual messages. In summary:
| Represents | Meeting isomorphism | Topic discussion isomorphism | |
|---|---|---|---|
| wave | Conversation | Meeting | Topic |
| wavelet | Conversation Thread | Agenda item (action point, discussion point, AOCB, etc) | Topic item (Where, Day schedule of ..., Costs, etc) |
| blip | Individual message, highlighted in green | Talk / Discussion | Talk / Discussion |
Some best practises.
TODO
Looking at the organisation of our normal meetings, the structure is:
This can directly translate into Google Wave speak, with each item becoming a wavelet and the discussion and any A.O.C.B points. And the blips becoming the talk.
TODO