This page lists processes and guidelines of the Code of Conduct Team.
CoC Team Processes
Conflict of Interest
Any member of the CoC Team may recuse themselves from participating in regards to a specific incident if:
- For personal reasons they don't feel comfortable being involved
- Their employer requires it if it involves an employee in the same company
To enable reports against members of the CoC Team, the CoC Team takes proactive steps to ensure confidentiality and prevent power above.
All emails sent to the CoC Team address go to all members of the CoC Team.
Emails sent to members directly are kept confidential unless required to proceed with the report. The reporter will be consulted about what of their report to share and with whom. If a report has been made against a member of the CoC Team they won't be notified or participate in discussions around their report. When action is taken against a member of the CoC Team, the rest of the team tries their best to hide the fact that a report has been made.
CoC Team composition
The CoC Team should try its best to select candidates which would make the team more diverse in terms of represented projects/interests as well as cultural and social background.
Anybody interested in joining the CoC Team is free to reach out to any of the current members directly or write to help@postmarketos.org.
It's expected that anybody joining the CoC Team will undergo CoC enforcement training which would be paid for by the postmarketOS board, or that they have gone through similar training in the past.
The members and of the CoC Team and their relevant affiliations are listed on the Code of Conduct page.
At least one member of the CoC Team should be a GitLab administrator, at least one member should be an infrastructure administrator.
Elections and Resignation
The current CoC Team may propose new candidates, the Core Contributors elect new CoC Team member among these candidates.
Members of the CoC Team have no term limit and can resign at any time.
The Core Contributors can remove a member of the CoC team with a 70% majority vote.
Personal Data Policy
The CoC Team keeps a permanent record of the following:
- Names and handles of the people the CoC team has taken formal action against
- Formal actions taken (bans, suspensions, improvement plans) alongside their reasons, duration, and date.
CoC Team Guidelines
The CoC team may take proactive actions independently or as a response to a report, these powers may also be delegated to administrators and moderators.
Documenting incidences
It's important to document things before taking actions, such as with screenshots. GitLab does not keep an edit history for comments, nor does it keep track of deleted comments. Taking a record of incidents is important for the CoC Team to be able to act on them and to potentially spot repeated patterns of behaviour.
Inappropriate comments
Take the following actions against comments that are inappropriate or hinder a healthy discussion:
- Edit the comment with a canned response such as:
- "This comment has been removed as discussion about Foo is off-topic, and should be discussed in its own issue"
- "This comment has been hidden due to inflammatory language, please assume good faith when participating in discussions."
- You can also delete the comment or add a spoiler tag when editing to preserve the original comment but have it be collapsed by default.
Be aware that no notification is generated for edited comments, unless you mention someone who was not mentioned before.
Limit engagement with problematic comments
Trying to argue with someone or accuse them of wrongdoing will many times make a situation worse, and can also complicate things from the perspective of the CoC Team. When problematic behavior occurs, it's recommended to keep responses brief and to the point - and to reach out to the code of conduct team if moderating the discussion fails.
Feel free to ask a more neutral person to deliver any messages in case there is a personal history between you and the persons involved or if you think it's better if the action can't be attributed to you directly.
Much of the text and process here is directly inspired by the freedesktop constitution.