Contributing to Spoofax¶
Thank you for your interest in contributing to Spoofax! We appreciate any way in which you contribute.
“If debugging is the process of removing bugs, then programming must be the process of putting them in.” – Edsger W. Dijkstra
Unfortunately all but the most trivial software contains bugs. We’ll try to fix them, but first we need to know about them. Feel free to report bugs liberally, even if you’re not sure if something is a bug or not. If you can, please search existing issues, as someone else may already have reported the issue. However, we won’t mind if you accidentally submit a duplicate bug report.
For an issue of Spoofax in IntelliJ IDEA, if you can, please include the
build-log/build.log files. You can find them by clicking on menu Help → Show Log in Files
menu, or by executing the Show Log in Explorer action.
To request a feature for the Spoofax for IntelliJ IDEA plugin, you can also file an issue.
You are welcome to implement a feature or fix a bug in Spoofax. We use the fork, branch and pull model described in GitHub’s documentation for pull requests. First you need to fork the relevant repository and clone it locally. Then create a new topic branch, for example:
git checkout -b fix-rtl-languages
Now you work in this branch. Once you’re done, you need to build and test your changes. See the chapter on building for more information. Once everything succeeds, file a pull request as described in the GitHub documentation.
The documentation needs to be kept up-to-date, and any improvements are very welcome. The documentation you’re reading now is generated from the documentation source files in our documentation repository. Documentation pull requests function in the same way as code pull requests. You can see your changes to the documentation in action by building it locally. Follow the instructions in the documentation’s Readme for more information.