Contributing to Gradle
There are many ways you can contribute to Gradle. Here are some possibilities:
Tell People About Gradle
If you like using Gradle, let people know about it. Blog about it, tell your coworkers, write a review, give a
presentation, or help port an open-source project to use it.
Give Us Feedback
Gradle is still in its early stages of developement, so your feedback is really important - both positive and negative.
Tell us what you like, and don't like about Gradle. Let us know what you think could be improved. Providing feedback is
a simple, low effort way you can contribute to Gradle. You can do this by:
- Joining some of the mailing lists and participating in the discussions there. Our
design discussions happen in the open, on the developer mailing list.
- Reporting bugs or adding feature requests to JIRA.
Help With Support
We need people to help answer questions on the user mailing list. This can be a good way of learning about how Gradle
works, by diving into the code to help solve user problems.
Improve the Documentation
There are lots of things you can do with Gradle, and some of these aren't well documented. Gradle also has a large API,
all of which needs documentation. You can help enormously by writing some documentation - for the user guide, FAQ,
API, website, or on the wiki. You can provide examples. Or you can help with design and layout. Or with editing and
proofreading.
You can find out more about the documentation on the development Wiki.
Or, you can just start adding stuff to the Wiki.
Write Some Code
Want something added to Gradle? Need a bug fixed? Got an idea for a new feature? The best way to get things done to
Gradle, is to write some code and contribute a patch. Even better if it has test cases. You can find out more on the
development Wiki.