Hello Alexei, Zabbix Developers, and Community
I am wondering what is the best way to report a bug and be able to track this for the beta series? Looking at sourceforge.net/projects/zabbix Tracker and Bugs I see the following:
Categories:
Compilation Errors
General
Interface
PHP Frontend
Groups:
Before v1.0
v1.0 (example)
So is this bug list the official list that is being tracked with the full test cycle? If so should there not be more/better categories and at least a group for beta versions? Rather than using the forums where there is no explicit assignment and tracking (and patch submission for a specific issue) it is somewhat difficult to help with the development efforts and/or track to see if a specific issue you are having is either fixed or even being worked on. Also I do notice that there are some prolific patch providers (James Wells for example), but it seems that most (all?) of these patches do not get included in upstream releases. I am wondering why, are these are not part of the roadmap? If so how do we as the community influence the roadmap? I think Zabbix is great but it is not quite there and I am really interested in getting to 1.4 which I believe will be an awesome product once the bugs are worked out. In the meantime how would you like the community to help? For instance I might be willing to do formal regressions on Fedora and Redhat EL3/4 but only if these became officially supported platforms as a result.
I also believe that ALL documentation should be in wiki format so that the community can update directly as well as add useful "in the trenches" insights and workarounds. At the very least there should be a facility for the community to add comments to existing documentation like they do at http://www.php.net. So much just gets lost in the forums, and the same questions get repeated quite often. This all being said I realize that you are a for-profit enterprise so this needs to be taken into account, we are willing to buy a support contract but not for version 1.1x.
Thoughts people?
Just my $.02
I am wondering what is the best way to report a bug and be able to track this for the beta series? Looking at sourceforge.net/projects/zabbix Tracker and Bugs I see the following:
Categories:
Compilation Errors
General
Interface
PHP Frontend
Groups:
Before v1.0
v1.0 (example)
So is this bug list the official list that is being tracked with the full test cycle? If so should there not be more/better categories and at least a group for beta versions? Rather than using the forums where there is no explicit assignment and tracking (and patch submission for a specific issue) it is somewhat difficult to help with the development efforts and/or track to see if a specific issue you are having is either fixed or even being worked on. Also I do notice that there are some prolific patch providers (James Wells for example), but it seems that most (all?) of these patches do not get included in upstream releases. I am wondering why, are these are not part of the roadmap? If so how do we as the community influence the roadmap? I think Zabbix is great but it is not quite there and I am really interested in getting to 1.4 which I believe will be an awesome product once the bugs are worked out. In the meantime how would you like the community to help? For instance I might be willing to do formal regressions on Fedora and Redhat EL3/4 but only if these became officially supported platforms as a result.
I also believe that ALL documentation should be in wiki format so that the community can update directly as well as add useful "in the trenches" insights and workarounds. At the very least there should be a facility for the community to add comments to existing documentation like they do at http://www.php.net. So much just gets lost in the forums, and the same questions get repeated quite often. This all being said I realize that you are a for-profit enterprise so this needs to be taken into account, we are willing to buy a support contract but not for version 1.1x.
Thoughts people?
Just my $.02