Le lundi 3 juin 2024, 00:21:58 UTC+2 E.M. a écrit : > Dear all, > > today I looked at the extensions web overview which we have improved in the > recent time. Special thanks to Daniel B. again. > https://xmpp.org/extensions/ > > I would like to enhance the filtering with tags or categories to help > developers when implementing the protocol. That way a quick selection of > relevant XEPs dependent on the implementation purpose could make onboarding > easier. All this may be clear to you, but is not to others and interest third > parties. Currently they get a numbered list, but no focus or priority nor > importance. > > For example, one could filter for the latest compliance suite and its > relevant XEPs. Or which are important around A/V implementation. Which XEPs > are part of base and advanced implementation? Which is related > And maybe you have many more better ideas to help and guide people. > > Theoretically, we have the solution already: Using tags. However, only one of > the XEPs has tags so far: > https://github.com/xsf/xeps/blob/master/xep-0488.xml#L25 > > So, if you agree and maybe also have ideas and/or suggestions I would call to > update the most relevant XEPs. > > If we have more tags we can also offer them as filter selections right away. > > Let me know what you think. > Eddie >
Hi Eddie, this is a great move, thanks for your suggestion and work in general. It would be useful to filter on topic such as "pubsub", "jingle", "microblogging", "e2ee". XEP dependencies can be a good starting point to automatically assign tags (for instance, all XEP depending on XEP-0166 are Jingle related). Best, Goffi
signature.asc
Description: This is a digitally signed message part.
