Versions Compared

Old Version 2

changes.mady.by.user Unknown User (elek)

Saved on

compared with

New Version 3

changes.mady.by.user Unknown User (elek)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Fortunately more and more new contributors are helping Ozone. Originally the Ozone community was a subset of HDFS project. But now a bigger and bigger part of the community is related to Ozone only.
  • It seems to be easier to build the community as a separated project
  • A new, younger project might have different practices (communication, committer criteria, development style) compared to old, mature project
  • It's easier to communicate (and improve) these standards in a separated project with clean boundaries
  • Separated project/brand can help to increase the adoption rate and attract more individual contributor (AFAIK it has been seen in Submarine after a similar move)
  • Contribution process can be communicated more easily, we can make first time contribution more easy
  • Apache Board is monitoring community activities. As the volume of Ozone contributions are slightly more than the 50% of all the Hadoop contributions, it seems to be reasonable to follow community development and activity on Ozone level (toay it's hart to differentiate between the Ozone part and core Hadoop part)

 From CODE point of view Ozone became more and more independent:

...

  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 comment AND/OR commits since the beginning of 2019.
  2. A discussion is started with these people about 1) what are the important factors of being a committer / pmc. 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)

Some points which named as important factor of being PMC:

...

It's also found especially important to include the user community to the project governance. End-users and adopter – 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 called as "user-seats" in PMC)

Initial PMC

TBD

members / Hadoop PMCs

Initial Committers

...

PMC)

Proposed Chair:

  1. Sammi Chen [sammichen] (Hadoop PMC)

Proposed PMC (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 Conduit
  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. Jitendra Nath Pandey [jitendra] (member, Hadoop PMC)
  15. Rakesh Radhakrishnan [rakeshr] (member, Hadoop PMC)
  16. Matt Sharp
  17. Mukul Kumar Singh [msingh] (Hadoop PMC)
  18. Tsz-wo Sze [szetszwo] (member, Hadoop PMC)
  19. Xiaoyu Yao [xyao] (Hadoop PMC)
  20. Nandakumar Vadivelu [nanda] (Hadoop PMC)
  21. Bharat Viswanadham [bharat] (Hadoop PMC)

Proposed committer list

  1. István Fajth
  2. Siyao Meng [siyao] (Hadoop committer)
  3. Nilotpal Nandi [nilotpalnandi] (Hadoop committer)
  4. Stephen O'Donnell [sodonnell] (Hadoop committer)
  5. Yisheng Lien [yisheng] (Hadoop comitter)
  6. Vivek Ratnavel Subramanian [vivekratnavel] (Hadoop committer)
  7. Aravindan Vijayan [avijayan] (Hadoop committer)
  8. Siddharth Wagle [swagle] (Hadoop comitter)
  9. Neo Yang (github.com/cku328)
  10.  Runzhi Wang (github.com/runzhiwang)
  11. Xiang Zhang (github.com/iamabug)
  12. Micah Zhao (github.com/captainzmc)

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 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