Re: [jupyter] Reviving the all-Jupyter video call
I'll just chime in to say I love this idea, and thanks in advance to those who are organizing it! As mentioned, one of the best way to "catch up" with what's going on in the Jupyter ecosystem is to attend a big meeting like Jupytercon, Pycon, Scipy, etc. It's a drag that they only happen once a year (and are expensive to attend). This would be a great supplement to that. By way of analogy: at my organization (a large university) we have developers of various sorts scattered across dozens of colleges and departments working on a huge variety of things. Over the past few years we've created a group (technically something called an "Informal Community of Practice") that enables us to have a monthly meeting that people can attend in person or remotely, that consists of 90 minutes of announcements, show-and-tell with Q, and lightning talks. It seems to have made an enormous difference in terms of helping our developers - especially those who are one of only 2-3 in a department - feel less isolated and more connected to the larger community enterprise, and has definitely had knock-on effects in terms of greater compatibility and shared best-practice use across the various projects they work on. In short, this sounds like a similar concept, so big thumbs up from me. On Wed, Feb 27, 2019 at 9:32 AM Zach Sailer wrote: > Hello Jovyans, > > I wanted to summarize some ideas shared during a recent discussion about > the "all-Jupyter" video calls. These meetings are intended to gather all > Jupyter community members, across sub-organizations (for lack of a better > word) and sub-projects, in a single video call. > > The topic of discussion was: > *how can we re-purpose the "all-Jupyter" video call to more effectively > benefit the Jupyter team and community?* > I’d like to use this thread to open the conversation to the community. My > hope is that we converge on an enjoyable+productive format for future > meetings. :) > > I would break our discussion today into 4 questions: > >- What is the purpose of these calls? >- Who are we targeting? >- Who should attend? >- What should the format be? > > In the rest of this post, I’ll share some ideas expressed in our meeting > today. > > *A little background* > > In the past, Jupyter had a *weekly* all-Jupyter video call. The goal was > to connect Jupyter team members once-a-week to discuss technical blocks and > share updates in their daily development. This made sense when Jupyter was > comprised of a handful of projects with similar goals. We’ve outgrown this > format. The Jupyter ecosystem is now composed of various sub-organizations > and many sub-projects. Sub-organizations began to grow, and Jupyter > developers began working on vastly different projects. > > As a result, attendance dwindled over time. This signaled that the meeting > needed to be *re-purposed.* There is a great benefit to getting all the > Jupyter teams together (discussed below), but the old format wasn't > working. The goal of this post is to explore how we can effectively do this > moving forward. > > *A major issue we’d like to address* > > 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 when all tools come from Jupyter > devs!). > > This also means that Jupyter *users* will likely miss important updates > and cool features that could improve their Jupyter experience. > Unfortunately, READMEs on Github are not the best way to learn of new > projects. Even tweets with GIFs don't always do it for me. Personally, I > discovered more tools, extensions, and helpful hints from three days at > JupyterCon than a year's worth of tracking Github/Twitter. Sometimes, > seeing a project demoed live from the core developer and having them answer > questions in real-time is more effective at attracting users. > > *A (proposed) new meeting format* > > Here's what I took away from our meeting today: > > What is the purpose of these calls? >> > > We discussed this meeting having a few main purposes: > >1. Developers (core or community) share their work. Use the video >format to *demo* and screen-share their cool extension, feature, or >sub-project. >2. Users share how they're using a Jupyter sub-project in some cool >way. This could be highlighting a blog-post or screen-sharing their >implementation of some Jupyter project. >3. A member of the Jupyter steering council share any >updates/announcements that the community should here. > > > More specific discussion about sub-organizations/sub-projects should > happen in their own Team meetings
[jupyter] Reviving the all-Jupyter video call
Hello Jovyans, I wanted to summarize some ideas shared during a recent discussion about the "all-Jupyter" video calls. These meetings are intended to gather all Jupyter community members, across sub-organizations (for lack of a better word) and sub-projects, in a single video call. The topic of discussion was: *how can we re-purpose the "all-Jupyter" video call to more effectively benefit the Jupyter team and community?* I’d like to use this thread to open the conversation to the community. My hope is that we converge on an enjoyable+productive format for future meetings. :) I would break our discussion today into 4 questions: - What is the purpose of these calls? - Who are we targeting? - Who should attend? - What should the format be? In the rest of this post, I’ll share some ideas expressed in our meeting today. *A little background* In the past, Jupyter had a *weekly* all-Jupyter video call. The goal was to connect Jupyter team members once-a-week to discuss technical blocks and share updates in their daily development. This made sense when Jupyter was comprised of a handful of projects with similar goals. We’ve outgrown this format. The Jupyter ecosystem is now composed of various sub-organizations and many sub-projects. Sub-organizations began to grow, and Jupyter developers began working on vastly different projects. As a result, attendance dwindled over time. This signaled that the meeting needed to be *re-purposed.* There is a great benefit to getting all the Jupyter teams together (discussed below), but the old format wasn't working. The goal of this post is to explore how we can effectively do this moving forward. *A major issue we’d like to address* 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 when all tools come from Jupyter devs!). This also means that Jupyter *users* will likely miss important updates and cool features that could improve their Jupyter experience. Unfortunately, READMEs on Github are not the best way to learn of new projects. Even tweets with GIFs don't always do it for me. Personally, I discovered more tools, extensions, and helpful hints from three days at JupyterCon than a year's worth of tracking Github/Twitter. Sometimes, seeing a project demoed live from the core developer and having them answer questions in real-time is more effective at attracting users. *A (proposed) new meeting format* Here's what I took away from our meeting today: What is the purpose of these calls? > We discussed this meeting having a few main purposes: 1. Developers (core or community) share their work. Use the video format to *demo* and screen-share their cool extension, feature, or sub-project. 2. Users share how they're using a Jupyter sub-project in some cool way. This could be highlighting a blog-post or screen-sharing their implementation of some Jupyter project. 3. A member of the Jupyter steering council share any updates/announcements that the community should here. More specific discussion about sub-organizations/sub-projects should happen in their own Team meetings separate from this all-Jupyter meeting (i.e. nteract, jupyterlab, and jupyterhub all have their own separate meetings). Who are we targeting with these calls? > This call targets both Jupyter *developers* and *users*. Jupyter developers get to hear about other projects in the Jupyter ecosystem, offer technical feedback, and guard against problems that arise from a lack of communication. Jupyter users can hear about awesome things happening in the Jupyter ecosystem, ask questions in real-time, and share their experiences with the various sub-projects. Who should attend these calls? > First, it's absolutely critical that most of the core Jupyter developers participate in some capacity. Whether that's preparing demos or speaking on the video call, having core developers attend demonstrates that we are invested in the team and the community. After that, *anyone and everyone* is welcome! Whether it's to present their work, engage in discussion, or just sit in and listen, everyone is welcome. This is a good chance for users to ask questions and meet other Jupyter people. What should the format be? > *(We will likely need to iterate on the format. This thread is a good place to discuss and collection ideas for a format.)* One initial idea is to follow a format similar to Jupyterhub/Binder meetings: Meeting Agenda: - The agenda is open and editable by anyone via HackMD. - Users/developers "sign-in" and
