1999

  • January: Jeremie Miller announces the existence of Jabber; an open technology for instant messaging and presence. Throughout the year development moves quickly on an open source server (jabberd), several open-source clients and code libraries, and open wire protocols for real-time XML streaming; as well as basic instant messaging and presence extensions. These same base protocols (with various improvements and extensions) are still in use today.
  • August: Jeremie submits a statement pledging the Jabber community’s support for the IETF standards process. This statement is consistent with the founding mission of the Jabber project: to foster freedom of conversation and support open standards and interoperability in real-time communications.

2000

  • February: The IETF publish work done by the Instant Messaging and Presence Protocol (IMPP) Working Group; in short, a model and set of requirements for instant messaging and presence systems.
  • May: Version 1.0 of the jabberd server is released and the base Jabber protocols (XML streaming, messaging, presence, contact lists, etc.) are stabilised.
  • October: jabberd 1.2 is released and the server dialback protocol introduced to prevent address spoofing on the rapidly growing network of Jabber servers.

2001

  • August: The Jabber Software Foundation (JSF) is formed to coordinate the growing number of open source projects and commercial entities building/using the Jabber technologies. The key focus of the JSF is to manage the protocols used within the Jabber/XMPP community, by documenting existing protocols and developing protocol extensions through an open standards process.

2002

  • February: The Jabber Software Foundation submits an Internet-Draft documenting the Jabber protocols to the Internet Engineering Task Force (IETF).
  • October: Formation of the XMPP Working Group is approved by the Internet Engineering Steering Group (IESG). As a result, JSF formally contributes the base Jabber protocols to the Internet Standards Process and assigns change control over those protocols to the IETF, under the name Extensible Messaging and Presence Protocol (XMPP).
  • November: First meeting of the XMPP Working Group is held at IETF 55 and includes presentations by Jeremie Miller, Joe Hildebrand, and Peter Saint-Andre.

2003

  • XMPP Working Group essentially completes work on formalising the base Jabber protocols for adaptation, as IETF-approved instant messaging and presence protocols; later revisions made to the base protocols focus on improving security and internationalisation.
  • Jabber Inc. submits an IPR Notice to the IETF regarding the JABBER trademark.

2004

  • October: The IETF publishes RFC 3920 and RFC 3921 defining the core functionality of XMPP as Proposed Standards.
  • Upon publication of the XMPP RFCs, the IETF announces the conclusion of the XMPP Working Group. However, development of further XMPP extensions continues at the XSF.

2005

  • June-August: The JSF participates in the Google Summer of Code.
  • August: Implementation and deployment of large-scale XMPP-based services continues, highlighted by the launch of Google Talk.

2006

  • June-August: The JSF participates in the Google Summer of Code.
  • July: The first XMPP Summit was held in Portland, Oregon, USA.
  • October: The JSF renames “Jabber Enhancement Proposals” (JEPs) to “XMPP Extension Protocols” (XEPs) and moves them to the xmpp.org website.
  • December: The JSF enters into a partnership with StartCom, to offer free digital certificates to administrators of Jabber/XMPP servers through the XMPP Intermediate Certification Authority.

2007

  • January: Jabber Software Foundation renames itself to XMPP Standards Foundation to more accurately describe its focus on developing open protocol extensions to the IETF’s base XMPP specifications, rather than open-source software.
  • February: The XSF holds the second XMPP Summit in Brussels, Belgium.
  • June-August: The XSF participates in the Google Summer of Code.
  • July: The XSF holds the third XMPP Summit in Portland, Oregon, USA.

2008

  • February: The XSF holds the fourth XMPP Summit in Brussels, Belgium.
  • June-August: The XSF participates in the Google Summer of Code.
  • July: The XSF holds the fifth XMPP Summit in Portland, Oregon, USA.

2009

  • February: The XSF holds the sixth XMPP Summit in Brussels, Belgium.
  • July: The XSF holds the seventh XMPP Summit in San Jose, California, USA.

2010

  • February: The XSF holds the eighth XMPP Summit in Brussels, Belgium.
  • July: The XSF holds the ninth XMPP Summit in Portland, Oregon, USA.

2011

  • February: The XSF holds the tenth XMPP Summit in Brussels, co-located with an interim meeting of the IETF’s XMPP Working Group, with a special focus on internationalization.
  • March: The IETF publishes RFC 6120 and RFC 6121 updating the core definition of XMPP.
  • June-August: The XSF participates in the Google Summer of Code.

2012

  • February: The XSF holds the eleventh XMPP Summit in Brussels, Belgium.
  • February: The XSF completes significant revisions to the XMPP multi-user chat extension (XEP-0045).
  • June-August: The XSF participates in the Google Summer of Code.
  • October: The XSF holds the twelfth XMPP Summit in Portland, Oregon, USA.

2013

  • January: The XSF holds the thirteenth XMPP Summit in Brussels, Belgium.
  • October: The XSF holds the fourteenth XMPP Summit in Portland, Oregon, USA.

2014

  • January: The XSF holds the fifteenth XMPP Summit in Brussels, Belgium.
  • May: Operators of servers on the public XMPP network permanently upgrade to encrypted communications.
  • September: The XSF holds the sixteenth XMPP Summit in Berlin, Germany.
  • October: The IETF publishes RFC 7395 defining XMPP over WebSocket.

2015

  • February: The XSF holds the seventeenth XMPP Summit in Brussels, Belgium.
  • June: The IETF publishes RFC 7590 updating the use of Transport Layer Security (TLS) in XMPP.
  • June-August: The XSF participates in the Google Summer of Code 2015.
  • September: The IETF publishes RFC 7622 modernizing the definition of XMPP addresses.
  • October: The XSF holds the eighteenth XMPP Summit in Richland, Washington, USA.

2016

  • February: The XSF holds the nineteenth XMPP Summit in Brussels, Belgium.
  • May: The XSF holds the twentieth XMPP Summit in Austin, Texas, USA, and host a booth at PyCon 2016 in Portland, Oregon, USA.
  • November: The XSF accepted a Special Interest Group on IoT.

2017

2018

2019

2020

  • February: The XSF holds the twenty fourth XMPP Summit in Brussels, Belgium.

2021

  • September: The XSF starts acting as a fiscal host for XMPP related projects

2022

2023

2024