# 2026-11-11 - coreboot Leadership Meeting

## Open Action Items
  * 2026-11-11 
    * Matt: Write a formal document on coreboot’s current position on the use 
of Rust.
  * 2026-10.28
    * Max/Felix: build system review / efficiency
        * Max’s patch: 
[https://review.coreboot.org/c/coreboot/+/96234](https://review.coreboot.org/c/coreboot/+/96234)
 
  * 2024-10-30
    * Add clarification to docs: "Do not use gerrit change-id or CB: format in 
reference to already-merged patches."
  * 2024-10-16
    * 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
    * 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
    * 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)
    * 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: [November 19, 2026](https://coreboot.org/calendar.html)
       
       
## Attendees
Werner Zeh, Ashmita, Mina Asante, Jay Talbott, Matt DeVillier, Julius Werner, 
Nicholas Chin, Jon Murphy, Alicja Michalska, Ingo Reitz.


## Minutes


### [Julius, Werner, Matt] Should we continue to allow people to sign-off with 
pseudonyms now that everyone can just submit AI-generated code that may trace 
back to some other license-incompatible code base? 
  * A real name policy might get people to take their “ensure you have the 
right to submit this” sign-off responsibility more seriously. 
(See:https://review.coreboot.org/95872)
    * [2023-04-16 Leadership 
Meeting](https://docs.google.com/document/d/1S1hLGc7nhBIaD3wN3eylyjhMMqEoI44TGy0zHj_hbr4/edit).
    * [Werner]: We should update [the sign-off procedure 
guidelines](https://doc.coreboot.org/contributing/gerrit_guidelines.html) to 
clearly reflect permitting a known real-world nicknames for people who want to 
protect their identity.
        * 
(https://review.coreboot.org/c/coreboot/+/97347/1/Documentation/contributing/gerrit_guidelines.md)

### [Julius] AI comment policy clarification: Should AI be allowed to close 
comments with “Ack” or “Done” on its own? 
([https://review.coreboot.org/97111](https://review.coreboot.org/97111))
  * [Julius]: I think it would be better if we require a human to click the 
“Done” button on gerrit.
    * How does the AI determine if an argument on a patch is resolved before it 
marks it as “Ack” or “Done”?
    * [Matt]: Would we want to revert the patch or push a new one that tweaks 
things?
        * [Julius]: Will take a closer look into it.
    * [Matt]: Let’s keep Martin updated with whichever route we decide to use.
 
### Rust in coreboot?
  * 
(https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ/edit?tab=t.0#heading=h.hu4v3rdwf28r)
        * [Matt]: No  decision was made at that time because there wasn’t any 
pressing use case.
        * [Werner]: We are not discouraging the use of Rust but to wait to see 
how many people starts to use it.
            * [Matt] AI: Do we have to write something up to formalize the 
project’s position on Rust as of now?
                * [Jon]: I think that would be great, especially with 
justification. 

### [jpmurphy]Log tokenization
  * [Compile-Time Console Log Tokenization for coreboot and 
libpayload](https://docs.google.com/document/d/1tN19v0Cj9Vq7ixURlXUGDC1sudFuQpi1IYLzOMkQ4yU/edit?usp=sharing)
        * Revisit this in the next 2weeks.

### [jpmurphy/kramasub] Backward compatible firmware from ToT
  * See [2024 archived coreboot leadership 
meeting](https://docs.google.com/document/d/1spx5B45u2IymaQitE-Thbqx4e4ykTok6a_g453AvdNE/edit?tab=t.0#heading=h.3zwn1kodfjq)
    * [coreboot & vboot_reference RO/RW Backward Compatibility 
Architecture](https://docs.google.com/document/d/1anORPwxT865B-bWZWjfGpJcOEdHjNhw2ha35M8mgR6E/edit?usp=sharing)
    * Revisit this in the next 2weeks.          

### [Alicja] I’ve been made aware of potential license violations in patches 
for Ampere SoCs (based on BSD -> GPL). 
I checked them and they seemed fine to me but IANAL, can we ask SFC about it?
  * [Ingo R]: GNU license details: 
(https://www.gnu.org/licenses/license-list.html#FreeBSD).
    * [Werner]: Let’s write an email to the SFC to clear all doubts. - Alicja


## Completed Action Items
  * Add clarification to docs: "Do not use gerrit change-id or CB: format in 
reference to already-merged patches."



# Next Leadership Meeting Date
  * November 25, 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]

Reply via email to