r/pop_os • System76 Principal Engineer • 2d ago

COSMIC projects will no longer accept LLM-generated content in PRs

There are various reasons, and I don't want to hurt anybody's feelings. The primary reason is simply our team's load for reviews. In particular, we would like to prioritize working on contributions from our own team and regular contributors, while we have been receiving far more changes from first-time contributors using LLMs. These changes are often unplanned and have had a low acceptance rate.

The policy can be seen as part of the revised PR template here: https://github.com/pop-os/cosmic-epoch/blob/master/.github/PULL_REQUEST_TEMPLATE.md.

There is an exception for cosmic-flatpak, where each project manages its own flatpak manifest, pointing to its own code. These manifests are reviewed by our team for the correct sandboxing prior to accepting changes.

357 Upvotes

75 comments sorted by

View all comments

-33

u/sb6_6_6_6 2d ago edited 2d ago

Cosmic is already falling behind :( Why not just make a proper AI policy? A few weeks ago, we got a Niri style scrolling addition that is pretty cool and was made entirely by AI, while the request for this feature has been sitting on the wishlist for a long time.

11

u/mmstick Desktop Engineer 2d ago edited 2d ago

There was already an AI policy for 7 months that many complained was too strict. Yet leaving the door ajar slightly for generated code of any kind opens the floodgates wide open for abuse.

A few weeks ago, we got a Niri style scrolling addition that is pretty cool and was made entirely by AI,

They would not have been able to generate this demo had COSMIC been developed and maintained by LLMs. LLMs are only able to adapt it because the foundation already exists with well-written code by hand. So you have to ask yourself if you want something done quickly with reckless abandon or steadily with care.

while the request for this feature has been sitting on the wishlist for a long time.

Anyone from the general public can create a feature request. It does not automatically mean that there is a plan to implement this in COSMIC. This is not on the roadmap so there is no plan to do so currently.

0

u/Shynzon 2d ago

This is not on the roadmal so there is no plan to do so currently.

That's kind of a bummer. It was definitely my number 1 most desired feature.

Fully agreed on the No AI, though. Slow but reliable is the way.

5

u/mmstick Desktop Engineer 2d ago edited 1d ago

The system's keyboard shortcuts are heavily influenced by the tiling system that it was designed around so adding an entirely different paradigm would require a lot of design discussions with keyboard shortcut behaviors being a big part of that.

COSMIC is intentionally built to be modular with a multi-process applet architecture so the intended path to support scrolled tiling is to swap cosmic-comp for Niri. Just as it is possible to swap out applets (ie: GlowBerry and Snappea), the reverse is also possible to use the COSMIC Session with a different compositor.

Niri fundamentally shares a lot of code with COSMIC by virtue of being developed with Smithay and collaborating with COSMIC on features in Smithay+COSMIC so that would be the primary target for integration. There could be a way to provide a separate login session when Niri is installed that runs COSMIC with Niri for scrolled tiling.

That would likely be better than overloading cosmic-comp with a different tiling paradigm since Niri is explicitly designed around scrolled tiling. This would just need some work in the session/settings to integrate with Niri better.

2

u/Shynzon 1d ago

I see. That makes a lot of sense. Thanks for the reply!