Dear community, Please be reminded that our coreboot leadership meeting is scheduled for Wednesday, October 2, 2024.[1] Kindly review the current agenda and share your thoughts or suggest additional items you would like to see discussed during the meeting.[2] Thank you.
## Current Agenda Items ### [jpmurphy] Have we solicited or received feedback on why organizations choose not to use coreboot? * Have we solicited or performed technical analysis of how we compare to other solutions or what features may be missing? ### [Werner] Present the workflow for Feature Request and Implementation which is an outcome of one of the OSFF’s workstreams. ### [jpmurphy] I opened a bug within Google to update our best practices on bugs being used with coreboot. There are at least two options, asking for feedback/alternatives: * 1. Use a public component that everyone can see accessible at <code>(https://issuetracker.google.com/)</code> * Some bugs will still need to stay private to protect business needs and may create the need for secondary bugs. For this reason, some Googlers prefer we not use this approach. * 2. Instead of using BUG=b: fields within commit messages, googlers could use a different ID to make it more clear it’s a Google bug. Felix S had suggested ChromeOS-Bug-Id. ## Announcements & Events * OCP Global Summit: San Jose, California on October 15–17, 2024 https://www.opencompute.org/summit/global-summit [1](https://coreboot.org/calendar.html). [2](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ/edit?pli=1). _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
