Re: [PATCH 0/9] ci: make Git's GitHub workflow output much more helpful

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 1, 2022, 16:52 UTC
Message-ID: <xmqqilsxsjib.fsf@gitster.g>
In-Reply-To: <nycvar.QRO.7.76.6.2203011111150.11118@tvgsbejvaqbjf.bet>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 6 quoted lines

> Let me again state my goal clearly, because some readers seem to be
> confused and believe that I want to improve the developer experience of
> veterans of the Git mailing list who are more than capable of finding
> their way through the build failures.
>
> My goal is instead to make new contributors' lives easier.

I understand who your primary target audiences are, and making them happy without robbing too much from others is a good thing to do. Instead of "Nah, this is not targetted for me" and ignoring the topic, I have been reporting my dogfood experience exactly to help that process---to notice if this variant worsens end-user experience and see if that is within the reasonable pros-and-cons tolerance, especially because they will start noticing the same hiccup as new contributors stay longer and gain experiences.

> In any case, thank you for integrating the patches into `seen` so that the
> impact of the patches can be "seen".

No, do not thank me. Thank yourself for writing it, and thank others to try it and tell you their experiences to help you make it better.

Thanks.