Difference between pages "User:Larma/Council Candidacy 2019" and "Membership Applications Q1 2020"

From XMPP WIKI
< User:Larma(Difference between pages)
Jump to navigation Jump to search
 
 
Line 1: Line 1:
== General ==
This page lists applications for membership in the [http://xmpp.org/about-xmpp/xsf/ XMPP Standards Foundation] received for Q1 2020.
Read about me on my [[User:Larma|user page]].


== Council Candidacy 2019 ==
Applications are welcome from people who are active in the Jabber/XMPP community!
I don't consider the Council or any of its members an authority. The council uses its expertise to testify standard proposals using certain rules, but personal opinions are not part of it. If people say "''X is not going to be accepted under the '''current''' council''", there is something wrong with the current council or with the envisioned future council and both should be fixed.


=== XEP Handling ===
To apply, create a wiki page about yourself. If you don't have a wiki account, join the [xmpp:jdev@conference.jabber.org?join jdev chatroom] or send your name, e-mail address, and preferred nickname in CamelCase to one of the [[Sysops]], who will be happy to create an account for you.
To me, the two main tasks of a Council members are
* Testify if a XEP suffices the basic requirements for being accepted as experimental
* Testify if a XEP suffices the requirements for approval as Draft as defined in [https://xmpp.org/extensions/xep-0001.html#approval-std XEP-0001]


While these tasks do require certain technical know-how, they don't ask for the council member's personal opinion. As a council member, I will try to stick to the process without including my personal opinion. If I am uncertain about specific issues in the XEP I will gather additional input from the authors, other community members and [[#SIGs|SIGs]]


That said, my criteria for accepting a XEP as experimental would be:
It is not enough to just add your name! We (the voters) want to know for whom we give a yes or no vote, and we want to know what you have done with Jabber/XMPP technologies and why you want to be a member of the XSF. See recent [[Membership Applications]] for examples.
* It should be possible to implement the protocol described in the XEP with little additional guidance (ignoring ambiguity or issues alike). This is in line with the intention from [https://xmpp.org/extensions/xep-0001.html#states-Experimental XEP-0001] to encourage implementations of experimental XEPs.
* It should be able to move to Draft within 12 months, according to rules in [https://xmpp.org/extensions/xep-0001.html#approval-std XEP-0001], i.e. it shouldn't look like the XEP is going to be in Deferred status a year later.
* It should solve a problem. If it's not obvious which problem it solves, the problem must be outlined in the XEP itself. Personal opinions can be a valid problem description, as long as they are justified.


For the elevation to Draft status I understand "''generally stable and appropriate for further field experience''" from [https://xmpp.org/extensions/xep-0001.html#approval-std XEP-0001] such, that there should be at least two implementations of the latest version (not necessarily used a lot in the wild, but existing and tested for interoperability). I'd also like to ensure that we move things to Draft faster as well as to actually move things to Final if they become wildly implemented. As an example, [https://xmpp.org/extensions/xep-0363.html XEP-0363] should probably be in Final already, but it didn't even reach Draft yet.
Please include as much information as possible when applying.


Moving things faster to Draft and Final status also means we should rarely do namespace bumps within a XEP anymore. That's because Experimental will become Experimental again (i.e. not widely implemented) and as such breaking things without a namespace bump in an Experimental XEP is actually fine. Draft standards however should remain backwards-compatible, which usually means that a namespace bump is not possible. If a significantly new iteration of a Draft or Final XEP is needed (that would imply a namespace bump), it should just start as a new ProtoXEP (and soon Experimental XEP).
The following information is required with each application:


=== SIGs ===
* full name
I'd like to revive the concept of Special Interest Groups within the XSF. Among the reasons are:
* Jabber ID
* SIGs increase the collaboration within the members and contribute to a more common understanding of their problem space
* e-mail address
* SIGs can produce XEPs as a team, reducing the work-load of each author while increasing the overall quality.
* Company name (however, everyone serves as an individual, not a company representative)
* SIGs can provide feedback on XEPs to the council, if they fall in their expertise. This is specifically mentioned as criteria in [https://xmpp.org/extensions/xep-0001.html#approval-std XEP-0001], but probably wasn't used a lot for quite some time


For a start I can imagine any of the following SIGs to be established
Note that we need the foregoing information because members may ask you some questions and we need them for our records. Some members ask questions using the discussion page of your application, please visit it from time to time. Your JID and e-mail are '''required''' to contact you upon acceptance!
* Encryption SIG (OMEMO 2.0, full stanza encryption, "SeX")
* Mobile SIG (battery and data usage)
* Server/S2S SIG (MAM 2.0 etc)
* Jingle/P2P SIG


=== Compliance suites ===
Responsibilities of XSF members are listed here.
For the sake of completeness: Compliance suites are the only XEPs that are opinionated, as they don't follow any factual criteria, but represent the Councils opinion on what is to be implemented. However this doesn't affect protocol development itself.


=== Own XEP work ===
Applications will be accepted until end of business '''February 23th, 2020''', then voted on by existing XSF members and approved in an official XSF meeting.
Should I be serving in the Council, I will obviously still continue authoring XEPs as needed. While I won't hand in proposals that I wouldn't accept myself otherwise, I pledge to always vote neutral on my own proposals to ensure neutrality.
 
== Meeting particulars ==
* Date: March 12th, 2020
* Time: 19:00 UTC
* Location: [xmpp:xsf@muc.xmpp.org?join xsf@muc.xmpp.org] chatroom
 
All applicants are invited to join this meeting.
 
== Applicants ==
 
== Reappliers ==
* [[Ludovic Bocquet Application 2020]]
* [[Jan-Carel Brand Application 2020]]
* [[Dave Cridland Application 2020]]
* [[Alexander Gnauck Application 2020]]
* [[Daniel Gultsch Application 2020]]
* [[Mathieu Pasquet Application 2020]]
* [[Daniel Pocock Application 2020]]
* [[Jérôme Poisson Application 2020]]
* [[Jonas Schäfer Application 2020]]
* [[Florian Schmaus Application 2020]]
* [[Winfried Tilanus Application 2020]]
* [[Matthew Wild Application 2020]]
* [[Tim Henkes Application 2020]]
* [[Damien Jeske Application 2020]]
* [[Dele Olajide Application 2020]]
 
== Do not reapply ==

Revision as of 11:59, 1 January 2020

This page lists applications for membership in the XMPP Standards Foundation received for Q1 2020.

Applications are welcome from people who are active in the Jabber/XMPP community!

To apply, create a wiki page about yourself. If you don't have a wiki account, join the jdev chatroom or send your name, e-mail address, and preferred nickname in CamelCase to one of the Sysops, who will be happy to create an account for you.


It is not enough to just add your name! We (the voters) want to know for whom we give a yes or no vote, and we want to know what you have done with Jabber/XMPP technologies and why you want to be a member of the XSF. See recent Membership Applications for examples.

Please include as much information as possible when applying.

The following information is required with each application:

  • full name
  • Jabber ID
  • e-mail address
  • Company name (however, everyone serves as an individual, not a company representative)

Note that we need the foregoing information because members may ask you some questions and we need them for our records. Some members ask questions using the discussion page of your application, please visit it from time to time. Your JID and e-mail are required to contact you upon acceptance!

Responsibilities of XSF members are listed here.

Applications will be accepted until end of business February 23th, 2020, then voted on by existing XSF members and approved in an official XSF meeting.

Meeting particulars

All applicants are invited to join this meeting.

Applicants

Reappliers

Do not reapply

Retrieved from "https://wiki.xmpp.org/web/index.php?title=User:Larma/Council_Candidacy_2019&oldid=12449"