James Purser's blog

Just a quick update to:

• Let you know this blog isn't dead
• A very quick status report on Wave In A Box

On the first, yes, I know this blog has been pretty much dead for the past few months, but I've decided to revamp it and start reporting on the status of Wave.

So to bring this up to speed here's the current status of Wave:

Apache Wave

Thought I would post this here for wider reading.

It's been a full 3 weeks since the last progress report, so this one is long and it includes the outcomes of the Wave Protocol Summit. To give better insight into what is going on, I have included a brief (incomplete) work-in-progress section at the end.

Community:

Okay I'm sitting here in Googles San Francisco office waiting for the start of day 3 of the Wave Summit so I thought I would put some notes down.

 When Google announced it was going to stop providing its own Wave service by the end of the year, it made two commitments.

Firstly, it was going to ensure that Google Wave users were going to be able to export their data so that  when the service was shut down, they weren't disadvantaged.

Secondly, the Google wave team maintained that they were going to keep working on the Open Source components of the project (including the protocols) right up until the switch is flicked on the main Google Wave service.

Well on both counts things are looking up.

Hrmm, been a while since I posted here, I blame Life(tm).

Anyway the last time we spoke, Google had just announced that it was stopping the development of Google Wave primarily because it hadn't achieved the sort of user take up that they had expected. As part of the announcement Google stated that they would start turning off the lights by the end of the year, but in the mean time they would be working out how people would be able to pull their data out of the system and what they could do with the Open Source FedOne project.

 Right, Google has decided that the Google Wave service is due for the dumpster. It hasn't achieved the sort of take up they were hoping for (I won't be talking about that right now, suffice it to say there is a whole blog post in that). This also means that the team working on Wave is going to be broken up, with people like Pamela Fox (the slightly manic but truly excellent Developer Relations person for Google Wave), Anthony Baxter and Dan Peterson being split up and sent on to greener pastures.

Okay, there have been some very interesting changes over the past few months that has brought Googles Wave service out of the geeky wilderness and into something that is now truly usable by regular people.

Feature #1: Notifications

Last Wednesday I was lucky enough to catch the March Google Wave Sydney Users Group at Google headquarters in Sydney.

 Okay, I've just nutted out a new structure for the Independant Wave book. I'm going to kill off the Google Wave book, because frankly. others are doing that better than I am. I'll leave the FedOne book up both for people looking for information on setting up FedOne and because I'm going to be stealing the content (if one can steal from oneself) to put into one of the chapters of the IWave book.

Okay here's the structure I'm looking at:

Introduction

Introduction

Chapter 1 - The Basics

What is wave?

 Well it has been a long time since I last posted here. This hasn't been due to any loss of interest in the ideas behind wave, rather it's been a case of work getting in the way of other stuff.

Since I last posted here, I've attended lca2010 and presented both on the Independent Wave (something which deserves it's own post) and PlonieBot.