[collectd] New to collectd - About licence of plugins

Arthur Havlicek arthurhavlicek at gmail.com
Wed Apr 5 22:50:50 CEST 2017


I must thank Florian Fosterwho correctly grasped my dilemna around 
derivative work and which answer is very accurate and correct.

I was unaware the daemon itself was in MIT licence, sorry, that 
eliminates A LOT of potential issues in my case since MIT is 
"non-contaminant".


Le 05/04/2017 à 08:34, Matthias Runge a écrit :
> Food for thought: as a customer relying on the functionality, you would
> probably be willing to pay for support, like getting help with
> installation, get a hand when it breaks, report false values, crashes,
> whatever. You could offer the plugin under the same license as collectd
> and offer professional support. Ideally, your plugin would be part of
> upstream collectd.
> Matthias
>
> [1] https://github.com/collectd/collectd/blob/master/COPYING#L1-L9

This is more complex than that. You may be able to run a business 
selling only service but if you run a restaurant you can't serve empty 
plates. I plan to make some kind of "plugin store" where i can sell 
plugin dev both on demand and on shelf, which is not something possible 
if your clients can freely exchange their plugins without coming back to 
you.

The idea of a plugin store might sound to an open source community like 
the devil, but truely for your community it's free testing and 
debugging, and most probably free pull requests for all existing OS 
plugins that I find not good enough, but not profitable to rewrite.



More information about the collectd mailing list