Bob Swift: outsidecontext we need to focus on new plugin system, what about writing a small roadmap for it? We defined a number of things in https://github.com/metabrainz/picard/pull/2419 but not everything is clear yet.
I was thinking about something regarding multiple plugins in same repo, we could have an optional top level toml file to list plugins in a dir: /plugins.toml /plugin1/manifest.toml /plugin2/manifest.toml. So we can first look for such file, and if present we read it to find about each plugin manifest. So if a plugin is moved to a standalone repo, there's no change to manifest (but the strictly needed ones in such
case). It would also let the user have multiple subdirectories that aren't plugins (and we will not have to go down to all subdirs).
Yeah, I'm not keen on that either. It was just a way to see if the tag actually existed before showing it in the "See also:" list. I'll look at a different way of checking.
Regarding the plugin system, I agree that is something that we need to firm up. One thing I have in mind is being able to register tags/variables for a plugin to show them in the autocompletion list and documentation if the plugin is activated. Functions registered by a plugin are already handled when registered.
