...

1. Code. File a bug and submit a patch, or pick up any one of the unassigned Jiras.
   1. Newbie Ozone jiras - https://s.apache.org/OzoneNewbieJiras
   2. All open and unassigned Ozone jiras - https://s.apache.org/OzoneUnassignedJiras.
2. Documentation Improvements. You can submit improvements to either:
   1. Ozone website. Instructions are here: Modifying the Ozone Website
   2. Developer docs. These are markdown files checked into the Apache Hadoop Source tree. E.g. https://github.com/apache/hadoop/blob/trunk/hadoop-ozone/docs/content/GettingStarted.md
   3. This wiki page. Please contact us at ozone-dev@hadoop-.apache.org and we can provide you write access to the wiki.
3. Unit Tests (JUnit)
4. Acceptance Tests. The Ozone source code includes a set of docker-based acceptance tests. See this guide for running the available acceptance tests - Running Ozone Smoke Tests and Unit Tests.
5. or just file bugs. Bug reports pointing out broken functionality, docs, or suggestions for improvements are always welcome!

...

If you have any questions, please don't hesitate to contact ozone-dev@hadoop-.apache.org.

Additional information

• To follow the progress of Ozone development you can check the JIRA dashboard

• A detailed discussion of Ozone file system and design docs can be found here. 
• A detailed and work items for the security of  Hadoop Distributed Storage Layer is tracked in this JIRA

• The documentation is part of the source code, but you can check out directly from github: https://github.com/apache/hadoop/tree/trunk/hadoop-hdds/docs/content See the markdown files with Ozone prefix (Or you can generate a new site from the feature branch)

• Review blog posts and talks on Ozone (here)