git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: vk <g@vkabc.me>, git@vger.kernel.org
Subject: Re: [GSoC] Microproject help
Date: Mon, 25 Mar 2024 22:59:14 -0400	[thread overview]
Message-ID: <CAPig+cSGWMDXh8FQXH=Qca8g61BMOdVJnsirnL4zUJHvSrAfAw@mail.gmail.com> (raw)
In-Reply-To: <xmqqv85aezxe.fsf@gitster.g>

On Mon, Mar 25, 2024 at 5:58 PM Junio C Hamano <gitster@pobox.com> wrote:
> During today's discussion, we came up another interesting one.
>
>     Follow one of our three tutorial documents to the letter to see
>     if they need adjusting, and come up with a set of patches to
>     adjust them.
>
> This kills a few birds with a stone.
>
>  - The student has to be familiar with the codebase and MyFirst
>    tutorials are meant as a gentle "dip your toes in the water"
>    introduction.  Following the examples and copy-pasting code
>    snippet and trying to build would be useful exercise for GSoC
>    candidates by itself.
>
>  - These tutorials, unfortunately, haven't been maintained as well
>    as they should have been, and some do not compile any longer due
>    to API changes, header shuffling, etc.  Identifying such breakages
>    and reporting them as bugs is already useful by itself, even if
>    the student does not manage to fix them.
>
>  - But if the GSoC student can learn to address such a bug (which
>    requires use of "git log" and "git blame" to spelunk where the
>    breakage happened, after which it would be obvious what the right
>    fix would be), that is valuable exercise by itself, even if it
>    does not reach the "patch submission" stage.
>
>  - And of course, the result of such a work can go through the usual
>    patch review cycle, which would serve as a microproject.
>
> Hmm?

That sounds like a reasonable project, as well.


      reply	other threads:[~2024-03-26  2:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 13:10 [GSoC] Microproject help vk
2024-03-25 18:25 ` Karthik Nayak
2024-03-26 11:56   ` vk
2024-03-27  6:36     ` Patrick Steinhardt
2024-03-29  3:57       ` vk
2024-04-02 10:35         ` Patrick Steinhardt
2024-03-29  5:46       ` Junio C Hamano
2024-04-02  9:52         ` Patrick Steinhardt
2024-03-25 20:51 ` Eric Sunshine
2024-03-25 21:23   ` Junio C Hamano
2024-03-25 21:37     ` Eric Sunshine
2024-03-25 21:58       ` Junio C Hamano
2024-03-26  2:59         ` Eric Sunshine [this message]

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='CAPig+cSGWMDXh8FQXH=Qca8g61BMOdVJnsirnL4zUJHvSrAfAw@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=g@vkabc.me \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).