Yeah, I broadly agree with what smooge noted here. The idea isn't to just swap konflux in for koji and call it a day, but rather to use konflux as a build pipeline.
The promise of konflux I could see it taking on things that are currently done by: pkgs / src.fedoraproject.org - it could download sources and verify them, removing the need to upload in many cases. robosignatory/sigul - it could handle signing artifacts and coordinating what artifacts are signed when by what. bodhi - bodhi could get out of the business of composing things and move to just being a UI to test and provide info back to konflux and others possibly. The things that I liked about what I have heard include ability for releng to define the pipeline of whats 'official', but at the same time users / sigs could define what they want to produce/distribute. As for other arches, my understanding is that for those all thats required is builder nodes of that arch. konflux will connect to them and build, no need for a bunch of extra clusters. I share some other folks concerns with some things I have seen, like I am not sure if the openshift permissions model will work for us, and the rpm building stuff is still really early, etc. I think there's a lot of promise, but to answer the question in the subject, I think the right time to discuss this in detail is probibly later this year when more things are known/have had time to develop, but by all means folks should look at provide feedback as they can. kevin -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
