DOC: Add Zulip announcement banner and mention in docs#11246
DOC: Add Zulip announcement banner and mention in docs#11246VeckoTheGecko wants to merge 3 commits intopydata:mainfrom
Conversation
And mention in contributing and core team guide
I also really want to get xarray-contrib/xarray.dev#821 out. and ideally have it be the top blog post so it gets a little love. so lets maybe do blgo fast and releaes it then that one on top? Altohugh beyond a blog post we can do whatever on xarray.dev. it could just be link on the homeapge |
doc/contribute/contributing.rst
Outdated
| The recommended place to ask a question is on `GitHub Discussions <https://github.com/pydata/xarray/discussions>`_ | ||
| , but we also have a `Discord <https://discord.com/invite/wEKPCt4PDu>`_ and a | ||
| The recommended places to ask questions are `GitHub Discussions <https://github.com/pydata/xarray/discussions>`_ | ||
| or the Xarray channel in the `OSSci Zulip <https://ossci.zulipchat.com/>`_. We also have a `Discord <https://discord.com/invite/wEKPCt4PDu>`_ and a |
There was a problem hiding this comment.
whats teh deal with the discord these days? If we can avoid splitting communication channels it would be great.
Similar thought on how we are directing to github disucssions (whihc are good things!) would be nice to clarify what is for what. although to be clear as is this is good
There was a problem hiding this comment.
I was just about to post an issue about it to be discussed separately/didn't want it to get in the way of this PR. I think core devs might have opinions about the mailing list and Discord (which are both quite dead).
From my POV
- promote Discussions and Zulip
- link to mailing list/discord in a "in the past we've communicated via mailing list and discord" - in case people want to look up prior coms
Co-authored-by: Ian Hunt-Isaak <ianhuntisaak@gmail.com>
We could also just have an announcement banner on the main website? |
And mention in contributing and core team guide
cc @ianhi
Should I whip up a blog post for xarray.dev?
Screenshot: