Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Jabber (also called XMPP) is an open and standardized IM protocol, which provides a feature called MUC (Multi User Chat), where users can create conference rooms on a jabber server to communicate with each other. We should consider to deploy this technology. This specifiation defines application fields of Jabber withhin the Ubuntu community and Pro / Cons for using it. In case of positive conclusion the implementation also goes into this specification.

Rationale

At the moment the most communication in the Ubuntu community takes place in Ubuntu forums, mailings lists and IRC. Those communications forms are limited to plain text messaging. Here possible reasons why we should deploy Jabber:

Use cases

Have a look at the links section.)

Scope

Design

Implementation

Unresolved issues

Proposal problems

Rationale problems

BoF agenda and discussion

By Per Ekström:

Note: This should probably move to a forum thread or something, but I'm posting this here in the meanwhile since no discussion page has been created yet, and I'm too unfamiliar with Wikis to dare create one.

Anyhow, great idea, here are a few suggestions on how to make it better (focusing on the MUC stuff, for now):

* Develop a Jabber Client which focuses on a rich MUC experience

* Using IRC-to-Jabber and Jabber-to-IRC transports to ease migration

Expanding on this idea would be beneficial since we could quite easily move the infrastructure to Jabber while keeping the IRC support intact, thus minimizing confusion - However, it would take a little extra work.

That's my two cents. Feel free to tear 'em to bits.

While it's important to ensure that no previous functionality is lost in a migration, it would also be good to keep an eye on what more there is to be gained. Collaboration can happen on more levels than a simple exchange of text messages and Jabber has a good track record as a vehicle for rich information. Audio conferencing, notetaking, whiteboarding, collaborative document authoring come to mind, see for example Coccinella and Buddyspace. (This usually meant that all parties had to use the same client. xmpp4moz, a project I worked on, removed the problem by using generic XMPP code on the client and moving real applications to the web.) This doesn't mean the pros quoted so far for IRC are any less relevant, but they'd probably be more useful as starting points than as goals. -- Hyperstruct


CategorySpec

EasyCollaborationWithJabber (last edited 2008-08-06 16:23:09 by localhost)