Re: native-git-svn: A Summer of Code 2010 proposal

[Sverre Rabbelier <srabbelier@gmail.com>]

Heya,

On Sun, Mar 21, 2010 at 13:25, Ramkumar Ramachandra <artagnon@gmail.com> wrote:
> Occasionally, it might help to post patches for small components
> of the project with unittests to get a wider test audience.

I suggest that (and this is a suggestion for all git GSoC projects)
that all students are required to post a weekly status update to the
mailing list. If they then prefix those mails with [GSoC update] it is
1) easy to filter out these emails for those who are not interested in
them and 2) easy later on to get a quick overview of who did what
when, by searching for all [GSoC update] emails. At first these emails
can just be a description of what was done  in the past week, which
design decisions were made (and why), and what the current status of
the project is. Later on these should be complemented by patches to
the git list (prefixed with [RFC/GSoC/PATCH] or such) with the
progress of the student so far.

In this particular case I think it'd be a good idea to start sending
patches around 3-4 weeks into the project, since by June 20 you hope
to have something minimally usable. I reckon it would be good to keep
these patches in pu to give them wider exposure, and to start merging
them to next as appropriate. For example, as soon as there is full
read support that would be a good time to merge to next to allow more
people to give it a try.

Junio, how do you feel about keeping these (most likely
fairly-unstable) GSoC patches in pu? I think it would be a great
motivation for our students (look, I've got my work into pu!), and
it'd be a great way to make it easy for everybody else to try out the
work of our students.

-- 
Cheers,

Sverre Rabbelier