Congrats everyone who was successful in being picked for this year's GSoC.
Fabian with Line options for git rebase --interactive [0]
Brian Gesiak with Unify and Refactor Temporary File Handling [1]
Tanay Abhra with Git configuration API improvements [2]
I look forward to seeing how you go!
[0]
Thank you!
I'm very excited to be participating in this year's GSoC. Google
recommends that students use the next few weeks to get to know their
mentors, read documentation, and get up to speed to begin working on
their projects. Students have also received instructions on submitting
tax forms
Michael Haggerty mhag...@alum.mit.edu writes:
Sounds good. I suggest we make your blob a paragraph before the list of
bullet points rather than part of the list. Please suggest some TBD*
then I'll add it to the text. Would we also fill in X with the name
of the actual student involved in
On 02/27/2014 08:19 PM, Junio C Hamano wrote:
Michael Haggerty mhag...@alum.mit.edu writes:
Sounds good. I suggest we make your blob a paragraph before the list of
bullet points rather than part of the list. Please suggest some TBD*
then I'll add it to the text. Would we also fill in X
Michael Haggerty mhag...@alum.mit.edu writes:
On 02/27/2014 08:19 PM, Junio C Hamano wrote:
Michael Haggerty mhag...@alum.mit.edu writes:
Sounds good. I suggest we make your blob a paragraph before the list of
bullet points rather than part of the list. Please suggest some TBD*
then I'll
On Tue, Feb 25, 2014 at 06:15:28PM +0100, Michael Haggerty wrote:
We didn't discuss earlier whether we would have any specific
requirements for students during the proposal period (e.g., having a
patch accepted). It would be good to put together rules (or barring any
specific
On 02/26/2014 11:23 AM, Jeff King wrote:
On Tue, Feb 25, 2014 at 06:15:28PM +0100, Michael Haggerty wrote:
Requiring students to submit a reasonable patch and follow up on review
comments seems like it would be a good way to filter out non-serious
students. (I hesitate to require that the
On Wed, Feb 26, 2014 at 11:41:21AM +0100, Michael Haggerty wrote:
Yes, though I think it makes sense to put them on a separate page. We
should probably write up some notes for students, too: how to get in
touch with us, what do we expect of them in the pre-proposal period,
what would we
On Tue, Feb 25, 2014 at 10:41 PM, Jeff King p...@peff.net wrote:
I'm pleased to announce that Git has been accepted to this year's Google
Summer of Code.
Student proposals will start coming in on March 22. In the meantime
students will be reading our Ideas page[1] and enquiring about the
On Wed, Feb 26, 2014 at 12:25:36PM +0100, Vicent Martí wrote:
On Wed, Feb 26, 2014 at 11:41 AM, Michael Haggerty mhag...@alum.mit.edu
wrote:
Since time is short, I already started on this. I wrote a first draft
of an introduction for the students. I also started looking for
On Wed, Feb 26, 2014 at 11:41 AM, Michael Haggerty mhag...@alum.mit.edu wrote:
Since time is short, I already started on this. I wrote a first draft
of an introduction for the students. I also started looking for
microprojects. I started going through our source files alphabetically,
and
On Wed, Feb 26, 2014 at 12:16 PM, Duy Nguyen pclo...@gmail.com wrote:
On Tue, Feb 25, 2014 at 10:41 PM, Jeff King p...@peff.net wrote:
I'm pleased to announce that Git has been accepted to this year's Google
Summer of Code.
Student proposals will start coming in on March 22. In the meantime
On Wed, Feb 26, 2014 at 12:24:13PM +0100, Vicent Martí wrote:
One thing I noticed after tg/index-v4-format is both libgit2 and jgit
do not seem to support index v4. So we could add index v4 support on
libgit2 to the idea page. It's a relatively small task though once
you get a hang on
On Wed, Feb 26, 2014 at 3:30 AM, Jeff King p...@peff.net wrote:
On Wed, Feb 26, 2014 at 12:24:13PM +0100, Vicent Martí wrote:
One thing I noticed after tg/index-v4-format is both libgit2 and jgit
do not seem to support index v4. So we could add index v4 support on
libgit2 to the idea page.
On 2014-02-25 16.41, Jeff King wrote:
I'm pleased to announce that Git has been accepted to this year's Google
Summer of Code.
I'm not sure if this is the right way to propose mini projects,
but in case the answer is not no, may I suggest one:
Motivation, the problem:
Since commit
Michael Haggerty mhag...@alum.mit.edu writes:
See my branch on GitHub [1] or read the appended text below.
Very nice.
## Introduction
It is strongly recommended that students who want to apply to the Git
project for the Summer of Code 2014 should submit a small code-related
patch to the
On 02/26/2014 08:48 PM, Junio C Hamano wrote:
Michael Haggerty mhag...@alum.mit.edu writes:
See my branch on GitHub [1] or read the appended text below.
Very nice.
## Introduction
It is strongly recommended that students who want to apply to the Git
project for the Summer of Code 2014
I'm pleased to announce that Git has been accepted to this year's Google
Summer of Code.
Student proposals will start coming in on March 22. In the meantime
students will be reading our Ideas page[1] and enquiring about the
program on the mailing list and on irc. There are many ways that
existing
Hi.
I was just going to write an email about that I would like to
participate in GSoC and contribute to Git project.
I don't have wide experience in C programming, but I could be start as a
janitor. I found several tasks here
https://git.wiki.kernel.org/index.php/Janitor. For example
On 02/25/2014 04:41 PM, Jeff King wrote:
I'm pleased to announce that Git has been accepted to this year's Google
Summer of Code.
Cool! Thanks to Peff and Thomas and Vicent and whomever else was
involved in getting our application done! For those who don't know, the
application covers both
20 matches
Mail list logo
