what-about-design: link to xmpp.org
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
parent
eb67356341
commit
e0db14e40e
1 changed files with 2 additions and 1 deletions
|
@ -56,7 +56,7 @@ entities taking part in it. And so on…
|
||||||
|
|
||||||
[XEP-0322]: https://xmpp.org/extensions/xep-0322.html
|
[XEP-0322]: https://xmpp.org/extensions/xep-0322.html
|
||||||
|
|
||||||
The XSF (XMPP Standards Foundation, previously known as Jabber Software
|
The [XSF] (XMPP Standards Foundation, previously known as Jabber Software
|
||||||
Foundation) is the entity that did the original work on the protocol and
|
Foundation) is the entity that did the original work on the protocol and
|
||||||
submitted it to the IETF. It now has a sheperding role. There is no
|
submitted it to the IETF. It now has a sheperding role. There is no
|
||||||
requirement that XMPP extensions be brought to the XSF, but it aims to be the
|
requirement that XMPP extensions be brought to the XSF, but it aims to be the
|
||||||
|
@ -64,6 +64,7 @@ place where technical knowledge around XMPP is gathered, so people can get
|
||||||
better feedback when submitting their new specification. Developers have
|
better feedback when submitting their new specification. Developers have
|
||||||
already layed out lots of protocol bricks for others to reuse through the XSF.
|
already layed out lots of protocol bricks for others to reuse through the XSF.
|
||||||
|
|
||||||
|
[XSF]: https://xmpp.org
|
||||||
[XEP-0001]: https://xmpp.org/extensions/xep-0001.html
|
[XEP-0001]: https://xmpp.org/extensions/xep-0001.html
|
||||||
[XSF_mission]: https://xmpp.org/about/xsf/mission.html
|
[XSF_mission]: https://xmpp.org/about/xsf/mission.html
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue