2025-06-11 - coreboot Leadership Meeting Minutes

# 2025-06-11 - coreboot Leadership Meeting



## Attendees

Julius Werner, Werner Zeh, Maximilian Brune, Alicja Michalska, Matt DeVillier,  Martin Roth, Ziang
Wang, Felix Singer, Mina Asante.



## Open Action Items

  * 2025-05-14
    * [Open] Martin: Review the list of people with +2 rights and update it before the next release.
  * 2024-11-27
    * [Open] Send out poll with regards to  LLM usage (requested by SFC)
  * 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.



## Minutes


### [Max] We need clear policies and/or guidelines for branches other than the main branch in coreboot.
  * Who is responsible for the other branches (coreboot community?)
    * The branch owner. 
  * Who is supposed to review the changes? (I personally don’t have time to review patches on other
branches even though I am the maintainer of the specific directory)
    * Whoever wants to. The branch owner is responsible.
  * Do we need reviewers or can we just merge changes without actual review (in that case I don’t mind just submitting them).
    * The branch owner is responsible for review and submitting them.
  * I don’t want to get emails or be in the reviewers list (from gerrit) for patches pushed to other branches (can I disable that?)
    * We can look into disabling this, but it would be in your personal settings. 

### The coreboot mascot name poll was left open for a week:
[https://forms.gle/aHe5wLpWgNVbbqw39](https://forms.gle/aHe5wLpWgNVbbqw39)
  * We want to go with “Blitz, The corebunny.”
  * We’ll do a blog post and publish it on the website.


**Information:**


### Asia meeting:
  * Use the same document
  * Mina can probably attend and help.
  * Will get everything figured out over the next couple of weeks.

### The 25.06 release is scheduled for June 20
  * If anyone is interested in joining the release team, we could use some help and replace some of the existing members.



# Next Leadership Meeting
  * June 25, 2025.
  * [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 minutes
https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]