Curate plugins

[ssm]

Plugins need a bit of cleanup.

• Which to keep in the "munin" repo
• Which to move to "contrib"
• Which to retire

Need to agree on plugin requirements for "munin" vs "contrib".

Implementation language: Perl/Shell in main repo, and anything else in "contrib"? Do we need to rewrite any plugins in perl for them to remain in "munin"?

Where to place the java plugins? Keep in "munin"? Move to "contrib"? Make a "java-plugins" repo?

Other points to consider per plugin:

• Plugin family
• Test requirements
• What is the plugin for? The operating system? A common application? An uncommon application? Free software or not?

[ssm]

Notes from IRC meeting on 2015-04-15:

Restrict core plugins to:

• Monitoring Open Source Software
• Written in sh or perl

Other plugins: relocate to "contrib", or rewrite.

Do not promote plugins from contrib to core at this time.

(See http://meetbot.debian.net/munin/2015/munin.2015-04-15-19.31.html)

[steveschnepp]

The only plugin that is special is diskstats, which has some kind of bypass card

[sumpfralle]

@steveschnepp out of curiosity: what is special about diskstats? It is written in perl and uses the Linux sysfs or procfs API.

Everything else looks very reasonable.