Skip to content

Hosting our weekly meeting #197

Open
@afshin

Description

@afshin

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
datehostbackup host
2023 06 21@afshin
2023 06 28@JasonWeill@afshin
2023 07 05@tonyfast@afshin
2023 07 12@afshin
date host backup host
2023 07 19 @andrii-i @afshin
2023 07 26 @JasonWeill @afshin
2023 08 02 @afshin
2023 08 09 @JasonWeill @afshin
2023 08 16 @andrii-i @afshin
2023 08 23 @afshin
2023 08 30 @JasonWeill @afshin
2023 09 06 @andrii-i @afshin
2023 09 13 @afshin
2023 09 20 @JasonWeill @afshin
2023 09 27 @andrii-i @afshin
2023 10 04 @afshin
2023 10 11 @JasonWeill @afshin
2023 10 18 @andrii-i @afshin
2023 10 25 @afshin
2023 11 01 @afshin
2023 11 08 @afshin
2023 11 15 @afshin
2023 11 29 @afshin
2023 12 06 @afshin
2023 12 13 (Community Call) @tonyfast
2023 12 20 @JasonWeill @afshin
2023 12 27 TBC no meeting
2024 01 03 @JasonWeill
2024 01 10 @andrii-i

Upcoming calls

date host backup host
2024 01 17 @gabalafou (oops)
2024 01 24 @gabalafou
2024 01 31 @JasonWeill
2024 02 07
2024 02 14
2024 02 21 @andrii-i
2024 02 28

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions