coreboot leadership meeting notes are now public: https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ/edit#heading=h.j7tqwova2640
Anyone interested in joining the leadership meetings in the future can check the calendar on the coreboot website for call-in information. ------------------------------------------------------------ 22 May 2019 Attendees: PatrickG, Werner, Jay Talbott, Martin, Matt DeVillier, Felix Held, Stefan, Kerry Brown, Ron, Philipp, Dhendricks Topics: * Results of polls (See https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/OWHSSHB4F7FESMUGJKFRB37PR2AYM5LQ/) * Implement this after the 4.10 release. * Copyrights * Winner in poll: Create an authors file and remove all existing copyright lines * Discuss with SFC - need to figure out if there are any issues with removing copyright lines. * Characters per line * Winner in poll: 96 character lines. * Will reformat in conjunction with the clang-format * Update the contributor guidelines now, but the tree will lag behind for a while longer * Reformatting with clang-format * Winner in poll: Submitters should run clang-format before submitting a patch and it should be rejected in gerrit if it’s not formatted properly with an error telling them how to format it. * Will reformat the tree on a directory-by-directory basis and enforcement will start as directories are reformatted * Need to finalize clang-format options before we start * src/vendorcode will not be reformatted * Number of people voting varied by question 59/68/61 * coreboot contributor expectations * This will be a guideline for now - No significant penalties at this point. * Code should be maintained as long as a chip/platform is being sold? * Stefan feels that we shouldn’t have different guidelines for individuals and companies. * David feels like rejecting patches is going to stifle progress. * We will discuss this further on the mailing list. * If we make guidelines, the community will likely take these as rules and reject patches if they aren’t followed. * No decision made for now, review again next week. * Shall we add a CREDITS file a la Linux for people who contributed but are no longer active? * How is this different than the authors file? * Credits is for people who are no longer involved in the project. This is for people who authored code that is no longer in the master branch. * Can we make this part of the AUTHORS file? Or does it need to be its own thing? * Decision: Put the credits list in the Authors file. * Can we adopt on principle removing all cpp guards on protos? * Add cleanup task - remove guards specifically around prototypes? * Having the prototypes outside of guards turns a compile time error into a linker error. * We should be more strict about how we define our blocks’ APIs. We should make better definitions about what each block exports. Document these better, and maybe be more strict about what code consumes which function. * Keep header file guards * No decision made for now * Release - still plan releasing on May 28th. * Need to update release notes. Pad at https://piratenpad.de/p/coreboot4.10-release-checklist * Issue tracker: * Philipp: Can we replace redmine? * Stephan: Not with bugzilla. We've already tried bugzilla and trac. * Monorail? Only runs on app engine. * Some people are not sure how to address issues on current bugtracker as there’s no gerrit integration. * There is a Gerrit redmine plugin, which might help * Use github as our bugtracker? * This would probably encourage other github use like merge-requests, which we don’t want. * “its-redmine” (or other plug-in) for gerrit-redmine integration? https://github.com/cyrilix/its-redmine ------------------------------------------------------------ 8 May 2019 Attendees: PatrickG, Martin, Matt Devo, Felix Held, Stefan, Marc Jones, Philipp, PatrickR, David Hendricks Topics: * People are trying to subscribe to the coreboot security mailing list. Who should be on that list (and what criteria decide this)? * We don’t want this to be widely available to the public in case a significant security issue is announced. We want to make sure we can fix it before it’s announced to the public. * There’s currently nothing on the list, maybe because out code is great, and maybe because the list isn’t widely known. * Who should have access? * Currently Stefan & Patrick are the only 2 on the list * Martin: people who can merge code to coreboot? * Should we turn this into an alias instead of a mailing list? * AI:Patrick Add the security list to the website and announce on the mailing list. * Decision: Keep as a list so that there’s an archive * Decision: Keep the Stefan & Patrick as the only people on the list for now * Decision: Bring this up again once there is activity on security@ and we know better what to do. * Community votes * Decision: The poll will be set up to start on Tuesday (May 14), running until the next leadership meeting on May 22nd. * 4.10 process (pgeorgi hasn’t announced anything yet) * AI:Patrick will announce today * GSoC * 4 students have been accepted * All have arrived on the mailing list or IRC * Finding a leadership group replacement for Marc * David Hendricks is the only one who responded to the self nomination. * Werner supports David to replace Marc (as claimed by Martin) * Stefan supports David * Marc also supports David * Decision: David Hendricks is voted in to replace Marc * David: “Thank you” * AI: Martin will notify the SFC (Done) * Martin to push picasso documentation to coreboot * Writing now, Need to get permission from AMD before publishing. * OSF Hackathon (June, Bochum) * Lunch will be served there, dinner is Hunt-Your-Own-Food * OSFC * We have some sponsors, but are still getting more * Ron needs photos from people “looking younger than they look today” for his anniversary talk * FSP 1.0 migration * Intel doesn’t seem to want to invest any resources in an update * Who is the owner for these at Intel? Is there a contact at this point? * Dhendricks might be able to work to get these updated to FSP 2.0 * AI: Patrick will look into the reasons for the migration (mailing list etc) and potentially write up a doc * Issue tracker * Over 200 users have applied but haven’t been authorized (never logged in). * Set up automatic notifications on IRC & current mailing list (& Set up new Mailing list if the bugs become too noisy) * AI: Patrick will look for plugins to get this set up. _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
