MusicBrainz Picard supports the addition of user defined functions and extensions through optional plugins. Initially, plugins were developed and included in an “official” list of plugins by pushing the plugin to the “metabrainz/picard-plugins” repository on GitHub. By scanning the repository, a list was displayed on the Picard website and was available to Picard through an API on the website. This is the list that is displayed by default in the Picard options settings.

In some cases, the original plugin authors have abandoned the plugin or have not provided maintenance or response to reported issues in a timely manner. Further, the issues are being reported on the MetaBrainz ticket tracking system, with the expectation that the Picard development team will address them. Even though the Picard team is trying to address the issues raised, this is not an appropriate expectation which can also unfairly impact the reputation of the Picard software. As more and more plugins are developed by third-parties, this concern continues to grow.

The intent of this “proposal” is to document the issues and concerns, and provide a means for collaboratively developing a plan for the ongoing management of plugins available for MusicBrainz Picard. As such, a “working document” has been created as a wiki page, inviting input and revision by the core team of Picard developers, and comments by third-party developers of plugins for use with Picard. The document is available at https://wiki.musicbrainz.org/User:Rdswift/PicardPluginProposal. I am open to suggestions for an alternate location or method for collaboratively developing the proposal if the Picard developers prefer.