Have you ever contributed to an open source project? There are tonnes of different ways to help out, and we want to show you how: From GitHub workflows and general contributing as well as more specific Icinga related topics. We at Icinga have been working on some guidelines for getting started with development on our projects – contributing to the Icinga project has never been easier! That could be working on a plugin, a webmodule, fixing bugs in Icinga Web 2 or Icinga 2, adding features to the director or simply adapting the documentation.

1. Contributing to Open Source

2. Who am I?
Feu Mourek they|them
GitLab Trainer for NETWAYS
Development Advocate for Icinga

3. Infrastructure Monitoring
Observe your entire IT in one Place
Monitoring Automation
Monitor massive amounts of data.
Cloud Monitoring
Monitor the private, the public and hybrid.
Metrics & Logs
Get the context and recognize trends.
Analytics
Analyze data and perform proactively.
Notifications
Get alerted and react with confidence.
The Icinga Stack

4. We’re an Open Source company
More than just open source code.
The people working on Icinga are more than just who we see in our office.
Icinga lives from your ideas and contributions.

5. Would you say, that you have ever
contributed to an Open Source project?

6. Making changes to the repositories
Making a difference for other users
Helping the developers
Contributing takes different forms
How to contribute

7. Making Changes to the Repositories
You can interact with Issues on GitHub.

8. Opening an Issue

9. Opening an Issue

10. Opening an Issue

11. Opening an Issue

12. Making Changes to the Repositories
You can interact with Issues on GitHub.
Or you could Fork the repository and submit a Pull Request.
Check for Contributing guidelines.

13. Forking and Branching
Only fix one issue per change.
Choose a meaningful name for a branch.
The same applies for your commits!

14. Opening a Pull request

15. Opening a Pull request

16. Opening a Pull request

17. Opening a Pull request

18. Opening a Pull request

19. Committing and Merging
Check for Contributing guidelines for your commits!
Fix problem with notifications in HA cluster
There was a race condition when restarting.
refs #4567

20. Opening a Pull request

21. Opening a Pull request

22. Opening a Pull request

23. Opening a Pull request

24. The CLA
CLAs might be required for some projects
CLA != CTA - the copyright is still yours
Most CLAs based on Apache Software Foundation Contributor License Agreement
Makes it possible to for the project to distribute your contributions

25. Documentation
Read through and fix typos
Test the installation
Suggest structural changes in issues or Pull Requests
Format: GitHub flavoured Markdown.
Location: doc/
Getting started: CONTRIBUTING.md or ask in the Forum

26. Making Changes for Other Users
Be active in the forums
Ask questions, start discussions
If you can, try to help others with their problems!
The Icinga forum is community.icinga.com

27. Making Changes for Other Users

28. Contribute your knowledge
Write a blogpost next time you solve a problem!
Talking about your experiences on social media
and starting conversations helps both the project and others

29. Helping the developers
Testing software is important.
Check out beta versions and new releases
Learn how to write good bug reports

30. Good Bug reports
Figure out how to reproduce your bug.
Describe as much of your environment as possible.
Security issues are to be treated with special care.

31. What do you say now?
Have contributed to an Open Source project?

32. twitter.com/icinga github.com/icinga facebook.com/icinga
icinga.com
Thank You!
What are your questions?