https://wiki.xmpp.org/web/index.php?title=Daniel_Gultsch_for_Council_2020&feed=atom&action=historyDaniel Gultsch for Council 2020 - Revision history2024-03-29T00:22:52ZRevision history for this page on the wikiMediaWiki 1.37.1https://wiki.xmpp.org/web/index.php?title=Daniel_Gultsch_for_Council_2020&diff=13192&oldid=prevDaniel: /* Council work */2020-10-14T15:58:22Z<p><span dir="auto"><span class="autocomment">Council work</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 15:58, 14 October 2020</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l15">Line 15:</td>
<td colspan="2" class="diff-lineno">Line 15:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Council work ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Council work ==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>I've previously served on Council for <del style="font-weight: bold; text-decoration: none;">two </del>terms in <del style="font-weight: bold; text-decoration: none;">the years </del>2017 and <del style="font-weight: bold; text-decoration: none;">2018</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>I've previously served on Council for <ins style="font-weight: bold; text-decoration: none;">three, non-consecutive </ins>terms in 2017<ins style="font-weight: bold; text-decoration: none;">, 2018 </ins>and <ins style="font-weight: bold; text-decoration: none;">2020</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>A majority of the votes in day-to-day council operation are going to be two things: Accepting XEPs as ''experimental'' and moving XEPs from ''experimental'' to ''draft''. The criteria in XEP-0001 leave room for interpretation and different people have interpreted them differently over the times. So if you are going to put me into Council you should know how I’m (generally) going to vote on these issues.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>A majority of the votes in day-to-day council operation are going to be two things: Accepting XEPs as ''experimental'' and moving XEPs from ''experimental'' to ''draft''. The criteria in XEP-0001 leave room for interpretation and different people have interpreted them differently over the times. So if you are going to put me into Council you should know how I’m (generally) going to vote on these issues.</div></td></tr>
</table>Danielhttps://wiki.xmpp.org/web/index.php?title=Daniel_Gultsch_for_Council_2020&diff=13191&oldid=prevDaniel: Created page with "== About me == My name is [https://gultsch.de Daniel Gultsch]. I’m self employed and work full time on XMPP related projects. One of my publicly known projects is the open s..."2020-10-14T15:31:02Z<p>Created page with "== About me == My name is [https://gultsch.de Daniel Gultsch]. I’m self employed and work full time on XMPP related projects. One of my publicly known projects is the open s..."</p>
<p><b>New page</b></p><div>== About me ==<br />
My name is [https://gultsch.de Daniel Gultsch]. I’m self employed and work full time on XMPP related projects. One of my publicly known projects is the open source Android client [https://conversations.im Conversations] but I also do consulting and contract work for commercial projects.<br />
<br />
=== XEPs ===<br />
There are currently three XEPs that bear my name:<br />
* [https://xmpp.org/extensions/xep-0363.html XEP-0363: HTTP File Upload]<br />
* [https://xmpp.org/extensions/xep-0398.html XEP-0398: User Avatar to vCard-Based Avatars Conversion]<br />
* [https://xmpp.org/extensions/xep-0411.html XEP-0411: Bookmarks Conversion]<br />
<br />
=== Security ===<br />
I concern myself with security in the open source ecosystem and have over the years documented a couple of vulnerabilities in various open source clients.<br />
* [https://gultsch.de/gajim_roster_push_and_message_interception.html CVE-2015-8688]: Gajim Roster Push Attack / Message Interception<br />
* [https://gultsch.de/converse_bookmarks.html CVE-2018-6591]: Converse.js leaking information about which rooms are bookmarked<br />
* [https://gultsch.de/dino_multiple.html CVE-2019-16235+]: Multiple Vulnerabilities found in Dino<br />
<br />
== Council work ==<br />
I've previously served on Council for two terms in the years 2017 and 2018.<br />
<br />
A majority of the votes in day-to-day council operation are going to be two things: Accepting XEPs as ''experimental'' and moving XEPs from ''experimental'' to ''draft''. The criteria in XEP-0001 leave room for interpretation and different people have interpreted them differently over the times. So if you are going to put me into Council you should know how I’m (generally) going to vote on these issues.<br />
<br />
=== Accepting a XEP as Experimental ===<br />
I’m a believer of providing a stable base for anything people want to work on. To be accepted as experimental a XEP doesn’t have to be perfect. I’m also open to giving a number to XEPs that I personally don’t agree with or find otherwise controversial. I believe that there is room for exploring different solutions to the same problem. However I think that a XEP has to be implementable to be accepted. In the past Council has accepted XEPs that were just a bunch of ''TODOs'' or otherwise contained a lot of placeholders. I believe that an independent developer has to be able to look at a XEP and start implementing it.<br />
<br />
=== Moving XEPs to Draft ===<br />
There are currently a lof of XEPs stuck in experimental that are widely implemented and a working ''fine'' for a lot of people (Most noteworthy are Message Carbons, Message Archive Management, HTTP Upload).<br />
<br />
If we are going to consider ''experimental'' as a lower quality just-provide-a-stable-base kind of stage (see previous section) we need to move those XEPs that are widely implemented (and are obviously working for a lot of people) on to draft to make them distinguishable from XEPs that are not fit for use.<br />
<br />
There is a chance that one or even all of the XEPs I used as examples above are not the most beautiful things the XMPP has ever come up with. But that doesn’t change the fact that these XEPs are different to the average lower quality experimental stage XEPs. The life cycle state of those XEP has to reflect that.<br />
<br />
If we promote those widely used but arguably not 100% perfect XEPs to ''draft'' now and come up with a better solution later we can still ''obsolete'' them.<br />
<br />
It is irritating that our Compliance Suits which are basically lists of XEPs to implement for a good & modern IM experience point to XEPs that then say »Please don’t implement me in production«.</div>Daniel