[coreboot] coreboot Meetings Announcement And Agenda Call
Dear community, Kindly note that we have an upcoming coreboot leadership meeting scheduled for Wednesday, June 12,2024.[1] We encourage that you please take a moment to update the current agenda items with matters you wish to see discussed during the meeting.[2] Thank you for your continued commitment and support to the coreboot project. Best regards, Mina Asante. [1](https://www.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
[coreboot] coreboot Meetings Announcement And Agenda Call
Dear community, Kindly note that we have an upcoming coreboot leadership meeting scheduled for Wednesday, May 29, 2024.[1] We encourage that you please take a moment to update the current agenda items with matters you wish to see discussed during the meeting.[2] Thank you for your continued commitment to the coreboot project. Best regards, Mina Asante. [1](https://www.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
[coreboot] coreboot Meetings Announcement And Agenda Call
Dear coreboot community, Please note that our upcoming coreboot leadership meeting is tomorrow, May 15, 2024.[1] You are welcome to review and update the current agenda items with matters you wish to see discussed during the meeting.[2] ## Current Agenda Items ### [Martin/Max] ARM has published their new spec with the coreboot stuff in it. * [ARM Base Boot requirements version 2.1](https://developer.arm.com/documentation/den0044/latest/) * coreboot doc:(https://docs.google.com/document/d/1z3fLdUmbOBKvHJfub8ki9YWjuqpK_1PY0H4BWwm4jh8/edit#heading=h.8ibdr2g3se3) *  ### [Martin] 24.05 release ### [Martin/Felixs] Server updates * Jenkins has been moved to the new coreboot server * Fossology will be moved soon * Gerrit and the git repos will follow * Additional coreboot services to move * Website * Gallery * Blog * Wiki * Gopher * Not moving: * Mailing list server is staying on the current machine. ### [Martin/FelixS] coreboot Brochure * [coreboot Brochure](https://docs.google.com/document/d/1l-dSWram1vpq6-fYYqecYmOXCpj_7YXSnBx-kaKftdU/edit#headig=h.ojn1hjjk61bs) ### [Martin] coreboot expectations for silicon initialization * I wrote a document to capture what we want from FSP and AMD openSIL. [coreboot expectations for external silicon init modules](https://docs.google.com/document/d/151yYCRMFoxJEqKrT10hntxjy3AjB_mHLDtXCJRQ9M0/edit#headin=h.jjzykfo62hda) ### [Martin] What coreboot swag do people want for OSFC? * Do we want just the rabbit logo, or the logo and text? Here are some ideas: * coreboot MX-Cherry keycap for their super key $10 (min 1) * Glassware - Tumblers / mugs with carved coreboot logo $22 (Min 24) * T-shirts - Embroidered logo $24 (min 10) * Case badge - 25 mm x 25 mm $7 (min 10) * Keyboard badge - 13 mm x 38 mm $7 (min 10) * High quality ‘Executive” lanyard 25 mm w/ detachable ends $3 (min 100) * High quality Temporary Tattoo 10cm x 10cm $21 (min 1) * Chocolate bars * Etched HOTO screwdriver pen set $30 (https://hototools.com/products/24in1-precision-screwdriver). ## Announcements & Events * FOSSY conference: August 1-4 2024 in Portland, Oregon, USA https://sfconservancy.org/fossy * [Community track proposals](https://sfconservancy.org/fossy/community-tracks) are open until April 18, 2024. * COSCUP - Taipei, Taiwan on 2024/08/03 ~ 2024/08/04 https://coscup.org/2024/en/landing * OSFC will be in Bochum Germany - September 3-5, 2024 https://www.osfc.io * [Call for participation](https://talks.osfc.io/osfc-2024/cfp) is open until May 31st, 2024 * OCP Global Summit: San Jose, California on October 15–17, 2024 https://www.opencompute.org/summit/global-summit [1](https://www.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
[coreboot] coreboot Meetings Announcement And Agenda Call
Dear community, Kindly note that we have an upcoming coreboot leadership meeting scheduled for Wednesday, May 15, 2024.[1] We encourage that you please take a moment to review and update the current agenda items with matters you wish to see discussed during the meeting.[2] Thank you for your continued commitment to the coreboot project. Best regards, Mina Asante. [1](https://www.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
[coreboot] coreboot Meetings Announcement And Agenda Call
Dear coreboot community, We are happy to announce that our upcoming coreboot leadership meeting is scheduled for Wednesday, May 1, 2024. [1] Kindly take a moment to review and update the current agenda items with matters you wish to see addressed during the meeting. [2] Thank you for your continued commitment to the coreboot project. Best regards, Mina Asante. [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
[coreboot] coreboot Meetings Announcement And Agenda Call
Dear community, We are happy to announce that the next coreboot leadership meeting is scheduled for Wednesday, April 17, 2024. [1] Kindly take a moment to update the current agenda items with matters you wish to see addressed during the meeting. [2] Thank you for your continued commitment to the coreboot project. Best regards, Mina Asante. [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
[coreboot] coreboot Meetings Announcement And Agenda Call
Dear community, Please note that the upcoming coreboot leadership meeting is scheduled for next Wednesday, February 21, 2024.[1] You are welcome to update the current agenda items with matters you wish to see addressed during the meeting.[2] ## Current Agenda Items ### We’ve switched to BigBlueButton for this meeting. * https://bbb.sfconservancy.org/b/mar-sfn-e22-axi * For phone access, call +1-718-247-9666, then enter 89421 as the conference PIN number. * It looks like there’s only a USA phone number. * I found some apps, but they seem to be to run the meeting, not to join it. * See the coreboot calendar for times and more information ### [FelixH] Look at the type that we should be using for readXX * Currently we’ve been using void*, but it’s been argued that using an uintptr_t would be preferable. * Should we use ‘_Generic’? * We’d like to have just a single type. ### [Nico] Revoking Gerrit privileges as punishment. I would like to discuss two matters about this. Not sure about the order. * My own case: I was removed from the core developers and reviewers groups 20 months ago. Without any charge nor chance to defend myself. There was Stefan's sentence, a discrediting rant about me with accusations that fit me not more than many other people, and an offer to reduce the sentence to a month if I were willing to come to the table. Which didn't make sense because I reached out to people long before Stefan's mail and it took Stefan, not me, over three months "to come to the table". And then he still couldn't tell me what I did worse than others. I asked again, Werner this time, what my charge is in 2023, again without results. And now I'm asking again. How can we make things better when we can't even say what was wrong? * [Martin] These issues are not discussed in a public forum where everyone with a pitchfork can get involved. That’s not useful. If you feel that the issues which led to this action being taken have changed, please email all the members of the leadership. Matt, Werner, and David. * Should we use Gerrit privileges as punishment at all? If so, shouldn't we have rules about it? * We will add this to the code of conduct page: ``` As a part of running the project, coreboot leadership has the right to revoke privileges as they see fit. This is not done lightly. Over the history of the coreboot project, there have been only a handful of times where an action needed to be taken. Discussions about these actions are not done publicly, for obvious reasons. If someone believes that the circumstances that led to an action have changed, please send an email to all the members of the leadership team for discussion. ``` * I will note that this text is already there: ``` If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event). ``` * https://doc.coreboot.org/community/code_of_conduct.html * Doesn't it hurt the project more when it loses a reviewer? (who can still get their own patches merged anyway). * [Martin] I’d say yes, and that’s something that the leadership group has to weigh when they decide to take an action against an individual. * [David] Yes, it does hurt the project when it loses a reviewer (or any contributor, for that matter). That's why it's important to deal with "toxic developers" effectively - to prevent others from leaving the project. No one developer is worth several others who will refuse to work with them. * Should we maybe do the opposite? don't merge their patches unless they do review? * [Martin] When the issue is something other than the quality of a person’s code, it doesn’t make sense to punish them by refusing to allow their patches to be merged. As many people in the community have jobs where they’re required to push code to coreboot, that could be the equivalent to getting them fired, which seems unfair. * If we want to use such punishment, should we apply it to other privileges as well? e.g. administrators, leadership members (IMO very important for trust inside the community) * [Martin] If two members of the leadership voted to take action against a third member, that’s completely allowed. The leadership team can take action as needed. I’ll note that I myself had submit rights taken away for a year. Yes, I’m one of the handful of cases mentioned. ### [Martin] Remove ChromeEC as a submodule - reimplement like a payload * The ChromeEC can currently be built (for some platforms) as a part of the coreboot build. It’s being downloaded as a submodule right now, but this creates a number of issues. With the change to Zephyr, the build process and requirements have changed. To address this, I’d like to propose that we drop the ChromeEC as a
[coreboot] coreboot Meetings Announcement And Agenda Call
Dear community, Kindly note that the upcoming coreboot leadership meeting is scheduled for Wednesday, February 21, 2024. [1] Please take a moment to update the current agenda items with matters you wish to see addressed during the meeting. [2] [1](https://bbb.sfconservancy.org/b/mar-sfn-e22-axi). [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
[coreboot] coreboot Meetings Announcement And Agenda Call
Dear community, Kindly note that the upcoming coreboot leadership meeting is scheduled for Wednesday, November 29, 2023. [1] You are welcome to add things you wish to see addressed during the meeting to the current agenda items.[2] ## Current Agenda Items ### [Arthur] A new bootflow on ARM64 server using more of TF-A - Motivation: More ARM-Server support in coreboot. - ARM wants to put coreboot in the ARM Base Boot. Requirements: https://developer.arm.com/documentation/den0044/latest - Vendors are more inclined to consider coreboot if it is in a spec written and supported by ARM. - It is currently planned to put the TFA -> coreboot -> Linuxboot bootflow in there as an alternative to the EDK2 variants. TFA can be open source as well as closed source so it is not entirely the same as letting FSP start at Reset. - The Idea is that coreboot is considered by big Vendors when they formulate their specs (so that coreboot doesn’t have to hack around to make stuff work for it). - Reuse working solutions (TF-A) can be a good idea: easier porting. - The scope of the coreboot side of things is small and very reusable: generating SMBIOS and ACPI is quite portable between platforms. - patches necessary to accomplish this mainly are the following: - https://review.coreboot.org/c/coreboot/+/74798/9 - https://review.coreboot.org/c/coreboot/+/78284/8 - patch missing that grabs FDT in bootblock (like done in RISC-V bootblock) - Using only ramstage can be minimally invasive. A similar thing was done to optionally build romstage sources inside the bootblock: https://review.coreboot.org/c/coreboot/+/55068 - coreboot's security model often relies on it being the first code that executes. This might need some changes. - Handoff data from TF-A is often in FDT format for which ramstage has support. - TF-A is BSD3 licensed. You may not always have access to the source code for your platform. - Maybe the ease of use and quality of coreboot convinces a more full adoption on server (use only BL31 like other platforms)? Maybe I'm naive on this? * [Martin] 1) This is taking a piece of coreboot and using it in a different way than normal. I recommended on the mailing list that we call this flow something other than just "coreboot' so as not to confuse things or dilute the meaning of what coreboot is. Maybe "ATF with coreboot technology" or something. 2) This allows us to expose coreboot to people who would otherwise be using a completely different solution. That's a *really* good thing in my opinion. 3) We should try to be a good player in the open source firmware space and work with other projects to create solutions. If this means using pieces of coreboot, I'm all for it, similar to wanting to be able to take pieces of other projects and use them to extend coreboot's functionality. Sure, we could block it here and force it to be forked, but that doesn't really help anyone. 4) Maybe to differentiate this, we can go further than just making it a Kconfig option and actually add a new makefile target. That would make it even more plain that this isn't the full coreboot build. ### [Martin/MaxB] Look at improving the readability of our build system * Our current build system uses make, but stretches it way beyond most makefile-based build systems. This was done to add abstractions which, for example, make it much easier to add files to the various stages. Because of this complexity at the heart of the build, it can be very difficult to understand what’s going on in any given section. One way that is being looked at to improve this is indentation of the if clauses, but this is problematic without rewriting some sections. See CB:79230 * PatrickG encourages folks to consider Burning the Diskpack because he feels that people are too reverent about old work. The build system is 14 years old (and replaced a build system that was 10 years old at the time): if there’s an opportunity to achieve a significant improvement in that area by replacing what we have with something else, go for it! (That doesn’t mean that it must be done. But consider it besides the various fixes that could be applied) * [Martin] I agree with Patrick, but have some qualifications. 1) We’re replacing an existing system that works. Is this the best place to spend our resources? 2) Because it would be replacing a working system, there should be relatively substantial benefits to be gained by updating before it’s considered. 3) As Patrick doesn’t want to discourage change just because the build process is old, we also shouldn’t look to throw it away just because it’s old. (Patrick agrees with all of that) ### [Patrick, Martin] How to present design proposals? * There’s some tension in the project between “folks write a whole new thingamabob and dump it on the project, and get indignant when the project doesn’t adopt it wholesale,
