- cross-posted to:
- opensource@programming.dev
- cross-posted to:
- opensource@programming.dev
Fuck AI, but a respectable stance.
And then you have the ShareX developer, using a screenshot of an AI response to respond to a GitHub issue.
And then you have the ShareX developer, using a screenshot of an AI response to respond to a GitHub issue.
based sharex dev, every foss dev should be legally allowed to shoot one issue creator each year
Wow
deleted by creator
So far the best AI tool use policy I’ve read, specially this bit:
Your PR body should be providing context to other developers about why a change was made, and if your name is on it, we want your words and explanations, not an LLM’s. If you can’t explain what the LLM did, we are not interested in the change.
What about the IP issues? Not even talking about the “ethics” of “ip theft via AI” or anything, you just know a company like Microsoft or Apple will eventually try suing an open source project over AI code that’s “too similar” to their proprietary code. Doesn’t matter if they’re doing the same to a much greater degree, all that matters is they have the resources to sue open source projects and not the other way around. If a tech company can get rid of the competition by abusing the legal system, you just know they will, especially if they can also play the "they’re knowingly letting their users use pirated media that we own with their software” card on top of it.
If anyone needs to translate, try out
Well I wish the AI would fix the Schedules Direct problem
I love this approach - clear and concise rules. They are being realistic about AI created code making it into their codebase, while setting some guidelines.





