From: Junio C Hamano <gitster@pobox.com>
To: Robear Selwans <rwagih.rw@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC][GSOC] Microproject Suggestion
Date: Thu, 13 Feb 2020 17:41:18 -0800 [thread overview]
Message-ID: <xmqqy2t6osht.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CALH1-Xr_pK02j6_51EnZN=ZrSz6dijt9tn0ANJ21331GzAmBdQ@mail.gmail.com> (Robear Selwans's message of "Fri, 14 Feb 2020 02:52:00 +0200")
Robear Selwans <rwagih.rw@gmail.com> writes:
> Hi, so it came to my attention that GSOC applicants will need to
> submit a microproject to be considered. I was thinking about ...
> So does that sound like a good idea?
Not really.
The purpose of a GSoC microproject is not about producing useful end
user product. It is to learn the end-to-end flow, starting from the
initial submission, interacting with the reviewers to polish the
patch, to reach the final version. For that purpose, we'd prefer a
bite-sized project (and that is why it is called "micro")---my
personal gut-feeling yardstick is that anything that takes more than
30 minutes to finish by an experienced Git developer to come up with
a perfect model answer is too big.
As a real patch for you to get your toes into Git development,
outside the scope of GSoC, I think it would be a good sized first
patch. It is a bit too big for a microproject, and it is a bit too
small for a main GSoC project.
For the feature itself, I'd just do
$ git reset --soft HEAD~$n ;# rewind
$ git commit --amend
to open an editor, and then to the editor to edit the log message,
I'd tell it to insert "git log ..@{1}" to the edit buffer to help me
formulate the log message for the consolidated change, so I do not
personally see me using it, even if it were available.
Thanks.
next prev parent reply other threads:[~2020-02-14 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 0:52 [RFC][GSOC] Microproject Suggestion Robear Selwans
2020-02-14 1:41 ` Junio C Hamano [this message]
2020-02-14 7:29 ` Robear Selwans
2020-02-14 8:49 ` Denton Liu
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy2t6osht.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rwagih.rw@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).