Hi Knurd,
Thanks for the feedback!
On Fri, Jun 05, 2020 at 02:24:13PM +0200, Thorsten Leemhuis wrote:
Lo! I'm slightly puzzled. These messages are now sent to
fedora-kernel-list, which kinda sounds like input from the fedora
community is wanted. But all this discussions look RHEL-specific to me.
Yes.
Or am I missing something? Fedora at least seems to enable
CONFIG_SENSORS_AMD_ENERGY if I read
https://gitlab.com/cki-project/kernel-ark/-/blob/os-build/redhat/configs/...
right. And that file is not touched by the patch. So from a perspective
of someone Fedora developer that subscribes to fedora-kernel-list this
and similar messages look like useless noise – and at the same time they
are hard to read, as it's not easy to see if a patch is relevant for
Fedora or not.
It is easy to see this as useless noise.
The original goal was to setup the Fedora kernel as the kernel RHEL is
derived from without negatively impacting Fedora's mission.
The hope would be to allow us to point our partners and customers towards
the Fedora kernel for early development and testing. Thus growing the kernel
community here and making a positive impact on the Fedora kernel overall.
However, that leads us to a situation about the kernel configs. Obviously
the Fedora and RHEL configs have different audiences, hence the internal
split.
But how to handle the changes? From a Fedora perspective, the Fedora kernel
maintainers make a best guess and commit things behind the scenes, no email
noise. If they get it wrong or if a modification is requested, a simple
email or irc poke is generally good enough.
RHEL is a little more structured and requires feedback from the stakeholders
of that subsystem. This added communication creates the noise you are
mentioning.
The aim was for some transparency so others (partners, customers and
community) could chime in with feedback if they wanted to help influence
RHEL. It was also thought, this noise usually stems from -rc1 fallout and
is only noisy every 8 weeks or so.
We could move this noise to another list, but the fear is confusion about
what changes are posted to what list.
I am open to suggestions to help create a better experience here. Would
adding a keyword in the subject line help filter this? Something else?
Maybe another mailing list for configs is something to bring back up?
Hopefully that explains the motivation, background and how we ended up here.
Please keep the feedback coming, we will slowly work through this!
Thanks!
Cheers,
Don