[Members] [Standards] LAST CALL: XEP-0345 (Form of Membership Applications)

Joachim Lindborg joachim.lindborg at sust.se
Wed Jul 23 12:18:22 UTC 2014


I know it's not a mandatory thing but as I just went through a voting
process and it helps alot if they look somewhat the same. I think it could
be stated in the introduction

*"It is recommended to review previous applications and provide some of the
topics mentioned by others ex. "XMPP experience", "Earlier XEP
involvement","Previous applications", "Why I'm applying"*


In the latest application common page, company name is stated as mandatory
http://wiki.xmpp.org/web/Membership_Applications_Q3_2014

*Regards*
Joachim Lindborg
CTO, systems architect

Sustainable Innovation  SUST.se
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg at sust.se
linkedin: http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270


2014-07-23 13:46 GMT+02:00 Dave Cridland <dave at cridland.net>:

> On 11 July 2014 08:27, Dave Cridland <dave at cridland.net> wrote:
>
>> Note that this Last Call affects XSF Members.
>>
>>
> This ends tomorrow. Any comments?
>
>
>>
>> ---------- Forwarded message ----------
>> From: XMPP Extensions Editor <editor at xmpp.org>
>> Date: 11 July 2014 01:25
>> Subject: [Standards] LAST CALL: XEP-0345 (Form of Membership Applications)
>> To: standards at xmpp.org
>>
>>
>> This message constitutes notice of a Last Call for comments on XEP-0345
>> (Form of Membership Applications).
>>
>> Abstract:
>>                         This specification outlines the form and
>> mandatory content
>>                         of membership applications.
>>
>>
>> URL: http://xmpp.org/extensions/xep-0345.html
>>
>> This Last Call begins today and shall end at the close of business on
>> 2014-07-24.
>>
>> Please consider the following questions during this Last Call and send
>> your feedback to the standards at xmpp.org discussion list:
>>
>> 1. Is this specification needed to fill gaps in the XMPP protocol stack
>> or to clarify an existing protocol?
>> 2. Does the specification solve the problem stated in the introduction
>> and requirements?
>> 3. Do you plan to implement this specification in your code? If not, why
>> not?
>> 4. Do you have any security concerns related to this specification?
>> 5. Is the specification accurate and clearly written?
>>
>> Your feedback is appreciated!
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/members/attachments/20140723/b5b709e4/attachment.html>


More information about the Members mailing list