dbax is a community driven project and accepts contributions of code and documentation from the community. These contributions are made in the form of Issues or Pull Requests on the dbax repository on GitHub.

Issues are a quick way to point out a bug. If you find a bug or documentation error in dbax then please check a few things first:

  • There is not already an open Issue
  • The issue has already been fixed (check the develop branch, or look for closed Issues)
  • Is it something really obvious that you fix it yourself?
  • If you are unsure if you have found a bug, then start a new thread in the dbax forum, in the Issues section!

Reporting issues is helpful but an even better approach is to send a Pull Request, which is done by “Forking” the main repository and committing to your own copy. This will require you to use the version control system called Git.

Not a Programmer?


We always need feedback on what works and what does not!. If you find something that is definitely a bug, and you are a Github user, please create a new "issue". If you are not a Github user, or if you are unsure if you have found a bug, then start a new thread in the dbax forum Issues section!


Every project needs good documentation! The dbax user guide is part of the Github project (mentioned above), and there is always room for more tutorials.


The word needs to be spread about good and worthy projects, which we think dbax is :) You can help by being active in the forums, answering questions, and by spreading the word inside your developer or user community.


The forum can always use moderators, to make sure that discussions/threads stay on topic, and to weed out the inappropriate users or comments!


Suggestions and help with our website, User Guide, dbax Console and forum design are always welcome! We are working on themes for each of these, which will be shared in their own Github repository.

Are You a Programmer?


If you would like to get involved in helping to build the next version of dbax, join us on Github! Use the Git-Flow branching model.


Every project needs a core group of developers, familiar with the project standards and conventions, to review proposed enhancements and fixes. We have been really fortunate with our group of reviewers so far, and hope to recruit a few more. Reviewers also have "commit" privileges for the code repository.

Do You see the Big Picture?

Wise Men

The direction that dbax takes, and hence its roadmap, needs to be carefully vetted and wisely chosen. We have a small group from the community, devoted to the framework, to form a council for discussing and choosing the future direction(s) of the framework!