Interested in volunteering with the Python Software Foundation?
The biggest job is mentoring students: Mentoring a
student as a primary mentor can be a pretty big time commitment (see
"What does it take to be a mentor?" for more information) but it's a very
rewarding chance to give a student an open source apprenticeship.
We mentor in teams, so if all you can handle is a few code reviews or taking
over for a week while someone's on vacation, you can team up with someone with more time.
The easiest way to become a mentor is to be part of one of the sub-orgs
that plan to be involved, so get in touch with them directly if you want to
help. If you're part of a group that would like to participate as a sub-org,
please read the section for sub-orgs below.
If you're not already part of a group
that wants to participate, we can try to match you with one, but be aware that to do
the best job of mentoring you're going to need to know the open source project pretty
well yourself. If you're not already a developer, you should be prepared to become
an active community member.
But we often need other volunteers! We're also looking for
friendly community members to help with other tasks! We'd love to have more
people available on IRC/Mailing lists to answer student and mentor
questions in various time zones. We are particularly looking for volunteers
who can read and comment on student blogs, remind students if they haven't
posted, and promote the work our students do to the larger Python community.
Or maybe you have another skillset you'd like to contribute? (Proofreading?
Recruiting diverse student applicants?) If you want to help, we can try to
find a way to make that happen.
If you'd like to volunteer, get in touch with a sub-org admin or
email the Python org admins at gsoc-admins(at)python(dot)org
To participate under the Python umbrella, a sub-org must do the following:
- Be a Python-based open source project that meets
- Have one sub-org admin and at least two mentors who are willing to commit
to the full GSoC period. (More is awesome!)
- If you want to connect with more potential volunteers,
to see if we can match you with volunters who don't have a project.
- Accept the Python
Community Code of Conduct for the duration of the
- Send an email indicating interest to gsoc-admins(at)python(dot)org before
the Python deadline (exceptions can be made if you get an amazing
student applicant later and want to sign up just for them).
- Have a good ideas page. We have a template below. Getting a
sometimes takes a few rounds of revisions; Meflin will work with you to make
sure your page is ready! Once you're ready for review, you can send
a pull request to get
added to this page
- Be able to handle meeting deadlines and following both Google
and Python's rules. We try to send important reminders for big deadlines, but we only
have limited volunteer time for nagging and cajoling. Groups that cause repeated problems
may be asked to take time off to limit core volunteer burnout.
- Disclose all potental conflicts of interest to the Python admins BEFORE accepting a
student. If you are unsure, ask. If a conflict is found after the fact the student and
sub-org may be dropped from the program. (Examples: student is involved in your research
student is your child, student owes you money, etc.)
We can't promise to take everyone who meets those criteria, but we do try to
take any group that we feel will give the students a great experience.
Terri has final say in which projects participate under the Python
umbrella, but please send any queries to all the admins at
gsoc-admins(at)python(dot)org to make sure we're all on the same page.
Python projects are welcome and encouraged to apply as separate
mentoring organizations directly with Google. We're happy to help
you in any way we can and we don't mind being your backup plan. We're also
happy to help advertise python based organizations not under our umbrella: we
want students to find projects that best suit them!