User:Kevin/Council 2022

Me
I'm Kev. I work for Isode, where I'm responsible for the various server and client XMPP projects/team. After a couple of years off Council as there were enough very qualified candidates, it looks like we're short this year so I'm throwing my hat back into the ring (and this page will probably be rather similar to my previous ones).

My Aims
For the past several years I've been trying to work towards how to use XMPP for enterprise-ish messaging. Snikket is driving progress well in what we might call the "WhatsApp sphere", but our story for the "Slack sphere" is where I've been putting my thought (there is, obviously, significant overlap). Because of my Isode work I'm also necessarily interested in use of XMPP on less reliable or more constrained networks, although I think most of this work is achievable without further protocol development.

My Past
I've been "doing XMPP" since before it was called XMPP. In that time I've (non-exhaustively, although exhaustingly) been project lead for the Psi client, worked on SleekXMPP, co-authored XMPP: The Definitive Guide for O'Reilly, served (mostly because I'm daft) in more Council terms than anyone else(at least, last time I counted), chaired Council the most terms (similarly), co-started the Swift client, worked on the M-Link server, now run the teams for both Swift and M-Link within Isode, helped with several of the Brussels summits, reviewed an obscene number of (proto)XEPs, written several XEPs, been GSoC admin and mentor assorted times and generally been Quite Involved with XMPP.

What Council Means
Some thoughts on what it means to be on Council, to me, and therefore what you can expect:
 * Attend the meetings (as much as possible)
 * Read the standards discussion on the mailing list, contribute where appropriate
 * Review all protoXEPs
 * Let through XEPs to Experimental as long as they're not obviously harmful/broken, or needlessly duplicating existing protocol
 * Provide guidance in the standards process