Getting Involved
How to contribute to JBoss Tools
Yup, we're open.
As an open-source project, the JBoss Tools community has many entry points. We welcome your participation however it suits your level of interest.JBoss Tools is a 100% open source project. This means that not only is the code open source, free to use and free to modify, the development process too is open. Core JBoss Tools engineers are always available on public IRC channels, publish design documents and roadmaps to public wikis and issue tracker. And this is where you can get involved.
Everything is on-line
Our code is on-line, so is our continuous integration and bug tracker, developer discussion mailing lists are public and so are our design wikis and issues. It's easy to get involved - just meet one of the core engineers on IRC and say hello.
Code on GitHub
Public issue tracker for JBoss Tools
Public issue tracker for JBoss Developer Studio
Public continuous integration (Deprecated)
Team meetings and live conversations on IRC (
logs
and
meetings
)
Developer discussions mailing list
(
archive
)
Public wiki
Developer wiki
Want to talk to us?
The JBoss Tools community is on-line, geographically distributed , and communicate in a number of ways. Visit our community page for more information.Community Reported Issues
We'd like to ask everyone who would like to contribute issues to JBoss Tools to enable the Eclipse Automated Reporting Interface (AERI) in JBoss Tools. You can read about configuring error reporting in JBoss Tools hereProject statistics
Disclosure
We'd like to make clear how this project works and who holds what responsibilities. We want everyone involved to understand how decisions are made and where they can contribute. If you feel this page does not reflect the current state of project ownership and responsibilities, please contact the project lead on the developers' mailing list.
Stewardship
This project is developed and released by Red Hat with assistance from the Java developer community. The project lead is appointed by Red Hat, and has the power to accept and reject contributions to the project and set the roadmap. Red Hat employees assigned to work on JBoss Tools as well as community contributors, in this regard, all answer to the project lead.
Requirement Definition
The requirements and roadmap for JBoss Tools are driven by Red Hat and by the community. Typically, when a major release is being planned, the project lead will take input from both Red Hat and the community, and evaluate what can be done in the necessary time. This will define what features will be addressed in a given release. The project lead will then publish the roadmap in the issue tracker JBoss Tools public roadmap.
JBoss Tools is the base for the JBoss Developer Studio , many requirements for JBoss Tools are often driven by Developer Studio. You can download Developer Studio for free from the Red Hat product page.
The best way for you to suggest requirements for a future release of JBoss Tools is to enter a feature request in JIRA. The JBoss Tools team uses the JIRA voting system to evaluate the popularity of an issue - lobby others in the community to vote for your feature request!
Release Cycle
JBoss Tools attempt to keep uptodate with the Eclipse.org release train. Meaning we do a release with new features once a year and 2 or 3 minor/micro updates (bug fixes and if needed support for new runtimes). JBoss Tools are incorporated into releases of JBoss Developer Studio.
Contribution
JBoss Tools welcomes, thrives on and greatly values community contribution, and makes the bar to contributing as low as possible. If you have any questions on contributing, join us on IRC and speak to a member of the core JBoss Tools team.
