On Tue, 17 Nov 2026 at 21:13, Kevin Wolf <[email protected]> wrote:
>
> Am 17.11.2026 um 21:40 hat Eric Blake geschrieben:
> > [Chiming in late]
> >
> > On Wed, Sep 30, 2026 at 10:54:30AM +0200, Paolo Bonzini wrote:
> > > +LLM-assisted and LLM-created contributions
> > > +''''''''''''''''''''''''''''''''''''''''''
> > > +
> > > +Use of generative AI can be classified in the following four buckets:
> > > +
> > > +- "background" assistance, such as completion and code review.  This does
> > > +  not need disclosure.
> > > +
> > > +- small LLM-assisted bugfixes (as a rule of thumb, below 10 lines of 
> > > code)
> > > +  are allowed with disclosure.  Splitting a submission in multiple parts
> > > +  is **not** a valid way to bypass this rule; repeated, frequent posting
> > > +  of such fixes must follow the rule for full contributions.
> > > +
> > > +- use of LLMs to help generating parts of a larger patch---test cases,
> > > +  adaptations of existing code, boilerplate code for a new API, a tool to
> > > +  help performing mechanical changes, etc.  These are generally allowed;
> > > +  disclosure is highly recommended for non-trivial, functional code.
> >
> > I see lots of discussion about whether to stop here (and s/four/three/
> > above), and leaving off the fourth bullet (or splitting it to a
> > separate patch for later) appeals to me personally. But I can also go
> > along with the final bullet if that is what the consensus lands on.
>
> If the consensus is that the legal arguments for the current policy
> aren't relevant any more, I'd like to have some policy update merged
> rather sooner than later. Without this concern, I think I'm mostly in
> the "it's just a tool" camp.
>
> I don't mind the fourth point and don't expect practical problems from
> it, but if some people do have concerns that would take months to
> resolve, I'd prefer to do without it for now and allow at least the
> uncontentious cases without waiting.

Yes, I would rather we accepted the uncontentious cases and then
had the discussion about the one where it's less clear we have
consensus, than that we hold all the changes up until we get
agreement on all four points. "Push for all four" has got us mostly
"no change" so far.

I think we definitely should have that community-call discussion
on the AI policy so we can see where we are collectively. I also
don't think we particularly need to tie our policy updates to the
release schedule: it's just a documentation change.

thanks
-- PMM

Reply via email to