All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Sidhant Sharma <tigerkid001@gmail.com>
Cc: Lars Schneider <larsxschneider@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC/GSoC] Introduction
Date: Sun, 20 Mar 2016 21:17:59 +0100	[thread overview]
Message-ID: <vpqwpow9a4o.fsf@anie.imag.fr> (raw)
In-Reply-To: <56E6DF17.2040106@gmail.com> (Sidhant Sharma's message of "Mon, 14 Mar 2016 21:26:07 +0530")

Sidhant Sharma <tigerkid001@gmail.com> writes:

> On Monday 14 March 2016 01:46 PM, Lars Schneider wrote:
>
>> I also thought about (2). The obvious advantage of having something like 
>> "ggit" as part of Git core is that it would be shipped with the standard
>> Git distribution. That would especially help beginners.

Yes. And that would allow any tutorial to start with something like
"Since you're a beginner, use the command ggit instead of git. When
you're confident enough, just drop the first 'g' and continue hacking."

Asking a beginner to install a separate tool before starting is a show
stopper to me. Or at least, it should be _very_ easy to install.

> I understand that this endeavour may or may not be merged into
> the official Git distribution (though I'd really like it to :)), but
> I still wish to attempt this. I'm also eager to continue work on this
> even after GSoC is over, so maintenance shouldn't be an issue ;)

My usual advice on this point (both for mentors and students): hope that
you will continue contributing after the end of the project, but plan as
if you won't. You don't want the survival of your code to depend only on
you.

I have experience similar to GSoC where I offer CS students to
contribute to open-source software as part of a school project. Almost
all of them told me that they would continue after and essentially none
of them did. I think at least most of them were sincere when they said
they would continue, but then they realize that days have only 24 hours
and life is short ;-).

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2016-03-20 20:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-12  6:59 [RFC/GSoC] Introduction Sidhant Sharma
2016-03-13 15:50 ` Lars Schneider
2016-03-13 18:33   ` Sidhant Sharma
2016-03-13 21:19     ` Kevin Daudt
2016-03-14  5:25       ` Sidhant Sharma
2016-03-14  6:15         ` Jacob Keller
2016-03-14  7:01       ` Junio C Hamano
2016-03-13 23:28     ` Jacob Keller
2016-03-14  5:25       ` Sidhant Sharma
2016-03-14  6:14         ` Jacob Keller
2016-03-14 16:00           ` Sidhant Sharma
2016-03-14  6:57   ` Junio C Hamano
2016-03-14  8:16     ` Lars Schneider
2016-03-14 15:56       ` Sidhant Sharma
2016-03-20 20:17         ` Matthieu Moy [this message]
2016-03-14 17:25       ` Junio C Hamano
2016-03-20 20:28         ` Matthieu Moy
2016-03-14 21:08       ` Philip Oakley
2016-03-17 14:52   ` Sidhant Sharma
2016-03-20 15:39     ` Lars Schneider
2016-03-20 15:51       ` Sidhant Sharma
2016-03-20 16:08         ` Lars Schneider
2016-03-20 16:22           ` Sidhant Sharma
  -- strict thread matches above, loose matches on Subject: below --
2016-03-22 17:51 Philip Oakley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vpqwpow9a4o.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=larsxschneider@gmail.com \
    --cc=tigerkid001@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.