|
| 1 | +--- |
| 2 | +layout: single |
| 3 | +author_profile: false |
| 4 | +title: Zarr Community |
| 5 | +permalink: /community/ |
| 6 | +sidebar: |
| 7 | + title: "Content" |
| 8 | + nav: sidebar |
| 9 | +--- |
| 10 | + |
| 11 | +Zarr is a community-driven open-source data format specification developed and maintained by diverse [contributors](https://github.com/orgs/zarr-developers/teams). The Zarr contributors aim to maintain an open, equal, diverse, and inclusive community. Please read the [Zarr Code of Conduct](https://github.com/zarr-developers/.github/blob/main/CODE_OF_CONDUCT.md) for the appropriate way to interact with the community and help each other. |
| 12 | + |
| 13 | +The Zarr community meets two times every two weeks via [community](https://zarr.dev/community-calls) and [ZEP meetings](https://zarr.dev/zeps/meetings/). Please have a look at our [community calendar](https://zarr.dev/community-calls/) for exact timings. |
| 14 | + |
| 15 | +Feel free to explore the various communication channels mentioned below. |
| 16 | + |
| 17 | +## Community meetings |
| 18 | + |
| 19 | +Zarr community meeting notes, joining instructions, agenda and calendar are available at: [https://zarr.dev/community-calls](https://zarr.dev/community-calls) |
| 20 | + |
| 21 | +## ZEPs |
| 22 | + |
| 23 | +ZEP stands for Zarr Enhancement Proposal. A ZEP is a design document providing information to the Zarr community, describing a modification or enhancement of the [Zarr specifications](https://zarr-specs.readthedocs.io/en/latest/), a new feature for its processes or environment. |
| 24 | + |
| 25 | +More info on ZEPs is available at: [https://zarr.dev/zeps/](https://zarr.dev/zeps/) |
| 26 | + |
| 27 | +We hold bi-weekly ZEPs meetings to propose, discuss, review and finalize discussions around [current ZEPs](https://zarr.dev/zeps/draft_zeps/) and [Zarr Specification](https://zarr-specs.readthedocs.io/en/latest/specs.html). More info available here: [https://zarr.dev/zeps/meetings/](https://zarr.dev/zeps/meetings/) |
| 28 | + |
| 29 | +> Please note ZEPs meetings are different from bi-weekly community meetings. The Zarr Community meets two times every two weeks. Please have a look at our [community calendar](https://zarr.dev/community-calls/) for exact timings. |
| 30 | +
|
| 31 | +## Blog |
| 32 | + |
| 33 | +Check out the Zarr blog [here](https://zarr.dev/blog). |
| 34 | + |
| 35 | +> The GitHub repository for the blog is [here](https://github.com/zarr-developers/blog). In addition, we’re always looking for guest blog posts. For more info, please read [this](https://github.com/zarr-developers/blog#contribute-to-zarr-blog). |
| 36 | +
|
| 37 | +## Join the community |
| 38 | + |
| 39 | +Most discussions and chats related to Zarr and its [implementations](https://github.com/zarr-developers/zarr_implementations) take place on Gitter and GitHub. If you are looking to: |
| 40 | + |
| 41 | +- Interact with the maintainers, contributors and users of the project; join the Gitter → [here](https://gitter.im/zarr-developers/community) |
| 42 | +- Want to ask questions related to [`zarr-python`](https://github.com/zarr-developers/zarr-python) usage, create a new discussion on GitHub → [here](https://github.com/zarr-developers/zarr-python/discussions) |
| 43 | +- Contribute and engage in discussion related to Zarr Specification; check out the `zarr-specs` [repo](https://github.com/zarr-developers/zarr-specs/) or create an issue → [here](https://github.com/zarr-developers/zarr-specs/issues) |
| 44 | + |
| 45 | +Also, find us on: |
| 46 | + |
| 47 | +- [Twitter](https://twitter.com/zarr_dev) |
| 48 | +- [GitHub](https://github.com/zarr-developers) |
| 49 | +- [YouTube](https://www.youtube.com/@zarr_dev/playlists) |
0 commit comments