for an rss On Wed, Aug 6, 2025 at 6:27 AM Thorsten Leemhuis <fed...@leemhuis.info> wrote: > > On 04.08.25 21:06, Justin Forbes wrote: > > When we started the migration to gitlab/kernel-ark for maintaining the > > Fedora kernel, an email bridge was created to help facilitate > > awareness of what was going on in that space. > > FWIW a quick note from a non-rh contributor that follows Fedora's > kernel development closely for more than two decades now: > > I understand this step (and others that lead to the creation of > kernel-ark). Nevertheless it bothers me somewhat, as I think we over > time more and more lost the "watch this mailing list and the commits > <over there> and you'll soon learn how Fedora's kernel is developed"[1]. > > And I wonder if this is something that will bite us in the long run, as > it imho makes things hard for newcomers[2] to find there way in; > together with other small annoying things, among them "links to > non-public rh-interna jira issues in kernel-ark merge requests and > commits" or "you can subscribe to merge requests on kernel-ark, but be > prepared to get drowned in noise from the CI bot".
That's part of the problem, the Jira bits, and frankly the majority of the traffic is not really relevant to Fedora at all. If it is for Fedora, it is tracked in Bugzilla (at the moment). As a result, the mailing list traffic was more of a RHEL next kernel list than a Fedora kernel list. And the few MRs that were actually relevant to Fedora get lost in the noise. If you do subscribe to the merge requests, you can always add a second filter to send the bot messages to /dev/null. They are pretty easy to filter. > But maybe that's just how it is these days and I only consider this to > be a problem because I got the feeling that it would scare me away if I > joined Fedora today and wanted to contribute to its kernel. I am hoping by keeping this list more relevant to the Fedora kernel, it becomes easier, or at least less intimidating for new contributors. > Just wanted to share this. Don't think there is anything easy we could > do to improve things[3]. > > Ciao, Thorsten > > [1] yes, there is https://src.fedoraproject.org/rpms/kernel/commits/, > but it makes it hard, as kernel-ark specific changes are squashed there; > cloning kernel-ark and the running "git log > kernel-ark/master..kernel-ark/os-build" will give you something nice, > but I failed to find something like that in the gitlab webui (ideally > subscribable by rss!); but maybe I did not look hard enough (I found > http://gitlab.com/cki-project/kernel-ark/-/compare/master..os-build, but > that is somewhat different and not really helpful). I do subscribe to https://gitlab.com/cki-project/kernel-ark.atom for an rss feed, but it does also get the bot traffic. Depending on your reader, you might also be able to set up something which tracks https://gitlab.com/cki-project/kernel-ark/-/commits/os-build > [2] yes, sure, gitlab makes some thing easier for them > > [3] I first wanted to suggest "link to the individual kernel-ark > specific commits in the git commit message for dist.git", but then I > thought "ahh, no, I guess that's not worth the trouble". -- _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
