Why is a RedHat "Platform Engineering Leader & Senior Principal Software Engineer" using AI in the most facile way to ask me to do work out of nowhere? It's extremely rude, and really tone deaf coming from a company built on the knowledge and time of open source maintainers. https://github.com/orgs/pallets/discussions/5744 #Python #Flask #RedHat
Proposal: Adopt Renovate for Automated Dependency Updates · pallets · Discussion #5744

Hi everyone, I'd like to propose adopting Renovate to automate our dependency updates. Renovate scans for outdated dependencies and opens pull requests with suggested upgrades — saving time and hel...

GitHub
Apparently GitHub discussion topics are still editable when locked? They edited an apology in. It all reads like they copy-pasted each time without refinement, it sure feels like I was talking to an AI directly. If there is a language barrier (they seem to communicate fine elsewhere), I'd vastly prefer and understand a direct translation of their own words, rather than AI-generated words.

@davidism Wow, that was ... weird. Reading the initial issue I definitely would have inferred that they were in the project, based on the wording.

Weird.

@davidism company goals (and therefore bonuses) now include (at least some) use of AI. Doesn't excuse this behavior, though. There are ways to fulfill the goal without being shitty to others.
@neverpanic Wow, that requirement is sure to backfire more times than this. I accept that people will use AI, but this case is exactly what not to do. It feels like I was chatting with an AI, rather than engaging with the person's actual words at any time.
@davidism side note: I so, so much agree with your blog post about scheduled updates. These bot PRs are so noisy, I wish people would use them less, or better yet, GitHub would distinguish them from actual PRs.
@davidism gosh that's a bad look but it really does seem like a language barrier plus tooling to help overcome it. I've seen very nice people come off horribly in their second language on the internet.
@jay I'm totally understanding of a language barrier, I read translated requests regularly without issue. This feels like the AI produced the full text, rather than using AI to translate an existing text. Along with the reply completely ignoring/fabricating what I'd written. I accept that people will use AI, but this isn't how to go about it.

@davidism I hate the size of that wall of text.
When you write, you are asking people to read.

♥️ to you for handling these sorts of interactions!

Liora Milbaum - Red Hat Research

Red Hat Research
@davidism If I should guess someone thought that this is how they can scale the outsourcing of an internal policy. "You are our dependency, and we want our dependencies to do X, so let's use AI to "engage" the maintainers at scale". But if that was the case there should be more examples of this.

@davidism Kinda OT, but you said she used "we" even though she is not part of the project. This has unlocked a new level of nightmare inside me 🙈.

I frequently use "we" when submitting issues or PRs, mostly because of my local traditions and native language. And also I think by using the project I'm part of the community. But after reading your comment, I think I should think a little before using "we" 😅.

@arunmani Don't worry about it too much. She didn't use "we", the AI she asked to write for her used "we". Given what was being asked and how, it was one more suspect thing among many. As long as you're writing in your own voice, even translated, you're doing better than that post.