Difference between revisions of "Roadmap"

From XMPP WIKI
Jump to navigation Jump to search
Line 1: Line 1:
(Moved from [http://www.jabber.org/jsf/roadmap.shtml http://www.jabber.org/jsf/roadmap.shtml]...)
+
This is a brainstorming page for items to be added to http://xmpp.org/about-xmpp/xsf/xsf-roadmap/ once the XSF membership comes to consensus about priorities.
  
The overall goal of the Jabber/XMPP community is to build an open, standardized, secure, feature-rich, widely-deployed, decentralized infrastructure for real-time communications in order to successfully compete with and supplant (or co-opt) proprietary, closed, centralized services such as AIM, MSN, Yahoo!, and Skype. The Jabber Software Foundation (JSF) has identified several high-priority technical and business initiatives for 2006-2007 to help achieve that goal, as described below.
+
The following list is quite old and needs to be updated. Edit away!
  
 
=== Technical ===
 
=== Technical ===

Revision as of 19:09, 7 September 2010

This is a brainstorming page for items to be added to http://xmpp.org/about-xmpp/xsf/xsf-roadmap/ once the XSF membership comes to consensus about priorities.

The following list is quite old and needs to be updated. Edit away!

Technical

  1. Advance XMPP Core and XMPP IM to a status of Draft Standard within the Internet Standards Process at the IETF.
  2. Ensure that the existing XMPP standards for security (i.e., TLS and SASL) are widely implemented and deployed, mainly through compliance testing and encouragement of implementation in high-profile open-source server, client, and library codebases.
  3. Work with existing certification authorities (CAs) to add support for XMPP identities to the certificates they issue, and establish the JSF (i.e., the XMPP Federation) as an intermediate CA for the XMPP server network through one or more root CAs.
  4. Finish definition of encrypted sessions as the go-forward technology for end-to-end encryption of XMPP communications, and encourage implementation in high-profile open-source client and library codebases.
  5. Finish definition of Jingle as an open technology for federated voice, video, and generalized multimedia communications, and encourage implementation in high-profile open-source client codebases.
  6. Continue to iteratively develop a complete suite of XMPP extensions for real-time communications (presence, messaging, data exchange, multimedia negotiation, collaboration, whiteboarding, etc.), and encourage integration of those XMPP extensions into widely deployed open-source technologies (e.g., Mozilla and OpenOffice) and Internet applications (e.g., last.fm and Plazes).

Business

  1. Clarify the branding of Jabber and XMPP, including migration of the JEP series to www.xmpp.org and re-launching of www.jabber.org. Note: This item is substantially complete.
  2. Hold regular (twice-yearly) developer conferences (including interop testing) to improve communication and forward progress (preferably one in North America and one in Europe each year).