The GNOME.org Extensions hosting for GNOME Shell extensions will no longer accept new contributions with AI-generated code. A new rule has been added to their review guidelines to forbid AI-generated code.

Due to the growing number of GNOME Shell extensions looking to appear on extensions.gnome.org that were generated using AI, it’s now prohibited. The new rule in their guidelines note that AI-generated code will be explicitly rejected

  • ikidd@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    21 hours ago

    Oh come on, Gnome 45 was only 2 years ago. I guess we’ll see how extensions go then, but I’m not holding my breath. I wouldn’t waste my time on building anything for Gnome at this point. I abandoned Gnome at the garbage-collector BS where they blamed extension devs for the memory leak then used the big hammer solution.

    In the meantime:

    Mar 2024: https://felipec.wordpress.com/2024/03/18/stupid-gnome-developers/

    May 2025: https://medium.com/@fulalas/gnome-the-insanity-never-ends-f84a77ec3e13

    • lastweakness@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      10 hours ago

      The medium post is mostly about bugs (it’s software, that happens, report them or patch them) and distribution packaging issues (they seem to use Manjaro, so makes sense). Then it talks about design inconsistencies and all, which basically every Linux desktop is worse than GNOME with. Then it uses lines of code as a metric? Then it uses memory and compares GNOME to less capable desktops and ignores that KDE’s memory usage is not too far away. I’m sure there’s a lot of legacy code everywhere though.

      I don’t know what to say about Felipe’s issue since he wants a behavioral change in a library and he’s mad that the GNOME devs aren’t making that change.

      That said, all these desktops rely on GNOME components, so idk why they have such an attitude specifically towards GNOME. It’s just software, don’t get too heated over it.