Re: Google Summer of Code 2013 (GSoC13)

2013-02-25 Thread Jaseem Abid
On Mon, Feb 18, 2013 at 10:53 PM, Thomas Rast wrote: > * We should prepare an "ideas page". Last year, Peff made one on > https://github.com/peff/git/wiki/SoC-2012-Ideas [Resending the mail, because the last one failed because of inline html content] One of the proposed ideas last year - '

Re: Google Summer of Code 2013 (GSoC13)

2013-02-25 Thread Junio C Hamano
Florian Achleitner writes: > For a student one aspect of GSOC is also quite important: It is a cool and > demanding summer job during the holidays, but it has to ramp down when the > new > semester starts. Thanks for sharing. I think an important lesson is that mentors and reviewers need to

Re: Google Summer of Code 2013 (GSoC13)

2013-02-25 Thread Florian Achleitner
[corrected David Barr's address] On Monday 18 February 2013 12:42:39 Jeff King wrote: > And I do not want to blame the students here (some of whom are on the cc > list ). They are certainly under no obligation to stick around after > GSoC ends, and I know they have many demands on their time. But

Re: Google Summer of Code 2013 (GSoC13)

2013-02-21 Thread Thomas Rast
Shawn Pearce writes: > On Mon, Feb 18, 2013 at 9:42 AM, Jeff King wrote: >> On Mon, Feb 18, 2013 at 06:23:01PM +0100, Thomas Rast wrote: >> >>> * We need an org admin. AFAIK this was done by Peff and Shawn in >>> tandem last year. Would you do it again? >> >> I will do it again, if people fe

Re: Google Summer of Code 2013 (GSoC13)

2013-02-21 Thread Carlos Martín Nieto
Michael Schubert writes: > On 02/18/2013 06:42 PM, Jeff King wrote: >> >> I will do it again, if people feel strongly about Git being a part of >> it. However, I have gotten a little soured on the GSoC experience. Not >> because of anything Google has done; it's a good idea, and I think they >>

Re: Google Summer of Code 2013 (GSoC13)

2013-02-20 Thread Michael Schubert
On 02/18/2013 06:42 PM, Jeff King wrote: > > I will do it again, if people feel strongly about Git being a part of > it. However, I have gotten a little soured on the GSoC experience. Not > because of anything Google has done; it's a good idea, and I think they > do a fine of administering the pro

Re: Google Summer of Code 2013 (GSoC13)

2013-02-20 Thread Matthieu Moy
Christian Couder writes: > - yes, we could improve mentoring by providing better projects and > insisting even more on submitting earlier A few words about my experience, not with GSoC, but with school projects (I've been proposing a few students in Ensimag to contribute to Git each year since 2

Re: Google Summer of Code 2013 (GSoC13)

2013-02-20 Thread Christian Couder
Hi, On Wed, Feb 20, 2013 at 7:50 AM, Shawn Pearce wrote: > On Mon, Feb 18, 2013 at 9:42 AM, Jeff King wrote: >> On Mon, Feb 18, 2013 at 06:23:01PM +0100, Thomas Rast wrote: >> >>> * We need an org admin. AFAIK this was done by Peff and Shawn in >>> tandem last year. Would you do it again? >>

Re: Google Summer of Code 2013 (GSoC13)

2013-02-19 Thread Shawn Pearce
On Mon, Feb 18, 2013 at 9:42 AM, Jeff King wrote: > On Mon, Feb 18, 2013 at 06:23:01PM +0100, Thomas Rast wrote: > >> * We need an org admin. AFAIK this was done by Peff and Shawn in >> tandem last year. Would you do it again? > > I will do it again, if people feel strongly about Git being a p

Re: Google Summer of Code 2013 (GSoC13)

2013-02-19 Thread Christian Couder
On Mon, Feb 18, 2013 at 9:02 PM, Jens Lehmann wrote: > Am 18.02.2013 20:34, schrieb Jonathan Nieder: >> That said, I won't have time to mentor a project on my own. It takes >> a lot of time (or luck, to get the student that doesn't need >> mentoring). > > That's my experience too. Also I think it

Re: Google Summer of Code 2013 (GSoC13)

2013-02-19 Thread Thomas Rast
Junio C Hamano writes: > Thomas Rast writes: > >> In defense of Thomas, whose project was mentioned earlier as a prime >> example of something that is "too big": >> >> He's in fact still working on the index-API angle, as part of a thesis >> at university. > > That is probably a good indicator t

Re: Google Summer of Code 2013 (GSoC13)

2013-02-19 Thread Junio C Hamano
Ramkumar Ramachandra writes: >> I was conflating between people who add "suggested project" and who >> act as mentors. I do not think mentors are primarily responsible >> for bad suggested projects. > > Why do mentors pick badly sketched-out projects to mentor? They're > free to pick anything t

Re: Google Summer of Code 2013 (GSoC13)

2013-02-19 Thread Junio C Hamano
Thomas Rast writes: > In defense of Thomas, whose project was mentioned earlier as a prime > example of something that is "too big": > > He's in fact still working on the index-API angle, as part of a thesis > at university. That is probably a good indicator that it was too big for a summer stud

Re: Google Summer of Code 2013 (GSoC13)

2013-02-19 Thread Ramkumar Ramachandra
Jeff King wrote: > On Tue, Feb 19, 2013 at 01:15:49AM +0530, Ramkumar Ramachandra wrote: > >> Take what I'm about to say with a pinch of salt, because I've never mentored. >> >> Mentors often don't provide much technical assistance: students should >> just post to the list with queries, or ask on #

Re: Google Summer of Code 2013 (GSoC13)

2013-02-19 Thread Thomas Rast
Ramkumar Ramachandra writes: > Jonathan Nieder wrote: >> Ramkumar Ramachandra wrote: >> >>> The short undiplomatic version of that is that our mentors suck (I'm >>> not pointing fingers, but that's what I infer from failing projects). >> >> Hold on a second. I'm not remembering such a grim outco

Re: Google Summer of Code 2013 (GSoC13)

2013-02-19 Thread Ramkumar Ramachandra
Junio C Hamano wrote: > Ramkumar Ramachandra writes: > >> Junio C Hamano wrote: >> ... >>> I think the real issue is everybody in the GSoC mentor candidate >>> pool grossly underestimates the scope of suggested projects, does >>> not encourage students to send early drafts to the public from the >

Re: Google Summer of Code 2013 (GSoC13)

2013-02-19 Thread Ramkumar Ramachandra
Jonathan Nieder wrote: > Ramkumar Ramachandra wrote: > >> The short undiplomatic version of that is that our mentors suck (I'm >> not pointing fingers, but that's what I infer from failing projects). > > Hold on a second. I'm not remembering such a grim outcome with 100% > failure from prior summe

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Ramkumar Ramachandra
Thomas Rast wrote: > Ramkumar Ramachandra writes: > > [...] On a related note, I don't like our Wiki. It's down half the time, and it's very badly maintained. I want to write content for our Wiki from the comfort of my editor, with version control aiding me. And I can't stan

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Junio C Hamano
Ramkumar Ramachandra writes: > Junio C Hamano wrote: > ... >> I think the real issue is everybody in the GSoC mentor candidate >> pool grossly underestimates the scope of suggested projects, does >> not encourage students to send early drafts to the public from the >> beginning, and perhaps overe

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jonathan Nieder
Ramkumar Ramachandra wrote: > The short undiplomatic version of that is that our mentors suck (I'm > not pointing fingers, but that's what I infer from failing projects). Hold on a second. I'm not remembering such a grim outcome with 100% failure from prior summers of code as you're describing.

Re: Potential GSoC13 projects (Re: Google Summer of Code 2013 (GSoC13))

2013-02-18 Thread Duy Nguyen
On Tue, Feb 19, 2013 at 4:11 AM, Jonathan Nieder wrote: > Ramkumar Ramachandra wrote: >> Jonathan Nieder wrote: > >>> - cross-compilable git >> >> Why, exactly? Git for embedded devices? > > My personal motivation would be building Git for Windows while > spending as little time on Windows as po

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Duy Nguyen
On Tue, Feb 19, 2013 at 12:23 AM, Thomas Rast wrote: > * Naturally that ideas page is a bit stale now, and three projects > shorter. Please propose new ideas and refresh or delete the old ones! > In particular some projects spawned long discussions on the list, and > the results of those di

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jonathan Nieder
Jeff King wrote: > On Mon, Feb 18, 2013 at 11:34:24AM -0800, Jonathan Nieder wrote: >> Some potential projects (unfiltered --- please take them with a grain >> of salt): >> [...] >> - collaborative notes editing: fix the default notes refspec, >>make sure the "notes pull" workflow works well

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Junio C Hamano
Jeff King writes: > This is not related to GSoC anymore, but I think handling multiple > versions is already pretty easy. You can just install to > "$HOME/local/git/$TAGNAME" or similar, and then symlink the "bin/git" > binary from there into your PATH as git.$TAGNAME (e.g., git.v1.7.8). Git > al

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Junio C Hamano
Ramkumar Ramachandra writes: > [corrected David Barr's email address] > > Jeff King wrote: >> And I do not want to blame the students here (some of whom are on the cc >> list :) ). They are certainly under no obligation to stick around after >> GSoC ends, and I know they have many demands on thei

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jeff King
On Tue, Feb 19, 2013 at 01:15:49AM +0530, Ramkumar Ramachandra wrote: > Take what I'm about to say with a pinch of salt, because I've never mentored. > > Mentors often don't provide much technical assistance: students should > just post to the list with queries, or ask on #git-devel. Mentors > s

Potential GSoC13 projects (Re: Google Summer of Code 2013 (GSoC13))

2013-02-18 Thread Jonathan Nieder
Ramkumar Ramachandra wrote: > Jonathan Nieder wrote: >> - cross-compilable git > > Why, exactly? Git for embedded devices? My personal motivation would be building Git for Windows while spending as little time on Windows as possible. People deploying git to 32-bit x86, 64-bit x86, and ARM (thi

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jeff King
On Tue, Feb 19, 2013 at 02:14:54AM +0530, Ramkumar Ramachandra wrote: > > - assimilating the distro builds: "make deb-pkg", "make rpm-pkg", > >etc along the same lines as the linux kernel's script/package/, > >to help people get recent git installed when they want it > > Overkill. I jus

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jeff King
On Mon, Feb 18, 2013 at 11:34:24AM -0800, Jonathan Nieder wrote: > Some potential projects (unfiltered --- please take them with a grain > of salt): > [...] > - collaborative notes editing: fix the default notes refspec, >make sure the "notes pull" workflow works well and is documented >w

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Ramkumar Ramachandra
Jonathan Nieder wrote: > Hi, > > Jeff King wrote: > >> I will do it again, if people feel strongly about Git being a part of >> it. However, I have gotten a little soured on the GSoC experience. Not >> because of anything Google has done; it's a good idea, and I think they >> do a fine of administe

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Thomas Rast
Ramkumar Ramachandra writes: [...] >>> On a related note, I don't like our Wiki. It's down half the time, >>> and it's very badly maintained. I want to write content for our Wiki >>> from the comfort of my editor, with version control aiding me. And I >>> can't stand archaic WikiText. >> >> Ag

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jens Lehmann
Am 18.02.2013 20:34, schrieb Jonathan Nieder: > That said, I won't have time to mentor a project on my own. It takes > a lot of time (or luck, to get the student that doesn't need > mentoring). That's my experience too. Also I think it really makes sense to have a co-mentor so you can balance the

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jens Lehmann
Am 18.02.2013 20:45, schrieb Thomas Rast: > Ramkumar Ramachandra writes: >> What's the harm of including something estimated to take 80% of a >> summer? > > Maybe even less than 80%. I didn't regret at all having split the summer's topic I mentored into smaller pieces. That made it easy to post

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jonathan Nieder
Ramkumar Ramachandra wrote: > Take what I'm about to say with a pinch of salt, because I've never mentored. > > Mentors often don't provide much technical assistance: students should > just post to the list with queries, or ask on #git-devel. Mentors > serve a different purpose; their primary resp

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Thomas Rast
Ramkumar Ramachandra writes: >> * Cannot look at the diff in word-diff mode (and apply it normally). [...] > Also: Having to figure out, heuristically, when to actually turn it on > might be a worthwhile feature, especially for services like GitHub. Actually that's a pretty cute idea of its

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Thomas Rast
Ronan Keryell writes: >> On Mon, 18 Feb 2013 18:46:05 +0100, Thomas Rast >> said: > > Thomas>The actual programming must be done in C using pthreads > Thomas> for obvious reasons. > > Are there obvious reasons OpenMP would not be enough to do the job? > > It looks like a tra

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Ramkumar Ramachandra
Jeff King wrote: > On Tue, Feb 19, 2013 at 12:14:19AM +0530, Ramkumar Ramachandra wrote: > >> I'll be frank here. I think the main reason for a student to stick >> around is to see more of his code hit `master`. I think it is >> absolutely essential to get students constantly post iteration after

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Thomas Rast
Ramkumar Ramachandra writes: > [corrected David Barr's email address] > > Jeff King wrote: >> And I do not want to blame the students here (some of whom are on the cc >> list :) ). They are certainly under no obligation to stick around after >> GSoC ends, and I know they have many demands on thei

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jonathan Nieder
Hi, Jeff King wrote: > I will do it again, if people feel strongly about Git being a part of > it. However, I have gotten a little soured on the GSoC experience. Not > because of anything Google has done; it's a good idea, and I think they > do a fine of administering the program. But I have noti

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jeff King
On Tue, Feb 19, 2013 at 12:14:19AM +0530, Ramkumar Ramachandra wrote: > I'll be frank here. I think the main reason for a student to stick > around is to see more of his code hit `master`. I think it is > absolutely essential to get students constantly post iteration after > iteration on the lis

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Ronan Keryell
> On Mon, 18 Feb 2013 18:46:05 +0100, Thomas Rast > said: Thomas>The actual programming must be done in C using pthreads Thomas> for obvious reasons. Are there obvious reasons OpenMP would not be enough to do the job? It looks like a trade-off between the code readability &

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Ramkumar Ramachandra
Thomas Rast wrote: > 2. Improving the `git add -p` interface > > * The terminal/line-based interface becomes a problem if diff hunks > are too long to fit in your terminal. I don't know if it's worth coming up with another interface. The best sol

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Thomas Rast
Thomas Rast writes: > * We should prepare an "ideas page"[...] > https://github.com/trast/git/wiki/SoC-2013-Ideas >From where I'm currently sitting, I won't have the time to mentor this year. So my two earlier proposals are essentially up for grabs: 1. Improving parallelism in various comm

Re: Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Jeff King
On Mon, Feb 18, 2013 at 06:23:01PM +0100, Thomas Rast wrote: > * We need an org admin. AFAIK this was done by Peff and Shawn in > tandem last year. Would you do it again? I will do it again, if people feel strongly about Git being a part of it. However, I have gotten a little soured on the GS

Google Summer of Code 2013 (GSoC13)

2013-02-18 Thread Thomas Rast
Hi, Google announced the 2013 incarnation of the Google Summer of Code program on Feb 11: http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Git has taken part in previous years, so I figure somebody should get the ball rolling again! The following items need to be sorted out: * We