I was going to wait till Google releases the source code for their web client but I think there's enough material to get started.

This is the development plan I had in mind

In order of priority

* Part 1 - Wave Server

http://code.google.com/p/wave-protocol/

* Part 2 - Basic Wave Client

http://code.google.com/p/wave-protocol/wiki/ConsoleClient

* Part 3 - Extensions (Robot API and Gadget)

http://code.google.com/p/wave-robot-java-client/

Gadgets should be compatible since they are written in JavaScript and xml

* Part 4 - Full Web GUI

This would be wave.google.com

Would it be great if we finish this before Google does? That would make history.

I've been thinking about the server part some more, and I think it's best to first create a fully functional server implementation. After that's complete it's a lot easier to infer a decent API from that. Can anyone compile a list of work items that we'll need to complete for each of the products? That way I think we have a good guideline on what to work on.

But..... just to ask: why server first????

Building a new server solution It would take a lot of time where we have a full functional server solution already available and ready to rock??

So.... client first, in my opinion, it's the best approach, even because it could be done without a so huge working community.

Cheers all
Lele

Server or Client, they both rely on the same underpinnings, once we have the basic XMPP/WCF Library, we can build a server and client at the same time

So, the plan is to build a WCF Wave Transport Channel and start to build from this brik??

Yes, see this thread http://wave.codeplex.com/Thread/View.aspx?ThreadId=72022

We are going to start a discussion on Google wave, do you guys all have access now?

Yes, im sparkesinator@googlewave.com

Nope, sorry... Hopefully it would be asap.