Frequently Asked Questions

Where can I get the software?
The code is maintained in a github repository at http://github.com/davec/openbrewcomp, where you can clone it with git or download a zip or tar archive of the source.
What do I need to run the software?
The software is written for the Ruby on Rails framework. See the list of requirements for detailed information.
Do you have a insert name of other language or framework version?
No.
How do I submit a patch?

The preferred way is to fork the project on github and send a pull request.

If you do not have a github account, you may email a patch, or set of patches, as generated by git format-patch 1 to openbrewcomp-bugs@crunchyfrog.net. Please include PATCH in the subject to ensure that your message gets through the spam filters.

Either way, be sure that your commit message describes what your patch does and why I should accept it. When it makes sense to do so, be sure to include tests that verify your patch.

How do I report a bug or suggest a new feature?

Create an issue (from the Issues tab) on the project’s github page.

If you do not have a github account, then you can send email to openbrewcomp-bugs@crunchyfrog.net. Please include either BUG or FEATURE in the subject to ensure that your message gets through the spam filters.

  1. If you are not using git as your source code management system, please submit patches in the unified diff format. You may need to specify an option to your SCM of choice to do so. For example, with CVS and RCS you need to add the -u option to the diff command to generate unified diff output. ↩