Documentation Development

[s_peter_g]

Hi
I could not find any document for development and guidance on developing zabbix engine and other component?
Does Zabbix have some policy about development document or any limitation to release?
Because I want to add some feature to zabbix engine I did not find any document!

[richlv]

please note that zabbix team currently does not have resources to evaluate external patches.
nevertheless, some basic development guidelines can be found at https://zabbix.org/wiki/Docs/specs/coding_style

[Colttt]

please note that zabbix team currently does not have resources to evaluate external patches.
nevertheless, some basic development guidelines can be found at https://zabbix.org/wiki/Docs/specs/coding_style

that mean does external developer has no chance to do bug-fixing?! shame.. its an opensource-project, right?!

a reason why have opensource success is that many different devs all over the world can develop on one project at the moment you said it is not possible.. its like SUN and OpenOffice or Oracle and MySQL..

maybe the success of nagios?!

[mgibson]

that mean does external developer has no chance to do bug-fixing?! shame.. its an opensource-project, right?!

a reason why have opensource success is that many different devs all over the world can develop on one project at the moment you said it is not possible.. its like SUN and OpenOffice or Oracle and MySQL..

maybe the success of nagios?!

Yes, it's open source. So if you're unhappy with the direction that the current Zabbix team is going in, simply fork the code and start your own version.

I'm not trying to attack you, but at the same time what you want would require them to have to start reviewing code patches of questionable quality, and take up a lot more time than just coding directly.

If you really want to help out Zabbix, figure out the codebase, and start submitting patches anyway. Either they'll begin to trust you, or not. Either way, you gain the experience with the Zabbix codebase that you're looking for.