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 just see how we work, our community rules are at the end of this page.

Project leads

Julien Dubois

Project lead

@juliendubois

Deepu K Sasidharan

Project co-lead

@deepu105

Pascal Grimaud

Project co-lead

@pascalgrimaud

Board of developers

Mathieu Abou-Aichi

Pierre Besson

@pibesson

Christophe Bornet

@cbornet_

Serano Colameo

@colameo

Christopher Dionisio

@chris_dns

Hippolyte Durix

@hdurix

Daniel Franco

@dandrfranco

Alexandre Gaspard-Cilia

@Screach_FR

Zsombor Gegesy

@gzsombor

Frederik Hahne

@atomfrede

Erik Kemperman

@erikkemperman

Sahbi Ktifa

@SahbiKtifa

Sendil Kumar N

@sendilkumarn

Joe Kutner

@codefinger

Vishal Mahajan

@vishal423

William Marques

@wylmarq

Gaël Marziou

@gmarziou

Aurélien Mino

@AurelienMino

Charlie Mordant

@Tcharl

Daniel Petisme

@danielpetisme

Matt Raible

@mraible

Jon Ruddell

@jonruddell

David Steiman

@theOnlyScrippi

Ray Tsang

@saturnism

Srinivasa Vasu

@srinivasavasu

Pm Verma

@pm_verma

Anthony Viard

@avdev4j

Panayiotis Vlissidis

@panvliss

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

Retired members of the board of developers

Flavien Cathala

@flaviencathala

Victor Da Silva

@VicAntune

Jérôme Mirc

@jeromemirc

Anders Steiner

@andidevv

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?

• 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)
  • Just one “-1” vote will reject the new member, but the person who votes “-1” will need to explain why

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”?

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 more than 1 year

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