Hosting our weekly meeting #197
Comments
afshin
added
question
|
I'm interested in co-hosting a weekly call, perhaps in a rotation. (I have access to the shared Zoom and Gmail accounts, and I've hosted calls before.) |
|
Here's JupyterLab weekly call hosting guide draft: https://docs.google.com/document/d/18-9HQVu9MvL1l98B37VX-UMF6cEb-GW-5KqbEb-8SBs/edit?usp=sharing. Comments and feedback are welcomed. When done, the guide can be published as a new issue. One issue we need to align on is how to provide access to Project Jupyter Zoom account for hosts. Based on discussion with @blink1073 last week, there is no apparent way to safely provide access to credentials to everyone/anyone but it's possible to do it for a defined group of people. I think it makes sense to restrict this group to JupyterLab council members and consider co-hosting for everyone else. |
|
And I'm also interested in (co-)hosting a weekly call. |
|
I can help with hosting, for now as a fallback and then on schedule from Q3. |
|
Cross-referencing jupyter/governance#169 |
|
I held back from a long time volunteering to host because I wanted to allow space for other people to step forward. But the call for new hosts has been out for a long time now, and it seems there is a real need for more hosts, so please feel free to add me as a volunteer host! :) |
|
You should be able to log into Zoom now:
|
|
I updated the top-level comment of this issue and will pin it on the issues page. It has a list of upcoming meetings and I have made myself the backup host for all of them so that they are not left un-hosted but once a volunteer steps up, I may remove myself to allow someone else to be the backup. CC: @JasonWeill @andrii-i @krassowski @gabalafou @jupyterlab/jupyterlab-council |
afshin
changed the title
|
I can host on June 28; updated the top comment. |
|
You can put me down for the following two dates:
Unfortunately, my office situation makes it difficult for me to host in July. |
afshin
removed
the
seeking consensus
|
I can host on July 19, updated the top comment accordingly |
|
Added @tonyfast as host for July 5, by his request on the call today |
|
do i need credentials to host the meeting? |
|
The creds are in the 1Password; if you don't have 1Password access, someone who does have access might be able to log in and pass you the host privilege |
|
I signed up to host next week, July 26. |
|
Signed up for 2023 08 16 |
|
Signed up for 2023 09 13 |
|
Signed up to host on 2023-08-30. |
|
Hi folks, I'm signed up to host tomorrow and two weeks after, but I think I need to back out. I recently relocated to Athens, and I'm discovering that connectivity is a bit trickier here. I have discovered that my apartment's Internet connection is not reliably fast enough; after working from home for a week, I have frequently experienced choppiness and lag in my Zoom and Google Meet calls. I recently joined a co-working space, but it closes at 7 PM Athens time, which is when the JupyterLab team call starts. I really don't want to host the call unless I have a top notch connection in a quiet space, and it's taking too much effort for me to find that in Athens, given the combination of factors that need to align. |
|
Removed @gabalafou from the table for tomorrow and two weeks after. |
|
Thanks, @andrii-i. Are we sure we have someone to host tomorrow's call? |
|
I can host tomorrow, August 9. |
|
I signed up to host on September 20 |
|
Signed up to host on September 27 |
|
Added October-December 2023 to the Upcoming Calls table, moved July and August entries to "Past calls" section |
|
Signed up to host on 10/18 |
|
I can host on Oct. 11 |
|
Signed up to host on 11/08 and 12/06. Might be unavailable on 12/27. |
|
I won't be able to host a meeting today. cc @afshin. |
|
Signed up for 12/13 Note that due to holidays, |
|
If you are available today, 22 November, and want to come, we will have a call. |
|
Signed up to host on 1/10 |
|
Removed @afshin as a back-up host for January as asked and discussed. If there are no volunteers for hosting the meeting, meeting participants should self-host. |
|
Folks, I'm so sorry for dropping the ball today. When I signed up for this meeting last week, I had plenty of buffer time on my calendar around the meeting, but then my calendar got filled, and I was in back-to-back meetings from the moment I started my work day until the JupyterLab team call, and I ended up being late. Lesson learned: block out 15-30 minutes on my calendar before the call if I'm hosting. Also, I searched all of my emails for the Project Jupyter Zoom login, but I couldn't find the invite. I searched "Project Jupyter Zoom", emails from Zoom, "1password", I searched my spam folder, nothing. @afshin could you re-send me the invite? (or whoever has access) I'll volunteer to host next week's meeting to make up for this one. Again, I'm so sorry 🤦♂️ |
|
@gabalafou No worries, we self-hosted. I think we as a group should be flexible enough to self-host anytime, today was a good opportunity to try. |
Original issue
I have been hosting our weekly calls – with some helpful substitutions – for a long time as the default host.
Let's come up with a plan where multiple people host. I'm happy to be one of a group of hosts.
@andrii-i has been documenting a guide for hosting, and I'm happy to meet with anyone who is interested in being a host. As a starting point, I would suggest every member of the @jupyterlab/jupyterlab-council consider it, but this also seems like a good way for someone who isn't yet on the council to get involved with the project.
Past calls
Upcoming calls
The text was updated successfully, but these errors were encountered: