Name of this repo

[jakirkham]

Called it governance for no particular reason. Another option might be zarr-governance. There could be other reasonable names I've ignored. Please feel free to suggest.

[alimanfoo]

Personally I'm fine with just "governance", seems to be what other projects are doing.

…

On Thu, 14 Feb 2019 at 20:45, jakirkham ***@***.***> wrote: Called it governance for no particular reason. Another option might be zarr-governance. There could be other reasonable names I've ignored. Please feel free to suggest. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAq8QsZpx_j8ZLU4LHggWGrk6iZ0cHQxks5vNcrzgaJpZM4a8aG7> .

-- Alistair Miles Head of Epidemiological Informatics Centre for Genomics and Global Health Big Data Institute Li Ka Shing Centre for Health Information and Discovery University of Oxford Old Road Campus Headington Oxford OX3 7LF United Kingdom Phone: +44 (0)1865 743596 or +44 (0)7866 541624 Email: alimanfoo@googlemail.com Web: http://a <http://purl.org/net/aliman>limanfoo.github.io/ Twitter: @alimanfoo <https://twitter.com/alimanfoo> Please feel free to resend your email and/or contact me by other means if you need an urgent reply.

[jakirkham]

Yeah it's just difficult when forking as other things use similar names making it harder to track what a repo came from. Though no strong feelings about this as it is easy to fix on user's end by renaming the fork. Just might be easier not to need to rename forks at all.

[alimanfoo]

Thinking about this again, I think it might be nice to rename this repo to "community" or "zarr-community". We would keep the idea that governance docs go here, but also other content related to community and outreach could live here too, i.e., it would be a focus for community activity and coordination. E.g., submissions to conferences, slide decks. Also e.g., the issue relating to the regular telecon could live here rather than in the "zarr" repo which currently holds the Python implementation.

Any objections to any of the following:

• Renaming this repo to "zarr-community".
• Migrating the following issues here:
  • https://github.com/zarr-developers/zarr/issues/315
  • https://github.com/zarr-developers/zarr/issues/291
  • https://github.com/zarr-developers/zarr/issues/316
  • https://github.com/zarr-developers/zarr/issues/284
  • https://github.com/zarr-developers/zarr/issues/334
  • https://github.com/zarr-developers/zarr/issues/333
  • https://github.com/zarr-developers/zarr/issues/320
  • https://github.com/zarr-developers/zarr/issues/300
  • https://github.com/zarr-developers/zarr/issues/289
  • https://github.com/zarr-developers/zarr/issues/286
  • https://github.com/zarr-developers/zarr/issues/285
  • https://github.com/zarr-developers/zarr/issues/279
• Migrating the scipy 2019 abstract here (currently at https://github.com/zarr-developers/zarr/blob/master/docs/talks/scipy2019/submission.rst).
• Using this repo for a PR with a slide deck for the scipy 2019 talk.

[alimanfoo]

cc @zarr-developers/core-devs

[mzjp2]

I like that idea, gives a clean split between the two repos

[jakirkham]

Personally I’d prefer to separate these. Namely a governance repo with just governance docs and CoC. A repo with outreach material slides, logos, etc.