(How to include or link) Plugins in non-scripting language (like Rust)

[Joerg Jaspert]

Hi,

I would like to include some plugins here (or better: have them linked from the Plugin Gallery), but it is not as trivial as a simple Pull Request: They are not in a scripting language. The plugins are Rust source, and as such need a Rust environment to compile and do not fit some of your requirements.

How to best go about making them more available to others?

More info:

I wrote a Rust crate (library), munin-plugin (Github, docs), which (IMO) makes writing Munin Plugins in Rust plenty simple. I have written one CPU graph plugin with 1-second resolution which can do plain "total" graphs or multigraph for each CPU core, one Interface graph plugin with 1-second resolution using that crate, and am in process of converting my Fibre Channel SAN stats graph plugin over to this lib. I also converted the plain load graph to it, but that was more to see how a simple plugin goes.

Including the Rust crate in the munin-monitoring/contrib repo doesn't make too much sense - Rust with it's package manager use crates.io. Including the Rust code of the plugins could be done, but then ideally each plugin would have it's own subdir, as one needs at least Cargo.toml too, including Cargo.lock also makes sense.

Next issue would be the wanted documentation/tags. Could probably be put into
/*
[...]
*/
block comments, so Rust ignores them. As long as the Gallery generator is happy with that?

Alternative idea would be to include "stub" files, that just have the neccessary comments, but otherwise link to the real GitHub Repos for the Plugins?

What do you think is the best way about it?

Ganneff