Philipp Hancke for Council 2013
I've been involved with Jabber since 2004, coming from IRC and PSYC. Most of that time opposing XMPP, which has given me a quite useful perspective. I can't say I like XML or XMPP, but it solves the use-cases I have.
I've (co)authored two rather boring XEPs which have recently advanced to draft - XEP 220 (Server Dialback) and XEP 288 (Bidi), both of which have solid implementations in psyced.
More exiciting is the stuff I do with WebRTC. Publically visible examples of that are the strophe.jingle plugin, the recently published gowebrtc API and a prosody module which implements XEP-0215 in a way that it's usable for the shared secret authentication plan described in this internet draft. I am attending Realtime Conference and WebRTC Camp in Portland this month, where I hope to demonstrate why XMPP is the right tool for deploying silo-free videochat together with Lance.
I tend to review specs carefully and give extensive feedback (including nits) and am also involved in the activities of the STOX WG (sip-to-xmpp) at the IETF.
I work and live south of Munich, employed at ESTOS GmbH, a Unified Communications vendor, where my position is technical lead for our emerging WebRTC-enabled products.
I continue to think that WebRTC is a great opportunity for XMPP. It solves the problem that the XMPP community had with Jingle (namely, lack of experience with voice/video), allowing XMPP developers to concrentrate on messaging problems. One such problem I'd like to see solved is applying carbons to forking jingle calls.
We also need to deploy ubiquitous TLS on server-to-server links and work on the tools we need for that like DNA and POSH.