Lance Stout for Council 2015

I'm Lance Stout, and this is my fourth 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 Fippo and Peter), focusing on integrating XMPP into our products and customer solutions.

=Experience=

My XMPP background consists of:


 * Editor for the XMPP over WebSocket RFC.
 * Author of stanza.io, a new JavaScript XMPP library that uses WebSocket and exposes a full JSON API for nearly all of the modern XEPs.
 * Former lead developer for the SleekXMPP Python library, with the experience of implementing over 60 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 313, 318, 319, 320, 338, and 353.
 * Author of web based IM client, otalk.im (which was forked and turned into getkaiwa.com), with support for modern features such as MAM, carbons, message correction, jingle, etc.

The majority of my work (as well as Fippo and Peter's) this past year has been on building up talky.io so that it is an XMPP based system, using Jingle and Colibri. Several of the new Jingle-related XEPs this past year stem from this work on finding where the gaps are in the Jingle specs so that it can be used with WebRTC.

=Goals=

My primary goal for the next year is to continue 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 continue to updating and bugfixing several Jingle XEPs, and also the creation of a few new XEPs to document how we've ended up making Jingle work for talky.io so that we have a full and complete Jingle experience documented.

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 stanza.io. But there are still some rough protocol edges to be resolved in order to create the kind of seamless 'just works' experiences we need.

=Contact = IM: [xmpp:lance@lance.im lance@lance.im] Mail: [mailto:lancestout@gmail.com lancestout@gmail.com]