Team Permalink to " Team"

JHipster is developed by a team of people around the world. We have a lot of contributors (top 100 list here), but members of the core team are listed here.

If you want to join the team, or see how we work, our community rules are at the end of this page.

JHipster Governance Structure Permalink to "JHipster Governance Structure"

JHipster is an open-source project, and we have a governance structure to ensure that the project is well maintained and that the community is well served. The governance structure is as follows:

• JHipster Developer Association: A French non-profit association (“Association loi 1901”) which serves as a legal entity for JHipster events and services.
• Governing Body: Advisory body overseeing all projects under the JHipster organizations and JHipster Developer Association. The Governing Body is responsible for the overall direction of the project.
• Project Leads: Leads are responsible for the day-to-day management of the project. Leads have admin rights and are responsible for releases.
• Board of Developers: The core team of developers who have write access to the main repository and have voting rights when it comes to project decisions.

Governing Body Permalink to "Governing Body"

Project leads Permalink to "Project leads"

Board of developers Permalink to "Board of developers"

JHipster streams Permalink to "JHipster streams"

JHipster supports a wide range of technology choices for your application and as it keeps growing we have come up with technology streams with specific leads to ensure smooth maintenance of the particular technology. Everything else will be lead by project leads.

The updated spreadsheet can be found here

Stream	Leader
Angular	William Marques
React	Sendil Kumar N
VueJS
JHipster Registry	Pierre Besson
JHipster core/JDL	Mathieu Abou-Aichi
JHipster Kotlin	Sendil Kumar N
JHipster IDE	Serano Colameo
JDL studio	Deepu K Sasidharan
JHipster online	Julien Dubois
Continuous Integration and Delivery	Pascal Grimaud
Gradle	Frederik Hahne
Maven	Daniel Franco
JHipster server-side libraries	Julien Dubois
Spring Boot	Daniel Franco
OIDC/OAuth	Matt Raible
Blueprints & modules system	Aurélien Mino
Heroku	Joe Kutner
GCP/GAE	Ray Tsang
Kubernetes	Pierre Besson
Istio	Ray Tsang
Infinispan	Srinivasa Vasu
Reactive	Christophe Bornet
Java	Julien Dubois
Docker	Pascal Grimaud
Cassandra	Cedrick Lunven
OpenAPI	Christophe Bornet

Retired members of the board of developers Permalink to "Retired members of the board of developers"

Where does the development team work? Permalink to "Where does the development team work?"

We do most of our work on the project’s GitHub page.

Internal team discussions happen in the following channels:

• The jhipster-dev mailing list
• The jhipster-dev-team Gitter chat

Those discussion channels are publicly viewable, as everything we do in JHipster is public, but only the board of developers can participate. The mailing list archives can be found on the Google groups page and the chat archives are available on Gitter.

How to join the board of developers? Permalink to "How to join the board of developers?"

• Participate regularly in the project (commits, PRs, etc)
• Ask someone from the current board, with some bio and background information, and that person will submit a vote on the dev mailing list
• Everybody on the dev mailing list can vote (+1 if they agree, -1 if they don’t)
  • One “-1” vote will decline adding the new member, but the person who votes “-1” will need to explain why

What do people in the board of developers gain? Permalink to "What do people in the board of developers gain?"

• Write access to the main repository, and to most of the projects under the JHipster organization.
• Costs associated with the project (for example travel costs to come to a JHipster conference) can be paid by our OpenCollective account. This depends on the money available on the account, and this is decided and validated by the project leads.
• Free licenses and free quotas that the project regularly gets from friendly companies.

Who are the “retired members of the board of developers”? Permalink to "Who are the “retired members of the board of developers”?"

JHipster is an Open Source project, we don’t ask anything from our members: they can leave the project or stop contributing at any time. But as members of the board have more rights than other people (including write access to the project), we need them to be active.

Board members will therefore become “retired” if:

• They tell us they want to leave the project
• They don’t contribute to the project for 2 years

Contributions are across the entire jhipter and hipster-labs organizations, and include:

• Commits
• Comments on issues/PR, responses to mailing list questions, activity on social media (Twitter, Gitter, Stack Overflow, Reddit, etc) related to JHipster
• Project maintenance (triage, PR reviews & merge, cleanup of issues, releases, project planning)
• CI/CD
• Marketing & advocacy (Promoting a JHipster project on social media, conference talks, blogs, books, trainings, etc)

Every year the team leads make a list of “inactive members” and send an official email to ask them if they want to retire. Then 3 cases can happen:

1. The contributor agrees to retire.
2. The contributor wants to stay in the team and tries to participate in any capacity possible. If the same person comes up in the inactive list twice in a row (inactive for 2 years) then that person is retired.
3. The contributor doesn’t reply for 5 weeks, then this person is retired.

“Retired” member can become active members again, if they contribute back to the project and get elected again. They will have an advantage over other contributors, as they already know the team.