I tend to agree with this in general (XEPs are hard to format and write, hard to read, etc.) but also we can barely keep editors around and doing their full job as is so having two things for them to maintain (or finding another body to maintain the new documents) seems impractical. I'd love to hear suggestions for how it could be made easier though.
—Sam On Fri, Jun 11, 2021, at 08:03, Andrew Nenakhov wrote: > A boy with a hammer sees everything as a nail. A member of XSF has a > clear procedure, so he sees everything as a XEP. > > However, imagine a fresh developer, who wants to create a messaging > app, and has these available sets of documents: > > https://xmpp.org/extensions/ https://matrix.org/docs/spec/ > https://docs.rocket.chat/ > > Which platform would he select to create an app? Why he is least > likely to choose XMPP? > > > пт, 11 июн. 2021 г. в 16:10, Ralph Meijer <ral...@ik.nu>: > > Hi Andrew, > > > > Thank you for your feedback. > > > > When the XSF (then JSF) started publishing XEPs they were known as > > Jabber Enhancement Proposals. We modeled this after other > > organizations, in particular the well-known PEP series of the Python > > Software Foundation. It is explicitly the intent to include both > > procedural and protocol standards documents in this series. This is > > why there are different *types* of XEPs, or *tracks* if you will. > > You can read up on this in XEP-0001. > > > > The fact that the expanded name is now XMPP Extension Protocol > > doesn't change that fact. Whether that change was a wise choice is > > debatable, and maybe indeed we should have used XMPP Enhancement > > Proposal or XSF Enhancement Proposal or some such. I remember there > > was a discussion on this way back when, but I haven't taken the time > > to look it up in our archives. > > > > Including procedural documents into standards series like this is a > > very common practice. Examples include the PSF mentioned above, > > numerous Apache Software Foundation procects, and the IETF. Doing it > > this way provides us with a clear framework for developing > > procedures and putting them in force. It doesn't preclude to > > possibility to (also) present the output of such proposals in other > > places, like a dedicated page on the XSF website. > > > > If you have suggestions on how to improve our processes, we welcome > > your constructive input. We then have clear ways to consider your > > suggestions, including proposals to include cookie recipes. > > > > -- > > Cheers, > > > > ralphm > > > > > > On 11/06/2021 10.40, Andrew Nenakhov wrote: > > > Yet another irrelevant document masquerading as a protocol > > > extension. I suggest stop using XEPs as an unsorted pile of > > > various texts, or else you'll soon have cookie recipes there. If > > > you want some place for a CoC, just put in on a website in > > > 'community' section next to 'membership' page. > > > > > > > > > чт, 10 июн. 2021 г. в 21:32, Jonas Schäfer <jo...@wielicki.name > > > <mailto:jo...@wielicki.name>>: > > > > > > Version 0.1.0 of XEP-0458 (Community Code of Conduct) has been > > > released. > > > > > > Abstract: This document describes the XMPP Standard > > > Foundation's Code of Conduct > > > > > > Changelog: Accept as Experimental after unanimous approval by > > > Board of the ProtoXEP draft for discussion within the > > > community. (XEP Editor (jsc)) > > > > > > URL: https://xmpp.org/extensions/xep-0458.html > > > <https://xmpp.org/extensions/xep-0458.html> > > > > > > Note: The information in the XEP list at > > > https://xmpp.org/extensions/ > > > <https://xmpp.org/extensions/> is updated by a separate > > > automated process and may be stale at the time this > > > email is sent. The XEP documents linked herein are up-to- > > > date. > > > _______________________________________________ > > > Standards mailing list Info: > > > https://mail.jabber.org/mailman/listinfo/standards > > > <https://mail.jabber.org/mailman/listinfo/standards> > > > Unsubscribe: standards-unsubscr...@xmpp.org <mailto:Standards- > > > unsubscr...@xmpp.org> > > > _______________________________________________ > > > > > > > > > > > > -- > > > Andrew Nenakhov CEO, redsolution, OÜ https://redsolution.com > > > <http://www.redsolution.com> > > > > > > _______________________________________________ > > > Standards mailing list Info: > > > https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: > > > standards-unsubscr...@xmpp.org > > > _______________________________________________ > > > > > > > _______________________________________________ > > Standards mailing list Info: > > https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: Standards- > > unsubscr...@xmpp.org > > _______________________________________________ > > > -- > Andrew Nenakhov CEO, redsolution, OÜ https://redsolution.com > <http://www.redsolution.com/> > _______________________________________________ > Standards mailing list Info: > https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: Standards- > unsubscr...@xmpp.org <mailto:Standards-unsubscribe%40xmpp.org> > _______________________________________________ > -- Sam Whited _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
