Attendees: Julius Werner, Patrick Georgi, Martin Roth, Stefan Reinauer, Werner Zeh, Philipp Deppenwiese
Make the coreboot leadership process more open - We need to start posting the meeting minutes to the mailing list again. - Discussed whether to make the coreboot leadership meeting public. - There was a concern about people who don't contribute taking up the participant slots (25 max with hangouts) - The leadership meeting will continue to use google hangouts for now, but could switch to another method if there are problems. - Accept suggestions for agenda items from the community. - There was no discussion on how to do this - For now we'll just use the mailing list. Decision: Stefan & Werner both vote for publishing minutes and making the meeting public
Marc Jones hasn't been able to attend for a while, and hasn't been as active in the community as he used to be. Martin reached out to him, and he said he was open to having his spot on the leadership board replaced. - Google and Siemens have employees on the leadership board, so others working for those companies cannot be considered. - We have several nominees and we will be reaching out to those individuals to see if they're interested before making their names public. - Take this up again in the next meeting 2 weeks from now.
What is the process of decision making? - The coreboot project has 3 leaders who make decisions - currently Stefan, Werner, and Marc. - Discussed the idea of making some decisions regarding code (Like line length) up to a community vote. - Further Discussed who should be able to vote on these coding changes - Final decision was that when voting, the group will be people who have been participating in coreboot's gerrit. This means people reviewing code, writing code, commenting on code, etc. - Decision: Stefan and Werner both agree that using gerrit participation is a good method. - Martin will gather gerrit metrics and we can decide further on criteria at that point. - We could use a system such as the Condorcet Internet Voting Service: https://civs.cs.cornell.edu/civs_create.html - Stefan voices concern that anonymous voting will skew the results due to lack of culpability of voters
Look at hiring someone to work on the project - Philipp suggested that the coreboot project look at hiring someone to work on the project. - Google has Patrick Georgi as the coreboot community liaison - To hire someone, the project would need to bring in a large and steady amount of money to guarantee their employment - Would it make sense to request money from companies using and contributing to coreboot? - This would be similar to Arm Trusted Firmware - Major companies make significant yearly contributions. - Not a good idea for the project to hire coders directly, for various reasons. - Stefan - If we decide we need to help with the project, it should be someone to help with communications, marketing and community building. Paying people for random code reviews sets the wrong incentives for the community - Werner - Not in favor of hiring someone to do deep technical parts, but ok with the idea of hiring a community manager.
Action Items: - Martin - Send out meeting minutes to coreboot community (Done!) - Martin - Post invite for next public meeting and a way to collect agenda items (Done!) - Martin - Gather Gerrit metrics for review in the next meeting - Martin - Reach out to leadership board nominees
Ongoing issues for future meetings: - Revisit coreboot leadership nominees - Discuss a vote for line lengths and automatic reformatting
New agenda items for future meetings: - How do we get better/more code reviews? - Discuss a standard for changes required for adding a copyright header.
The next meeting will be 2019-04-10 at 17:00 UTC - https://coreboot.org/calendar.html
If there are any additional items that you'd like to have discussed in a future meeting, please respond to this email, and items will be added as time permits.
-
Martin Roth