I wonder what’s the reason to make it optional? I think I’ve seen this approach with other projects as well. Isn’t transparency and accountability a good thing? Also, this kind of information helps immensely when reading pull requests or silly bug reports. And Debian acknowledge there might be licensing issues. So it might become some sort of liability to them once it taints everything and we can’t even tell?! So why? What’s the upside? Adorn oneself with borrowed plumes and not being forced to disclose the fact? Or too much bookkeeping?
I think that’s a commendable effort. Usually I do it the same way. Just feels massively unfair to me towards human contributors. I’ve seen the AI pull requests and bugreports come in. And it’s very time consuming to deal with them. They’re long, convoluted, touch a lot of code… There’s frequently a good amount of “hallucinations” in them, because they’re sent in autonomously or by people who don’t know what they’re doing. There might be dozens of them in quick succession as with the larger projects. They eat up time and effort which is now missing to deal with human contributions or wishes. My own opinion is: Transparency would help a lot to prioritize stuff. I mean AI isn’t sentient, and as long as that holds true, I’d rather treat people with respect and the amount of attention they deserve… (In contrast to a level playing field between human and machine… Because the machines will easily beat us by sheer volume.)
True, but I think the kind of people who send those monster PRs either already have AIs cosign it or they aren’t reading the policy anyway. There have also been a number of studies that show LLMs usually ignore this kind of instruction.
Hmmh. Sure. People also deliberately instruct their agents not to reveal the fact. I can empathize with that, because there’s all these people out there yelling at you, and launching shit storms.
I believe the uptake in “co-authored by …” is due to some companies making it the default setting in their frameworks. It’s to some degree Microsoft being nice to us, not necessarily benevolence of the people sending in those PRs. Doesn’t really matter to me though. It’s enough to make me happy if that’s attached to some commit or PR. I don’t care how it got there, as long as it fits the purpose.
Edit: And thanks for your comment. I don’t think I agree. Nonetheless this might be the answer to my question.
There are ways to enforce it.
Yeah, you won’t be able to make everyone follow the rule, but it’s the same with any law and any public policy and they’re still valuable.
You don’t make campaigns against DUI because you expect everyone to stop doing it, as that’s a nirvana fallacy, you make them because you expect them to reduce DUI.
I wonder what’s the reason to make it optional? I think I’ve seen this approach with other projects as well. Isn’t transparency and accountability a good thing? Also, this kind of information helps immensely when reading pull requests or silly bug reports. And Debian acknowledge there might be licensing issues. So it might become some sort of liability to them once it taints everything and we can’t even tell?! So why? What’s the upside? Adorn oneself with borrowed plumes and not being forced to disclose the fact? Or too much bookkeeping?
Because the idea is to judge the code by its quality, not by who or what wrote it.
I think that’s a commendable effort. Usually I do it the same way. Just feels massively unfair to me towards human contributors. I’ve seen the AI pull requests and bugreports come in. And it’s very time consuming to deal with them. They’re long, convoluted, touch a lot of code… There’s frequently a good amount of “hallucinations” in them, because they’re sent in autonomously or by people who don’t know what they’re doing. There might be dozens of them in quick succession as with the larger projects. They eat up time and effort which is now missing to deal with human contributions or wishes. My own opinion is: Transparency would help a lot to prioritize stuff. I mean AI isn’t sentient, and as long as that holds true, I’d rather treat people with respect and the amount of attention they deserve… (In contrast to a level playing field between human and machine… Because the machines will easily beat us by sheer volume.)
True, but I think the kind of people who send those monster PRs either already have AIs cosign it or they aren’t reading the policy anyway. There have also been a number of studies that show LLMs usually ignore this kind of instruction.
Hmmh. Sure. People also deliberately instruct their agents not to reveal the fact. I can empathize with that, because there’s all these people out there yelling at you, and launching shit storms.
I believe the uptake in “co-authored by …” is due to some companies making it the default setting in their frameworks. It’s to some degree Microsoft being nice to us, not necessarily benevolence of the people sending in those PRs. Doesn’t really matter to me though. It’s enough to make me happy if that’s attached to some commit or PR. I don’t care how it got there, as long as it fits the purpose.
Edit: And thanks for your comment. I don’t think I agree. Nonetheless this might be the answer to my question.
I think it’s just the simple fact that there’s no way to enforce it
There are ways to enforce it. Yeah, you won’t be able to make everyone follow the rule, but it’s the same with any law and any public policy and they’re still valuable. You don’t make campaigns against DUI because you expect everyone to stop doing it, as that’s a nirvana fallacy, you make them because you expect them to reduce DUI.
With systems starting to move to watermarking tech a lot of them will actually be detectable.
Either way that doesn’t make it a bad idea or less useful.
Which tells a lot about how good they are. Slop is slop because it’s bad, but a high quality PR isn’t