This bug report is an attempt to reference existing bugs that have the greatest impact on the environment (power consumption, resources, etc.) over the entire lifecycle of the end user's computer and its local network.
How Skia is relevant here?
> How Skia is relevant here? Hardware rendering allows Libreoffice to run specific binary code that makes optimal use of the hardware. In addition, it can increase the use of parallelism and thus optimize the resources usage during the lifecycle of a computer (the computer lasts longer, etc).
I have added the meta-bugs for dark modes as they make it possible to use lower lighting conditions around the screen. Also, non-backlit displays have lower power consumption with a dark mode.
This is kind of a stretch with no functional requirement to track "environmental impact of end user's computer" nothing resulting would be actionable. Energy use, illumination levels, sound, repetitive stress risk--none are fundamental concerns for LibreOffice project development and this META just causes thrash of the projects Bugzilla issue tracker Please remove the noise.
What's the extra value of this META here? IMHO, this bugtracker should be set RESOLVED/INVALID. If you really want to help environment, either you're a programmer and you can try to fix perf/dark mode issues or you're not and you can try to collect money to pay people/companies to do it.
This can help an organisation to choose which bugs it will give money for.
This is just exploiting a buzzword, without any real estimation how much any of the imagined affecting bugs actually affect this. E.g., I asked how Skia affects this. And the idea that fixing Skia bugs affect the environmental footprint is absolutely fictional. The GPU performance of GPU-accelerated drawing could be higher, but it absolutely doesn't mean that the heaters called GPUs that people put into their boxes help lower the power consumption. Putting Memory here, alongside with GPU, is self-contradictory: most CPU-effective low-consumption algorithms have higher memory requirement, and vice versa. Only some specific memory problems could be considered affecting this, but not the whole category. Most 100% CPU consumption bugs are not "affecting environment", but simply bugs making software unusable; so putting them here is just trying to play on some emotions, where it's absolutely unneeded. And so on.
Changed dependencies from "depends on" to "see also" for many meta-bugs.
Jérôme: please discuss within the QA contributors group before doing decisions like this.
I agree with what has been said above. I think that the environmental impact of software (and technology in general) is a very important topic, but a bug tracker meta for this topic is too nebulous to be useful, it will create more noise than anything else. Alternatively, a kind of "project" page could be created, maybe on the wiki (after discussion with the community), with a rationale, links to meta bugs and Redmine tickets that are most likely to help in that regard (e.g. related to dark mode, file size reduction, memory use, website footprint, etc.), and recommendations for potential contributors wanting to focus on that aspect. I would be happy to help with that if there is support for it. Maybe some inspiration from KDE: https://eco.kde.org/ For now, I agree with the "invalid" status.