Merge pull request #5789 from tpepper/cocc-processes

CoCC: describe more the info clarifying process

Author: k8s-ci-robot

committee-code-of-conduct/incident-process.md

@@ -99,6 +99,8 @@ It is our intention to put as little emotional labor on those who have been harm
 
 In all instances these clarifying discussions are confidential.
 
+Clarifying discussions typically take the form of email, Slack DM, or Zoom meeting 1:1 between a member of the Code of Conduct Committee selected during our triaging of an incident report and the individual from whom clarification is sought.  The Code of Conduct Committee member will explicitly identify themselves and indicate they are engaging in conversation as a representative of the Code of Conduct Committee.  If the individual prefers we will endeavor to make the meeting/conversation not 1:1, but rather also include an observer/scribe agreed by both parties and still with all discussion being confidential.
+
 ## Incident response workflow
 
 ### Reconvening the Committee
@@ -130,4 +132,4 @@ When we have decided on a course of action, we do the following:
 - We clearly communicate our decision to those who need to hear it, without violating the confidentiality of those who requested it during an investigative process (if one was undertaken).
 - If and only if it is needed, we work with other leadership bodies (e.g., Steering Committee and the Linux Foundation) 
     - This may be necessary if the incident extends to other communities or event spaces, particularly if we feel there is elevated risk of harm to members of those communities
-    - In rare cases, we might find it necessary to issue a public statement, either jointly or separately
+    - In rare cases, we might find it necessary to issue a public statement, either jointly or separately