There are types to describe this graph. Thing > CreativeWork > SoftwareApplication CreativeWork.comment r: [Comment] http://schema.org/SoftwareApplication http://schema.org/Comment ( #PEP426JSONLD because this is a graph of SoftwareApplication(s); now with TOML metadata ) There could be edge types as well. e.g. what is the relation between PIL/Pillow. - maintainerSuggests - communitySuggests - communitySaysUnmaintained - unaddressedVulns - etc Adding an embedded JS comments widget does/would add some additional maintenance burden (because user-generated content). Authors can specify an email address as structured data; and whatever they consider relevant in the long_description. On Jul 13, 2016 9:33 PM, "Steve Dower" wrote: On 13Jul2016 1456, Glyph Lefkowitz wrote:

On Jul 13, 2016, at 1:54 PM, Steve Dower

...

mailto:steve.dower@python.org> wrote:

Possibly such user-contributed content would be valuable anyway

https://alternativeto.net but for PyPI? :)

Or just more general reviews/warnings/info. "Doesn't work with IronPython", "Works fine on 3.5 even though it doesn't say so", etc. Restrict it to 140 chars, signed in users, only allow linking to other PyPI packages, let the maintainer delete comments (or mark them as disputed) and I think you'd avoid abuse (or rants/detailed bug reports/etc.). Maybe automatically clear all comments on each new release as well. Doesn't have to be complicated and fancy - just enough that users can help each other when maintainers disappear. Cheers, Steve _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig