...

NOTE: Please do not make any edits to this cwiki page as the vote is concluded. (Except typo/grammar/clarifications)

Abstract

Apache Hadoop Ozone provides storage for Hadoop-based and Cloud-native environments.

...

• Ozone is a new (sub) project and it's a top priority to make it more inclusive and contributor friendly.
• (moved) Ozone Community Calls are weekly calls between Ozone developers and users. This is the same call where the active developers sync with each other and open for anybody.
• The meeting minutes are posted either to the mailing list (or added to the wiki and references to the mailing list). To have an open and async conversation about all the related topics.
• Recently a new survey is initialized to make this call more inclusive. (The current time of this call is not China friendly, and we tried to identify the best way to include all the contributors from all the timezones)
• Based on the feedback we started to record the meetings and an additional APAC friendly sync is initiated.
• The pull request queue is monitored frequently and it's the number one priority to keep the number of open pull requests low. All the pull requests are looked into within a reasonable time.
• The only possible way to close/abandon a Pull request is when the author is not responsive. Pull requests are not closed due to inactivity if a committer action is required.
  
  
• The documentation and the developer process tries to make the development process easy and developer-friendly. A "newbie" label is added to issues in Jira that can be taken up by first-time contributors.
• The community contributions are monitored. And new contributors are proposed based on pure merits.
• Ozone is a distributed storage project and as is, the initial contribution can be hard. To make it easier to understand the main architecture decisions a new video series has been started for developers and/or users.

• To make it easier to understand the earlier decisions, the design docs are added to the documentation page (from the next release https://github.com/apache/hadoop-ozone/tree/master/hadoop-hdds/docs/content/design). Ozone doesn't require a very formal proposal process (like Flink or Kafka), yet, but it's a continuous effort to make all the design discussions open and transparent.

...

1. PMC: As Ozone is a Hadoop subproject today, all the existing Hadoop PMCs with noticeable Ozone contributions are added to the initial list. (Definition of noticeable contribution: all the related GitHub / Jira content is downloaded, and we selected all the Hadoop PMCs with at least 30 comments AND/OR commits since the beginning of 2019.
2. A discussion is started with these people about 1)
   1. what are the important factors of being a committer / PMC.
   2)
   2. Who should be added to the initial list?
3. Committer: similar to submarine Hadoop committers can get opt-in committer membership to the Ozone project (except PMC veto)

...

It's also found especially important to include the user community to the project governance. End-users and adopters – who are actively helping with the projects with feedback during the design discussions – should be invited to the PMC (even without code contribution). (During the discussion they are called as "user-seats" in PMC)

The initial selection rules and PMC list is shared on the ozone-dev mailing list (people who are nominated in 2b are added explanatio) where additional methods are suggested (add everybody to the PMC who are Hadoop PMC and contributed at least 10 patches in this year) and accepted.

Proposed Chair:

1. Sammi Chen [sammichen] (Hadoop PMC)

...

1. Arpit Agarwal [arp] (member, Hadoop PMC)
2. Shashikant Banerjee [shashikant] (Hadoop PMC)
3. Li Cheng [licheng] (Hadoop committer)
4. Dinesh Chitlangia [dineshc] (Hadoop committer)
5. Clay Baenziger
6. Attila Doroszlai [adoroszlai] (Hadoop committer)
7. Junping Du [junping_du] (member, Hadoop PMC)
8. Márton Elek [elek] (Hadoop PMC)
9. Anu Engineer [aengineer] (Hadoop PMC)
10. Uma Maheswara Rao G [umamahesh] (member, Hadoop PMC)
11. Lokesh Jain [ljain] (Hadoop PMC)
12. Hanisha Koneru [hanishakoneru] (Hadoop PMC)
13. Yiqun Lin [yqlin] (Hadoop PMC)
14. Siyao Meng [siyao] (Hadoop committer)
15. Jitendra Nath Pandey [jitendra] (member, Hadoop PMC)
16. Rakesh Radhakrishnan [rakeshr] (member, Hadoop PMC)
17. Matt Sharp
18. Mukul Kumar Singh [msingh] (Hadoop PMC)
19. Tsz-wo Wo Nicholas Sze [szetszwo] (member, Hadoop PMC)
20. Xiaoyu Yao [xyao] (Hadoop PMC)
21. Nandakumar Vadivelu [nanda] (Hadoop PMC)
22. Bharat Viswanadham [bharat] (Hadoop PMC)

Proposed committer list

1. István Fajth
2. Siyao Meng [siyaoSiddharth Wagle [swagle] (Hadoop committer)
3. Nilotpal Nandi [nilotpalnandiStephen O'Donnell [sodonnell] (Hadoop committer)
4. Stephen O'Donnell [sodonnellVivek Ratnavel Subramanian [vivekratnavel] (Hadoop committer)
5. Yisheng Lien Aravindan Vijayan [yishengavijayan] (Hadoop committer)

Proposed committer list

1. Wei-Chiu Chuang [weichiuVivek Ratnavel Subramanian [vivekratnavel] (Hadoop committerPMC)
   
2. István Fajth
3. Nilotpal Nandi [nilotpalnandiAravindan Vijayan [avijayan] (Hadoop committer)
4. Siddharth Wagle Yisheng Lien [swagleyisheng] (Hadoop committer)
5. Baoloong Mao (github.com/maobaolong)
6. Neo Yang (github.com/cku328)
7. WeiWei Yang (wwei) (Hadoop committer)
8.  Jie Wang [runzhiwang]
   
9. Xiang Zhang (github.com/iamabug)
10. Micah Zhao (github.com/captainzmc)
11. Masatake Iwasaki [iwasakims] (Hadoop committer)
12. Prabhu Joseph [prabhujoseph] (Hadoop committer)
13. Ayush Saxena [ayushsaxena] (Hadoop PMC)
14. He Xiaoqiao [hexiaoqiao] (Hadoop committer)
15. Surendra Singh Lilhore [surendralilhore] (Hadoop PMC)
16. Vinayakumar B [vinayakumarb] (Hadoop PMC)
17. Bibin A Chundatt [bibinchundatt] (Hadoop PMC)
18. Hemanth Boyina [hemanthboyina] (Hadoop Committer)
    
19. Hui Fei
20. Lisheng Sun

Affiliations

Induviduals of the initial PMC are employed by Cloudera, Tencent, Bloomberg, Ebay, Target, SirionLabs. Cloudera and Tencent are known for employing  significant number of full-time Ozone developers.

The committer list also contains induvidals employed by Microsoft, Huawei and others (including induvidal contributors.)

Required Resources

• Mailing lists: ozone-dev mailing list already exists it can be moved to a separated TLP domain
• Source code: Source code is already separated from the main Hadoop repository (apache/hadoop-ozone and apache/hadoop-docker-ozone). It can be moved easily to separated project
• Issue tracker: Ozone already uses separated Jira subproject (HDDS)
• Github repositories
  • Rename apache/hadoop-ozone to apache/ozone
  • Rename/move apache/hadoop-docker-ozone to apache/ozone-docker-release