Hi,
I'd like to propose a kind of mini-google summer of code to the
students of the the school where I teach, i.e. Ensimag, France
( http://ensimag.grenoble-inp.fr/ ). In short, this means having a few
students working for Git for a month at no cost ;-).
Currently, the students have an end-of-year project (in equivalent of
master 1) with the choice between many subjects, some of them being
somehow "real-life" (i.e. actually usefull things), and other being
artificial (i.e. enjoy doing it, and throw it away afterwards).
This year, I'd like to propose a subject "contribution to an existing
free software", and since the one I know best currently is Git, this
would take the form of "contribution to the Git project". I'd see the
practical organization a bit like the google summer of code: chose a
feature (the GSoC proposals on the wiki can be a good source of
inspiration), and implement it with the goal of being eventually
merged upstream. There would be no money involved, but the students
get a grade at the end. I would anyway follow the work of the
students, but a co-mentoring from a Git expert would be great.
The students work full-time for about 3 weeks (May 20th to June 16th),
and are grouped by teams of 2 to 4 students. Given my bandwidth, I
plan to propose only one group of 4 students this year, but we may
scale up later, who knows.
We have plenty of time before this starts, but I'm just sending this
email to get your feeling on it.
Any opinion? Do you like the idea?
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:47:37
Hi,
On Tue, 27 Oct 2009, Matthieu Moy wrote:
I'd like to propose a kind of mini-google summer of code to the students
of the the school where I teach, i.e. Ensimag, France (
http://ensimag.grenoble-inp.fr/ ). In short, this means having a few
students working for Git for a month at no cost ;-).
Do not underestimate the cost of time and nerves, both on the student's
and the mentor's part.
I spent an insane amount of time on the Google Summer of Code this year,
a relatively small (but not less frustrating) part of which was with Git.
Ciao,
Dscho
From: Clemens Buchacher <hidden> Date: 2016-06-15 22:47:37
On Tue, Oct 27, 2009 at 11:12:52AM +0100, Matthieu Moy wrote:
The students work full-time for about 3 weeks (May 20th to June 16th),
and are grouped by teams of 2 to 4 students. Given my bandwidth, I
plan to propose only one group of 4 students this year, but we may
scale up later, who knows.
That's not much time to get familiar with a complex project like git. So you
will have to do something extremely simple, which probably means that it
won't be anything exciting. If it were, someone else would have done it
already.
Clemens
Hi,
I'd like to propose a kind of mini-google summer of code to the
students of the the school where I teach, i.e. Ensimag, France
( http://ensimag.grenoble-inp.fr/ ). In short, this means having a few
students working for Git for a month at no cost ;-).
From: Jakub Narebski <hidden> Date: 2016-06-15 22:47:37
Clemens Buchacher [off-list ref] writes:
On Tue, Oct 27, 2009 at 11:12:52AM +0100, Matthieu Moy wrote:
quoted
The students work full-time for about 3 weeks (May 20th to June 16th),
and are grouped by teams of 2 to 4 students. Given my bandwidth, I
plan to propose only one group of 4 students this year, but we may
scale up later, who knows.
That's not much time to get familiar with a complex project like git. So you
will have to do something extremely simple, which probably means that it
won't be anything exciting. If it were, someone else would have done it
already.
Let's take a look at some projects from SoC2009Ideas and Wishlist:
* "smart" HTTP transport is being actively worked on
* narrow / sparse checkout is being worked on
* directory renames development stalled, I think last was in
http://thread.gmane.org/gmane.comp.version-control.git/99529
* git-svnserver has supposedly partial Python implementation
* restartable clone, which should be fairly easy to add to "dumb"
protocols, and quite challenging to add to "smart" protocols;
even without a code, having fresh ideas would be nice
* (optional) support for empty directories, needs index extension,
there were some patches, but the area might be muddy
It all depends on what you want to achieve in this short time. Would
it be to get to know OSS development workflow (submitting patches,
answering reviews, etc.), or would it be solving interesting real-life
problem, or perhaps solving some problem from beginning to the end
(the code being accepted).
--
Jakub Narebski
Poland
ShadeHawk on #git
Hi,
I'm resurecting an old thread :
http://thread.gmane.org/gmane.comp.version-control.git/131321
(message copied below)
and welcoming Diane, Axel and Clément (CC-ed), 3 students who have
chosen this project. Right now, they're trying to get familiar with
the codebase. As a first exercice, they'll try to add textconv support
to git-blame. The next tasks are undecided yet (but advices are
welcome).
I hope the project will be productive, both for students and the Git community!
On Tue, Oct 27, 2009 at 12:12 PM, Matthieu Moy
[off-list ref] wrote:
Hi,
I'd like to propose a kind of mini-google summer of code to the
students of the the school where I teach, i.e. Ensimag, France
( http://ensimag.grenoble-inp.fr/ ). In short, this means having a few
students working for Git for a month at no cost ;-).
Currently, the students have an end-of-year project (in equivalent of
master 1) with the choice between many subjects, some of them being
somehow "real-life" (i.e. actually usefull things), and other being
artificial (i.e. enjoy doing it, and throw it away afterwards).
This year, I'd like to propose a subject "contribution to an existing
free software", and since the one I know best currently is Git, this
would take the form of "contribution to the Git project". I'd see the
practical organization a bit like the google summer of code: chose a
feature (the GSoC proposals on the wiki can be a good source of
inspiration), and implement it with the goal of being eventually
merged upstream. There would be no money involved, but the students
get a grade at the end. I would anyway follow the work of the
students, but a co-mentoring from a Git expert would be great.
The students work full-time for about 3 weeks (May 20th to June 16th),
and are grouped by teams of 2 to 4 students. Given my bandwidth, I
plan to propose only one group of 4 students this year, but we may
scale up later, who knows.
We have plenty of time before this starts, but I'm just sending this
email to get your feeling on it.
Any opinion? Do you like the idea?
Thank you for this information.
As we are about to finish to add textconv support to git-blame, we'll
now look to add it to git-gui blame.
We wonder what would be the best choice between add a second option "Use
Textconv For Blames", or transform the existing one (introduced by the
patch above) into "Use Textconv For Diffs and Blames" (so the user
wouldn't have the choice to use textconv only for Diffs or only for
Blames; is it really usefull ?).
Your advice is welcome !
Thanks,
Clément