Open PRs with Packit config for new Fedora packages

[lbarcziova]

This is a follow-up of the discussion on Flock, where this idea came up.

TODO:

• listen to the messages about new package repository in dist-git (check which one is the best fit, e.g. pagure.project.new)

  • if we can’t be sure the repo is prepared for accepting the PRs in that moment, implement scheduling the task later (e.g. after 24h)

• open PRs for those

  • description should contain brief introduction to Packit and downstream automation capabilities
  • PR should contain a default Packit configuration (created by packit dist-git init)

Notes from refinement

• It would also be possible to keep a list of newly added packages and manually onboard them, e.g., once a week
• Open up a Fedora Discussion about this

[lachmanfrantisek]

Here's a list of issues tracking new repositories being created so we can see the frequency:
https://pagure.io/releng/fedora-scm-requests/issues?status=all&search_pattern=new+repo&close_status=

[nforro]

We decided to make this a Fedora Change, here is an issue to file a Change Proposal.

[lbarcziova]

One note to the functionality itself we probably haven't considered so far, we should probably also handle adding the project to release-monitoring.org as this is now not automatic for new packages, and also enabling the monitoring (or just including these instructions in the PR description, though that would lead to worse UX).

[lachmanfrantisek]

Today, we discussed the possibility of starting with the opt-in approach and waiting for Fedora Change with the opt-out, but agreed on not doing this and rather wait either for the approval or at least for the discussion around the change. The opt-in approach does not provide much benefit.