linuxmint / linuxmint/mintupdate
Enhance the history of updates with size and maybe network name
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 425
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Flatpak updates can be very large and it would be useful to be able to track how much data they pull in. This makes it easier to decide if having certain Flatpak apps is worth it or not.
Describe the solution you'd like
The simplest solution:
- add a "Size" column in the history view.
A more elaborate solution:
- additionally, allow range select, and even Ctrl+click to add other items outside of a range, to display the total size of the selected updates
An even more elaborate solution:
- additionally, add buttons for update sizes based on type (
All, or a specific type) and period of time (This Month,Past 3/6 Months,This Year,Specific Year,All Time)
The latter solution can cache its results for optimal performance, but a re-analyze button would serve well to recover from any data corruption with the existing stats, or if new types get added.
Optional (but useful and also nice to show off): Allow exporting the data to CSV, so people can make custom graphs. This would obviously be more useful to sysadmins (especially for data aggregation) and people who have network traffic constraints.
The complication with the CSV export is that there would be an obvious need for a new column to indicate which network was used to update. There's no perfect solution here because people can use different wired connections that can be metered or not. So it would be entirely up to them to correlate the network name with the date and time of the updates, but adding the network name would be useful.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the history view and the existing update-history data in the Mint Update Manager codebase. First clarify which scope is wanted: a Size column, selection totals, period/type summaries, or CSV and network metadata. Done should include an agreed scope, displayed or exported size data, and verification that the history view reports it correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100