81
edits
Difference between revisions of "Summer of Code 2007"
Jump to navigation
Jump to search
→Roadmap Project Ideas
| Line 28: | Line 28: | ||
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: | ||
* VoIP | * Jingle for VoIP etc. | ||
* | * Certification | ||
* Personal eventing | * Personal eventing | ||
* Message archiving | * Message archiving | ||
| Line 37: | Line 37: | ||
Detailed descriptions of these project ideas are provided below. | Detailed descriptions of these project ideas are provided below. | ||
== Jingle == | |||
Jingle (defined in several specs, start with [http://www.xmpp.org/extensions/xep-0166.html XEP-0166]) is our emerging technology for Voice over IP, video, and other multimedia interactions. Because adding Jingle support is a big project, it probably makes more sense to develop a specific aspect of Jingle support, such as the file transfer content type or a particular transport method. This is client-side only so there are no server projects here. Talk with the maintainers of a client you're interested in about what makes sense here, since some client codebases are farther along than others in Jingle implementation. | |||
== Certification == | |||
We are working on a certification program for 2008 and beyond. This will enable client, server, and library codebases to be certified for various levels of protocol compliance. For that reason we have defined two main compliance levels: [http://www.xmpp.org/extensions/xep-0073.html XMPP Basic] and [http://www.xmpp.org/extensions/xep-0117.html XMPP Intermediate]. These protocol suites will be stable by June 30 2007 for 2008 certification. Bringing an existing codebase up to the Basic or Intermediate level will help those projects achieve compliance and enable us to deploy more standardized clients and servers across the network. Talk with the maintainers of client, server, and library projects to figure out what the "gap" is for your codebase of interest. | |||
== Personal Eventing == | == Personal Eventing == | ||