Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add postfix-policyd-spf-python plugin #644

Merged
merged 2 commits into from Sep 6, 2015
Merged

add postfix-policyd-spf-python plugin #644

merged 2 commits into from Sep 6, 2015

Conversation

lynix
Copy link

@lynix lynix commented Sep 1, 2015

Very simple but useful plugin to monitor postfix-policyd-spf classification results. Written by me some time ago, but still works :)

@ssm
Copy link
Member

ssm commented Sep 2, 2015

Could you pick a license for it, please, and add it to the plugin?

Either a copyleft or permissive opensource license would be fine, but it should be explicitly stated which license to use in the plugin.

@lynix
Copy link
Author

lynix commented Sep 3, 2015

Sure, I'd like to go with the MIT license (although I don't care much, so if you've got a better suggestion I'm open to it). Shall I paste the entire license in the script or just state the name of the license?

I'm a bit irritated because I've seen many plugins without any license information (partially even without author information).

@ssm
Copy link
Member

ssm commented Sep 4, 2015

Alexander Koch notifications@github.com writes:

Sure, I'd like to go with the MIT license (although I don't care much,
so if you've got a better suggestion I'm open to it). Shall I paste
the entire license in the script or just state the name of the
license?

For most plugins in the "munin" repo, we just state the name of the
license in the plugin. (MIT/Expat, MIT/X11, GPL-v12345, Apache-2.0,
etc…)

Some plugins have the entire license text. I'm fine with both
alternatives.

I'm a bit irritated

Sorry about that. :/

because I've seen many plugins without any license information
(partially even without author information).

Yes, there are many of those, unfortunately. Tracking down previous
authors, in case that becomes necessary, will take a lot of time. The
alternative may be to drop them altogether.

Stig Sandbeck Mathisen

@lynix
Copy link
Author

lynix commented Sep 4, 2015

Thanks for the info :) I've added the license commit.

ssm added a commit that referenced this pull request Sep 6, 2015
add postfix-policyd-spf-python plugin
@ssm ssm merged commit b785526 into munin-monitoring:master Sep 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants