Every now and again we get a compliment or two on how amazing Icinga is. These moments always bring a smile to our faces, but to be honest… what really floats our collective Icinga boat is some sort of community love.
There are so many forms this can come in that many are just not aware of. So we’ve put a list of the top 10 ways to say “thank you for the awesome software”:
10. Spread the word
Whether on Twitter, Facebook or your own blog, if you think Icinga is good then help us share it with the world. If you run Icinga at work or for charity, you can even make your recommendation official by joining our Icinga Users.
9. Offer an idea to improve Icinga
Did you know Icinga Mobile started from an idea off our Icinga Feedback channel? For all those times you think, “if only Icinga had…” don’t keep it to yourself – let the community know! It could just be that hundreds of other users could do with that one killer feature that your idea would have inspired.
8. Share how you did it
From installation on Debian and optimizing IDOUtils to integrating PNP graphs and implementing NSCA – if you have done it before, why not share how you did it by writing a guide on Icinga Wiki or Icinga Docs? Plenty of users would thank you for it.
7. Share a plugin or addon
There are thousands of plugins and addons available on repositories such as MonitoringExchange.org. These were all written by users before you, who were kind enough to share their work and save you from reinventing the wheel each time you integrate a new service. If you write a plugin then pay it forward!
6. Help a fellow user
You know that feeling when you get stuck configuring Icinga to check SNMP? After scouring the docs, wiki and web, when you finally find that one person who has had the exact same issue and knows how to solve it – don’t you just want to run up and give them a virtual hug?
Thankfully the good karma goes both ways, you can give and receive help and hugs on our user mailing list, IRC user channel and the monitoring-portal.org community forum.
5. Report a bug
4. Test Icinga
To save you from reporting bugs post release, we usually present a beta release a week or two prior to the final one. This is the best time to find bugs without the pain of picking them out in a production environment. So help us test, test, test!
3. Submit a patch
If you find a bug and know how to get rid of it, we welcome you to write a patch and submit it for review and application. Check out our Developer Guidelines to make sure it goes upstream the first time. When it does, we’ll salute you through our credit roll in change log of each release.
2. Package Icinga for others
We’re lucky that maintainers have come on board to serve up pre-packaged Debian, Ubuntu, FreeBSD, Gentoo, etc. versions of Icinga. However, there are plenty of distributions that are still awaiting Icinga packages. If you know your distro well, get in touch with us.
1. Help code Icinga
There is no better way to say thank you than to contribute to the Icinga code itself. If you are ready to commit (pun intended) to developing the best open source monitoring software on the planet, we love to hear from you on our IRC developer channel and devel-mailing list.
Icinga is nothing without you, our community. Your contributions – be it patches, bug reports, wiki guides or helpful online advice – are all the thanks that we, the Icinga community could ever need.