# ZEP1 Public Statement

On the topic of ZEPs (and before the **[community call](https://zarr.dev/community-calls/)** in a few hours), some news regarding [ZEP0001](https://zarr.dev/zeps/draft/ZEP0001.html), since there's been some understandable concern about its progress:

- Due to time constraints, @alimanfoo has stepped down as lead author for ZEP0001. He can say more himself, but I can't imagine it was an easy choice. For my part and probably most Zarristas, huge thanks to Alistair for all he's done to make Zarr what it is! :bouquet:
- Before stepping down, Alistair drafted a response for the feedback on [PR149](https://github.com/zarr-developers/zarr-specs/pull/149). The response document can be viewed [here](https://hackmd.io/@alimanfoo/SJ1DNVRxo).
- @jstriebel will take over as the principal author of ZEP1. He has agreed to spearhead the ZEP0001 and resolve all pending comments on the PR along with the help of the document mentioned above. He's been tracking work on a GH [project board](https://github.com/orgs/zarr-developers/projects/2) that should be visible within the org.
- Moving forward (as discussed during the last [ZEP meeting](https://zarr.dev/zeps/meetings/2022-11-03.html) and summarized [on the PR](https://github.com/zarr-developers/zarr-specs/pull/149#issuecomment-1302440391)), we’ve decided to open separate issues for all the unresolved feedback on the ZEP0001 PR. The issues will be closed once there’s a PR submitted against it. Once all of the conversations are resolved on the ZEP0001 PR, we’d merge it, marking the completion of ZEP0001.

Happy to take feedback on the plan above, and very much looking forward to everyone's continued participation! :rocket: