Comment on Feedback Wanted: Manage Plugin Dialog
matterhorn103@discuss.avogadro.cc 2 weeks ago We could just fall back to the main repo URL. Or, the script in avogadro/plugins that extracts the metadata from the plugins’ TOML files to generate the index could automatically generate the appropriate issues URL for any plugin that is on GitHub and doesn’t manually specify project.urls.issues.
Not sure I’m a huge fan of something that’s Python-specific, encodes the metadata using Python code, and is a solution specific to that one implementation. This CITATION.cff is GitHub’s own solution, but it is at least supported by Zotero and Zenodo. But I don’t have strong feelings. It’s a shame there’s no standardized way to handle companion publications, really – it would be good if citations of academic papers were part of the SPDX Bill of Materials specification, for example.
That would be my suggestion, since most (all?) of the current plugins don’t use
project.urls.issues:slight_smile:It’s fairly common for people to list things in the README, but that’s not very uniform and I’m a little reluctant to try to extract DOI or BibTeX from the README.
I guess the alternative would be to add something like
pyproject.urls.doias a list in thepyproject.tomlas an alternative if theCITATION.cffisn’t found.Here’s my latest version. The author list grows if needed (e.g., here) and gives a download count and a link to the bug tracker.
Thoughts? Ideas? Right now, the keywords are stored in the model but in a hidden column. (Not that any current plugin includes keywords in their pyproject.toml yet.)