Mastodawn

Does anyone have good templates or examples of "do not allow slop machines in this project" issue tracker posts?

I want to enforce one in a project I've helped with (LibreSplit speedrun timer) because I can see LiveSplit (the most common speedrun timer, Windows only) has been getting LLM commits in the open (Cryze ran all the open issues through Claude and commited them, for some fucking reason)

I just haven't been able to properly write it in a good way. I think it'll go through, and as far as I'm aware there's a general anti AI sentiment with the main users and devs, but yeah... Help?

Show thread

kaevel Mar 15

@MxCraven

Starlight Network is working on a No-AI List of projects here: https://noai.starlightnet.work/list.html

Included is a link to evidence of their no AI policy, which hopefully can help you figure out some good wording for your use!

Starlight Network No-AI List

Show thread

kaevel

@MxCraven Wait no I just realized I misunderstood your post, you're looking at proposing no AI usage, not a statement of contribution.

I've been following and commenting on the Fluxer issue for revising contribution guidelines and I think it has some good ideas in there, including examples of other major projects looking to do similar:

https://github.com/fluxerapp/fluxer/issues/435

Consider revising contributor guidelines concerning LLM tool use · Issue #435 · fluxerapp/fluxer

What needs fixing? This issue concerns the following section of CONTRIBUTING.md: Understand the code you submit ... LLM-assisted contributions. You're welcome to use LLMs as a tool for automating m...

GitHub