On Fri, Sep 20, 2024 at 10:02 PM Maxwell G <maxwell@xxxxxxx> wrote: > > On 9/20/24 10:33 AM, Nikola Forró wrote: > > Hi, > > Thanks for the announcement and the informative Flock talk! > > > based on a discussion after Packit talk [1] at Flock, to ease Packit > > onboarding [2], we are planning to automatically open pull requests > > with autogenerated Packit configuration file in newly created projects > > at src.fedoraproject.org, along with a description and instructions > > on how the automation works and how it can be adjusted. > > Have you considered filing a Change Proposal after the plan for the > opt-out/configuration mechanism you mentioned is more concrete? This > way, it can get wider feedback and formal FESCo approval before being > rolled out and packagers won't get surprised by the automated PRs. > > > We want to give package maintainers the option to opt-out or to tweak > > the defaults (for example disabling certain jobs or adjusting default > > permissions). It probably makes sense to do that per maintainer, > > i.e. FAS username, however we would like to know what you think would be > > the best way to handle it - ideas are welcome. > Yeah, I definitely think some sort of configuration per package type > (one for all golang-* packages, one for rust-* packages, one for > python-* packages, etc.) is important here. For example, Rust crates > will need a configuration that regenerates the specfile with rust2rpm > each time. Other package types may be ill-suited for Packit and need to > be opted out entirely. Making this a Change Proposal (or something similar) sounds like a good idea. Speaking for Rust, the default configuration of packit *will* result in broken packages, so filing PRs for those would be actively harmful without some kind of special handling. Fabio -- _______________________________________________ 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