Shaking the dust off this thread! Checking in to see if there is interest in hosting a monthly Jupyter meeting for the community. Basic parameters are this: a monthly one hour meeting which would remain at Tuesday morning 9am Pacific. This meeting would be recorded and published to the Jupyter YouTube channel. Agenda would be as follows: Updates from the various areas or subprojects (for lack of a better word) in the Jupyter universe. These would be the same as what we had in the previous agenda, what would be different is the frequency (1xMonth instead of 1xWeek) and the intended audience (the community). At the end of this chance for updates/news/discussion would be a demo from one area of our project. Either to provide a more in depth review of a new development or to show off a compelling user story. The goal would be to give our community a chance to interact with core developers and for us to share the latest news and developments in our work. @Zsailer and @damianavila have both shared thoughts with me on this idea and I'm sharing this more widely now to see if there is interest.
Feel free to add any further info I may not have captured Zach/Damian.
I think a monthly meeting makes more sense than weekly. It would be great if it were more demo-focused or at least "let me know show you what I've been working on" vs. "let me talk about what I've been working on." It would be cool to see someone from each subproject spend a couple minutes showing what's new with that project. We could reserve some time at the end for community members to ask questions and new contributors to receive guidance.
Afshin Taylor Darian
@Ruv7 I think a monthly meeting is a really good idea. I miss having these conversations and I think they benefit our community as well.
I like @gnestor ’s idea to reserve time for community members to ask questions and new contributors to get some help.
I like these ideas!
Thanks all - that's not a huge amount of buy in but enough that it's worth scheduling and seeing how this turns out. I would propose the first one be Tuesday February 26 at 9am PST. This would set up the cadence of meeting once a month, the last Tuesday of every month. If this format goes well and the core team contributes I would suggest sharing the March meeting with the community on Twitter and in Google Groups. One of the issues with the previous meetings was lack of buy in and participation so I wouldn't want to talk this up for the first one and then get little or no participation from the core group. I am happy to host the first one and then ask for people to step up and rotate the responsibility of the intro and the recording parts for future meetings. @betatim@jasongrout@afshin@gnestor@Zsailer
Afshin Taylor Darian
Good plan, Ana! :+1:
and this gives us a chance to talk about it at the dev meeting before March's meeting
and get buy-in there, or other suggestions
:+1: That sounds great, thanks Ana!
how do people imagine the "community members get help" or "help new contributors" sections would go? Q&A style?
I imagine it's more strategic Q&A about the things presented, more than "can you help with my install issue"
or perhaps "I tried following the new contributor docs, but ran into issues here and here." and us interviewing them about what their experience was like, and us understanding better how to onboard new contributors
probably at least at the start, there would be introductions of new contributors too?
with my binder hat on: i think i'd struggle to make a 5-10min overview every month of high level news from the project :-/ there is simultaneously "no news" and we fill a one hour agenda at our team meeting each month :-/ what i'd find easier and maybe more interesting for community at large is a walk through for contributing or demo of something.
the other thing i've been pondering: in an ideal setup for a community call should the jupyter team be in "listening" mode? maybe set the mood and then give a stage to people from the community to show off their work?
-> should we start a spreadsheet with a list of projects/people who we can target to give a demo at the meeeting?