81
edits
Difference between revisions of "Summer of Code 2007"
Jump to navigation
Jump to search
→Roadmap Project Ideas
| Line 25: | Line 25: | ||
= Roadmap Project Ideas = | = Roadmap Project Ideas = | ||
In general, we are most interested in projects that are relevant to our [http://www.xmpp.org/xsf/roadmap.shtml roadmap]. These include: | In general, we are most interested in projects that are relevant to our [http://www.xmpp.org/xsf/roadmap.shtml roadmap]. These include: | ||
| Line 34: | Line 30: | ||
* VoIP or other media sessions with [http://www.xmpp.org/extensions/xep-0166.html Jingle] | * VoIP or other media sessions with [http://www.xmpp.org/extensions/xep-0166.html Jingle] | ||
* Compliance with the [http://www.xmpp.org/extensions/xep-0073.html XMPP Basic] and [http://www.xmpp.org/extensions/xep-0117.html XMPP Intermediate] protocol suites (to help prepare projects for certification in 2008) | * Compliance with the [http://www.xmpp.org/extensions/xep-0073.html XMPP Basic] and [http://www.xmpp.org/extensions/xep-0117.html XMPP Intermediate] protocol suites (to help prepare projects for certification in 2008) | ||
* | * Personal eventing | ||
* | * Message archiving | ||
* End-to-end encryption | * End-to-end encryption | ||
| Line 41: | Line 37: | ||
Detailed descriptions of these project ideas are provided below. | Detailed descriptions of these project ideas are provided below. | ||
== End-to- | == Personal Eventing == | ||
Several years ago we defined a robust protocol for generalized "publish-subscribe" (pubsub) functionality. More recently we defined a friendly "subset" or "profile" of pubsub that is suitable for IM networks. This "personal eventing" technology will enable us to deploy fun extended presence and social networking features like user moods ("how are you feeling?") and real-time music feeds ("what are you listening to?"). | |||
The personal eventing protocol is defined in [http://www.xmpp.org/extensions/xep-0163.html XEP-0163] and support can be added to both servers and clients. Adding support to a server will involve only the core eventing itself. Adding support to a client will involve eventing as well as event payloads like [http://www.xmpp.org/extensions/xep-0107.html user mood] and [http://www.xmpp.org/extensions/xep-0118.html user tune]. | |||
== Message Archiving == | |||
Traditionally, Jabber clients have archived or logged messages on the local machine of the user. But what if you use a web client, or you switch back and forth between different devices? It would be great to save your messages on the server so that you could retrieve them from anywhere, so we've defined a protocol for doing just that in [http://www.xmpp.org/extensions/xep-0136.html XEP-0136]. A SoC project could add support for message archiving to a client (especially a web client) or a server. | |||
== End-to-End Encryption == | |||
We have been working on specifications for end-to-end encryption of XMPP communications. Building support for these technologies is an ambitious project, however it can be broken down into several, more manageable pieces. | We have been working on specifications for end-to-end encryption of XMPP communications. Building support for these technologies is an ambitious project, however it can be broken down into several, more manageable pieces. | ||