Google Summer of Code

Peter Arrenbrecht peter.arrenbrecht at
Fri Mar 7 01:23:57 CST 2008

On Thu, Mar 6, 2008 at 11:14 PM, Dirkjan Ochtman <dirkjan at> wrote:
> Matt Mackall wrote:
>  > And yes, please take the admin crap job.
>  Alright, then.
>  First of all, does someone want to be backup admin crap person?

If nobody else volunteers, I would.

>  Second of all, they request answers to these questions. I could just
>  come up with some answers myself, but if any of you have ideas...
>  What is your plan for dealing with disappearing mentors?

So we should have one or two backups (not per topic, overall, I'd say)?

>  What steps will you take to encourage students to interact with your
>  project's community before, during and after the program?

If they follow the established dev procedure, they cannot avoid it
during the program, can they? And I guess having very competent and
responsive committers in the community should be an enticement. (Yes,
that's a kudo to you guys.)

Maybe pointing them to chapters 4, 6, 8 of would help, too?

>  What will you do to ensure that your accepted students stick with the
>  project after GSoC concludes?

"ensure"? Will Google sponsor t-shirts with the hg logo on them? Then
we just need to keep the master copy around: "One t-shirt to bind them

Seriously, I think the concepts it embodies, the traction it has
already gained, and the supportive dev community should help to keep
one interested.


More information about the Mercurial mailing list