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 rdieter for Fedora downstream automation #2238

Closed
2 of 6 tasks
Tracked by #2204
lbarcziova opened this issue Oct 27, 2023 · 3 comments
Closed
2 of 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 (Matrix/Slack/email), 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
@mfocko mfocko moved this from new to backlog in Packit Kanban Board Oct 31, 2023
@lbarcziova lbarcziova moved this from backlog to ready-to-refine in Packit Kanban Board Dec 5, 2023
@lachmanfrantisek lachmanfrantisek moved this from ready-to-refine to refined in Packit Kanban Board Dec 7, 2023
@xsuchy xsuchy self-assigned this Jan 4, 2024
@xsuchy xsuchy moved this from refined to in-progress in Packit Kanban Board Jan 4, 2024
@xsuchy
Copy link
Contributor

xsuchy commented Jan 5, 2024

Does not uses Packit.

For lots of packages he is a comaintainer. But
https://src.fedoraproject.org/rpms/filelight
can be good candidate.

@xsuchy
Copy link
Contributor

xsuchy commented Jan 5, 2024

Email sent.

@lbarcziova lbarcziova added the blocked We are blocked! label Mar 11, 2024
@xsuchy
Copy link
Contributor

xsuchy commented Apr 8, 2024

I wrote Rex several times. No response. Closing as he is likely not interested in.

@xsuchy xsuchy closed this as completed Apr 8, 2024
@github-project-automation github-project-automation bot moved this from in-progress to done in Packit Kanban Board Apr 8, 2024
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
Archived in project
Development

No branches or pull requests

2 participants