Changes to Draft RIPE Code of Conduct: Process and Consequences
|Legend||(+) Added||(-) Deleted|
|Changed||Tag Added||Tag Deleted|
This draft process document has been produced by the delete: <a data-val="80dc2d86e8b0481aafe8c30b9bea0c00" href="../../../../../resolveuid/80dc2d86e8b0481aafe8c30b9bea0c00" data-linktype="internal"> insert: <a data-val="80dc2d86e8b0481aafe8c30b9bea0c00" href="../../../../../resolveuid/80dc2d86e8b0481aafe8c30b9bea0c00" data-linktype="external"> Code of Conduct Task Force . Any discussion of this draft should take place on the insert: <a data-val="https://www.ripe.net/mailman/listinfo/ripe-list/" href="https://www.ripe.net/../mailman/listinfo/ripe-list/" data-linktype="external"> RIPE Discussion List. List insert: </a> . insert: </p>insert: <p>
Note: square brackets in this document indicate links that will be added once all documents are approved. insert: </p>insert: <p>
Comments are also invited on the accompanying document on insert: <a data-val="c7f611fce3d1418a832374f5da458453" href="../../../../../resolveuid/c7f611fce3d1418a832374f5da458453" data-linktype="internal"> appointment and responsibilities of the CoC Team insert: </a> .
Deadline for comments: 2 May 30 September 2022
Download delete: <a data-val="9483e08900ca4b2384f03566a686dd12" href="../../../../../resolveuid/9483e08900ca4b2384f03566a686dd12" data-linktype="internal"> insert: <a href="http://www.ripe.net/publications/docs/ripe-documents/other-documents/draft-ripe-code-of-conduct-process-and-consequences/@@diff-items?id=draft-ripe-code-of-conduct-process-and-consequences-v2" data-val="http://www.ripe.net/publications/docs/ripe-documents/other-documents/draft-ripe-code-of-conduct-process-and-consequences/@@diff-items?id=draft-ripe-code-of-conduct-process-and-consequences-v2" data-linktype="external"> Draft RIPE Code of Conduct: Process and Consequences v2 changes (PDF)
Status of This Document
This is a draft document prepared by the Code of Conduct Task Force for review by the RIPE community. It is based on similar documents developed by the Python and Mozilla communities.
This document describes the process to be followed by the Code of Conduct (CoC) Team when handling reports. The same process applies equally to everyone who participates within the RIPE community.
How the Code of Conduct Team Relates to the Rest of the RIPE Community
Everyone who organises activities or fills a role within the RIPE community has a responsibility to make sure that people understand what is appropriate behaviour. However, only the CoC Team is responsible for handling reports and making decisions about outcomes.
WG Working Group chairs are responsible for their respective mailing lists and WG sessions in a proactive way. In contrast, the role of the CoC Team is a reactive one – it will only act once a report has been submitted. As If a WG chair thinks someone has breached the CoC in one of their sessions, they will report this is likely to be more complicated in practice, establishing who has the final authority in every case does not seem helpful. Instead, it is expected that the to the CoC Team. The WG chairs Chair Collective and the CoC Team will liaise as needed and that the two groups will maintain a cooperative relationship.
This section describes the steps the CoC Team will take when handling reports.
1. Report is Submitted
People can submit reports electronically [electronically] or in person. They will receive by speaking with a member of the CoC Team in-person at an event. RIPE NCC staff can also help people to contact the CoC Team if needed. insert: </p>insert: <p>
When someone makes a report, they will get confirmation that the CoC Team it has been received their report and it and is being reviewed. reviewed by the CoC Team. When a report is made in-person, the CoC Team a member who receives the report will of the CoC Team will take notes and make sure it is properly entered into the system.
Electronic reports can also be submitted anonymously. In this case, the person making the report will not receive a confirmation or be notified of any outcomes. insert: </p>insert: <p>
The member of the CoC Team who receives a report will be responsible for forming an assessment group to handle the report. The purpose of this triage step is to make sure the report is not seen by more people than necessary.
2. Assessment Group is Formed
The assessment group will be formed within one week of a report being made. In practice, this will often need to happen much faster, especially during an event. This smaller group should consist of three people: at least two members of the CoC Team and one RIPE NCC staff member who is appropriately qualified. The member of the CoC Team who initially received the report would preferably be one of the two CoC Team members in of this group.
Before assessing a report, CoC Team members will consider whether there are potential conflicts of interest. Reviewing the names of the people involved should be enough to determine whether this is the case. Any members of the assessment group who see a potential conflict of interest will recuse themselves so that someone else can take their place.
3. Report is Assessed
Depending on the nature of the report, elements of the assessment process may include (but are not limited to):
- Contacting the subject of the report to hear their side of the story
- Obtaining reports from witnesses
- Reviewing any relevant materials (photos, videos, screenshots, messages, emails, etc)
- Consultation with others as appropriate
- Group discussion and assessment of the evidence
The role of the RIPE NCC staff member in the group is to provide administrative and legal support to the volunteers on the CoC Team as needed. Members of the CoC Team will do their best to be discreet when assessing reports.
4. Decision is Made
Once the assessment group feels that it properly understands the reported incident, it will decide whether this represents a breach of the Code of Conduct. If the group believes that a breach has taken place, it will agree on a course of action.
When deciding on the appropriate actions, outcomes, the group will consider a range of factors, such as the severity of the breach, its impact on others, and any past incidents involving the same person. person, and the potential for future harm to members of the community. insert: </p>insert: <p>
Actions taken by the CoC Team can be understood as ‘minor’ or ‘serious’ outcomes. An example of a minor outcome would be giving someone a warning and asking them not to repeat certain behaviour. Serious outcomes are where the RIPE NCC needs to implement an action, such as revoking someone’s RIPE Meeting badge, banning them from future meetings, or removing them from a mailing list.
In cases where the group believes that strong consequences serious outcomes should be applied, such as expelling someone from a RIPE Meeting, it may notify or seek input from other parties, such as the RIPE NCC’s Events Team or Legal Department. However, while it might seek input from other parties, only the assessment group is responsible for making a final decision.
If the group decides that serious outcomes are required, it will inform the RIPE Chair Team and the RIPE NCC before any next steps are taken. insert: </p>insert: <p>
Once the group has made its decision, the relevant parties will be notified of the outcome as appropriate. In all cases, both the person who made the report and the subject of the report should be informed. delete: </p> delete: <p> If the group decides that strong actions Where possible, this notification should be taken, it will inform the RIPE Chair Team and the RIPE NCC happen before they any outcomes are implemented. applied.
5. Required Actions Outcomes are Taken Applied
Once the assessment group has decided on next steps, outcomes, it will arrange for them to be implemented applied as soon as is practical and appropriate. Depending on the outcome, the RIPE NCC may need to take certain actions and the staff member who supported the assessment group will be responsible for making sure this is done. They will report back to the CoC Team as appropriate.
People who dispute the outcome of a report can contact the CoC Team to make an appeal. An appeal must be initiated within one month of being informed of the outcome. In this instance, a different group of CoC Team members must review the case. The request for an appeal will probably not prevent certain consequences from being applied. For example, someone who is ordered to leave the RIPE Meeting will not be able to remain at the meeting while their appeal is being considered.
6. Decision is Recorded Recorded
The RIPE NCC will maintain a record of all assessments made by the CoC Team. Any personal data contained in these assessments will be stored and processed according to the relevant European data protection regulations, for the periods and purposes described below. delete: </p> regulations. insert: </p>insert: <h2>
Data Protection Information insert: </h2>insert: <p>
Assessments by the CoC Team will contain the personal data (for example: name, email and/or phone number) of the following people: insert: </p>insert: <ul>
- insert: <li>
- The person named in the report insert: </li> insert: <li>
- The person who submitted the report insert: </li> insert: <li>
- Any witnesses or others included in the report insert: </li> insert: </ul>
Personal data will be retained processed for the following purposes:
- For the RIPE NCC to maintain records that allow it to implement any actions required as part of the CoC Team’s decisions instructed by the CoC Team
- For the CoC Team to review consider past behaviour of individuals and context when deciding on actions (i.e. investigating reports insert: </li> insert: <li>
- For the CoC Team to inform the relevant parties of any outcomes insert: </li> insert: <li>
- To inform the relevant parties and request additional information in the event of repeated breaches of the CoC, or repeated invalid reports from or about the same person). an appeal
Regarding the periods for which In line with the definitions of ‘minor’ and ‘serious’ outcomes (see section 4 above), the personal data will be retained, a distinction is made between ‘minor’ and ‘major’ breaches of the CoC. A major breach is defined as a case where the RIPE NCC is required to implement of everyone included in an action. Examples could include revoking someone’s RIPE Meeting badge assessment will be retained for the following periods: insert: </p>insert: <ul>
- insert: <li>
- 18 months for minor outcomes or removing them from a mailing list (numbers 4-8 and 3-6 on the first and second lists of potential consequences in the next section). delete: </p> delete: <p> In the event of a minor CoC breach, or if a report is reports that are not considered to be a breach of the CoC, CoC. insert: </li> insert: <li>
- 36 months for serious outcomes. If the RIPE NCC needs to apply a ban or similar outcome for longer than 36 months, it will retain insert: <u> only insert: </u> the data of the person named in the report for the corresponding period. insert: </li> insert: </ul>
All personal data will be retained for a period of 18 months. For major breaches, personal data will be retained for 36 months. In cases where actions are applied for a period that exceeds 36 months (e.g. banned from attending RIPE Meetings for five years), personal data will be held for only as long as these actions must be maintained. delete: </p> delete: <p> removed from assessments once the relevant periods have expired. Assessments will also contain the personal data of the people who made the report and any witnesses. This will be retained according to this 18/36 month timeframe depending on whether the report is related to a minor or major CoC breach. In the case of longer-term actions that exceed these periods, the personal data of these other parties will not be kept for an extended period. In the case of an appeal, the personal data of all parties will be retained until the conclusion of the appeal process. This would be to allow the CoC Team to inform relevant parties of any outcomes and to follow up if more information was needed. delete: </p> delete: <p> Once the period for which personal data may be kept has expired, it will be removed from any corresponding assessments. These assessments can then be stored indefinitely. This will allow the CoC Team to identify trends and to see what review actions it has taken in previous cases. It will also allow cases. insert: </p>insert: <h2>
Statistics and Reporting insert: </h2>insert: <p>
The CoC Team will share anonymised statistics to be shared with and update the RIPE community for transparency. on its work and identify areas for improvement at least once each year. Statistics might include the number of reports submitted over a certain period, categories of reports, number of reports that resulted in were valid, and a summary of actions being taken and a summary of actions taken, etc. on the basis of reports.
Potential Consequences of Breaching the CoC
This section outlines some of the possible actions outcomes that may be taken as a result of from breaching the RIPE Code of Conduct. It is important to be clear that these are all examples and are not definitive lists. This is especially the case as not every form of participation is described, such as interactions via instant messaging or at virtual events. Both lists are ordered on a scale from least to most serious.
When deciding where on this scale a specific case belongs, the Code of Conduct Team will consider a number of different factors, such as whether that person has done anything similar in the past and how they have affected others. The CoC Team are empowered by the RIPE community to apply their best judgement when selecting a consequence for an action.
Meeting Sessions and Social Events
- Asked to apologise Told not to repeat a certain kind of behaviour
- Removed from the room for a period of time to allow emotions to settle
- Removed from the room for the remainder of a session
- Removed from the meeting venue for the day
- Removed from the social event for the remainder of the event
- Removed from the meeting venue for the remainder of the meeting
- Not allowed to attend future events for a period of time
- Permanently banned from attending RIPE events
Note: in the case of virtual events, consequences would roughly correspond to their real-world equivalent. For example, someone might be asked to leave a conference call to calm down rather than leaving a physical room.
- Asked to apologise Publicly told not to repeat a kind of post
- Temporary ban from posting to the list
- Permanent ban from posting to the list
- Temporary ban from posting to any RIPE mailing list
- Permanent ban from posting to any RIPE mailing list
Loss of Community Role
The procedures to remove people from various roles within the community are covered in the relevant RIPE Documents. The CoC Team does not have any additional powers in this regard, and so this is not a consequence an outcome it can apply. However, it may be the case that a person is no longer able to carry out their role after other consequences have been applied following a serious breach of the CoC, such as being banned from mailing lists or prevented from attending RIPE events.insert: <h2>
Appendix - About the Code of Conduct TF insert: </h2>insert: <p>
The Code of Conduct Task Force was formed after RIPE 80 to finalise the updated RIPE Code of Conduct documents. It was chartered to create three documents: insert: </p>insert: <ol>
- insert: <li>
- An updated RIPE Code of Conduct (now published as insert: <a data-val="9dd05c4071e44de6b7aa9aea4bd9213b" href="../../../../../resolveuid/9dd05c4071e44de6b7aa9aea4bd9213b" data-linktype="internal"> ripe-766 insert: </a> ) insert: </li> insert: <li>
- A process for selecting the Code of Conduct Team insert: </li> insert: <li>
- This document insert: </li> insert: </ol>
The TF has four community members and is supported by two RIPE NCC staff members. The insert: <a data-val="80dc2d86e8b0481aafe8c30b9bea0c00" href="../../../../../resolveuid/80dc2d86e8b0481aafe8c30b9bea0c00" data-linktype="internal"> TF’s web page insert: </a> provides more details and links to mailing list archives, where meeting minutes are published. insert: </p>