Attention is currently required from: Anastasia Klimchuk.
Patch set 3:Code-Review +2
16 comments:
Patchset:
Random thoughts and rephrases, feel free to ignore
File doc/about_flashrom/team.rst:
All contributors and users are expected to follow Development guidelines,
Code of Conduct and Friendliness guidelines.
We kindly request all contributors and users to adhere to our Development guidelines, Code of Conduct, and Friendliness guidelines.
:
Members of the group can do full approval of patches (i.e. vote +2).
In general, members of the group have some area of responsibility in the MAINTAINERS file,
and are automatically added as reviewers to patches when the patch touches this area.
The responsibilities are the following.
* React to patches when added as a reviewer.
* Try to respond to technical questions on the mailing list if the topic is something you know about
and can provide a useful response.
* Know development guidelines and check the patches you are reviewing align with the guidelines.
This group is made up of individuals who hold the authority to fully approve patches, signified by a +2 vote. As a rule, members of this group often shoulder specific responsibilities noted in the MAINTAINERS file and are automatically included as reviewers for patches that touch upon their areas of responsibility.
Here is a list of what's expected from a member of this group:
Members of the group can merge patches.
The responsibilities for the members of the group are described in more details below.
Members of this group are authorized to merge patches. Below is a more detailed description of the group members' duties.
There is no expectation on how much time you spend on your duties, some non-zero amount of time,
whatever capacity you have. But in general, you stay around on flashrom.
We don't set any stringent demands on how much time you should devote to your duties. Any non-zero amount of time, as per your capacity, is appreciated. However, consistent engagement with flashrom and the community is expected.
If you disappear for some time (life happens), especially for a longer time, like several months,
especially without a warning: you implicitly agree that the others will handle the duties and make decisions if needed
(potentially without waiting for you to come back, if the decision is needed quickly).
If circumstances cause you to step away for a considerable length of time, particularly for several months and especially without notice, it is assumed that the remaining team members will take up your responsibilities and make necessary decisions (possibly without waiting for your return if a quick decision is required).
Patch Set #3, Line 44: Merge all contributors's patches (when they are ready), not just your own.
Merge all contributors' patches when they're ready, not just their own.
Members of this group are expected to:
Be at least vaguely aware what development efforts are ongoing, this helps to make decisions
in what order the patches should be merged, and where could be merge conflicts.
Maintain a basic awareness of ongoing development efforts to aid decision-making regarding the sequence of patch merging and possible merge conflicts.
Patch Set #3, Line 49: Know development guidelines, and educate other contributors if needed (e.g. give links).
Understand the development guidelines and guide other contributors if necessary, for example by providing relevant links.
Patch Set #3, Line 51: * React to patches when added as a reviewer.
Engage with patches when marked as a reviewer.
* Try to respond to technical questions on the mailing list if the topic is something you know about
and can provide a useful response.
Attempt to respond to technical inquiries on the mailing list if the topic falls within your knowledge and you can provide a helpful response.
Patch Set #3, Line 56: * From time to time show up in real-time channel(s) and/or dev meetings.
Occasionally participate in real-time channels and/or developer meetings.
* Follow the Code of Conduct and Friendliness guidelines, be a good example for others.
Adhere to the Code of Conduct and Friendliness guidelines, setting a positive example for others.
* Bonus point: if you work in a [software] company, educate and help contributors from your company
with upstream culture and dev guidelines.
Bonus: If you're employed at a company that uses flashrom, please try to guide and educate your company's contributors about the upstream culture and development guidelines.
To view, visit change 76075. To unsubscribe, or for help writing mail filters, visit settings.