Could the make.py be adapted to generate a list of the Built-in plugin registration attributes?
Yesterday, while collating a cross-reference of a Timeline related Gramps features, I discovered an long-standing Web Pages report addon-on that had no wiki page. (A wiki page has been started. Still need to add docs for the 4 tabs of options.)
The addon_en files in the https://github.com/gramps-project/addons/tree/master/gramps52/listings folder can be used as a quick checklist to spot overlooked Gramps Plug-in Registration elements and discover missing documentation.
A couple of us have tried submitting various .gpr.py improvements for various built-in and addon plug-ins to bring them up to 5.2 standards. (Specifically, comprehensive help_url creation for all plug-ins.) It has become apparent that we need a more systematic approach to satisfy approval criteria. None of the quality improvement have been accepted.
We are about to do another release without the help_urls attributes for all the built-in plugins.
So maybe generating a list of ALL the built-in plugin registration attributes would could prove systematic completion?
(If an addon-xx.json could be generated for the built-in, maybe it could be used as a static, non-updating reference Project for the Addon Manager, giving a pretty GUI for searching built-in plug-ins, accessing Wiki pages and seeing Version data? The user documentation siloing between built-in and addon plug-ins is becoming detrimental to users.)
Further…
The old CSV text version was far, FAR easier to import into a spreadsheet than the new JSON. (Unfortunately, the addon-xx.txt files in the 5.2 folder are the result of an error and have only 2 plug-ins listed. @GaryGriffin , can you purge the .txt file clutter in that directory?)
Perhaps someone has a hint about importing in JSON data to a spreadsheet or specialized tabular viewer/editor? If there is, the proliferation of JSON use in Gramps means that we will need a wiki article about exploring such data.