|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [BUG] hw/xen: features published after InitWait since 240cc11369fc
On Fri, Sep 11, 2026 at 03:56:22PM +0100, Peter Maydell wrote: > On Fri, 11 Sept 2026 at 15:39, David Woodhouse <dwmw2@xxxxxxxxxxxxx> wrote: > > I wasn't *actually* setting out to comment on the AI policy today — in > > fact I didn't really have a strong opinion on it. I spend enough of my > > life tilting at windmills *intentionally*; this wasn't meant to be one > > of them. snip > Yes. I view that email as pretty strong data for 'even a policy > shift which says "we're OK with accepting some kinds of AI > generated code" should still be pretty strong on "text intended > for humans to read (docs, commit messages, mailing list posts, etc) > should be written by humans"'. I think that review commentary on > Paolo's RFC about a less strict policy tended to be in that direction, > so I don't think I'm completely out on a limb here. The latest proposed policy explicitly forbids sending AI text to people: https://lists.gnu.org/archive/html/qemu-devel/2026-09/msg00260.html [quote] ### No AI-written text must reach maintainers These rules apply when publishing AI-assisted work to GitLab or the mailing list: - **AI-written cover letters and commit messages are banned**. These are easy to recognize and waste reviewers' time. - **AI-generated responses to reviewer comments are banned**. This undermines the human-to-human interaction fundamental to code review. - **AI-written issue ("work item") descriptions or comments are banned**. These are verbose and waste triagers' time. [/quote] With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |