Format to 80-character line limit.

reporting_guidelines.md

@@ -1,51 +1,75 @@
 # Reporting Guidelines
 
-If you believe someone is violating the code of conduct we ask that you please report it to Backdrop CMS by emailing conduct@backdropcms.org.
+If you believe someone is violating the code of conduct we ask that you please
+report it to Backdrop CMS by emailing conduct@backdropcms.org.
 
-**All reports will be kept confidential.** In some cases we may determine that a public statement will need to be made. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.
+**All reports will be kept confidential.** In some cases we may determine that a
+public statement will need to be made. If that's the case, the identities of all
+victims and reporters will remain confidential unless those individuals instruct
+us otherwise.
 
-If you believe anyone is in physical danger, please notify appropriate emergency services first. If you are unsure what service or agency is appropriate to contact, include this in your report and we will attempt to notify them.
+If you believe anyone is in physical danger, please notify appropriate emergency
+services first. If you are unsure what service or agency is appropriate to
+contact, include this in your report and we will attempt to notify them.
 
 In your report please include:
 
 * Your contact info for follow-up contact.
 * Names (nicknames, pseudonyms, or legal names) of any individuals involved.
-  * If there were other witnesses besides you, please try to include them as well.
+  - If there were other witnesses besides you, please try to include them as
+    well.
 * When and where the incident occurred. Please be as specific as possible.
 * Your account of what occurred.
-  * If there is a publicly available record (e.g. a mailing list archive or a public IRC logger) please include a link.
+  - If there is a publicly available record (e.g. a mailing list archive or a
+    public IRC logger) please include a link.
 * Any extra context you believe existed for the incident.
 * If you believe this incident is ongoing.
 * Any other information you believe we should have.
 
 ## What happens after you file a report?
 
-You will receive an email reply acknowledging receipt as soon as possible, but within 24 hours.
+You will receive an email reply acknowledging receipt as soon as possible, but
+within 24 hours.
 
-The Project Management Committee will immediately meet to review the incident and determine:
+The Project Management Committee will immediately meet to review the incident
+and determine:
 
 * What happened.
 * Whether this event constitutes a code of conduct violation.
 * What kind of response is appropriate.
 
-If this is determined to be an ongoing incident or a threat to physical safety, the committee's immediate priority will be to protect everyone involved. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe.
+If this is determined to be an ongoing incident or a threat to physical safety,
+the committee's immediate priority will be to protect everyone involved. This
+means we may delay an "official" response until we believe that the situation
+has ended and that everyone is physically safe.
 
-Once the team has a complete account of the events they will make a decision as to how to respond. Responses may include:
+Once the team has a complete account of the events they will make a decision as
+to how to respond. Responses may include:
 
 * Nothing (if we determine no code of conduct violation occurred).
-* A private reprimand from the Project Management Comittee to the individual(s) involved.
+* A private reprimand from the Project Management Comittee to the individual(s)
+  involved.
 * A public reprimand.
 * A request to engage in mediation and/or an accountability plan.
-* An imposed vacation (i.e. asking someone to "take a week off" from participating in online communication channels such as GitHub issue queues, Gitter, or Twitter).
-* A temporary or permanent ban from some or all Backdrop CMS spaces (events, meetings, GitHub issue queues, Gitter chat chanels, etc.)
+* An imposed vacation (i.e. asking someone to "take a week off" from
+  participating in online communication channels such as GitHub issue queues,
+  Gitter, or Twitter).
+* A temporary or permanent ban from some or all Backdrop CMS spaces (events,
+meetings, GitHub issue queues, Gitter chat chanels, etc.)
 
-We'll respond within one week to the person who filed the report with either a resolution or an explanation of why the situation is not yet resolved.
+We'll respond within one week to the person who filed the report with either a
+resolution or an explanation of why the situation is not yet resolved.
 
-Once we've determined our final action, we'll contact the original reporter to let them know what action (if any) we'll be taking. We'll take into account feedback from the reporter on the appropriateness of our response, but our response will be determined by what will be best for community safety.
+Once we've determined our final action, we'll contact the original reporter to
+let them know what action (if any) we'll be taking. We'll take into account
+feedback from the reporter on the appropriateness of our response, but our
+response will be determined by what will be best for community safety.
 
 ## Appealing the response
 
-Only permanent resolutions (such as bans) may be appealed. To appeal a decision of the Project Management Committee, contact Backdrop CMS at conduct@backdropcms.org with your appeal and the PMC will review the case.
+Only permanent resolutions (such as bans) may be appealed. To appeal a decision
+of the Project Management Committee, contact Backdrop CMS at
+conduct@backdropcms.org with your appeal and the PMC will review the case.
 
 _Revision 1.0, DRAFT, proposed March 2016_
 _Reporting Guidelines derived from those of the [Django Software Foundation](https://www.djangoproject.com/conduct/reporting/)._