Difference between revisions of "User:Jwi/Application 2018"
(Pre-create my 2018 application) |
(Update my application for 2018 \o/) |
||
| Line 1: | Line 1: | ||
; Name: Jonas Wielicki | ; Name: Jonas Wielicki | ||
; Profession: Computer Science student | ; Profession: Computer Science student | ||
; JID/Email: | ; JID/Email: jonas@wielicki.name, j.wielicki@sotecware.net (both work as Email and JID) | ||
; Nicknames: jonasw (in MUCs), horazont (on GitHub and IRC) | ; Nicknames: jonasw (in MUCs), horazont (on GitHub and IRC) | ||
; University: Technische Universität Dresden | ; University: Technische Universität Dresden | ||
; Company: Cloud&Heat Technologies GmbH | ; Company: Cloud&Heat Technologies GmbH | ||
==== Background ==== | ==== Background ==== | ||
I am mainly in the realm of client development | I am mainly in the realm of client development. I started actually using XMPP in about 2010, and soon began to develop "bots" which perform several tasks based on SleekXMPP. The versatility of XMPP I learnt about in that process hooked me for the protocol. | ||
In 2014 I decided to start developing an XMPP library ([https://github.com/horazont/aioxmpp aioxmpp]) and client ([https://github.com/horazont/mlxc mlxc], very incomplete) on my own. The client is targeted for the Desktop user while the library has no specific target audience and is intended to be usable for about every client scenario. As a newcomer, I am very interested in the quality of the XEP specifications, because this is essentially the only resource developers have when writing code for XMPP entities. | In 2014 I decided to start developing an XMPP library ([https://github.com/horazont/aioxmpp aioxmpp]) and client ([https://github.com/horazont/mlxc mlxc], very incomplete) on my own. The client is targeted for the Desktop user while the library has no specific target audience and is intended to be usable for about every client scenario. As a newcomer, I am very interested in the quality of the XEP specifications, because this is essentially the only resource developers have when writing code for XMPP entities. | ||
==== | ==== Why should I vote for you? ==== | ||
My | This is my second term. My first term helped me to stay closer to the standards process, especially since I joined the Editor team. I helped resurrecting the xmpp.net checker (although it is still not working flawlessly). | ||
I intend to continue my Editor team membership and further contribute to the editor infrasturcture, website and other pieces of the XSF. In addition to that, I intend to continue to follow the standards process and contribute; even though this is nothing for which I ''technically'' need to be a member, being integrated in the XSF structure helps motivate that. | |||
Revision as of 14:05, 11 January 2018
- Name
- Jonas Wielicki
- Profession
- Computer Science student
- JID/Email
- jonas@wielicki.name, j.wielicki@sotecware.net (both work as Email and JID)
- Nicknames
- jonasw (in MUCs), horazont (on GitHub and IRC)
- University
- Technische Universität Dresden
- Company
- Cloud&Heat Technologies GmbH
Background
I am mainly in the realm of client development. I started actually using XMPP in about 2010, and soon began to develop "bots" which perform several tasks based on SleekXMPP. The versatility of XMPP I learnt about in that process hooked me for the protocol.
In 2014 I decided to start developing an XMPP library (aioxmpp) and client (mlxc, very incomplete) on my own. The client is targeted for the Desktop user while the library has no specific target audience and is intended to be usable for about every client scenario. As a newcomer, I am very interested in the quality of the XEP specifications, because this is essentially the only resource developers have when writing code for XMPP entities.
Why should I vote for you?
This is my second term. My first term helped me to stay closer to the standards process, especially since I joined the Editor team. I helped resurrecting the xmpp.net checker (although it is still not working flawlessly).
I intend to continue my Editor team membership and further contribute to the editor infrasturcture, website and other pieces of the XSF. In addition to that, I intend to continue to follow the standards process and contribute; even though this is nothing for which I technically need to be a member, being integrated in the XSF structure helps motivate that.