Are cpupower commands missing?

Understand that my stance revolves about

  • the collection and collating of reported incident test cases (within the UM context),
  • clarification of issue reports using the correct language (with which UM developers are more adept,
  • submitting those to the "source" developers, again using appropriate language (which the general users are not likely to know),
  • communicating the scope of impact (more on that later),
  • (tricky one) every 2 months, "ping" developers for an indication of progress until resolution (i.e. "follow-up"),
  • "roll-in" the updates and publish the release.

Regarding scope of impact for any reported issue, if there was an automated process to

  • define,
  • publish (reference draft bug report for review),
  • harvest impact (no_workaround[10], workaround[6], annoyance[2], no_experience[0]), and
  • harvest relevance perception (in-scope[10], contextual[4], out-of-scope[0])

the results of such a survey, for every reported issue, this would go a long way to

  • put visibility on the scope of impact from each issue, or
  • put visibility on the lack of shared perception of importance/criticality of the issue to the community.

It is my strong belief that having such a visible "pulse" on all such issues would make UM a very attractive Community to join.

@mdd12, regarding your specific reference to LibreOffice, a case could be made for that stance ... but I know when not to push my luck ... on the basis that LibreOffice is too massive a package, edging towards the size of the OS itself ... and that would be an unreasonable expectation, likewise for web browsers and mail clients ! :slight_smile:

However, if the UM developers noticed a trend of issues that were specifically being reported ONLY (or predominantly) by members of the UM Community, then I would be persuaded to rationalize that UM developers should be able to recognize their own interests (functionality and desirability of the UM Distro) are being undermined by not taking a more active part, along the lines I outlined at the beginning of this response.

Thank you for your consideration of my viewpoint.