Closed ewdurbin closed 8 years ago
Original comment by Arc Riley (Bitbucket: arc, GitHub: arc):
Sure if you want to be super specific you could also have a trove classifier for every XEP supported by the package, too. Or at least the big ones, such as Adhoc Commands, Data Forms, MUC, and Publish Subscribe.
There are only a dozen or so currently maintained (*) XMPP packages on PyPI, so since the primary purpose of trove classifiers is to aid in search a single global "Topic :: Internet :: XMPP" should be more than enough.
I'd prioritize many low-hanging fruit ahead of an XMPP-IM specific entry, eg:
#!
Environment :: Raspberry Pi
Framework :: AsyncIO
Topic :: Database :: ORM
Topic :: Software Development :: Version Control :: GIT
Topic :: Software Development :: Version Control :: Mercurial
Topic :: Internet :: RTP
Topic :: Internet :: WWW/HTTP :: CSS
Topic :: Internet :: WWW/HTTP :: WebSocket
Topic :: Internet :: WWW/HTTP :: WebRTC
(*: Packages which are not currently maintained are unlikely to utilize new trove classifiers, so this is only relevant to new packages and packages likely to see new releases soon)
Following up on this (sorry it fell off my radar), I agree with your reasoning there, Topic :: Internet :: XMPP
is probably enough for now. What would it take to get this moving forward? Is it agreed that it should be a thing? Would a PR be enough?
Per https://github.com/pypa/pypi-legacy/issues/301#issuecomment-226940147, this needs to be reported to https://github.com/pypa/warehouse now.
completed.
Originally reported by: Sam Whited (Bitbucket: SamWhited, GitHub: SamWhited)
I would like to request that the
Topic :: Communications :: Chat
namespace have a new classifer for XMPP added:This would make the full namespace (at the time of this writing):