Re: [PATCH 2/2] doc: add another way to identify if a patch has been merged

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 2, 2017, 16:28 UTC
Message-ID: <xmqq60e6djcu.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <xmqqini6dkmu.fsf@gitster.mtv.corp.google.com>

Junio C Hamano <gitster@pobox.com> writes:

Show 14 quoted lines

> I think the exchange Stefan cited was an example that we want to
> have more of.  The contributor is indicating that, even though the
> patch could be a drive-by patch by one-timer from whom we will never
> hear again, it is not--the contributor is willing to learn the way
> things are done here, and showing that it is worth _our_ time to
> explain the things so that the future patches will take less effort
> to accept on our side.
>
> Because we do not have a group of dedicated volunteers, it is done
> by more experienced people around here but that can be done only
> when they have time.  I view it as a more severe problem than any
> documentation.  An abbreviated version of the documentation to
> invite more new people means that we must be prepared to give more
> high-touch onboarding help to them.

Just to make sure there is no misunderstanding, I am not saying "do not update the doc to have an abbreviated version, because we will get more clueless newbies". I am saying that it is not a good idea to add an abbreviated version _before_ we are prepared to handle more patches from new people that require high-touch help.

If you are volunteering to coordinate and form the onboarding helpers group, that would be great.

Thanks.