Git Product home page Git Product logo

core-sprint's People

Contributors

aeros avatar brettcannon avatar corona10 avatar ericsnowcurrently avatar gpshead avatar gvanrossum avatar isidentical avatar lewisgaul avatar mariatta avatar markshannon avatar methane avatar nanjekyejoannah avatar pablogsal avatar pganssle avatar scoder avatar shihai1991 avatar taleinat avatar warsaw avatar willingc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

core-sprint's Issues

Write a detailed doc on how the sprint will work

Write up details:

  • Who can participate? (all core devs are invited)

  • How to participate?

  • How to discover projects? (see also #2 )

  • How will we communicate? (Discord & Zoom)

  • How to start a group meeting?
    Meetings should be visible to other core devs
    Allow core devs to join and participate in the meeting
    Record the meeting, or have a note-taker to share summary

  • The PSF's Code of Conduct applies and will be enforced

etc

Sprint activity: Tech Check before sprint starts

Idea from Barry: We should definitely have a pre-sprint "tech day" where people can install, check, and fix whatever tools they need to participate.

We will schedule some time on Sunday for the tech check.

The relevant techs and tools are:

  • Discord
  • Zoom, for meetings and all hands
  • Note taking app, Google Docs
  • Calendar, Google Calendar

Grant access for "notes" docs to all participants.

I tried accessing one of the notes docs (in this case the one for "C-API/subinterpreters") and got a permission-denied message, along with the option to request access. I have done so for that one doc, but would like access to all the notes docs (without having to request access for each).

I would expect others to want the same and it would probably make sense to give access to all registered participants.

Core dev sprint sponsorship prospectus

Sponsorship prospectus for the core dev sprints

Ewa to bring up on Monday to the SC

Can be a 10 min slot for organizations to address core devs

These funds can be used to send F&B allowances to core devs attending the sprint, could also be used to pay for the fun activities (such as virtual escape room)

Escape room choices: any preference?

Continuing from #12, based on current signups, 17 people indicated that they're interested in playing virtual Escape Room.

I've researched several choices, and wondering what you all think:

  1. Moonshot: https://www.tryreason.com/moonshot/
    Promo video: https://www.youtube.com/watch?time_continue=2&v=7fKKYQ0fGvU&feature=emb_logo
    Cost: 30 USD pp (minimum 10 people, so minimum $300).
    We will need to book a session, since they will have one employee joining and assisting us as the host. They're based in San Francisco, so their availability is limited to their local time: between 8:15 AM to 5:30 PM Pacific.
    If we choose this, we need to pick one timeslot, and all of the players will be playing together at the same time. We will be split into several groups, and we'd be competing against the other group. If we choose this game, I think the best time for us to play would be 8:15 AM Pacific.
    I've played this with my co-workers and we had a great time.

  2. The Escape Game Unlocked: https://store.theescapegame.com/collections/teg-unlocked
    Promo video: https://www.youtube.com/watch?time_continue=1&v=7qdsJfoVTKk&feature=emb_logo
    10$ per game (or two games for $17)
    Instead of paying per person, we'd pay for access code to the game. Each access code can only be used once. The recommended is 3-4 players per game. We'd be playing using our own browser and set up our own zoom calls, and one person has to screenshare so the others can see the game. (only one person can login to the game). We can purchase several game access codes, and form several groups, so people will have the flexibility to find a time convenient to their group.
    I haven't played this game.

  3. Escape From Cell 126: https://escthegame.com/
    Cost: 25$/game
    This is very similar to the option 2 above, the difference is it allows multiple players logging in at the same time using the same code. They recommend 6-8 people per game, so we would still need to get several access codes, and split into several groups. But as a player we'd have more freedom in "exploring" the game, instead of having one person share the screen.
    I've played this with my family; 2 adults and 2 kids, and we find it quite challenging and fun. We "escaped" after 1hr 30 minutes. With combined brainpower of 6-8 adults, I'm sure you all would be able to escape much sooner :)

Let me know what you all think.

Idea: design sprint swag like t-shirt/mug for participants

I think it would be cool to design some kind of swag to be sent out to sprint participants. e.g. t-shirt, mug, sticker sheet, pin, etc. Not sure if this is something people would be interested in, and whether we could get the fund for it.

Create a central editable collaborative notes of sprint project

From Discourse, it was suggested to "set up some kind of easy-to-edit central collaborative notes/links/tasks document with a schedule and notes broken up by days, where it’s easy to jump to the section about a particular day (Google Docs or something like it)"

What will we use? GDocs? Hackmd?

From @brainwane on Discourse:
Prep for discoverability – participants need to know who’s working on what so they can work together. But this is harder to serendipitously find out remotely. And some participants are reluctant to commit to a project ahead of time, or forget to update any central board/wiki page/doc as they work. So:

  • if you can, come to a rough consensus at least a few days before the event, agreeing on a few goals you want to achieve, and getting a few people to step up as topic leads; those topic leads should set up some spaces (Zulip threads, videocall rooms, etc., whatever seems good to them) for work on those topics
  • privately, give participants a list of other participants at least a few days ahead of time
  • set up some kind of easy-to-edit central collaborative notes/links/tasks document with a schedule and notes broken up by days, where it’s easy to jump to the section about a particular day (Google Docs or something like it)
  • if a voice or IRC/Zulip conversation gets to where people are making decisions or sharing key info, have a notetaker put notes in that central doc
  • each day, not in a big meeting but as a series of quick small conversations, have a person check in on what everyone’s working on, and take some brief notes and put them in that central document

Plan social and fun activities

Schedule some fun and social activities.

Perhaps poll core devs on 7 activities and pick the top 3

Some suggested activities:

  • virtual escape room
  • group pixel drawing
  • https://gather.town/
  • online board games
  • virtual lunch/ coffee break
  • ???

Sprint activity: all hands kickoff and sendoff

Suggestion from @brainwane on Discourse:

Two big (short) all-hands meetings: kickoff and sendoff – If people trickle in at the start and out at the end without a clear start and end to the sprint, then participants miss opportunities to catch each other, feel less connected, and miss logistical reminders. So: schedule a simultaneous all-hands chat for the kickoff (probably 10 minutes on logistics and 10 minutes summarizing what teams are working on what), and a call for the end of the last day (20 minutes on accomplishments and next steps).

Set up Python Discord for online chatting during the sprint.

Just use the hosted version instead of trying to set it up ourselves.

Python Discord can host the sprint on their server - easiest option
Contacted Python Discord owners to confirm, they are 100% on-board with hosting it
Bot integration using Zapier

Create a shared calendar

Please consider creating a shared calendar that we can subscribe to. This calendar should hold all the events that are currently planned, and individual projects should be able to add meeting times and such to it.

Sprint activity: Q&A session between core devs and Python community/users

At past sprints, sometimes we'd have a core dev Q&A Panel at the host company. Since we're doing a virtual event this year, there is no host company. So instead I think it would be great to have a core dev Q&A with Python community members.

Some ideas on how to make this work:
- collect questions ahead of time: create a form / slido?
- We can record the Q&A and publish the video later

We will collect questions as issue comments in this repo.
We need a list of core devs participating in the Q&A.
We will record the Q&A session.
We will schedule a time for core devs to meet and answer the questions.

Tasks to complete:

  • Schedule a time during sprint (maybe 1 hour) to host the Q&A
  • Post the list of core devs participating in the Q&A
  • Create the issue within this repo for collecting community questions, along with instructions to give a 👍 reaction to comments they want to upvote
  • Send out announcement about the Q&A to various channels
  • python-dev mailing list
  • Python Discourse under Users category
  • psf-community mailing list
  • Twitter
  • Facebook (?)
  • LinkedIn (?)

Track pull requests reviewed and closed during the sprint

We can give out prizes for top contributors.

I'm interested in writing a web app to automatically track and display progress during the sprint. Or if folks know of an existing tool, please do share.

What are we tracking?

  • number of pr reviews by each core dev
  • number of PR merged/rejected
  • number of PR comments

Is this just for CPython repo, or for other repos as well? (like devguide, peps, all the bots, etc?)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.