> The XEP Editor would like to Call for Experience with XEP-0050 before > presenting it to the Council for advancing it to Final status. > > > During the Call for Experience, please answer the following questions: > > 1. What software has XEP-0050 implemented? Please note that the > protocol must be implemented in at least two separate codebases (at > least one of which must be free or open-source software) in order to > advance from Draft to Final. > > Psi. It's there for decades.
> 2. Have developers experienced any problems with the protocol as > defined in XEP-0050? If so, please describe the problems and, if > possible, suggested solutions. > > 3. Is the text of XEP-0050 clear and unambiguous? Are more examples > needed? Is the conformance language (MAY/SHOULD/MUST) appropriate? > Have developers found the text confusing at all? Please describe any > suggestions you have for improving the text. > > Probably Remko Troncon or Kev can tell us this story. (Psi git history starts later) > If you have any comments about advancing XEP-0050 from Draft to Final, > please provide them by the close of business on 2020-06-09. After the > Call for Experience, this XEP might undergo revisions to address > feedback received, after which it will be presented to the XMPP > Council for voting to a status of Final. > I haven't heard any complains about XEP-0050 for years but also I haven't reviewed it close enough. Even so I think the XEP serves its purpose well.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
