Proposal for Jupyter Dev Meeting Redesign

jupyter-dev-meeting-template.md

Sub-teams

Here is a list of proposed sub-groups to give anouncements each meeting:

1. Jupyter Core
2. Jupyter Lab
3. nteract
4. Jupyterhub
5. Binder
6. IPython Core
7. Events and Community

motivation.md

Proposal: change format of IPython/Jupyter Team Meetings

The main goal to shift Team Meetings towards a more user-focused format. To do this, we propose the following changes:

• Reduce the frequency of the meetings to once-a-month.
• Focus the meeting to 1. making announcments and 2. sharing future goals.

These calls should not be:

• where developers discuss technical issues.

Background

The IPython/Jupyter community has grown significantly since we started the Team Meeting video calls. In many cases, the

Few developers show up. Most people are working on different projects that don't overlap. Here, we explore the question, do we need them?

Some thoughts:

Each sub-team in the Jupyter ecosystem has their own meetings (i.e. jupyterlab, jupyterhub/binder, nteract, etc.). These phone calls are the place for developers to discuss technical aspects of the project.

Motivation

Let's re-evaluate their purpose.

What is the purpose?

The purpose is to inform the public of things happening in the Jupyter ecosystem.

Some follow up questions:

• How often do new things arrive in Jupyter?
• How technical should these "announcements" be?

Here is a list of possible purposes for such a call:

1. Announce new features
2. Revisit a project's roadmap? How much progress have we made? What's next?
3. Welcome new developers to the team?
4. A word from the steering council?
5. Share a public success! :)

Proposed plan

Moderator

update-template.md

Sub-group Name

Representative for this meeting

• Next developer meeting: Date, Time, Link
• Home page of project

Announcments/changes users should know!

This section lists updates we want to communicate to the public. Each item should be 1-2 user-friendly sentences.

• Cool thing added in master #1. (Link to PR or demo)
• Cool thing added in master #2. (Link to PR or demo)
• ...

Updates to look foward to:

This section lists "things to look forward to". Each item should be 1-2 user-friendly sentences.

• Cool thing we are working on next #1.
• Cool thing we are working on next #2.
• ...

User success