Learn more about these different git repos.
Other Git URLs
The https://pagure.io/releng/fedora-scm-requests/ project is used for few things:
The first two tasks are requested by tickets at: https://pagure.io/releng/fedora-scm-requests/issues and processed by releng using fedrepo-req.
The last two tasks are requested by PRs and could be automatically reviewed and merged.
I would like to propose that we do this automation, all it requires is checking that the person opening the ticket has ACLs on the project (up to us if we want to limit this to admins for example). If these people have ACL on the project, then it's just like on pkgdb before, we let the users configure things the way they want. I do not think there is a good reason to be blocking any changes the maintainers want to do on their package.
admins
Thoughts?
Metadata Update from @ausil: - Issue tagged with: meeting
Ask for a new package to be added to the distro
Can never be automated.
Ask for a new branch on an existing package
It can automated in the future but not right now as it needs lots of checks.
Tune the anitya integration flag Set bugzilla overrides (so EPEL bugs go to a different person than the Fedora ones)
These can be automated.
Ask for a new package to be added to the distro Can never be automated.
Well, it could but that's a different discussion, it's not what this ticket is about :)
Ask for a new branch on an existing package It can automated in the future but not right now as it needs lots of checks.
Same as above, this is not the point of this ticket :)
Tune the anitya integration flag Set bugzilla overrides (so EPEL bugs go to a different person than the Fedora ones) These can be automated.
This is what this ticket is asking for :)
@pingou As long you are automating
you are good to go.
@pingou , any update?
@mohanboddu, what's the action here? Who is doing the automation?
From our grooming discussion on #fedora-releng channel on Apr 12 2019
proposal: note that pingou has a proof of concept version for anytia integration as a pagure plugin, ask him if we can do that for the bugzilla overrides and where he would like to track that (if not here, point to that and close this)
@pingou , any update on this ticket?
@pingou I think this can be closed now.
Agreed, soonish the git repo in that project will no longer be used.
Metadata Update from @pingou: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.