GI is an open source project and we could use your help. There are a number of ways to get involved including:
GI is open source. That means you can download the source code and modify it in almost any way you want. The GI team uses Subversion for source control. For more information on Subversion read the book.
We have deployed the fabulous source code intelligence tool FishEye to give you all sorts of insight into the code, including recent changes, branch history and code metrics. Visit our Fisheye Repository.
The GI team uses JIRA for tracking bugs and feature requests. All bug reports are public and can be viewed at http://www.generalinterface.org/bugs/. There you can see what bugs are fixed and track closed issues. To file bugs, or request new features you will need to create a community account.
If you think you have identified a bug in GI follow this process:
You can always check out the code from Subversion and create a build using the build tools. To save you a step we automatically create builds on a daily basis and post them for you to download and test.
The GI team does all its planning out in the open. Here are the home pages for the various versions of GI in development.
Most user support, roadmap discussion, and feature ideas come from the forums. Once you've registered for an account, you can begin to get involved. Helping others is great way to give something back, and the forums are the easiest place to get started. You can find answers to your questions by searching messages in the Discussion Forums, or post a new topic.
If you've gone through the trouble of identifying a bug or writing a test case, you may find it just as easy to also fix the bug.
The easiest way to submit patches to GI is to create diffs and attach them to existing JIRA tickets. This is a straightforward process, but the Dojo Foundation will need a "Contributor's License Agreement" (CLA) on file from you.
Once your CLA has been received, project committers can review and (potentially) merge your changes to fix the bug. To increase the odds that your patch will be merged, keep the following guidelines in mind.
Project contributors are encouraged to use the following mediums of communication when discussing the project: