The next wave user group...
1 view
Skip to first unread message
Brett Morgan
Jul 30, 2009, 8:41:06 PM7/30/09
to sydney-google-...@googlegroups.com
Hey All,
I'm interested to hear your thoughts on how we can make the wave user group a better and more useful environment for all of you guys.
What I am seeing are that there are three focii:
* Business / Creative / Design / Users who are interested in thinking about the user experience the wave technologies enable
* Front end developers who are thinking about how to develop these new user experiences
* Back end developers who are thinking about how to architect systems to handle the massively increased write load
I am looking for how to best serve these three groups, and how to facilitate communication between these groups.
My first ideas are:
Business / Creative / Design / Users could do with a creative brain storming session to start thinking about what is now possible. This is a discussion I want to have, as I see a lot of potential experiences, but I don't know if they are _useful_.
The front end developers could use discussions around the technologies used in the google wave user client, as demonstrated in the 80 minute Google IO '09 launch demo. I want to understand the tools and techniques used to make this possible. GWT, Content Editable, etc.
The back end developers could use discussions around how to deal with the write load. Caching strategies, how to shard load, etc. A great place to start, per @pamelafox, would be a mini hackathon to get the sample fedone sample servers up and running.
What are your thoughts about this? What have I missed? How can I better serve you as the sydney google wave user group organiser? =)
Looking forward to seeing where we can take this,
brett
--
Brett Morgan http://domesticmouse.livejournal.com/
I'm interested to hear your thoughts on how we can make the wave user group a better and more useful environment for all of you guys.
What I am seeing are that there are three focii:
* Business / Creative / Design / Users who are interested in thinking about the user experience the wave technologies enable
* Front end developers who are thinking about how to develop these new user experiences
* Back end developers who are thinking about how to architect systems to handle the massively increased write load
I am looking for how to best serve these three groups, and how to facilitate communication between these groups.
My first ideas are:
Business / Creative / Design / Users could do with a creative brain storming session to start thinking about what is now possible. This is a discussion I want to have, as I see a lot of potential experiences, but I don't know if they are _useful_.
The front end developers could use discussions around the technologies used in the google wave user client, as demonstrated in the 80 minute Google IO '09 launch demo. I want to understand the tools and techniques used to make this possible. GWT, Content Editable, etc.
The back end developers could use discussions around how to deal with the write load. Caching strategies, how to shard load, etc. A great place to start, per @pamelafox, would be a mini hackathon to get the sample fedone sample servers up and running.
What are your thoughts about this? What have I missed? How can I better serve you as the sydney google wave user group organiser? =)
Looking forward to seeing where we can take this,
brett
--
Brett Morgan http://domesticmouse.livejournal.com/
Fil Mackay
Jul 30, 2009, 9:56:43 PM7/30/09
to Sydney Google Wave User Group
Hi Brett,
Firstly thanks for organising this, and for the googlers who took some
time out (from coding, presuambly..) to attend and for the very brave
souls who actually consumed some alchohol whilst talking shop.
I think segregating the content is a great idea, but something else
that I think is missing is some further input from Google. We had
visibility of a lot of productive roles, but not enough of the
visionary. I think the audience would love to hear from these people
(Lars et al) who I think connect the various pieces that we heard
about individually last night. Whilst segregating the content is a
resonable response to distinct islands of interest - the main benefit
of these user groups is to expand our knowledge by connecting them
together. eg. the reasoning behind the design goals of the OT
framework from a high level, I think would be really beneficial.
Secondly, it's really important to get some people demonstrating stuff
they've built with Wave - getting some creative airplay and some
create feedback to Google.
As way of feedback I learned the following:
1. The Wave vehicle is an SUV not a zippy convertable
2. The focus of Wave is collaboration, not real-time data distribution
3. The best search company in the world cannot find a bad smell?
Regards, Fil.
Firstly thanks for organising this, and for the googlers who took some
time out (from coding, presuambly..) to attend and for the very brave
souls who actually consumed some alchohol whilst talking shop.
I think segregating the content is a great idea, but something else
that I think is missing is some further input from Google. We had
visibility of a lot of productive roles, but not enough of the
visionary. I think the audience would love to hear from these people
(Lars et al) who I think connect the various pieces that we heard
about individually last night. Whilst segregating the content is a
resonable response to distinct islands of interest - the main benefit
of these user groups is to expand our knowledge by connecting them
together. eg. the reasoning behind the design goals of the OT
framework from a high level, I think would be really beneficial.
Secondly, it's really important to get some people demonstrating stuff
they've built with Wave - getting some creative airplay and some
create feedback to Google.
As way of feedback I learned the following:
1. The Wave vehicle is an SUV not a zippy convertable
2. The focus of Wave is collaboration, not real-time data distribution
3. The best search company in the world cannot find a bad smell?
Regards, Fil.
Brett Morgan
Jul 31, 2009, 4:03:31 AM7/31/09
to sydney-google-...@googlegroups.com
Heya Fil,
I agree, I am very thankful to all the googlers who gave graciously of their time and hospitality to give us a home last night.
Along the lines of splitting the content, and managing expectations, I am proposing the following format going forward. We have the room every second thursday of the month, so how about the following?
Thursday 10th of September: Business & Front End focus
A presentation or open forum discussing business opportunities with wave, and
A focus on how the wave client was built in GWT, and fun & games with content editable.
I am trying to figure out a better way to communicate "what google wave is." There are a lot of parts, and a lot of different points of view. Is it a real time email client, or a collection of technologies? There is some truth to both of these points of view. I think of it like the wave particle duality...
Anyways, I am more than happy to hold long discussions about "what google wave is" to me, and hopefully in batting ideas about we can all learn from each other.
brett
I agree, I am very thankful to all the googlers who gave graciously of their time and hospitality to give us a home last night.
Along the lines of splitting the content, and managing expectations, I am proposing the following format going forward. We have the room every second thursday of the month, so how about the following?
Thursday 13th of August: FedOne mini hack-a-thon.
For people interested in federation and operational transforms. Get the federation code base working, and then pulling it apart.
For people interested in federation and operational transforms. Get the federation code base working, and then pulling it apart.
Thursday 10th of September: Business & Front End focus
A presentation or open forum discussing business opportunities with wave, and
A focus on how the wave client was built in GWT, and fun & games with content editable.
Thursday 8th of October: Post Sept 30 "what is wave" user training group.
Given the Wave.google.com launch, it would probably be a good time to get new users together and play with the wave client and robots.
Given the Wave.google.com launch, it would probably be a good time to get new users together and play with the wave client and robots.
I am trying to figure out a better way to communicate "what google wave is." There are a lot of parts, and a lot of different points of view. Is it a real time email client, or a collection of technologies? There is some truth to both of these points of view. I think of it like the wave particle duality...
Anyways, I am more than happy to hold long discussions about "what google wave is" to me, and hopefully in batting ideas about we can all learn from each other.
brett
pamela fox
Aug 6, 2009, 6:59:25 PM8/6/09
to sydney-google-...@googlegroups.com
Sounds good.
As for "what google wave is", I like to always bring it back to the three P's - "protocol, platform, product" - and highlight which of those I'll be discussing. Otherwise it can get fairly confusing.
As for "what google wave is", I like to always bring it back to the three P's - "protocol, platform, product" - and highlight which of those I'll be discussing. Otherwise it can get fairly confusing.
Brett Morgan
Aug 6, 2009, 8:17:09 PM8/6/09
to sydney-google-...@googlegroups.com, Alison VanHees
Yeah, fair call. I'm looking for lots of feedback on explaining wave to people, I've tried a bunch of different tactics so far, and they've been epic fails on pretty much all counts. Maybe if I put together some material and test it on you and alison?
Nic Fulton
Aug 6, 2009, 8:49:28 PM8/6/09
to sydney-google-...@googlegroups.com, Alison VanHees
Brett et al,
I wrote the attached summary of Wave a month ago for briefing people
inside the company I work for (Thomson Reuters). I've removed
proprietary bits regarding our business and how we may leverage Wave,
but I hope it's vaguely useful as a starting point for explaining
Wave. I certainly got the 3Ps message and that's the way this is
structured.
I'm sure there are much better descriptions out there (please send me
pointers) but I just wanted to share.
I should put it on Wave and we can collaboratively author... although
that sounds too much like eating our own dogfood!
Cheers,
Nic.
--
--------------------------
Sent from my clunky wirefull desktop
I wrote the attached summary of Wave a month ago for briefing people
inside the company I work for (Thomson Reuters). I've removed
proprietary bits regarding our business and how we may leverage Wave,
but I hope it's vaguely useful as a starting point for explaining
Wave. I certainly got the 3Ps message and that's the way this is
structured.
I'm sure there are much better descriptions out there (please send me
pointers) but I just wanted to share.
I should put it on Wave and we can collaboratively author... although
that sounds too much like eating our own dogfood!
Cheers,
Nic.
--------------------------
Sent from my clunky wirefull desktop
db
Aug 10, 2009, 12:31:37 PM8/10/09
to Sydney Google Wave User Group
I thought it was a 'platform' with a protocol, with products within
it.
So that others can have their own 'platform', linked or not
(federation) via the protocol and offer their own products.
:)
On Aug 7, 8:59 am, pamela fox <pamela....@gmail.com> wrote:
> Sounds good.
> As for "what google wave is", I like to always bring it back to the three
> P's - "protocol, platform, product" - and highlight which of those I'll be
> discussing. Otherwise it can get fairly confusing.
>
it.
So that others can have their own 'platform', linked or not
(federation) via the protocol and offer their own products.
:)
On Aug 7, 8:59 am, pamela fox <pamela....@gmail.com> wrote:
> Sounds good.
> As for "what google wave is", I like to always bring it back to the three
> P's - "protocol, platform, product" - and highlight which of those I'll be
> discussing. Otherwise it can get fairly confusing.
>
> On Fri, Jul 31, 2009 at 6:03 PM, Brett Morgan <brett.mor...@gmail.com>wrote:
>
> > Heya Fil,
>
> > I agree, I am very thankful to all the googlers who gave graciously of
> > their time and hospitality to give us a home last night.
>
> > Along the lines of splitting the content, and managing expectations, I am
> > proposing the following format going forward. We have the room every second
> > thursday of the month, so how about the following?
>
> > *Thursday 13th of August*: FedOne mini hack-a-thon.
>
> > Heya Fil,
>
> > I agree, I am very thankful to all the googlers who gave graciously of
> > their time and hospitality to give us a home last night.
>
> > Along the lines of splitting the content, and managing expectations, I am
> > proposing the following format going forward. We have the room every second
> > thursday of the month, so how about the following?
>
> > For people interested in federation and operational transforms. Get the
> > federation code base working, and then pulling it apart.
>
> > *Thursday 10th of September*: Business & Front End focus
> > federation code base working, and then pulling it apart.
>
> > A presentation or open forum discussing business opportunities with wave,
> > and
> > A focus on how the wave client was built in GWT, and fun & games with
> > content editable.
>
> > *Thursday 8th of October*: Post Sept 30 "what is wave" user training
> > and
> > A focus on how the wave client was built in GWT, and fun & games with
> > content editable.
>
Reply all
Reply to author
Forward
0 new messages