Skip to content

Vert.x 3 Official stack and component maintainers

Julien Viet edited this page Dec 12, 2018 · 48 revisions

Official stack

This is the set of components as documented on the vertx.io documentation page:

http://vertx.io/docs/

Most of the components in the official stack will be distributed in one or more of the Vert.x binary distributions.

The Vert.x committer team maintains the official stack and makes sure releases are done on time, bugs are fixed and the quality is maintained at a high level.

Vert.x committer team

The Vert.x committer team is the set of developers who have made a commitment to maintain one or more components of the official stack.

The Vert.x committer team is formed from developers of the Vert.x community. It is not controlled by any one company or organisation.

New Vert.x committers can be proposed by existing committers and must be voted in by a majority of existing Vert.x committers.

Official component maintainers

Each component in the Vert.x official stack must be maintained by a Vert.x committer. It is the responsibility of the committer to ensure releases are done on time, bugs are fixed and the quality of the component is maintained at a high level.

The maintainer should review and manage pull requests from the community, and ensure the Eclipse CLA has been signed by any contributor.

The maintainer should be familiar with, and follow the Vert.x development process: https://github.com/vert-x3/wiki/wiki/Development-Process

Components maintainers have push/pull rights to at least the component they are maintainers for.

If a Vert.x committer is not able to commit to maintaining a component they must pass on maintainership to another Vert.x committer.

If there is no Vert.x committer with the necessary skills to maintain a component, then the component should be droppped from the official stack.

The roadmap for the official stack is determined by the Vert.x committers so a component maintainer should not make any major new features or refactorings that diverge with the current roadmap without first discussing with the other committers.

Proposing new components for the official stack

If the community believes a new component should be included in the official stack, then this can be proposed to the committer team. A maintainer must also be proposed for the component. The maintainer can be an existing member of the committer team or a new committer can be proposed from the community. Any new committer must pledge to maintain the component as described previously.

It is the responsibility of the maintainer to ensure that code quality and documentation of the component is brought to a sufficiently high level to allow its inclusion in the stack.

Component maintainers are free to delegate work to other members of the Vert.x community but the fundamental responsibility is on the maintainer to ensure timeliness and quality of the component.

Vert.x project lead

Julien Viet

The project lead has the power to resolve disputes and determine direction if committers cannot come to a concensus on an approach to take.

Component maintainers

Core

  • Vert.x Core - Julien Viet

Web

  • Vert.x Web - Paulo Lopes

Data access

  • Mongo Client - Martijn Verburg, John Oliver
  • JDBC Client - Paulo Lopes
  • SQL Common - Paulo Lopes
  • Redis Client - Paulo Lopes
  • MySQL/PostgreSQL client - Jochen Mader
  • Consul client - Ruslan Sennov

Integration

  • SMTP Client - Alex Lehmann
  • JCA Adaptor - Stefano Maestri
  • Camel bridge - Claus Ibsen
  • AMQP bridge - Robbie Gemmell
  • Vert.x Proton - Robbie Gemmell
  • Vert.x RabbitMQ Client - Pavel Drankov, Guillaume Charhon

Auth

  • Vert.x Auth - Paulo Lopes

Rx / Reactive

  • Vert.x Rx - Julien Viet
  • Vert.x Sync - Julien Ponge
  • Reactive Streams - Julien Viet

Metrics

  • DropWizard Metrics - Julien Viet
  • Hawkular Metrics - Thomas Segismont

Testing

  • Vert.x Unit - Julien Viet
  • Vert.x Junit 5 - Julien Ponge

Clustering

  • Hazelcast Cluster Manager - Thomas Segismont
  • Zookeeper Cluster Manager - Stream Liu
  • Apache Ignite Cluster Manager - Andrey Gura
  • Infinispan Cluster Manager - Thomas Segismont

IOT

  • Vert.x MQTT - Paolo Patierno

Services

  • Service Factories - Clement Escoffier
  • Service Proxies - Clement Escoffier
  • Maven Service Factory - Clement Escoffier
  • HTTP Service Factory - Clement Escoffier
  • Microservices Toolbox - Clement Escoffier
  • gRPC - Julien Viet
  • gRPC Java Compiler - Paulo Lopes

Microservices

  • Service Discovery - Clement Escoffier
  • Circuit Breaker - Clement Escoffier

Cloud / Docker

  • Vert.x OpenShift Cartridge - Clement Escoffier
  • Vert.x Docker Images - Clement Escoffier

Codegen/docgen

  • CodeGen - Julien Viet
  • Docgen - Julien Viet
  • Codetrans - Julien Viet

Distributions

  • Vert.x Stack - Julien Viet

Web site

  • Website - Michel Kramer

Examples

  • Examples - Clement Escoffier

Language implementations

  • JavaScript - Paulo Lopes
  • Ruby - Julien Viet
  • Groovy - Julien Viet
  • Scala - Jochen Mader
  • Kotlin - Guido Pio Mariotti, Sergey Mashkov
  • Python - Jordan Halterman
  • Ceylon - Stephane Epardaud

Retired components

  • JGroups Cluster Manager

Retired contributors

  • Tim Fox (Founder & Emeritus)
  • Norman Maurer (Emeritus)
  • Pid ster
  • Nick Scavelli
  • James Strachan
  • Fabio Marinelli
  • Rajith Attapattu
  • Joern Bernhardt
Clone this wiki locally
You can’t perform that action at this time.