Tutorial Team Roles

Running PyCon Tutorials is a big a job for one or two people to do sustainably, but there are several relatively independent tasks that account for most of the overall effort, so for 2014 we're trying to spread the workload more broadly.

Below are descriptions of the various tasks with rough estimates of the time required. Names of those who have expressed interest in specific tasks are in square brackets.

• Tutorial Request for Proposals [Xu]

  Prepare for the request for proposals, improving and cleaning up documentation on how to submit a proposal. 3-8 hours in June leading up to the July 1st CFP.

• Tutorial Reviewer Whip [Ruben]

  Monitor the progress of tutorial reviews and encouraging reviewers to review, highlighting proposals or areas that need more reviews, and soliciting help from domain experts. 1-2 hours per week from mid-July when proposals start arriving to roughly October when reviewing/voting winds p.

• Tutorial Reviewers [Ruben]

  This is one of the biggest tasks in terms of overall effort and needs a core team of 5 to 10 people willing to review lots of proposals in July, August, and September, and participation in tutorial review sessions via IRC, web conferences, and/or phone conferences.

  For effort, at the low end any amount of reviewing is helpful, and there's no limit to how much time one could contribute. Ideal is a core team of 5 to 10 reviewers who spend 1-2 hours per week reviewing all ~100 proposals as they arrive and then spend 1-2 hours per week average in September and October at review meetings (typically fewer meetings in September and more in October).

• Tutorial Proposal Feedback Coordinator [Ruben]

  Attend tutorial review sessions as the person charged with giving feedback on proposals that don't get accepted.

  Communicate proposal acceptance and rejection notices.

  Effort is 1-2 hours per week attending review meetings, then a few hours to send out the feedback.

• Tutorial Scheduling [Xu]

  Help the coordinator plan the tutorial schedule. 2-5 hours.

• Tutorial Instructor Tax Info Communications

  Handle communication to instructors about required tax information, soliciting tax forms, reminding them, threatening them, etc., to get their tax information submitted. 3-4 hours per month from December through PyCon.

• Tutorial Assistant & Host Coordinator [Harry]

  Organize volunteer tutorial assistants and tutorial hosts. 1 hour per week December to PyCon, increasing to 2-3 hours the last couple of weeks and some hours onsite at PyCon.

• Tutorial Handouts [Jessica]

  Handle communication to instructors about submitting handouts for printing and then collecting them. 1 hour every 2 weeks starting in December, then 3-4 hours about 10 days before PyCon.

• Tutorial Evaluations [Xu]

  Improve the tutorial evaluation survey, and after PyCon is over reviewing and distributing evaluation data to instructors. 3-8 hours anytime before PyCon, optionally some time during PyCon analyzing data if we want quick data feedback, and 3-5 hours after PyCon.