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

RFE: Make f-u-f easier to use for new users #5

Open
genodeftest opened this issue Oct 10, 2021 · 1 comment
Open

RFE: Make f-u-f easier to use for new users #5

genodeftest opened this issue Oct 10, 2021 · 1 comment

Comments

@genodeftest
Copy link

Thanks for this nice tool!

I've been using fedora-easy-karma regularly many years ago and just started fedora-update-feedback today on Fedora 35 beta. I found the large number of packages waiting for an update quite overwhelming (62 updates). Although I think I know quite much about fedora, I really would be unable to judge whether a package is being used for every single package.

That said, how about providing an overview page at start where users have some of the info in a table as an overview before starting the feedback? This table could consist of e.g. package name, update type, current karma, (maybe stable karma), number of linked bugs, number of comments. Then it would be useful to have some kind of selection mechanism (maybe ncurses-like) to "select all" (the current default), "select none" and manually selecting some of the listed updates (e.g. by arrow up/down + pressing the space key).

PS: I know this is just a vague idea so feel free to close if it is too vague or too much work to do.

@decathorpe
Copy link
Member

The number of updates in updates-testing should not be so large except during the pre-release phase, so this should be less of a problem later.

Since the tool is right now just written as "loop over all updates installed from updates-testing, sorted by publication date, and skip ignored updates", I'm not sure how I would integrate such an overview functionality.

However: I've been thinking about / experimenting with writing a simple GUI for the tool (with the same backend code, but a nice GTK interface instead of the terminal promts), which would probably work similarly to what you describe above. If I ever find the time to continue working on that ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants