On Wed, Jun 11, 2025 at 4:02 AM Eoghan Glynn <eglynn@redhat.com> wrote:

(Kicking off the discussion here, since the June board meeting was cancelled)

Colleagues,

It turns out the proposed "Assisted-By" commit message label is already in use, as can be seen from these two in-flight reviews:

nova-specs/+/951222[1]
owner: Sean Mooney 
Assisted-By: deepseek-r1
Assisted-By: google-gemini-flash-2.5

project-team-guide/+/948484[2]
owner: Goutham Pacha Ravi
Assisted-By: OpenAI ChatGPT

(As an aside: there's nice symmetry to the nova-specs one, as I first heard the new "Assisted-By" label suggested by Sean back in early April, in advance of the board discussion)

Also worth noting the actual choice of models in this small sample suggests not much weight is being put on the current policy's steer towards: "exclusively using compatible licensed inputs to train the model, using a model released as open source, using a model trained exclusively on compatible licensed code".


Indeed, this can be observed with the Generated-By label. A huge amount of the feedback we've gotten from non-Red Hat folks is that the policy is basically too long and needs to be more like a single paragraph. I have an outstanding todo to revisit the draft revision I started a month or so ago and try to craft a TL;DR section like what was done with the code of conduct, I've just not had time.
 
To catch up with emerging practice, I'd suggest that we augment the formal policy with "Assisted-By" as soon as possible. FWIW, I think we should also simplify, shorten, and make the policy more permissive overall (e.g. by removing the language on the choice of model, and pushing the secondary scanning into the code review or merge gating flow). Though at least we should get the Assisted-By option codified soon.


I concur we need to regarding Assisted-By, unfortunately the push to not hold a meeting from the staff due to onboarding pulled the wind from my sail a couple weeks ago. 

The path forward seems to be to finish revisions to a draft, get a quick legal review, and then bring it up as an item to vote on in the next meeting, if we're able to achieve the necessary review steps in time.
 
Thanks,
Eoghan

[1] https://review.opendev.org/c/openstack/nova-specs/+/951222
[2] https://review.opendev.org/c/openstack/project-team-guide/+/948484

--

Eoghan Glynn

He/Him/His

Senior Director, OpenStack Engineering

Dublin, Ireland

M: +353-86-8175024

_______________________________________________
Foundation-board mailing list -- foundation-board@lists.openinfra.org
To unsubscribe send an email to foundation-board-leave@lists.openinfra.org