2024-03-20 - coreboot Leadership Meeting Minutes

# 2024-03-20 - coreboot Leadership Meeting Minutes

## Attendees
Martin Roth, Felix Held, Felix Singer, Jay Talbott, Matt DeVillier, Nicholas Chin, David Hendricks,
Arthur Heymans, Mina Asante, Julius Werner,Christian Walter, Max Brune, Jon Murphy, Karthik,
Patrick Georgi.

## Announcements
  * FOSSY conference: August 1-4 2024 in Portland, Oregon, USA
[https://sfconservancy.org/fossy/].
  * OSFC will be in Bochum Germany - September 3-5 - [https://www.osfc.io/].

## Open Action Items
  * 2024-03-20
    * [Open] Martin: Set up a new meeting link for the next leadership meeting.
    * [Open] Martin:  Add a note to the gerrit guidelines to email the leadership.
  * 2024-03-06
    * [Open] Martin: To update documentation on gerrit contributing guidelines.
    * https://doc.coreboot.org/contributing/index.html 
  * 2024-01-10
    * [Open] Werner: Push patch based on https://ticket.coreboot.org/issues/522
      * 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

### [Martin] BigBlueButton 
  * The invite for this meeting still has the google chat link on it.  We should have Patrick cancel his invite and set up a new one.
  * The BBB version that the SFC offers is from 2021 and has issues on mobile. There could also be unfixed CFEs (speculation).
    * Do we want to switch back to Google chat until the SFC can update to a newer version? Martin can set up an open invite for up to 100 users. $20 per month (I believe). 
    * Can also use OSFF - 250 people, record, etc - everyone can join.
  * Decision: switch back to Google Meet

### [Martin] Adding Max Brune and Jon Murphy as core developers. 
  * | Name             | Patches | Reviews | Comments |First Patch |
    |------------------|---------|---------|----------|------------|
    | Maximilian Brune | 67      | 88      | 43       | 2022-05-16 |
    | Jon Murphy       | 115     | 130     | 29       | 2022-02-24 |
  * Others who could be considered, but we’d like to see more community involvement, reviews, and/or comments from before considering them.
    * Frans Hendriks
    * Bora Guvendik
    * Keith Hui
    * Maulik Vaghela
    * Naresh Solanki
    * Tyler Wang
    * Varshit B Pandya
    * Kapil Porwal
  * If anyone feels that I’m mistaken about people in either group, please reach out to me or the leadership about these people. 
    * [FelixH] We should only look at the number of commits and things from the past 2 years instead of over the entire span that they’ve been working on the project.
      * [Martin] I can recalculate who other than Max & Jon could be considered.
  * Decision: Only look at the past 2 years?
  * [Felix] How should we react when people don’t do a good job submitting code?
    * [Martin] I think that the leadership should talk with the user.
    * [MattD] No formal policy - let the leadership handle it.
  * TODO: Add a note to the gerrit guidelines to email the leadership

### [Martin] RFC: Link Time Optimization [LTO]
  * Jacob Garber pushed patches a few years ago to get GCC working - Arthur took these over. See Jacob’s initial email:
[https://mail.coreboot.org/hyperkitty/list/[e-mail]/message/JIIW...]
  * Working on adding clang - works differently & only works with specific linkers.
[https://mail.coreboot.org/hyperkitty/search?q=lto&page=1&mlist=coreb...]
  * Do we want to make this a default?
    * [Martin] We can decide that after testing.
  * [Arthur] ARM (not arm64) is broken - maybe the toolchain is broken. Arm builds don’t even complete.
  * Would there be a reason to keep non-LTO?
  * Maybe to debug issues and see if they’re caused by LTO.
  * To add LLVM with LTO we need to add LLD as part of the project when building LLVM.
    * How does this affect our linker scripts?
  * LLD doesn’t understand “=.” but setting a variable works.

### [Martin] Bugs
  * Large number of outstanding bugs - how can we close these? No good solution?
    * Reduce barriers
      * Introducing single sign-on would help.
      * Having the email to the mailing list seems to help.
        * Being able to reply to the email and have it show up in the bug would help.
  * Why is tracker.coreboot.org down right now?
  * Is there any progress integrating with Gerrit?
    * Felix would like to move away from redmine. Highly depends on plugins and there isn’t good modern
functionality. Removed support from open-connect - so people can’t use
    * Propose we switch to forgejo for bug tracking.
      * Can we use our current logins from gerrit, or does it require a new login? This is the biggest
issue we’ve heard from users with redmine.
      * Does this help integration with gerrit?
        * What are we looking for?
          * Links from bugids from gerrit to the ticket. 
        * Yes? I think we can do this just with gerrit. The same as we do with the CB: links.
  * Decision: Let’s look at Forgejo and see

### [Martin] Coverity issues
  * Current open issues spreadsheet
    * [chart of issues by area]
(https://docs.google.com/spreadsheets/d/e/2PACX-1vRYUlOLQTysbdPQoOKaCnRN_K4Ca...
6gATqtvgDlzSl1S4DaijcTyF7yAAs3qm/pubchart?oid=502535263&format=interactive).
    * [chart of issues by type]
(https://docs.google.com/spreadsheets/d/e/2PACX-1vRYUlOLQTysbdPQoOKaCnRN_K4Ca...
6gATqtvgDlzSl1S4DaijcTyF7yAAs3qm/pubchart?oid=1369215095&format=interactive).
  * Link to the coreboot project coverity:[https://scan.coverity.com/projects/coreboot].
  * As an alternative to coverity, Felix is adding a code-checker Docker container, and we’ll be moving to it from the current scan-build website. This is not a replacement for coverity, just a nicer interface to the current scan-build that we’re already doing.
    * [https://codechecker.readthedocs.io/en/latest/].
      * coreboot.org/scan-build is currently broken. :(

# Next meeting
  * April 3, 2024.
    * [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
[2024-03-20](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKj...
1).