Lance Stout for Council 2013

Jump to: navigation, search

I'm Lance Stout, and this is my second time running for Council. I've been developing applications using XMPP since 2009, and an active member of the XSF since summer 2011. I currently work at &yet (with Bear), focusing on integrating XMPP into our products.


My XMPP background consists of:

  • Current editor for the XMPP over WebSocket draft (now accepted as an official XMPP WG item!)
  • Primary developer for the SleekXMPP Python library, with the experience of implementing over 60 XEPs
  • Author of, a new JavaScript XMPP library that uses WebSocket and exposes a full JSON API for nearly all of the modern XEPs.
  • Author of XEP-0328 (JID Prep) for making it easier for Web-based clients to properly handle JIDs
  • Implement(ed/ing) Jingle as a modular JavaScript library that other JS XMPP libraries are able to use.
  • Wrote the new MemberBot that will be running this election (The code is available for review; there are no biases :)
  • Feedback and collaboration on several other XEPs, such as XEP-0318 and XEP-0319.
  • Author of web based IM client,, with support for modern features such as MAM, carbons, message correction, jingle, etc.

Outside of XMPP, I've been involved with building applications using WebRTC, such as I'll be presenting at RealTimeConf, along with Philipp Hancke and Lloyd Watkin, on my experiences using XMPP for implementing full-fledged web applications and its use for WebRTC signaling with Jingle.


My primary goal for the next year is to work with the Jingle SIG to keep Jingle in alignment with the new developments with WebRTC. At &yet we're pushing hard for XMPP+Jingle to become the default signaling mechanism to establish federated, silo-free communications and applications. The XMPP community historically has not had strong experience implementing A/V in applications, but WebRTC offers a way to get around that. Part of this effort will be calling up several of the Deferred Jingle XEPs to be reviewed and hopefully passed to Draft, and also the creation of a few new XEPs to fill in some of gaps needed for 100% WebRTC suitability.

The secondary goal, as WebRTC is mainly a browser-based feature, is to continue efforts to make using XMPP as easy and pleasant as possible for Web developers. Otherwise, the vision for XMPP Jingle signaling simply won't happen. A lot of work has gone into library projects such as Lloyd Watkin's XMPP-FTW and my own But there are still some rough protocol edges to be resolved in order to create the kind of seamless 'just works' experiences we need, such as finishing up revisions to BOSH and working out some vague areas where XEPs intersect.


IM: Mail: