On Wed, Apr 6, 2022 at 5:51 PM Jared Dominguez jaredz@redhat.com wrote:
[snip]
Per my reply to you yesterday, I would be grateful if you would list out examples here. This is the second time I've heard this, and it's not concrete enough for a constructive conversation on that topic.
- The packages are locked down so there is no way for the community to help
- At various times, people have explicitly said "patches NOT welcome"
Robbie already responded to this, but I would like to add that if any of this ever actually becomes true, I would like to know so that I can address any such issue with this Red Hat team. From what I've seen, we very much welcome community involvement. In fact, we are collaborating on a daily basis with the bootloader community on grub2 and shim development.
As Robbied said, I added the /etc/dnf/protected.d/grub2-*.conf to the grub2 package after Neal filed that BZ and he also mentioned to me back then that pull requests were disabled for the grub2 dist-git and I re-enabled it after asking Peter if he was OK with that (and he told me that sure go ahead).
BTW, Peter also did the same for shim and added /etc/dnf/protected.d/shim.conf even though the dist-git for shim was open at the time. So I don't see how grub2 dist-git not having pull requests enabled (for whatever reasons) could be a blocker since a change for shim wasn't proposed either. I mean, one could attach a patch in the BZ, send an email to a maintainer, etc. Is not that PRs in dist-git is not the only possible way to share a diff...
Anyway, I also personally never said "patches NOT welcome" to anyone. It may be that I didn't have time to review/apply some proposed but that's a different thing.
Best regards, Javier