Sidnei da Silva-2 wrote: > >> 2/ ugly views >> >> since a package can be found in tons of categories, the front page will >> become >> ugly with a PyPI-like trove classifier: >> http://products.ingeniweb.com/catalog > > That page should only display Trove classifiers that start with 'Topic::' >
Mmm, sounds like the current PSC 'categories' is closer to the 'Topic::' branch then maybe the trove should be managed in a new field then, and the categories mapped with the 'Topic::' branch, like the other fields Licenses, etc. Maybe we could have a new kind of field for each existing field, that maps by default to the trove classifier *or/and* with its own values: - Categories => Topic:: - Available licenses => License:: - Versions etc.. - Platforms etc.. But this is getting rather complex because the trove classifier branches are not of the same depth, depending on were you are located. *brainstroming here* :) -- View this message in context: http://www.nabble.com/PloneSoftwareCenter---PyPI-%3A-classification-coherence-tp14692639s20094p14693823.html Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
