Bug 212840 - Add support for Google's WAVE
Summary: Add support for Google's WAVE
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.3
Platform: unspecified Unspecified
: NOR wishlist with 126 votes (vote)
Target Milestone: ---
Assignee: Volker Krause
Depends on:
Reported: 2009-11-03 01:28 UTC by KDE Brainstorm Submissions
Modified: 2018-08-27 21:50 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:

akonadi architecture scheme modified with proposed Wave integration (112.69 KB, image/png)
2009-12-02 18:21 UTC, bzhbok

Note You need to log in before you can comment on or make changes to this bug.
Description KDE Brainstorm Submissions 2009-11-03 01:28:30 UTC
Version:            (using KDE 4.3.2)
Installed from:    I Don't Know

Google have a new project under development. In their presentaion (wave.google.com) they say they asked themselves "how would you design email if you started the design from scratch today?".

What they have is going to be open standard and basic implementaiton is freely available. It sort of like a cross between InstantMessanger & E-Mail with live co-operative editing throuwn in. I think KDE should have integration with Akonadi and a client for this. It would be a hug fether in our cap if KDE was first to have this feature built in default.

If you get the chance watch the video presentation it's a hour long but even if you just skim through it you'll get the idea of how much of a revolution it could become and since it's going to be open standard you wont have to be tied to Google to use it.:-P

This feature request was originally submitted through KDE Brainstorm, and has been submitted to Bugzilla due to popular demand. Original idea: http://forum.kde.org/brainstorm.php?mode=idea&i=61626
Comment 1 Heinz Wiesinger 2009-11-27 15:17:17 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 bzhbok 2009-11-27 18:03:51 UTC
(I copy information from my post on the braistorm of forum.kde.org)

Wave is both a documented non-proprietary protocol (google wave federation protocol) and an open-source software (the basic client/server implementation from Google - and some other component) that allows to synchronize personal data between several computers or servers. The data are store inside "waves" which are XML files that contains the whole history and content of the data tree. This wave is synchronized between all the computers that have a copy of it in real time or asynchronously. It can be edited concurrently on the different computers, so it has to resolve the conflicts between the differents versions of the wave on the different computers.
The clients for waves rely on a server that keeps a version of the wave, so that you can access it from everywhere. It does not mean that there is a central server (as for msn for example) that you have to use : you could have your account at wave.google.com and me at (let's imagine...) freewave.fsf.org and we could share a wave and do our concurrent edit of the wave. Somebody from wave.kde.org may also be invited to join the wave and it will still be ok (it is similar to git where there is not necessarilly a central repository)

For more information:
From a user point of view, a wave can be used for:
- instant messaging
- asynchronous messaging (like emails)
- like a forum
- like a social network (you can control who is invited to see a wave, share photos,music...)
- like an online data storage (you can drop documents inside a wave and they are copied on the server)
- as a collaborative tool (people can edit it concurrently)...
So it is a very ubiquitous technology. Google invented a really nice technology, but it's better if there more than one provider...

Currently wave is very tied to Google : you basically must use their servers and their web application. But it's open platform nature allow the FOSS community to make wave his tool. Let KDE client for Wave be to Google Wave what Eclipse have been to Sun's Java...;-)

I propose sevral names for a Wave client in kde (which would be the kmail of wave):
- Tsunami : the relation to wave is obvious, but it's associated with not very nice events. I like it though...
- Aerial : it refers to a surf figure where the surfer jumps above the wave.
- Tow-ins : refers to the technique to be town inside the wave by a motorised boat when the wave is too big to go in by hand.
- Swell : regular waves that travels long distance
- Glassy : when the waves are very smooth, thus nice to ride
Comment 3 matt 2009-11-28 18:08:30 UTC
i´d also love to have wave support.
I don´t like the name suggestions so far - should be like other kde programs - with a K inside.
So - my name suggestion would be simple:

-> kave

As far as i know wave is jabber based - so another big plus for that.
Comment 4 bzhbok 2009-12-02 18:21:06 UTC
Created attachment 38771 [details]
akonadi architecture scheme modified with proposed Wave integration

I modified the architecture schema found on akonadi official page with the proposed Wave support:
- take the code of Google wave federation
Comment 5 bzhbok 2009-12-02 18:26:54 UTC
(oouups unvolontary submit my previous comment before finishing writing it...)
I modified the architecture schema found on akonadi official page with the
proposed Wave support:
- take the code of Google wave federation server and makes it "talk" with akonadi
- make a Kde wave client that uses Akonadi as a backend.
(I have no idea if it is realistic or not, since I'm no akonadi nor google wave develloper)
Comment 6 Nico Schlömer 2010-05-19 20:05:30 UTC
Btw, Wave is open for everyone from today.

Comment 7 Angel Blue01 2010-09-11 02:33:26 UTC
Given that Google Wave no longer exists, I think this issue should be closed
Comment 8 Alexey Shildyakov 2010-09-11 07:07:03 UTC
Why Google Wave doesn't exist? Google said they won't support and improve Wave, but Google Wave are still working.
Comment 9 p92 2010-12-08 01:33:22 UTC
Projet is now in Apache Incubator :
Comment 10 Daniel Vrátil 2018-08-27 21:50:57 UTC
The project has been retired even by Apache back in January, so I think we can close this now.