follow-up issues in `zarr-python`

[MSanKeys963]

Linking this from #54. Conversations on some issues have gone stale. Here are issues in zarr-python that need follow-up from the author, and then we can decide the best action to take:

• https://github.com/zarr-developers/zarr-python/issues/1035
• https://github.com/zarr-developers/zarr-python/issues/991
• https://github.com/zarr-developers/zarr-python/issues/1029
• https://github.com/zarr-developers/zarr-python/issues/1017
• https://github.com/zarr-developers/zarr-python/issues/1104
• https://github.com/zarr-developers/zarr-python/issues/962
• https://github.com/zarr-developers/zarr-python/issues/904
• https://github.com/zarr-developers/zarr-python/issues/868
• https://github.com/zarr-developers/zarr-python/issues/864
• https://github.com/zarr-developers/zarr-python/issues/784
• https://github.com/zarr-developers/zarr-python/issues/777
• https://github.com/zarr-developers/zarr-python/issues/776
• https://github.com/zarr-developers/zarr-python/issues/809

If you think this is in the right category, feel free to follow up on the issue. Thanks!

[joshmoore]

• to-be-reproduced / needs-unit-test (new label)

  • https://github.com/zarr-developers/zarr-python/issues/1035
  • 809

• yes, just check in

  • 991
  • 1029
  • 868 (possibly reproduce)
  • 864
  • 777

• maybe close (these are trickier)

  • 1017 (docs, help?)
  • 962 (after asking for comments?) possibly a documentation issue
  • 784 (synchronization is often a tricky one)

• help wanted / good first

  • 904

• needs a review or first comment

  • 776 (suggest a PR?)

[joshmoore]

Updated my comment for all the issues listed here, @MSanKeys963.