# 16th June 2022, 6:00 - 7:00 UTC+0
Attendees: Nikolai, Evan, Felix, Anastasia, Nico, Edward
## Decisions Summary
* We want a maintainers file as coreboot has one. Felix will take care of adding one and hooking it up to Gerrit so that the magic happens. * Active members of the community need to take care of other people's patches/discussions and if something goes wrong, help. For example, join a discussion on Gerrit and try to help to calm down people; bring people to talk in-person (for example on the meeting) instead of texting; ask each other if everything is okay with a patch/feature etc. Take care of each other.
* [FelixS] Reusing coreboot’s maintainer [file](https://github.com/coreboot/coreboot/blob/master/MAINTAINERS) mechanism for flashrom hooked up with the following [script](https://github.com/coreboot/coreboot/blob/51f3b3225504707ce6df81b12e373ce8ff... ). * I think it would be great if we could add a maintainers file, like coreboot has one, where people can be assigned to specific files or folders, and hook this file up to Gerrit so that maintainers are notified. * Edward +1 for driver owners. * aklm +1 especially for new people. * AI Felix to create a patch to introduce the MAINTAINER file and aklm to review to get this idea going. * [Edward] How do we get the community to adopt the [https://flashrom.org/Friendliness%5D(https://flashrom.org/Friendliness) policy for real? * Examples of violations are snide remarks of code reviews to poor grammar (non-native speaker), dissecting peoples speech and building up encyclopedias of text of authors motivations instead of straight to the point actionable items. * This *must* end! * How are remediation dealt with? * How are violations considered and what is the result of a violation? * Who (more than one person hopefully) is responsible for enforcement? * Maybe find a group of people outside of the flashrom community who could help with this? It seems like this is an issue that many groups struggle with. Maybe we can look at creating a group of people from various open source projects that can look objectively at any issues and make some decisions about how to deal with problems. Whether the projects want to accept and implement those decisions would be up to the individual project. My fear is that the flashrom project is too small to police these issues objectively. * [aklm] just for completeness: existing rules on the Friendliness page say the following: * “If you feel like you have been treated in an unfair way, we want to hear about it so we can fix it. Our arbitration committee (Carl-Daniel Hailfinger <email> and Stefan Reinauer <email>) can be contacted directly and will listen to you. If you don't get a response within a few days, your mail was probably lost. Feel free to resend your mail to another member of the arbitration committee in that case.” * Is this still up-to-date? Does this strategy work? * If code review goes bad , maybe pause for a moment . Maybe try to get a conversation in person? * Bring up very concerning issues in GVC. * It’s hard to admit fault or in trouble. * Take care of others to allow people to say they are in trouble. * If someone notices a discussion is going off the rails that person should be afforded the chance to try and help bring things back to the topic. * What to do (for active members of community) * First starting with the person is ok before deep diving into the technical issue that went off the rails. * Add yourself to the patch and comment on the patch, trying to extract relevant ideas * If a person is on the meeting , you can ask them if everything is alright with the patch/feature * Reach out to person by email , or private chat * Bring people to the meeting? * For new people: ask what they are trying to achieve? What are you trying to do? * Two separate patches should be considered independent. * Actively try to determine the point where things got misunderstood and try to refocus the discussion back to a simpler point to realign to make progress. * Less is more, simple points to bring things back to focus and help build bridges. * What can a person do who feels in trouble? * [aklm] I created a category in bugtracker “Easy Projects” so that we can have a collection of easy tasks (for example for new people). This may be easier to keep alive than [https://www.flashrom.org/Easy_projects%5D(https://www.flashrom.org/Easy_proj...) * Thanks!