public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Mahendra Dani <danimahendra0904@gmail.com>
Cc: JAYATHEERTH K <jayatheerthkulkarni2005@gmail.com>,  git@vger.kernel.org
Subject: Re: [GSoC] Microproject: Updating Documentation
Date: Sat, 08 Mar 2025 13:29:42 -0800	[thread overview]
Message-ID: <xmqqo6ybb48p.fsf@gitster.g> (raw)
In-Reply-To: <CABGrwBDLO9=FCjUW_LfJ_RZ95bRXWHFFNvdJfOuiYocGXdj3Mg@mail.gmail.com> (Mahendra Dani's message of "Sat, 8 Mar 2025 23:03:45 +0530")

Mahendra Dani <danimahendra0904@gmail.com> writes:

> I'd suggest trying to submit a microproject listed in [1]. Further,
> please go through the General Microproject Information[2] and
> MyFirstContribution[3].

All good suggestions, but we also welcome students who try to
scratch their own itch, as long as it is small enough to be suitable
as a microproject material.  And it is fine to ask if doing X
qualifies as a microproject or if it is too involved.

The primary objective for a micro-project is to get used to the
workflow, i.e. working with the community mainly via this mailing
list, how you explain your changes in your proposed commit log
message, how to work with those who gave you reviews, how your
updated submission should look like, etc., etc.  Given that, it is
rare that anything is too trivial as a microproject material, but
you would not want to choose something too involved, as it would
slow you down in learning the procedure, which is the main focus on
the microproject period.

Another thing I noticed in the original message that is worth
reacting is that you do not need to ask for permission to start
working on anything around here.  "Am I allowed to do X for my
microproject" is not the question you want to ask; rather "I see
document X says A, B, and C, but A is outdated and I think it is
better to phrase it like D.  Would it be a suitable microproject
material?" is something we can work with. Answers may depend on the
nature of A, B, C, and D and would range from "nah, A is fine and D
is not better because ...; don't do it" to "great, yes A may have
been suitable a decade ago, but no longer relevant, and D would be a
great addition", to "Yeah, I agree that A is not great, but D is not
all that better, how about E?", to "Yes that is a great suggestion,
but wouldn't it may be a bit too much as a microproject".

To solicit such productive reaction from others, you'd need to be a
bit more specific than "I see flaws and want to improve".

Thanks, and good luck with your microproject selection.

  reply	other threads:[~2025-03-08 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-08 15:41 [GSoC] Microproject: Updating Documentation JAYATHEERTH K
2025-03-08 17:33 ` Mahendra Dani
2025-03-08 21:29   ` Junio C Hamano [this message]
2025-03-09  9:59     ` JAYATHEERTH K
2025-03-09 14:55       ` JAYATHEERTH K
2025-03-10 21:45       ` Karthik Nayak
2025-03-12  8:19         ` JAYATHEERTH K

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=xmqqo6ybb48p.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=danimahendra0904@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jayatheerthkulkarni2005@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox