git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Reviewed-by given by celebrities (no subject matter expertise on Git development)
Date: Sat, 03 Apr 2021 19:27:12 -0700	[thread overview]
Message-ID: <xmqqeefqzsvz.fsf@gitster.g> (raw)
In-Reply-To: <345a7b27-8ee4-4b64-0340-40b002a25d1f@gmail.com> (Bagas Sanjaya's message of "Fri, 2 Apr 2021 12:45:45 +0700")

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> Junio, what will you do in such situation above (celebrities reviewing
> patches and giving Reviewed-by despite of lack of subject matter
> expertise)?

I find the scenario highly unlikely, and I do not see the point of
wasting my time on a trick question, thinking about what I would do
in a scenario that is not realistic, so I was tempted to ignore this
message.  If you have something you really want to ask, ask it
directly instead.

But I'll make it an exception this case, since you are relatively
new.

I do not think the celebrity status of a person who sends a
Reviewed-by matters.  What matters aroud here is the quality of
review that comes with "Reviewed-by".

Just a "Reviewed-by" without comments would most likely not count at
all, unless the perceived competence and expertise the reviewer
possesses in the area is reasonably high.

The "perceived" is a rather important word here.  It does not matter
how good one actually is.  One must have had demonstrated one's
competence and expertise on the list sufficiently to earn trust by
other readers on the list for one's "Reviewed-by" to really count.

"I read the patch with fine toothed comb, I found it very well done,
I have nothing else to add.", coming from somebody who is KNOWN to
know the area the patch touches well, would mean a lot.  When the
same statement was given by somebody who hasn't earned the trust of
the collective mind on the list, regardless of the celebrity status,
would mean a lot less.

  reply	other threads:[~2021-04-04  2:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02  5:45 Reviewed-by given by celebrities (no subject matter expertise on Git development) Bagas Sanjaya
2021-04-04  2:27 ` Junio C Hamano [this message]
2021-04-07 20:24   ` Jeff King
2021-04-07 20:57     ` Junio C Hamano
2021-04-07 21:18       ` Jeff King

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=xmqqeefqzsvz.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    /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).