Feedback from Pycon 2018

[chalmerlowe]

Below are a summary of items shared with us a feedback from the 2018 Pycon Intro to Sprints workshop. Putting them all here as a quick dump... where possible, will be moving them to separate Issues and deleting from this list:

• Video recording for certain tasks >>> having short videos showing certain tasks would allow us to a) speak about the content of the video without having to speak and type. b) would allow us to point at OR highlight some of the content as it is happening. Would allow students to replay the material at their leisure c) represents an additional level of complexity that should be discussed.
• Provide better instructions around the fact that the Issues tab only appears if a certain setting is set.
• Identify a defined period of silence for each task to go with/in the Time Box >>> When the students are told to "GO!" it was hard to focus on tasks for some of the parts when the instructor immediately started speaking from beginning to end (i.e. Timebox 3/10 might mean... aim for 3 minutes of silence, 7 minutes of explanation and a total of 10 minutes)... SPUN off an alternate Issue: Revise the Time Box timings... #176
• In teacher prep, add a suggestion that the room be available for set up, about an hour beforehand for installation software.
• MERGE: Add content related to teaching merging (see below) (NOTE: breaking this out as a separate ticket - CL)
• MERGE: Make a command executive decision on how we want to handle accepting PRs to the codeless repo (had conflicts when lots of people pushing to repository) (see above)(NOTE: breaking this out as a separate ticket - CL)
• MERGE: Suggest that we have everyone do a successful push. Then we go into the upstream and make a single change and have the class make a conflicting chang... and then have everyone do a pull, resulting in a merge that must be resolved.(NOTE: breaking this out as a separate ticket - CL)
• Consider the number of people that can attend ... too many people can be noisy due to many people talking & resolving issues. At Pycon, we had ~80 people and the room was too small.
• Consider additional trouble shooting guides in the docs
• Consider whether conda is the path we want to continue using: pipenv OR other? (NOTE: breaking this out as a separate ticket - JKE)
• Consider the timing: is late Sunday the best time to have the workshop? Having this training earlier in the week would give new comers to join even though they may not be able to sprint
• Add Kevin's challenge coin picture as part of the presentation (Chalmer has a copy of this pic)
• Create draft blog post/advertisement with details
• Create draft mentor blog post/advertisement out early AND get signups ahead of time (estimating X students per mentor)
• Edit the hyperlink to the git overview (got a 404 during the tutorial >>> question... was this due to rate limiting OR is the link broken)
• add closing lesson on what to expect during sprints: SPUN off into Issue UPDATED: Add closing section: include non-technical support/helps/ideas #57
• Create a set of instructions / suggestions for TA resources into a "Preprarations for the TAs" and/or in the "Preparations for Instructors" page. I would suggest that we identify some best practices from djangogirls AND software carpentry

[seawolf42]

To anyone working on this ticket: as these are fixed, obviously check the box; also check the box if you spin off a separate ticket for an item so it's clear it's not being tracked here any longer.