From: "Maciej Barć" <xgqt@gentoo.org>
To: Eli Schwartz <eschwartz93@gmail.com>, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] .github: Add pull request template
Date: Wed, 1 May 2024 17:18:45 +0200 [thread overview]
Message-ID: <507bc969-5620-40fd-8c82-a1ac3c84d160@gentoo.org> (raw)
In-Reply-To: <8ddd270b-e7f4-49a0-a348-a57fc87bcc4b@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2215 bytes --]
> Maybe the solution here is that developers who merge patches from
> contributors should test the PR before merging.
Of source, of course they should! (thats how the bug was discovered in
the case I recalled). It's all about communicating to the contributor
the most important things that we expect in the PR --- if not, then
whats the point of having the PR template?
W dniu 1.05.2024 o 17:15, Eli Schwartz pisze:
> On 5/1/24 11:02 AM, Maciej Barć wrote:
>> Well, not really, there were many cases where pkg was broken on sandbox!
>> The latest example would be nim (before I updated it myself) where
>> contributor submitted broken pkg without telling anybody. It was a WIP
>> PR but nowhere they specified that it did not merge under sandbox. I
>> want to encourage contributors to outright say when they know/think
>> something might be wrong with package.
>
> And adding another checkbox is going to stop people from submitting WIP
> draft PRs without marking them as drafts?
>
> Maybe the solution here is that developers who merge patches from
> contributors should test the PR before merging. At least if you don't
> have a preexisting relationship with the contributor such that you have
> trust in the contributor to publish high quality ebuilds that pass basic
> smoketests.
>
> I mean, you probably want to do that anyway because if someone shows up
> with their first ever PR and the change looks okay but has a broken
> checksum it is awfully hard to tell without actually running it. I
> certainly hope that if PRs are merged without being tested locally by
> the developer doing the merge, that it's for proxied packages
> contributed by the proxied maintainer, not packages where the Developer
> that maintains the package is merging untested patches just because
> someone suggested a change.
>
> And if proxied maintainers make a habit of breaking their packages by
> submitting WIP drafts maybe they aren't such great proxied maintainers
> and there's a larger infrastructural problem going on.
>
>
--
Have a great day!
~ Maciej XGQT Barć
https://wiki.gentoo.org/wiki/User:Xgqt
9B0A 4C5D 02A3 B43C 9D6F D6B1 14D7 4A1F 43A6 AC3C
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 16315 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2024-05-01 15:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 13:32 [gentoo-dev] [PATCH] .github: Add pull request template Michał Górny
2024-05-01 14:27 ` Maciej Barć
2024-05-01 14:47 ` Eli Schwartz
2024-05-01 15:02 ` Maciej Barć
2024-05-01 15:15 ` Eli Schwartz
2024-05-01 15:18 ` Maciej Barć [this message]
2024-05-01 14:59 ` Michał Górny
2024-05-01 15:14 ` Maciej Barć
2024-05-01 14:28 ` Ionen Wolkens
2024-05-01 14:38 ` Maciej Barć
2024-05-01 14:54 ` Eli Schwartz
2024-05-01 15:01 ` Ulrich Mueller
2024-05-01 15:05 ` Maciej Barć
2024-05-01 15:52 ` Ulrich Mueller
2024-05-01 16:00 ` Maciej Barć
2024-05-01 15:00 ` Michał Górny
2024-05-03 4:41 ` Sam James
2024-05-03 4:41 ` Sam James
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=507bc969-5620-40fd-8c82-a1ac3c84d160@gentoo.org \
--to=xgqt@gentoo.org \
--cc=eschwartz93@gmail.com \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox