[Building Sakai] Integrate Apache Wave with Sakai?

[John A. Lewis]

I agree that EtherPad is simpler and perhaps therefore more compelling.
If I had to choose only one, I'd definitely want to see Etherpad in
Sakai 2 and Etherpad-like / Google Docs-like functionality in Sakai 3's
content authoring focus. It's great for collaborating directly on
producing some text, especially work synchronously while in voice
communication via another channel.

Wave seems to address a more long-running, more asynchronous use case.
Somewhere between email, discussion forums, and Etherpad / Google Docs.
But perhaps all that vagueness is it's very downfall. It certainly
failed to catch on as a consumer service mostly because we didn't really
"get it".


On 12/09/2010 11:26 AM, Eli Cochran wrote:
> I would prefer to see the full integration of Etherpad over Wave. 
>
> IMHO, Wave failed because it was overly complex and confusing. While it filled a need (perhaps too many), it failed to communicate to the user "how" you were supposed to use it. I spent quite a bit of time with it and was never clear what the _right_ way to use it was. In any given situation was I supposed to create something new, edit what was there, comment on what was there, send a chat, etc... 
>
> This was when it first came out, and perhaps it has been improved on, but unless there have been significant improvements to the UI, I don't think that it's worth the effort. 
>
> Etherpad however just works. And though it does much less than Wave, it does it very well in a way that is clear to understand. (Big kudos to Steve Githens for the work that he's already done bringing EtherPad into Sakai.)
>
> My 2 cents,
> Eli 
>
> On Dec 9, 2010, at 9:53 AM, John A. Lewis wrote:
>
>> Now that Google Wave has become Apache Wave (see
>> http://googlewavedev.blogspot.com/2010/12/introducing-apache-wave.html
>> ), is anyone thinking about integration with either Sakai 2/CLE or Sakai
>> 3/OAE?
>>
>> I think we were all intrigued by Wave when it launched, but saw it more
>> as a collaboration and discussion tool rather than "the next generation
>> of email" as Google tried to position it. In the context of a course or
>> other focus collaboration area, it seems like a very powerful evolution
>> of the discussion forum.
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> . . . . . . . . . . .  .  .   .    .      .         .              .                     .
>
> Eli Cochran
> manager of user experience design
> user interaction developer
> Educational Technology Services, UC Berkeley
>
> "Progressive Enhancement: An escalator can never break, it can only become stairs."
>     - Mitch Hedberg
>
>
>