[Python-Dev] GSoC Student Introduction

Christian Heimes lists at cheimes.de
Wed Apr 23 12:56:44 CEST 2008

Martin v. Löwis schrieb:
> I certainly can't speak for the respective mentors, but I feel that
> "use bazaar" really isn't the right answer to "can I get commit access?"
> One motivation for GSoC is also community bonding, and having the
> mentor (but not *only* the mentor) comment on the proposed changes,
> and monitor the progress of the project. That the development branch
> sits on the student's laptop doesn't really help in that process.

Students have to sign the contributor agreement anyway or we can't use
their work. I don't see a problem with giving them svn commit privileges
as long as they restrict themselves to their sandbox.

> (*) FWIW, Google does provide the infrastructure; students are
> encouraged (required?) to commit their work to code.google.com.

People doesn't require the students to use their infrastructure. Google
just wants three evaluations from the mentors (after the community
bounding phase, mid term and at the end). Google also requires the
student to send in a tarball with their work - patches, docs, tests and
so on. The tarball is just required for legal reasons. Leslie once
explained it's a social and legal hack to make the contract work and the
lawyers happy.


More information about the Python-Dev mailing list