2026-08-19 - coreboot Leadership Meeting Minutes

# 2026-08-19 - coreboot Leadership Meeting


## Open Action Items
  * 2024-10-30
    * [Open] Add clarification to docs: “Do not use gerrit change-id or CB: format in reference to already-merged patches.”
  * 2024-10-16
    * [Open] Matt: Set up a meeting to discuss board status alternatives and send out invites. 
      * Decouple data collection with uploading
      * Require gerrit credentials or other auth to push
      * Json format?
      * https://github.com/chrultrabook/linux-tools/blob/main/debugging.sh
  * 2024-09-18
    * [Open] Jon: Schedule a dedicated meeting to discuss the Coverity defects and action plan.
      * Werner: Send out an invite for the meeting. 
        Sent out a poll to find a time slot: https://rallly.co/invite/1c8J3azXAcje
  * 2024-05-01
    * [Open] Nick Van Der Harst volunteered for Dutch. "gogo gogo" would like to translate to Russian (?).
  * 2024-01-10
          * Nico: (https://review.coreboot.org/q/topic:enforce_region_api)
      *  [Open] Daniel: Look at how we want to localize (non-console) strings for coreboot. Long-term project.
      
      
## Announcements & Events
  * Next Open System Firmware - OCP Project Meeting 
    * Date : [August 27, 2026](https://coreboot.org/calendar.html)
  * [OSFC 2026](https://www.osfc.io) 
    * Date: 15 - 17 September


## Attendees
Mina Asante, Alicja Michalska, David Hendricks, Julius Werner, Werner Zeh, Ingo Reitz, Ashmita, Karthik R, Jon Murphy.


## Minutes


### [Julius] Maybe discuss AI contribution rules (see [https://review.coreboot.org/93682](https://review.coreboot.org/93682))?
  * Julius’ suggestion:
    * Humans always held responsible for their AI’s actions
    * Using AI to generate review comments: allowed, but need to manually double-check each comment before sending it out
    * Using AI to respond to human reviewers’ comments: always forbidden
    * Should add this to gerrit_guidelines.md and hold contributors responsible for following it, but should also create agents.md to help AI self-police.
    * Using AI to generate code: Open for debate? We could adopt guidelines [like Linux](https://docs.kernel.org/process/coding-assistants.html) (human must manually review, ensure license compliance, add Assisted-by tag)?
        * Chromium Gerrit update: https:(//chromium-review.googlesource.com/c/chromium/src/+/7624701)
  * [Werner] I agree with writing up the rules to define the scope for both, humans and LLMs. Can we mark AI generated responses as such?
    * [Julius] We can try to advise the AI via the [agents.md](agents.md) file to add a disclaimer about it. Sounds reasonable to have a response marked as AI generated.
    * [Ingo Reitz] Take the recently introduced rules in Rust as an advice
      * (https://blog.rust-lang.org/inside-rust/2026/08/05/rust-langrust-is-adopting-an-llm-policy/).
      * (https://forge.rust-lang.org/policies/llm-usage.html)
    * [Julius]: Will create a draft and send it for review. What about code generation by AI?
        * [Werner] I would love to involve a broader community in this question. Can we go for a mailing list discussion?
    * [Julius] Sure, we can do that later after we have set up the policy.
  * [David] Here is an example for AI generated code: (https://review.coreboot.org/c/coreboot/+/93439)

### New core developers from July 22 meeting discussion
  * The core developers group on Gerrit has yet to be updated with the list of new candidates from the leadership meeting 4 weeks ago (not that I’m personally in any rush to get added, just making sure it hasn’t been forgotten).
    * [Werner] I hoped Martin would step in and add it as he brought it up.
    * [David] Will take a look and update the groups.
        * Done
        
### [Jon Murphy] cmocka repo is down. We need to react as we are using it as a submodule
  * (https://cmocka.org/)
  * (https://git.cryptomilk.org/projects/cmocka.git)
  * (https://gitlab.com/cmocka/cmocka)
  * They may want to migrate to gitlab so we may want to follow that. A first reachout was not responded to by the project.
    * [Julius] For now let us just switch to something that is working. We can try later to get in contact with the project to understand their goals.
  * [Jon] Will do the update to submodules to gitlab → Looks like I cannot do this
    * [Werner] We need to ping Felix Singer for that, will do so



# Next Leadership Meeting Date
  * September 2, 2026.
  * [coreboot Calendar](https://coreboot.org/calendar.html).


# Notice
Decisions shown here are not necessarily final and are based
on the current information available. If there are questions or comments
about decisions made, or additional information to present, please put
it on the leadership meeting agenda and show up if possible to discuss
it.
Of course items may also be discussed on the mailing list, but as it's
difficult to interpret tone over email, controversial topics frequently
do not have good progress in those discussions. For particularly
difficult issues, it may be best to try to schedule another meeting.


# coreboot Leadership Meeting Notes
https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ.
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]