Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-25018

[RFE] Group GNOME Settings, Tweaks, Extensions in the same categories

    • ZStream, 0day
    • 4
    • rhel-sst-display-desktop-foundation
    • ssg_display
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • DESKTOP Cycle #1 10.beta phase, DESKTOP Cycle #3 10.beta phase, DESKTOP Cycle #4 10.beta phase, DESKTOP Cycle #2 10.beta phase
    • Approved Blocker
    • None
    • None
    • None

      What is the nature and description of the request?
      We'd like to see the apps GNOME Control Center, GNOME Tweaks, and GNOME Extensions in the same category so they are easy to find in the Applications menu (from the Applications Menu extension)

      Can you elaborate on the operational requirements for this RFE?
      Control Center is found in "Other", Tweaks is in "Utilities" and Extensions is in "Accessories". We want all of those in the same spot. Doesn't matter which one, as long as they are in the same spot. I'd argue "Utilities" probably makes the most sense and "Other" should not even exist, but that's a different topic.

      How would you like to achieve this? (List functional requirements here.)
      All three apps in same category. Boom.

      For each functional requirement listed, how can we test to confirm the requirement is successfully implemented?
      I'd say we pretty much will celebrate a well-deserved victory when all three apps are in the same category.

      Is there an existing RFE bug upstream?
      Not that I know of.

        1. Tweaks.png
          Tweaks.png
          44 kB
        2. Settings.png
          Settings.png
          29 kB
        3. Extensions.png
          Extensions.png
          28 kB

              rhn-engineering-rstrode Ray Strode
              rhn-support-amike Andrew Mike
              Matthias Clasen Matthias Clasen
              Barry Dunn Barry Dunn
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: