Who makes the decision whether to include a plugin as a standard feature?

• Jul 3, 2019 - 04:42

After relenting and reading the entire Musescore online manual, I was thrilled to find a batch converter plugin (from .mcsz to .pdf)

For me, this just saved me over two hours of horrible computer work.

Then I began to wonder why aren't some of these wonderful plugins standard with the software, considering the immense value they contain?

The ability for me to be able to automatically convert all my .mcsz files to .pdf is a wonderful feature, and I just can't fathom why it wouldn't be standard with the software, or why it took me 3 - 4 years to discover it.


Community requests + contributors + maintainers.

The main idea is that it is very hard to figure out which plugins are useful to which users. Having them shipped but disabled still wouldn't help their discoverability much. Enabling them "clutters" the Plugin menu according to some.
Also, if MuseScore endorses a plugin enough to ship it by default, it also takes a responsibility to keep it up to date with each release.

With that in mind, the consensus these past years have been to only ship some tech demos. They act as reference for plugin developers.
A long standing request to better integrate and discover plugins is now being addressed as a google summer of code project: A better plugin resource manager that pulls in the plugin repository from this site should provide us with best of both worlds. See https://musescore.org/en/handbook/developers-handbook/google-summer-cod…

Do you still have an unanswered question? Please log in first to post your question.