Repository Intention

[seanenck]

What is the true relation between this (and the other redhat-plumbers) repositories and the actual upstream at this point? Fedora generally tracks spec files in pagure and yet here there is a spec file and changes to the workflow actions here though this will not be part of a normal Fedora build/release at this time (isn't that just fully duplicate work at this point)?

Additionally this creates a lot of confusion about upstream/downstream and packaging. Is Fedora going to cut releases from this repository and therefore this is a full fork? Is the relationship then that upstream will be merged in at points? Does Fedora (and RedHat) no longer work items upstream to support other distributions?

Is this repository actually used for anything at all or just a public testbed for ideas?

There is a lot of confusing information to be found here:

• https://src.fedoraproject.org/rpms/dracut/pull-request/54
• fix(90kernel-modules): fix MMC and NVMe on kernels 6.0+ dracutdevs/dracut#2103 (comment)

[pvalena]

Sorry, I didn't get around to writing a README yet. This is a source-git, as you've correctly identified downstream PR, it was generated from this state (without any other manual work). So consider this on par with dist-git (inheritance can go both ways), as it should never diverge.

The plan is to have the changes fully automated, so when PR gets merged here (i.e. new commits land), a new PR with changes gets opened to pagure.

I've elaborated on a relation with upstream in the downstream PR, hopefully it's clear enough. There's no plan to diverge from upstream at all. Source-git actually helps getting feedback to upstream better (please see packit docs on source-git[1]).

[1] https://packit.dev/source-git