The list excludes folks who have been active on Ozone for over 1 year with significant design contributions and patch counts in the high double digits. They'd merit being on the project PMC by any objective basis so it was likely an unintentional oversight.
There are a couple of options: 1. Include long-time contributors in the initial list. I've made a few edits to the list in the proposal. Please make further edits if I missed anyone. 2. Restrict the initial PMC to Hadoop PMC members, and once the TLP is formed let's elect the folks left out at the start with priority. At least that avoids the obvious perception of unfairness. My vote is for #1, let's not be another Hadoop. Thanks, Arpit On 8/26/20, 4:05 AM, "Elek, Marton" <[email protected]> wrote: Hi all, Ozone TLP proposal is updated with the proposed project membership list. The initial list is based on pure statistical data from Jira (HDDS and HDFS-7240 sub issues, hadoop-ozone/hadoop/hadoop-docker-ozone git contributions) all active Hadoop PMC members/committers/contributors are added to the list. As earlier discussed, it’s important to acknowledge non-code contributions. Therefore, I asked everybody on the initial list (which is based contributions) to suggest more people, to make sure, everybody is included who can help us to make Ozone successful. Thanks to the feedback additional people to make Ozone even stronger: Matt and Clay are regular members of the community meetings and design discussion, they helped a lot with design decisions and helping to choose the right direction based on their existing expertise. Uma and Rakesh already started to contribute to Ozone, and their expertise and enthusiasm already proven as Hadoop PMC members. They are suggested more members to include as they can help significant Ozone to be successful. Junping helped a lot with designs feedback and to get the first enterprise adoption of Ozone for production. Sammi was so kind to accept the nomination to be the initial Chair of the project from the side of an “adopter/user” company. (Hadoop bylaw suggest rotating this role, if we keep the same bylaw we can rotate it later between different community members). The initial version of this list (With existing Apache id, Apache membership and Hadoop project membership information) can be found on the proposal page: https://cwiki.apache.org/confluence/display/HADOOP/Ozone+Hadoop+subproject+to+Apache+TLP+proposal As any other list it’s not perfect. It can be extended, but in this phase it’s harder to get a full consensus (no Ozone specific private list or place for private conversation). I hope we can add more people after creating the new Ozone project. (NOTE: as usual, the proposed members can reject this opportunity, we need to ping everybody on the list) IMPORTANT1: if you have any more suggestions, opinion please share it. (if you prefer to do so, you can do it in private, you can send it to me or any proposed PMC members, and the information will be shared between the proposed PMC members). IMPORTANT2: Based on the previous example of Submarine, and the request of the Hadoop community any Hadoop committers can request opt-in committer role and can have automatic membership (except somebody from the initial PMC list has a strong veto). Thanks, Marton --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
