# 2023-10-04 - coreboot Leadership Meeting Minutes ## Attendees
David Hendricks, Christian Walter, Daniel Maslowski, Felix Held, Jay Talbott, Julius Werner, Karthik Ramasubramanian, Martin Roth, Matt Devillier, Maximilian Brune, Mickey, Simon Glass, Tim Crawford, Werner Zeh, Wilhelmina Asante, Stefan Reinauer. ## Action Items
- Martin: Write a tutorial for gerrrit.
- OSFF: Look into making a video about using gerrit.
- Martin: Write a documentation about vendorcode submodules.
- Martin: Work with David to create a vendorcode submodule for intel.
- Simon: Will send patches related to RFCv2 for post-build control of the serial console.
> Fallback method
> Add enums. ## Minutes: ### OSFC 2023 - California Bay-area in October - Next week!
* Tickets are available at [https://osfc.io%5D(https://osfc.io) ### sjg - RFCv2: Post-build control of serial console There’s been a lot of discussion about this on the mailing list, but not much contribution from anyone other than Simon and Martin. Are others ambivalent?
* There have been complaints about people just doing things without consulting the community first, but this lack of comment makes it feel like that’s just complaining, and it doesn’t actually matter.
* Simon will send patches.
* Fallback method
* Add enums ### Martinr] How do people feel about recording the coreboot leadership meeting and posting them on youtube or something so that others can watch them later?
* Martin] I got one comment opposed to this idea because we sometimes discuss things of a more private nature that we don’t want to go into the minutes. If we record a video, these items can’t be private.
* [FelixS] I don’t like that for that same reason either. Also, I fear that it becomes more comfortable to do discussions (or even decisions) at the meeting instead of on the mailing list where more people can participate.
* Nobody is in favor of this. ### Martinr] Gmail has flattened the minutes to a list instead of maintaining indentation a couple of times. The coreboot blog does the same. What’s the best way to distribute the meeting minutes?
* [PatrickG] won’t be there, so put it on here: markdown files in Documentation/? That keeps them for eternity, though… (but so do mailing list and blog posts)
* [Martin] If we’re satisfied with just text formatting, we can just keep posting the minutes to the mailing list, it just seems like we could do something with better native formatting.
* This makes it hard to have a dialog.
* Mailing list should work even if the minutes are just text.
* Look at attaching as markdown.
* Look at modifying the way we’re taking minutes?
* Use a different service - Use a markdown editor to take minutes?
- Etherpad
- Trippad
- [https://codepen.io/%5D(https://codepen.io/).(Online code editor)
- [https://hackmd.io/%5D(https://hackmd.io/). (Hackmd.io)
- [https://hedgedoc.org/%5D(https://hedgedoc.org/) (hedge)
- [https://codi.hostile.education%5D(https://codi.hostile.education)
- [https://codepen.io/%5D(https://codepen.io/).(Online code editor)
- [https://hackmd.io/%5D(https://hackmd.io/). (Hackmd.io)
- [https://hedgedoc.org/%5D(https://hedgedoc.org/) (hedge)
- ( [https://codi.hostile.education%5D(https://codi.hostile.education) is Daniel Maslowski's personal instance)
* Something that formats the meeting minutes so they can be easily copy+pasted to the mailing list without ruining formatting. ### Martinr] Incentives for work.
* In an email exchange Daniel Gröber mentioned that he feels like gerrit gives less incentive to do work as it isn’t seen as widely. Thoughts?
* [https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/message/DPF5...)
_I like to philosophize about incentives. So what incentives does a contributor have to get themselves added to that maintainers list?_
_The cynic in me says: none. It's just hard work nobody wants to do, but that doesn't explain the fact that there are in fact plenty of mostly-volunteer projects with a thriving development community._
_My current theory is, this happens when people see some kind of social reward for doing that hard work._
* One big issue is a lack of hardware. Most modern platforms are not hackable easily.
* New platforms are mostly done by companies, so focus on community work?
* How can we improve as a community?
* Can we find a cheap board that can be ported? Make a class?
* FelixS is working on this with the up-extreme - unfortunately a little bit expensive. Has everything that’s needed for development, and are very small.
* Need documentation
* Simon] Indexed approach to finding docs.
* What infrastructure there is.
* [Maximilian] Enhance online presence for blogs
* Martin] I’m not sure if this is accurate, but I’m often wrong. We could do a number of things, like send merged patches to email, weekly lists of contributors to email, add contributors to release notes, or something similar.
* Simon] Gerrit does make patches sort of invisible.
* Maximilian] Not sure of the issue with gerrit.
* DanielM: Maybe do some gerrit documentation.
* Martin is willing to write up a tutorial.
* Many people are used to github workflow, which is very different. Need to educate people.
* Matt] In the dashboard it shows patches in order of activity - This is frustrating. Documentation could help - how to view patch trains.
* FelixH] Multiple people confused about merge conflicts later in the patch train.
* Werner] Make a webinar talk about using gerrit?
* [FelixS] People could record a video and upload it on our youtube channel as a timeless alternative
* Felixs] What can we link to?
* https://review.coreboot.org/c/coreboot/+/76937
* Pretty much anything that people think would be useful. ### Martinr] Make vendor code submodules that the vendors are responsible for instead of having that code go directly into coreboot?
* Embedded into the structure, not at the top vendor code level.
* All submodules will have a copy of the code hosted by coreboot.org
* Not forcing vendors to use submodules, but making them available. # Next meeting
October 18th, 2023
* [Meeting link](https://meet.google.com/pyt-newq-rbb (https://meet.google.com/pyt-newq-rbb))
* [coreboot Calendar](https://coreboot.org/calendar.html (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/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKj... (https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKj...)