It's the Community Call Y'all

🏃run all 🖹document mode 📽presentation mode ⊟collapse all the code
⊞expand all the code jupyterlab-deck voila 🔍inspector 👯side-by-side

about today's event

This is a place to celebrate what people are doing in the Jupyter ecosystem and build connections across communities. There’s a couple things to know while we are here.

1. We want to remind everyone that community calls and chat are recorded.

2. This is a part of the Jupyter community we are all held to the Jupyter Code of Conduct. You can find this at any time at jupyter.org/conduct.

3. Presenters have submitted what they want to share ahead of time and can be found on the agenda. Presenters will keep talks between 5-7 minutes. Since we have a full program, we'll defer questions to the Zoom chat.

4. There are several ways to participate if you aren't demoing:

   • Keep the Zoom chat zoom active with questions, links and other discussions.
   • Help take and record links notes on the collaborative HackMD
   • React with Emoji's in Zoom

Who Is Excited to See Demos?

🎉 Use the Zoom chat and emoji reactions to let us know how excited you are to see some demos!

Thank yous

• thanks to all y'all for being here!
• thank you to all the participants in jupyterlab/team-compass/issues/223 who helped organize this event as a community
• thank you to the executive council, jupyter community building working group(JCB), and jupyter media strategy working group (JMS) for support in organizing this call

Updates from the Executive council

• Executive Council update from May 2023
• How Jupyter is governed.
• Ways to connect with the community on Jupyter.org

thank you Isabela Presedo Floyd

• thank you for single handedly organizing, hosting, and sharing 2 years of community calls
• for anyone that wants to host future calls there a bunch of prepared Ctrl + C/Ctrl + V resources

thank you Zach Sailer

• reviving the community call

• communicating the major challenge that the community calls overcome

  > There is often little cross-talk between Jupyter developers in sub-organizations and sub-projects. This isn’t personal; it’s one of the expected pains of being a large, open-source organization. I often find myself surprised by libraries, extensions, tools, etc. created by colleagues that I didn’t know about! While that’s a fun surprise, it can lead to each sub-organization re-inventing the wheel or worse, creating tools that do not work together (even though they are both from Jupyter devs!).

• first community call

about today's event

This is a place to celebrate what people are doing in the Jupyter ecosystem and build connections across communities. There’s a couple things to know while we are here.

1. We want to remind everyone that community calls and chat are recorded.

2. This is a part of the Jupyter community we are all held to the Jupyter Code of Conduct. You can find this at any time at jupyter.org/conduct.

3. Presenters have submitted what they want to share ahead of time and can be found on the agenda. Presenters will keep talks between 5-7 minutes. Since we have a full program, we'll defer questions to the Zoom chat.

4. There are several ways to participate if you aren't demoing:

   • Keep the Zoom chat zoom active with questions, links and other discussions.
   • Help take and record links notes on the collaborative HackMD
   • React with Emoji's in Zoom

---

---

Demonstration or Demolition Time! Which will it be?

---

---

suggestion for the community

on a monthly basis, repurpose a major team meeting eg lab, server, hub to host a community call. using established meetings to host community calls:

• gives community leaders a break. for example, today we are repurposing the normal weekly JupyterLab.
  • shout out the small group of rotating JupyterLab meeting hosts using the sign up to host issue
• reduces and redistributes organizing efforts for community call organizers
• stimulate cross project communication
• caution: don't repurpose meetings near releases

suggestion to ammend the community working group charter to include community calls.

Community Building Committe Areas of Responsibility should include community calls in its charter.

• Jupyter Community Workshops
• JupyterCon
• Jupyter Community Events Staff
• Operations and Budget
• Diversity, Equity, Inclusion
• Reporting
• Membership
• Community Calls

Advocate for the consistent support of the Community Calls and their hosts on Discourse or Github.

Fin

Thank you to everyone presenting and attending! We're happy to have you all as a part of the Jupyter community.

If you have any feedback, please direct it at https://github.com/jupyterlab/team-compass/issues/223. We’d love to hear what you think about the call, even if it just an emoji reaction.

Our next community call will be when all y'all decide. Check out the Jupyter community calendar to see what other types of meetings are happening in between.

• Join the new documentation working group
• Triage meetings are great beginner friendly meetings. (could some share more meeting information in the hackmd link in the call notes)

If you have any interest in sharing on future community calls, please do! It doesn’t have to be a big share, a polished share, or a technical share, just show off what you do with Jupyter that excites you.

If you’re interested in hosting a community call, or JupyterLab meeting, feel free to reach out. We have community event resources prepared to support you. It would be great to get different people interacting with the community.