-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Name of this repo #1
Comments
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: [email protected]
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.
|
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. |
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:
|
cc @zarr-developers/core-devs |
I like that idea, gives a clean split between the two repos |
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. |
Called it
governance
for no particular reason. Another option might bezarr-governance
. There could be other reasonable names I've ignored. Please feel free to suggest.The text was updated successfully, but these errors were encountered: