On Tue, 11 Mar 2025 at 05:41, Kashyap Chamarthy <kchamart@xxxxxxxxxx> wrote:
On Sat, Mar 08, 2025 at 07:50:49AM +0000, Richard W.M. Jones wrote:
> On Fri, Mar 07, 2025 at 12:56:21PM -0800, Brendan Conoboy wrote:
attestation report? Something else? I didn't get a direct answer to
this, but the presenter (Mike McLean) said he was there to share how
_he_ is using Konflux to build RPMs.
Fair enough, but my question remains: did the Konflux project consider
the option of investing this effort into Koji to produce the artifacts
they need? Maybe it was already considered and ruled out due to valid
As far as I know Mike Mclean is part(most?) of the Koji development team. This seems similar to the X/Wayland debate. The same people who are working on Wayland are the ones who maintain X but it gets asked why Wayland is getting resources and X isn't.. because the people working on both have decided to focus on one. Mike has decided to focus on helping Konflux.
In the end, I think Konflux is getting more resources overall because it is meant to solve multiple problems which could be sold as services. Koji/brew was really meant to solve a problem: allow multiple developers to batch build RPMs using a central resource system. That just turns out to be part of the technical problems in building an distribution 'ecosystem'.
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
