# 2024-10-30 - coreboot Leadership Meeting
## Attendees
Felix Held, Felix Singer, Marshall Dawson, Matt DeVillier, Jeremy Compostella,
Alicja Michalska,
Maximilian Brune, Pono, Mina Asante, David Hendricks, Jay Talbott, Julius
Werner, Ron Minnich.
## Open Action Items
* 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.
* 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.
## Minutes
### [Elyes] How to know when we should follow Linux rules and when those of
coreboot ? Please make
it clear.
* I’m asking because of Felix’s comment here :
https://review.coreboot.org/c/coreboot/+/84074
about “`Commit <first 12 chars of commit> ("<commit title>")"`
* [Matt] coreboot’s checkpatch should detect and enforce this:
* [Matt] looks like we don’t explicitly state this in the coding style or
documentation, and
probably should just for clarity
* AI: add clarification to docs, do not use gerrit change-id or CB: format
in reference to
already-merged patches.
### [David] Follow-up on discussion with SFC regarding use of LLM-generated code
* It's a new thing that doesn't have a good policy yet. SFC is getting a lot
of questions regarding
this, and there seems to be widespread adoption in various companies but with
various restrictions
surrounding how they are used. It's unclear how this applies to the world of
free software.
* We need to gather data at this time to figure out how many people are using
LLMs and how. This
will help SFC craft appropriate policy.
* How do we do this? Ask people to annotate commit messages if they used an
LLM? This would be
voluntary (we have no good way to enforce it).
* We don't necessarily know who is using it now, and we don't have a good
way of tracking it. So we
treat patches the way we currently do, regardless of whether an LLM was
involved in their creation
or not.
### [David] Is anything needed with regard to Russian maintainers/contributors?
* We asked the SFC back in April '23, but did not get a response. Given the
recent drama in Linux
it seems we need to revisit this topic and avoid running amok of sanctions.
* [Pono] This is a confusing issue.Continuing as normal for now is OK, but
SFC will let us know if
this changes.
* How could this be enforced? IP address scanning? Is there some retention
period for logs?
* Pono will follow-up with Karen about this.
* Does this only apply to people working at sanctioned companies, or everyone
living in the
country?
* [Alicja & others] - It may only apply to sanctioned companies.
* How does this apply to certain community members? We believe there is at
least one who may be
impacted.
# Next Leadership Meeting
* November 13, 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
https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
