Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Sylvain Corlay
    @SylvainCorlay
    Thx!
    Damian Avila
    @damianavila
    Thx
    Afshin Taylor Darian
    @afshin
    Cheers, Ana.
    Ana Ruvalcaba
    @Ruv7
    @/all - heads up that @Zsailer and I are working on a proposal for switching up the frequency and format for this meeting. We will not be meeting this Tuesday.
    Min RK
    @minrk
    Thanks!
    Sylvain Corlay
    @SylvainCorlay
    thanks
    Jason Grout
    @jasongrout
    are we meeting today?
    Jason Grout
    @jasongrout
    guess not...
    Sylvain Corlay
    @SylvainCorlay
    @jasongrout do you want to meet?
    Jason Grout
    @jasongrout
    Yep. Are you still around @SylvainCorlay?
    Sylvain Corlay
    @SylvainCorlay
    yes
    Ana Ruvalcaba
    @Ruv7
    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.
    Grant Nestor
    @gnestor
    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.
    Tim Head
    @betatim
    :+1:
    Afshin Taylor Darian
    @afshin
    @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.
    Zachary Sailer
    @Zsailer
    I like @gnestor ’s idea to reserve time for community members to ask questions and new contributors to get some help.
    Jason Grout
    @jasongrout
    I like these ideas!
    Ana Ruvalcaba
    @Ruv7
    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
    @afshin
    Good plan, Ana! :+1:
    Jason Grout
    @jasongrout
    :+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
    Zachary Sailer
    @Zsailer
    :+1: That sounds great, thanks Ana!
    Tim Head
    @betatim
    how do people imagine the "community members get help" or "help new contributors" sections would go? Q&A style?
    Jason Grout
    @jasongrout
    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?
    Tim Head
    @betatim
    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?
    Jason Grout
    @jasongrout
    sort of like an ongoing online jupytercon?
    Afshin Taylor Darian
    @afshin
    JupyterConline strikes again.
    Brian E. Granger
    @ellisonbg
    I like the idea of having meetings with a more targeted purpose
    Tim Head
    @betatim
    JupyterConline :laughing:
    not sure what the right thing is -> writing my current idea and see what others think or modify it
    Ana Ruvalcaba
    @Ruv7
    So far sounds like agreement that Feb 26 at 9am is good for a kick off for this new meeting. @betatim - in the case where there is no news worthy technical development that a "sub project" (for lack of a better word) would like to report, I like the idea of that subproject using their time to share with the community a topic or message that is meant to engage or educate them in that area of Jupyter. So for example, sharing a bit about the vision and future of the subproject, reviewing where new contributors can go to if they need help with technical issues, or anything else that may be helpful. One thing I don't see us do much of is repeat our important messages to the community and so it's hard for people who join our community to figure us out. Simple things like where to go for documentation, help, or how to get started if they're thinking about contributing could all be valuable info to include in this call.
    Ana Ruvalcaba
    @Ruv7
    Regarding the idea of making it a fully open call where we invite the community to provide user stories / demos - I think it makes a GREAT idea for a webinar or special event but not for an ongoing monthly call. I say this because the goal I had in mind for this meeting is to use it as an opportunity for core developers to connect with the wider Jupyter community. If the goal was to highlight user stories as means to inspire folks the second format may work better. So let's talk about the goal, I didn't quite state that in my proposal. Any thoughts on what may be more impactful? I don't have the bandwidth to do both.
    Tim Head
    @betatim
    @Ruv7 my thinking/understanding on the goal was: build excitement, highlight what is happening in the jupyter world, improve the network between community members and core devs
    -> give a stage to people (core devs or not, basically who ever has something to say?!) to show off what they are working on/have worked on/spread the word about going ons. That could be a demo of upcoming feature from a core dev or a demo of something someone who isn't a core dev made or someone from jupyter showing how they approach a new PR or a walk through of how to start contributing
    things that fit into 5-10min slots
    Tim Head
    @betatim
    my personal experience/view is that if i want to contribute to a project i need to be able to find the docs/instructiosn for doing so right then and there when i want to do it. otherwise i don't ("i wanted to send you a bug fix but hey i cna't figure this out so well i guess someone else will....") i don't think i'd wait till in two weeks time to learn it. i've probably forgotten that i made a bug fix by then.
    i do agree that repeating things is important because most people aren't listening most of the time. which is why it is totally fine to repeat stuff. so a slot that is about "where to find the instructions for contributing and what do the words in those instructions mean" could run every three months or so
    when i first read the "help new contributors with issues" i was thinking more of a 20min or longer session where you actually answer questions from people
    i'm not sure that will be useful, mostly because me being me i'd not expect many people to come. i think a short (more meta) session on "where to go with your questions" would be better
    Ana Ruvalcaba
    @Ruv7
    I'd like to gather feedback from as many people as possible on what the goal of these meetings should be. I think this goal and what we believe will make the biggest impact (while minimizing time required to organize) should drive which format and agenda gets chosen for future meetings. One challenge we've faced in the past has been getting people to show up for this meeting so I would want us to have a plan to make this meeting easy/appealing to participate in. Also I have not issue with experimenting and iterating on different options. If we try something and it doesn't work we can always pivot and try something else. I would propose that we use that first meeting to have a working session to establish some consensus around this topic. Thoughts?
    Zachary Sailer
    @Zsailer
    :+1: on using the first meeting to discuss further meeting goals/structure.
    Zachary Sailer
    @Zsailer
    I’m hoping this call also becomes a way for all the branches of the Jupyter “ecosystem” to stay in touch, learn from one another, appreciate the awesome tools each is creating, and share outside (for lack of a better word) perspective+ideas on one another’s projects. As much as this could be a call for users, it could also be a great way for team members to stay involved in projects outside their immediate work.
    Carol Willing
    @willingc
    Hmm...I wonder if it makes more sense to talk about this in person at the March meeting. Right now, although these are all good ideas, the upcoming call feels very much like what we had before just less often. Personally, I don't feel as if I have a working view of what the priorities are for the project as a whole and what direction the subprojects are taking. I also feel as the front-ends evolve that the notebook format and jupyter server have become more critical to all the projects. I would like to see something more along the lines: 15 minutes Strategic State of the Project given by Fernando/Brian/Ana - what is the current focus/grants/next quarter/next year goals; 10 minutes per JupyterLab, widgets, hub/binder, classic/ipython/nbconvert on new activity and strategic challenges (i.e. resources, changes needed to nb format and apis); closing with 5 minutes recognizing the good things within the entire project.