Many successful Eclipse projects have more than one project lead. Markus would be a great fit as an additional project lead for the Eclipse Project for JAX-RS. Everyone who followed the development of JAX-RS in the last months can confirm, that Markus would be a great choice. He bootstrapped the first discussions about how to work together on the project a few days after the mailing list has been provisioned and actively helped many committers to join the boat. Markus coordinated the provisioning of our Jenkins instance, prepared the build pipeline and did most of the work to perform the first releases, including one of the first EE4J releases ever published. He authored the Java SE Bootstrap API and its Jersey implementation, which is the first major new feature of the upcoming JAX-RS 2.2 release. Markus is very familiar with the EDP and is often the first one responding to new issues or questions on the mailing list. He helps us keeping a level playing field and has an eye on the EF’s rules. He also speaks on conferences for getting people attracted to EE4J. The Eclipse Foundation is a meritocracy. Therefore, I strongly believe that Markus deserves to become the second project lead for the JAX-RS project.
| Voter | Vote | Comments |
|---|---|---|
| Christian Kaltepoth | +1 | +1 implied by nomination |
| Sebastian Daschner | 0 | |
| Markus Karg | 0 | |
| Alessio Soldano | 0 | |
| Kevin Sutter | 0 | |
| Andy McCright | -1 | While he is a very skilled and talented developer, and has great passion and ideas for the JAX-RS project, I have found Markus to be confrontational and difficult to work with. I would prefer the project leadership to be more inclusive. That said, I very much appreciate Markus's technical contributions to the JAX-RS project. |