How does this not lead to a situation where no honest person can use any AI in their submissions? Surely pull requests that acknowledge AI tooling will be given significantly less attention, on the grounds that no one wants to read work that they know is written by AI.
Isn't that a good thing?
AI tooling must be disclosed for contributions
41–50 of 482 posts
Re: AI tooling must be disclosed for contributions
#42Earlier quoted context omitted.
Except you can enforce this rule some of the time. People discover that AI was used or suspect it all the time, and people admit to it after some pressure all the time. Not every time, but sometimes. The threat of being caught isn't meaningless. You can decide not to play in someone else's walled garden if you want but the least you can do is respect their rules, bare minimum of human decency.
It. doesn't. matter. The only legitimate reason to make a rule is to produce some outcome. If your rule does not result in that outcome, of what use is the rule? Will this rule result in people disclosing "AI" (whatever that means) contributions? Will it mitigate some kind of risk to the project? Will it lighten maintainer load? No. It can't. People are going to use the tools anyway. You can't tell. You can't stop th…
Yes that is the stated purpose, did you read the linked GitHub comment? The author lays out their points pretty well, you sound unreasonably upset about this. Are you submitting a lot of AI slop PRs or something?
P.S Talking. Like. This. Is. Really. Ineffective. It. Makes. Me. Just. Want. To. Disregard. Your. Point. Out. Of. Hand.
Re: AI tooling must be disclosed for contributions
#43I’m loving today. HN’s front page is filled with some good sources today. No nonsense sensationalism or preaching AI doom, but more realistic experiences. I’ve completely turned off AI assist on my personal computer and only use AI assist sparingly on my work computer. It is so bad at compound work. AI assist is great at atomic work. The rest should be handled by humans and use AI wisely. It all boils down back to hu…
It might just be my point of view, but I feel like there's been a sudden paradigm shift back to solid ML from the deluge of chatbot hype nonsense.
Re: AI tooling must be disclosed for contributions
#44I just submitted my first big open source contribution to the OpenAI agents SDK for JS. Every word except the issue I opened was done by AI. On the flip side, I’m preparing to open source a project I made for a serializable state machine with runtime hooks. But that’s blood sweat and tears labor. AI is writing a lot of the unit tests and the code, but it’s entirely by my architectural design. There’s a continuum here…
I think its simple, just don't hide it. I've had mutliple contributors try to hide the fact that they used AI (E.g removing claude as a code author - they didn't know how to do it and close the PR when it first happened.). I don't really care if someone uses AI, but most of the people who do also do not test their changes which just gives me more work. If someone: 1.) Didn't try to hide the fact that they used AI 2.)…
Re: AI tooling must be disclosed for contributions
#45How does this not lead to a situation where no honest person can use any AI in their submissions? Surely pull requests that acknowledge AI tooling will be given significantly less attention, on the grounds that no one wants to read work that they know is written by AI.
Isn't that a good thing?
Re: AI tooling must be disclosed for contributions
#46So if the code is integrated, the license of the project lies about parts of the code.
Re: AI tooling must be disclosed for contributions
#47This seems very noisy/unhelpful.
Re: AI tooling must be disclosed for contributions
#48Earlier quoted context omitted.
Except you can enforce this rule some of the time. People discover that AI was used or suspect it all the time, and people admit to it after some pressure all the time. Not every time, but sometimes. The threat of being caught isn't meaningless. You can decide not to play in someone else's walled garden if you want but the least you can do is respect their rules, bare minimum of human decency.
It. doesn't. matter. The only legitimate reason to make a rule is to produce some outcome. If your rule does not result in that outcome, of what use is the rule? Will this rule result in people disclosing "AI" (whatever that means) contributions? Will it mitigate some kind of risk to the project? Will it lighten maintainer load? No. It can't. People are going to use the tools anyway. You can't tell. You can't stop th…
If this rule discourages low quality PRs or allows reviewers to save time by prioritizing some non-AI-generated PRs, then it certainly seems useful in my opinion.
Re: AI tooling must be disclosed for contributions
#49I’m not a big AI fan but I do see it as just another tool in your toolbox. I wouldn’t really care how someone got to the end result that is a PR. But I also think that if a maintainer asks you to jump before submitting a PR, you politely ask, “how high?”
I can generate 1,000 PRs today against an open source project using AI. I think you do care, you are only thinking about the happy path where someone uses a little AI to draft a well constructed PR.
There's a lot ways AI can be used to quickly overwhelm a project maintainer.
Re: AI tooling must be disclosed for contributions
#50Do I also have to disclose using tab completion? My IDE uses machine learning for completion suggestions. Do I need to disclose that I wrote a script to generate some annoying boilerplate? Or that my IDE automatically templates for loops?