-
Notifications
You must be signed in to change notification settings - Fork 33
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
Jan 2024 - Jupyter Community Call #705
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
We don't have a weekly time slot, are you thinking of a different team? Regardless, if you edit your message to include the date/time that'll make it clear to everyone, and please feel free to re-advertise it every month. It's always handy to have a reminder! |
Hey @manics, thanks for the quick reply! This issue was actually to see if the JupyterHub folks would mind if we use your time slot for a Community Call. Last month we used the JupyterLab time slot, and the idea is that having a rotating time slot that's already blocked off in peoples' calendars might make it easier for some people to join / to have different areas of the project more represented. We totally understand if that'd be hard for you to swing because JupyterHub has less frequent meetings though! Just wanted to gauge interest. |
Our January meeting already happened on Tuesday, so we don't meet again until February now. Is that too far away? |
FYI, here is the info for our next meeting #707 |
Hello! My name's Mason and I will be hosting this month's Jupyter Community Call, with help from @marthacryan.
I was wondering if you all would be willing to open up your weekly meeting time slot in the last week of January for the January Jupyter Community Call.
It will be an hour-long call where community members will have a chance to showcase what they are working on/have built.
The text was updated successfully, but these errors were encountered: