团队

JHipster是由世界各地的一个团队开发的。我们有很多贡献者(这里的前100个列表),但是核心团队的成员在这里列出。

如果你想加入这个团队,或者只是看看我们是如何工作的,我们的社区规则就在这一页的末尾。

Project leads

Julien Dubois

Project lead

@juliendubois

Deepu K Sasidharan

Project co-lead

@deepu105

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

Pascal Grimaud

@pascalgrimaud

Frederik Hahne

@atomfrede

Erik Kemperman

@erikkemperman

Sahbi Ktifa

@SahbiKtifa

Sendil Kumar N

@sendilkumarn

Joe Kutner

@codefinger

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

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

Stream Leader
Angular William Marques
React Sendil Kumar N
VueJS Sahbi KTIFA
JHipster Registry Pierre Besson
JHipster Console Pierre Besson
JHipster core/JDL Mathieu Abou-Aichi
JHipster Kotlin Sendil Kumar N
JHipster IDE Serano Colameo
UAA David Steiman
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

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 :

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.