Accent colors provide a way for users to personalize their desktop in a simple, developer-friendly, and effective way. Throughout the community there has been a general interest in the inclusion of accent colors within apps and desktop environments. This proposal aims to standardize an accent color key on the Settings portal.

A new key on the Settings portal, accent-color, would be defined under the org.freedesktop.appearance namespace.

Via @orowith2os@tech.lgbt

And endorsed by #GNOME, #KDE, #CosmicDE, #ElementaryOS, and #Budgie, at that!

  • russjr08@outpost.zeuslink.net
    link
    fedilink
    English
    arrow-up
    3
    ·
    10 months ago

    Yes, but I think the implication of the supposed semantics is that if we’re only ever referring to “Linux” as the kernel itself, then Linus possibly would’ve seen it.

    Not sure if he would’ve merged it, my knowledge of the kernel development process is a bit lacking - but I thought all the various subsystems of the kernel had their own maintainers who handled merging patches.

    • Salix@sh.itjust.works
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      10 months ago

      Not sure if he would’ve merged it, my knowledge of the kernel development process is a bit lacking - but I thought all the various subsystems of the kernel had their own maintainers who handled merging patches.

      Per this:

      https://www.kernel.org/doc/html/latest/process/2.Process.html#how-patches-get-into-the-kernel

      There is exactly one person who can merge patches into the mainline kernel repository: Linus Torvalds.

      When the merge window opens, top-level maintainers will ask Linus to “pull” the patches they have selected for merging from their repositories. If Linus agrees, the stream of patches will flow up into his repository, becoming part of the mainline kernel.

      While there are top level maintainers for the subsystems, it looks like Linus is the only one who can merge them into the mainline kernel.