Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[rest-dev] Nomination for Extra Project Lead: James R. Perkins

Fellow Committers,

triggered by a problematic situation in another former Java EE project, where the project lead felt sick for more than one year, I would like to propose that we install a backup for that role in our spec project. Not being dependend of a single point of failure helps to prevent getting stuck in similar situations. As engineers we pretty good know that it is always good to have redundancy, "just in case". Also, while I do appreciate Santiago doing a great job in the past years, he was never officially elected (as per the Eclipse Foundation's rules), so it might make sense, to strengthen our project's formal organization by having elections for project leadership.

Therefore, I like to propose the nomimation of James R. Perkins (IBM) as an ADDITIONAL project lead besides Santago, and to explicitly "confirm for formal reasons" Santiago as our CONTINUED project lead. For both movements I like to reach consensus on this mailing list, as it makes no sense to perform official elections if somebody would veto it anyways. So I am kindly asking ALL COMMITTERS of this project to briefly comment on this movement within the next days. If I do not receive any veto or otherwise good reason for holding me back, I will then file the nominations on the EF's official voting platform. Thank you!

To make clear: The role of "Project Lead" is just a MANAGEMENT position between the EMO (the EF's formal organization) and our own project. Its main duty is to do all the paperwork needed for releases, committer elections, etc. He is in particular responsible that our project follows the EF's rules. A project lead is NOT an owner of the code or the project, NOR has any other powers, veto rights, etc. inside the project itself, compared to any other committer. Also, a project lead is NOT a marketing or dev rel position. Just in case you did not know already.

For those who did not work with them so far:

James did a great management job in the current and recent releases sorting out all the issues and branches, and my personal view is that without him, we possibly wouldn't have had the last, or wouldn't have the next release, at least not within the official time frames. I am grateful for his dedication and esprit, and it was a pleasure to work with him before and behind the scenes. James, please confirm that you would accept a nomination for project leadership.

After I managed the first few JAX-RS minor releases on my own, it was Santiago who took over release management for many years, and he did (and does) a great job. I know what a lot of work that was, and he was the rock we built upon. Thank you for taking all that time! I would be glad, if you would confirm that you "formally accept" this re-nomination to finally get elected as our project lead.

To make it absolutely clear: Both nominations are NOT exclusive/alternative choices. My proposal is that we elect BOTH as project leads. This is DEFINITIVELY NOT an attempt to "unelect" Santiago!

Requesting Comments! :-)

Regards

-Markus



Back to the top