You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hiccups that prompted #377 have also made it apparent that we don't have a good way of communicating organizational/scheduling issues. To change this, I'd like to introduce a Google group (https://groups.google.com/g/dask-maintainers) that we can use to communicate on organizational issues. The main benefits are:
It's email, so that information will disseminate faster than via GitHub issues and everyone uses it.
Everybody who's interested can sign up, so we have a way to reach all possible attendees.
We can add the Google group to the Calendar event, so everybody who signs up automatically gets sent an invite, no more hassle with subscribing to the calendar and synchronizing it with your own calendar.
The text was updated successfully, but these errors were encountered:
On Thu, May 2, 2024 at 10:30 AM Hendrik Makait ***@***.***> wrote:
The hiccups that prompted #377
<#377> have also made it apparent
that we don't have a *good* way of communicating
organizational/scheduling issues. To change this, I'd like to introduce a
Google group (https://groups.google.com/g/dask-maintainers) that we can
use to communicate on organizational issues. The main benefits are:
- It's email, so that information will disseminate faster than via
GitHub issues and everyone uses it.
- Everybody who's interested can sign up, so we have a way to reach
*all* possible attendees.
- We can add the Google group to the Calendar event, so everybody who
signs up automatically gets sent an invite, no more hassle with subscribing
to the calendar and synchronizing it with your own calendar.
—
Reply to this email directly, view it on GitHub
<#378>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTCHASU4ZODGJUZD2V3ZAJLZRAVCNFSM6AAAAABHD6KJ7SVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3TKOBSHA3TCNI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
(details reconstructed in an offline conversation)
Yes, that would be great! If [email protected] creates any problems with the governance (the sync is open to everyone after all), something like [email protected] would be a good alternative. I'm probably overthinking it though.
The hiccups that prompted #377 have also made it apparent that we don't have a good way of communicating organizational/scheduling issues. To change this, I'd like to introduce a Google group (https://groups.google.com/g/dask-maintainers) that we can use to communicate on organizational issues. The main benefits are:
The text was updated successfully, but these errors were encountered: