Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Try to onboard package(s) of FAS user mhayden for Fedora downstream automation #2239

Open
6 tasks
Tracked by #2204
lbarcziova opened this issue Oct 27, 2023 · 1 comment
Open
6 tasks
Tracked by #2204
Assignees
Labels
area/fedora Related to Fedora ecosystem blocked We are blocked! complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/other Other kind than the specified ones.

Comments

@lbarcziova
Copy link
Member

lbarcziova commented Oct 27, 2023

Followup of #2227

  • check whether the maintainer already uses Packit, if yes, contact them and ask about the feedback, offer help with setting up Packit for their other packages

If no:

  • contact the maintainer, introduce Packit downstream automation and ask if you could create a PR with Packit config for one of their packages (you can ask whether they have access to the upstream repos or would be interested in having the config only in dist-git)

After an agreement:

  • check this spreadsheet for the list of packages and choose one (ideally with pending release to rebase, having Git upstream, easy to configure),
    • the spreadsheet should be updated accordingly, make sure that the package was not onboarded already (there is overlap of the packages since they can have multiple maintainers)
  • create a Packit configuration setting up the Fedora downstream automation (for syncing start with one branch to not spam)
  • optionally test the syncing locally (see comment)
  • create a PR, try to do a test run (/packit pull-from-upstream --with-pr-config) and communicate further with the maintainer the follow-up steps (e.g. create issues if some functionality is missing, setup on more of their packages)

Part of #2204 epic

@lbarcziova lbarcziova added area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. impact/low This issue impacts only a few users. gain/high This brings a lot of value to (not strictly a lot of) users. kind/other Other kind than the specified ones. labels Oct 30, 2023
@lachmanfrantisek lachmanfrantisek added blocked We are blocked! and removed blocked We are blocked! labels Nov 2, 2023
@majamassarini majamassarini added the blocked We are blocked! label Nov 27, 2023
@lachmanfrantisek
Copy link
Member

Requires #2343

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/fedora Related to Fedora ecosystem blocked We are blocked! complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/other Other kind than the specified ones.
Projects
Status: in-progress
Development

No branches or pull requests

3 participants