Why contribute to Zabbix plugins?
- By contributing to open source Zabbix Monitoring Solution software you gain recognition in community and potential customers for new plugins development.
- A better understanding of Zabbix agent 2 and Zabbix frontend modules
- Helps in being prepared for the next monitoring project.
- Sharing plugin code reduce future development and testing costs.
- Builds the contributor’s reputation.
- It helps Zabbix team to improve plugins interface and make plugins code clean.
Contributor License Agreement
Whenever a non-Zabbixer wants to submit any contribution (for example, any source code, object code, patch, tool, localization/translation, sample, graphic, specification, manual, documentation) to open source Zabbix Monitoring Solution software, such contributor must first sign a Contributor License Agreement (CLA).
The CLA allows contributor to retain contributor’s ownership in the code submitted while granting Zabbix the necessary legal rights to use and distribute that contribution. When the contributor signs the CLA, contributor gives Zabbix the legal permission to use and distribute the contribution. Contributor does not surrender ownership of the contribution, and contributor does not give up any of contributor’s rights to use the contribution elsewhere.
The CLA only needs to be signed once and it covers all contributor’s present and future contributions to Zabbix.
The CLA helps Zabbix to provide reliable software product through collaborative open source software development.
It is the responsibility of Zabbix to ensure that contributors have signed a CLA before accepting their contributions. When a contributor submits a contribution to Zabbix, Zabbix will verify that the contribution is covered by a CLA. If Zabbix finds that the submission is not covered by a CLA, contributor will be notified and Zabbix will not accept the submission unless contributor signs the CLA.
If the individual owns the contribution, the individual can sign an ICLA.
If the contribution is owned by contributor’s employer/ corporation, then Zabbix must have a CCLA on file for contributor’s employer/ corporation. Contributor must also be on contributor’s employer’s/ corporation’s list of authorized contributors. The CCLA legally binds the corporation, so it must be signed by a person with authority to enter into legal contracts on behalf of the corporation.
Please note that a CCLA does not remove the need for every contributor to sign their own ICLA as an individual, which covers both contributions which are owned and those that are not owned by the corporation signing the CCLA.
It’s up to the contributor to know whether contributor’s work is owned by contributor’s employer/ corporation or not.
If you need to change the copyright holder for the contribution you submit (for example, if you start contributing on behalf of a new corporation), please send an email to [email protected].This will let Zabbix know the situation so Zabbix can make sure an appropriate CLA is completed.
Zabbix, in accordance with its legitimate interests, may publicly disclose the fact that contributor has submitted the contribution to Zabbix and has signed a CLA. Contributor’s name will be published by Zabbix, and contributor’s email address and other contact details will not be published.
The ICLA is not tied to any employer contributor may have, so it is recommended for the individual to use personal email address in the contact details, rather than work email address.
After contributor’s CLA is signed and one CLA’s signed original is delivered physically by mail or courier to Zabbix mailing address at 117 Dzelzavas street, Riga, LV-1021, Latvia, it will need to be reviewed by Zabbix. Zabbix checks to make sure that there isn’t already a CLA on file and that the CLA was signed by someone with necessary authority. This normally takes a few days. In addition to that, a scanned copy of the signed CLA in .pdf format should be emailed to [email protected].
Please note that only a paper copy of the CLA, signed by hand, will be considered as a valid commitment. Typing contributor’s name in the field at the bottom of the CLA is not signing, regardless of the font that is used. Signing is one of writing your signature by hand on a printed copy of the CLA. Zabbix does not accept unsigned or digitally signed CLA (e.g., signed via AdobeSign, DocuSign or similar digital signature tool).
Once the CLA has been accepted, contributor will receive an email with approval that contributor is covered by the CLA.
After contributor’s CLA is approved and contributor has Zabbix account contributor is ready to contribute.
Collaboration with Zabbix development team is carried out through ticketing system support.zabbix.com.
You will find Zabbix code at git.zabbix.com and should be able to:
- Create new feature ticket ZBXCTR or implement already reported.
- Create branch of type contrib/ZBXCTR-
- and make your changes.
A. If branch already exists and you want to start alternative implementation then add "-1", or "-2" to the branch name.
- Make pull request to Git pull request to master and/or supported release branches:
A. Reassign ticket to "Zabbix Development team" for review.
B. Zabbix developers are responsible for pull request code review and code merge into Git master.
If you'd like to stay on top of the development, download our nightly builds. These are produced from current development snapshots of Zabbix, straight from its Git repository. The builds are generated twice a day at 00:00 and 12:00 UTC time.
Building the nightlies may fail occasionally - that's part of why we do them. If that happens, you're welcome to report any problems by contacting us directly or registering the issue in Zabbix Support System.
|Zabbix Sources||pre-5.0.41rc1||4e0ffeeb41a||1 December, 2023||Download|
|Zabbix Sources||pre-6.0.25rc1||2afd2bfe10a||1 December, 2023||Download|
|Zabbix Sources||pre-6.4.10rc1||9c08d3f85b0||1 December, 2023||Download|
|Zabbix Sources||pre-7.0.0alpha9||bda8345e255||1 December, 2023||Download|