Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/contribution_sprints/checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,5 +85,8 @@ This checklist is written for the 2026 conference which is being held at the end
### During conference

- [ ] Verify strong Wi-Fi in the venue (work with the venue team on this)
- [ ] Pin message with project spreadsheet and information about sprints in Slack
- [ ] Support people creating project signs for their tables (writing materials, etc)
- [ ] Check the temperature of the sprints rooms
- [ ] Make sure sprinters know when & where lunch is so food isn't wasted
- [ ] Make sure sprinters know when & where lunch is so food (if provided) isn't wasted
- [ ] Project introductions
1 change: 1 addition & 0 deletions docs/contribution_sprints/history.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,5 @@ nav_order: 3

## Previous Contribution Sprints Chairs

- Tim Schilling & Kudzayi Bamhare (2026)
- Sean Helvey (2024-2025)
10 changes: 10 additions & 0 deletions docs/contribution_sprints/playbooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,3 +56,13 @@ The simplest approach is to create the event in Google Calendar and export it:
3. Copy the `.ics` link, or download the file directly to attach to the email.

Alternatively, use an online generator such as [icalendar.org](https://icalendar.org/ical-generator.html) to build the file manually. Create one `.ics` file per session.

## Hosting Sprints during conference

1. 30 minutes before the scheduled start, prepare the venue. People need signs or ways to indicate their project, there should be an open spreadsheet with project info and links, and optionally dedicated chat channels for each project.
2. Any scheduled presentations should start at 9am or later, not when the doors open.
3. Greet people as they join, ask their interest or if they're leading a project. Guide them around the room as necessary.
4. Prior to project introductions, the chair should make announcements on general schedule
5. Project announcements from each project leader. Name, what the project is, what they want help on, any special skills a person needs to contribute.
6. [Optional] Presentation on how to contribute to Django
7. 10 minutes before the event closes, the chair should announce that people should begin wrapping up.