# 2022-01-26 - coreboot Leadership
Attendees: Felix Singer, Jay Talbott, Werner Zeh, Tim Crawford, Patrick Georgi, Stefan Reinauer, David Hendricks, Eric Peers, Felix Held, Martin Roth, Daniel Maslowski, j. redpath, Christian Walter, Ron Minnich
Agenda / Minutes
* [Felix S.] flashrom is looking for mentors * [https://mail.coreboot.org/hyperkitty/list/flashrom@flashrom.org/thread/VADY5...) * Looking for mentors. If someone is interested in being a mentor, please respond to this mail mentioned above and also send a copy to Anastasia K. [aklm@chromium.org](mailto:aklm@chromium.org). * homepage.git: who should be able to set Verified+1 there? * Right now, only Stefan, Patrick and Martin can. * We could extend this to an existing Gerrit group, e.g. users who can submit coreboot changes, or create a new Gerrit group with this specific permission. * Patrick is created [a new group](https://review.coreboot.org/admin/groups/2a680d10d3cdc6990a84d68d1aa2e5413d3...) * Inherits the “Core Developers” group (those with submit rights to coreboot) * Allows adding more website maintainers who are not coreboot submitters easily * [Felix S.] coreboot GSoC participation * [https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/PGKTA...) * Looking for projects and mentors (see the email above) * [Jay T.] CAR layout for Xeon SP * workaround implemented in coreboot: [https://review.coreboot.org/c/coreboot/+/61164%5D(https://review.coreboot.or...) * SysPro and 9esec collaborating on solution and discussing with Intel * LVFS * Suggesting to provide coreboot for older/no longer supported (EOL) devices (postmarket) as an alternative on LVFS * [https://github.com/fwupd/fwupd/wiki/LVFS-Community-Meeting-2022-01-28%5D(htt...) * Should coreboot.org ship binaries? * No. * Probably best left to folks like Mr. Chromebox * Who would do Lenovo support? Libreboot et al ship binaries * Could make things easier for certain projects like Heads that already use coreboot. * Werner: Instability with eMMC devices * Need initialization, seems to be in scope for coreboot * ITRenew server heading for Martin still not there * Martin is ready (space, cables, …) * [New videoconferencing system?](#bookmark=id.ehzxgz9a1ta0) * Google changed policy to require Googler to allow access for Googler-initiated meeting. * Public version? 1 hour limit? Number of people? * coreboot account? * This seems problematic, but can be worked. It’s free for non-profits, but the SFC is the non-profit, not coreboot. * OSFF’s google meet? * BigBlueButton worked relatively well for most people, though some still seemed to have issues. * Matt - BBB did a poor job of filtering background noise. Not as good from an audio perspective. * Felix - same. Audio is much better in google meet. * Probably no * Jitsi * Tested [https://meet.jit.si/%5D(https://meet.jit.si/) Limits: 100 ppl is free limit * [http://meet.coreboot.org%5D(http://meet.coreboot.org) now exists, too. * Jitsi performed very well compared to all the other open source solutions that we’ve used. * Unfortunately it flopped in the buildbot discussion on Dec. 8 with only 8-10 participants (https://meet.coreboot.org/BuildbotJenkinsReplacement) * Does this work with firefox? * Firefox worked well compared to a couple of years ago. * In the vpub, we ran into a jitsi issue where some people couldn’t hear each other. * Downside: no phone bridges. If we had one or several SIP servers people can call into, we could hook it up (add-on feature on meet.jit.si but available OOTB for custom installs like meet.coreboot.org) * Audio propagation issues on meet.coreboot.org * Should we change videoconferencing systems for the leadership meeting or not? * Ron: projects keep trying to switch and keep coming back to meet. * Not urgent. If Meet gets too aggravating, waiting to join, we can decide at that point. * We're not going to change now. Meet gives consistently good audio and video quality even with a large number of people. We need to choose the defects, and can look again if we get fed up with google meet. * New social media accounts: * [https://mastodon.technology/@coreboot%5D(https://mastodon.technology/@corebo...) * [https://mastodon.technology/@flashrom%5D(https://mastodon.technology/@flashr...) * People who want to help promote them, reach out to Felix S. or Patrick G. * Decision making at flashrom * Project should get some structure, not on how the code is being managed but everything around it (e.g. Twitter accounts), who volunteers to reach out to folks?
# 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.