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

[Ramkumar Ramachandra <artagnon@gmail.com>]

Hi,

> Personally, I would have little problems just adding the remote and
> checking out the branch, just to test the thing after I got a promising
> progress report. And I think those who are truly interested in
> git-remote-svn will have little problems, either. The important part would
> be the visible progress (i.e. mails by the student to this list).

Thanks for the elaborate explanation. The way I see it, there are two
extreme situations I must avoid. The first is being opaque for the
risk of not being able to integrate it into git.git at the end of the
summer term. The other extreme is worrying so much about the
integration of each little bit that the project keeps getting
detracted, and eventually loses focus. To strike a balance, I will
post progress reports to the mailing list (atleast) once a week, and
keep a public development branch for myself. Occasionally, it might
help to post patches for small components of the project with
unittests to get a wider test audience.

Ramkumar