Difference between revisions of "Sam Whited Application 2015"
(Created page with "== Metadata == * Full Name: Sam Whited * Jabber ID: sam@samwhited.com * E-Mail: sam@samwhited.com * Job: Platform engineer with Atlassian (HipChat) == About me == I'm a pla...") |
|||
| Line 10: | Line 10: | ||
I'm a platform engineer at HipChat where I mostly work on adding client facing features to our custom XMPP server and attempt to make it more standards compliant. While my professional interest in XMPP only started fairly recently (until this job I've always worked in the infosec industry), I've complained about, I mean, "been an avid user of", the protocol for many years. | I'm a platform engineer at HipChat where I mostly work on adding client facing features to our custom XMPP server and attempt to make it more standards compliant. While my professional interest in XMPP only started fairly recently (until this job I've always worked in the infosec industry), I've complained about, I mean, "been an avid user of", the protocol for many years. | ||
My contributions to XMPP include a great deal of work on the Android client Conversations (https://github.com/siacs/Conversations/commits/master?author=SamWhited) — including adding SCRAM-SHA-1 support, implementing the blocking command, and many other changes besides — lots of minor work on XEPs (https://github.com/xsf/xeps/commits/master?author=SamWhited), and a few that I've authored myself (Current OTR Usage, Mobile Considerations, OTR Disco, HipChat's Entity Versioning protocol, etc.). | My contributions to XMPP include a great deal of work on the Android client Conversations (https://github.com/siacs/Conversations/commits/master?author=SamWhited) — including adding SCRAM-SHA-1 support, implementing the blocking command, and many other changes besides — lots of minor work on XEPs (https://github.com/xsf/xeps/commits/master?author=SamWhited), and a few that I've authored myself (Current OTR Usage, Mobile Considerations, OTR Disco, HipChat's Entity Versioning protocol, etc.). I was also recently voted on to the XSF editors team (and then told I couldn't participate until I actually became a member, which I'm doing now). | ||
My primary objective in joining the XSF would be to help my crusade to weed out duplicate protocols that lead to client interop issues, and to make sure that I'm actually allowed to help where needed. | |||
Revision as of 16:11, 30 September 2015
Metadata
- Full Name: Sam Whited
- Jabber ID: sam@samwhited.com
- E-Mail: sam@samwhited.com
- Job: Platform engineer with Atlassian (HipChat)
About me
I'm a platform engineer at HipChat where I mostly work on adding client facing features to our custom XMPP server and attempt to make it more standards compliant. While my professional interest in XMPP only started fairly recently (until this job I've always worked in the infosec industry), I've complained about, I mean, "been an avid user of", the protocol for many years.
My contributions to XMPP include a great deal of work on the Android client Conversations (https://github.com/siacs/Conversations/commits/master?author=SamWhited) — including adding SCRAM-SHA-1 support, implementing the blocking command, and many other changes besides — lots of minor work on XEPs (https://github.com/xsf/xeps/commits/master?author=SamWhited), and a few that I've authored myself (Current OTR Usage, Mobile Considerations, OTR Disco, HipChat's Entity Versioning protocol, etc.). I was also recently voted on to the XSF editors team (and then told I couldn't participate until I actually became a member, which I'm doing now).
My primary objective in joining the XSF would be to help my crusade to weed out duplicate protocols that lead to client interop issues, and to make sure that I'm actually allowed to help where needed.