I love this part in particular:

"If you are someone who is familiar to the maintainers, and know that they already trust you to make high quality contributions, your contribution must still genuinely be understood and created personally by you, regardless of what tools you may use to assist you."

👍️

Yup, the smoking challenge, patience vs hunger.

What'd ya smoke? Today I did dove poppers. Instead of just green jalapenos I swapped out half for red jalapenos, which was a great choice. Next time I'll probably do all red.

This is pretty standard practice, and follows the Fedora packaging guidelines.

> The intent is to give the user a hint as to what changed in a package update without overwhelming them with the technical details. They must never simply contain an entire copy of the source CHANGELOG entries.

https://docs.fedoraproject.org/en-US/packaging-guidelines/#changelogs

It sounds like what you're looking for is the upstream changelog.

https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/1.6.4/NEWS

Sure, I can take care of that. First pass posted on the bug.

If you want to review swap, I've got this one in the queue. A few people have commented, but so far no one has assigned it to themselves.

https://bugzilla.redhat.com/show_bug.cgi?id=2439787

The dnf devs didn't preserve the old dnf4 syntax, but the dnf5 setopt syntax still works since it's usable for setting other options as well.

Indeed, that is the even older dnf4 syntax. It's probably the most common thing you'll find online since CentOS/RHEL still uses it. Basically the syntax started ok, got worse initially in dnf5, and now it's better (shorter) than ever.

You're just talking nonsense now. Clearly you're not a serious person, in addition to not know how RHEL and CentOS work.

Clearly not. If you don't know how something works, it's ok to just not comment on it at all. And if you do comment on it and later find out you're wrong, it's ok to admit it.