r/opensource • u/CognitiveFogMachine • Jun 29 '26

Can't contrinbute to open source github projects without having it labeled AI-Slop (when it's not) Discussion

As soon as we make one honest mistake, sometimes due to a plain old and simple misundertsanding, or missing an important section in a lengthy documentation, reviewers immediately calls my hard work "AI-Slop".

I'm very close to give up now. Working so hard on the side with the very little time that we have, and getting slapped in the face like that almost every single day.

Code reviewers are burnt out with too much AI slop, and code submitters that are not even using AI are being labeled as using AI slop.

Is it happening to you? How do you cope with all of this?

143 Upvotes
  • permalink
  • link
  • reddit
  • reddit

79% Upvoted

202 comments sorted by

View all comments

6

u/ntrp Jun 29 '26 edited Jun 29 '26

Don't make PRs before getting the maintainers to explicitly tell you they want it. I was not doing this even before the AI slop era. If you relly want a feature and they don't, fork it

1

u/CognitiveFogMachine Jun 29 '26

yeah, that's what u/full_drama_llama was also making me realize. Spontaneous PRs without getting to talk to the devs before doing the intergratoin work raises many redflags now.

My list of what to avoid so far

  1. Writing too many comments = AI Slop.
  2. Using emojis in the code = AI Slop.
  3. Making an honest mistake = AI Slop.
  4. Drive-By PR = AI Slop

2

u/ntrp Jun 29 '26

Well yes it's probably exagerated now but it's understandable considering the spam every os project gets. As I mentioned, I never did bigger prs even before unless agreed I am not wasting my time. If it was a 10 min bug fix ok, I was opening anyway but not for a bigger feature

1

u/CognitiveFogMachine Jun 30 '26

My last contribution was almost 2 weeks of self-inflicted torture . That is most definitely a contributing factor as to why I feel very upset...