Henshin - Getting Involved
As a community-driven project, we are happy to welcome new contributors offering their support to make Henshin better. To get involved with Henshin, you can follow any of the following steps:
Join the mailing list
- We have two separate mailing lists: the user mailing list for user requests, and the developer mailing list for coordinating the development of Henshin.
Contribute bug reports and feature requests
- Use Bugzilla for bug reports and feature requests. To create issues in Bugzilla, all you need is an Eclipse account.
- To make sure that we can address your bug reports efficiently, please be as specific as possible. Provide a detailed, step-by-step description for reproducing the bug. Minimal example projects (use the zip export) and/or screenshots are a great help.
- For further information, see: FAQ How do I report a bug in Eclipse?
- Check out our codebase from the Git repository at Eclipse. Please refer to our instructions for importing projects and resolving dependencies.
- Ideally, please use Gerrit to contribute changes to the codebase. This allows us to apply our quality assurance process to all contributions. In our Wiki, we provide more detailed descriptions for working with Gerrit.
- Alternatively, you can also submit patches via e-mail -- especially if you want to contribute relatively small changes that do not justify the overhead of setting up Gerrit. In this case, get in touch with us.
- Since our examples section is one of the most important reference points for new Henshin users, we are thankful for additions to this section. If you have an idea for a contribution in this direction, get in touch with us.
- Our Wiki is another important resource for users, and we aim to make it as accurate and complete as possible. To improve articles in the Wiki or contribute new articles, all you need is an Eclipse account. For feedback, get in touch with us.
- Do not hesitate to contact us with ideas and improvement suggestions. For establishing a first contact, please send an e-mail to the project lead (Daniel Strüber).