[group-organizers] Running a CPython sprint for new contributors

[Jessica McKellar]

Hi organizers,

This April, Boston Python ran its first CPython sprint for new
contributors. Here's a detailed writeup of the event:

http://pythonsprints.com/2013/05/5/bostons-cpython-sprint-new-contributors/

Because CPython is such a mature project, the barriers to entry are
particularly high, and often even if folks make the plunge and submit
a patch they find it languishing on the issue tracker for months. We
wanted to provide a supportive environment in which prospective
contributors could get help with environment setup, some direction on
what to work on, and timely responses to their first attempts at
contributing.

In particular, to make this 1-day sprint successful we:
* had attendees complete all the setup prior to the sprint
* had several committers and experienced contributors at the event
* curated a list of bite-sized bugs for attendees to choose from
* personally followed up on the tickets that were worked on to make
sure they had timely resolutions after the sprint

This was a very successful initiative that brought together 20 new
contributors who made progress on almost 40 tickets. I look forward to
running more CPython sprints with Boston Python, and I'd love to see
more user groups pursuing this event style to bring new folks into the
contributor community.

Our only cost was lunch, which was covered by the Python Sprints
committee (http://pythonsprints.com/contact/).

I'd like to heartily encourage you to consider running a CPython
sprint with your group! Please let me know if I can provide any
further details on our experiences in Boston.

Regards,
-Jessica