From owner-svn-doc-all@freebsd.org Fri Dec 13 16:32:33 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3B0521D16E0; Fri, 13 Dec 2019 16:32:33 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47ZGRP0s3Dz4CmQ; Fri, 13 Dec 2019 16:32:33 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id F3F9FEF5C; Fri, 13 Dec 2019 16:32:32 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id xBDGWWOJ064272; Fri, 13 Dec 2019 16:32:32 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id xBDGWWWf064269; Fri, 13 Dec 2019 16:32:32 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201912131632.xBDGWWWf064269@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Fri, 13 Dec 2019 16:32:32 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53686 - head/en_US.ISO8859-1/htdocs/internal X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/internal X-SVN-Commit-Revision: 53686 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2019 16:32:33 -0000 Author: bcr Date: Fri Dec 13 16:32:31 2019 New Revision: 53686 URL: https://svnweb.freebsd.org/changeset/doc/53686 Log: Move the Code of Conduct reporting into its own separate file. Link to it from the main Code of Conduct and vice versa. The Code of Conduct itself was not changed. Submitted by: jeff Discussed within: core Approved by: brooks, allanjude, imp, jhb, bcr Differential Revision: https://reviews.freebsd.org/D22322 Added: head/en_US.ISO8859-1/htdocs/internal/conduct-reporting.xml (contents, props changed) Modified: head/en_US.ISO8859-1/htdocs/internal/Makefile head/en_US.ISO8859-1/htdocs/internal/code-of-conduct.xml head/en_US.ISO8859-1/htdocs/internal/policies.xml Modified: head/en_US.ISO8859-1/htdocs/internal/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/Makefile Fri Dec 13 14:44:59 2019 (r53685) +++ head/en_US.ISO8859-1/htdocs/internal/Makefile Fri Dec 13 16:32:31 2019 (r53686) @@ -11,6 +11,7 @@ DOCS= about.xml DOCS+= bylaws.xml DOCS+= clusteradm.xml DOCS+= code-of-conduct.xml +DOCS+= conduct-reporting.xml DOCS+= core-vote.xml DOCS+= data.xml DOCS+= developer.xml Modified: head/en_US.ISO8859-1/htdocs/internal/code-of-conduct.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/code-of-conduct.xml Fri Dec 13 14:44:59 2019 (r53685) +++ head/en_US.ISO8859-1/htdocs/internal/code-of-conduct.xml Fri Dec 13 16:32:31 2019 (r53686) @@ -111,128 +111,10 @@
  • Knowingly making harmful false claims about a person.
    • -

    Reporting Instructions

    - -

    If you believe someone is violating the code of conduct we ask - that you report it to the &os; Code of Conduct Committee by - emailing conduct@freebsd.org.

    - -

    All reports will be kept confidential whenever possible. We - strive to protect the identity and safety of reporters. In some - cases we may need to make a public statement of some form, in - which case we will use the minimum of details and identifying - information necessary to protect our community. In rare cases, - we may need to identify some of the people involved to comply - with the law or protect other potential victims. In these - cases, we will consult with the reporter to find out what their - wishes are and take them into account in our final decision. In - all cases, we will not directly or indirectly identify reporters - without their consent unless we see no other option.

    - -

    If you believe anyone is in physical danger, please notify - appropriate law enforcement first.

    - -

    In your report please include:

    - -
      -
    • Your name and contact info (so we can get in touch with you - if we need to follow up)
      • - -
    • Names (real, nicknames, and/or pseudonyms) of any - individuals involved. 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, tweet, or a - public IRC logger) please include a link and/or screen - shots.
      • - -
    • Any extra context you believe relevant 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 from the &os; Code of Conduct - Committee acknowledging receipt of your report within 48 - hours.

    - -

    The committee will meet as quickly as possible to review the - incident and determine:

    - -
      -
    • Whether an investigation is needed, including interviewing - additional parties or witnesses;
      • - -
    • What appears to have happened and;
      • - -
    • Whether the behavior constitutes a Code of Conduct - violation.
      • -
    - -

    If a member of the &os; Code of Conduct Committee is one of - the individuals included in the report they will recuse - themselves from handling the report.

    - -

    Once the working group has a complete account of the events - they will make a decision as to how to respond. Actions taken - may include:

    - -
      -
    • Nothing (for example, if we determine that no violation - occurred).
      • - -
    • If determined to be solely technical in nature or if it - falls outside the scope of the Code of Conduct, forwarding the - incident to the &os; Core Team
      • - -
    • A private reprimand from the working group to the - individual(s) involved.
      • - -
    • A public reprimand.
      • - -
    • An imposed vacation from &os; Project controlled spaces - (e.g. asking someone to "take a week off" from a - mailing list or IRC).
      • - -
    • A permanent or temporary ban from some or all &os; - Project controlled spaces (events, meetings, mailing lists, - IRC, etc.)
      • - -
    • A request for a public or private apology.
      • - -
    • A request to engage in mediation and/or an accountability - plan.
      • -
    - -

    We will do our best to 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 have determined our final action, we will contact the - original reporter to let them know what action (if any) we will - be taking. We will take into account feedback from the reporter - on the appropriateness of our response, but we do not guarantee - we will act on it.

    - -

    Finally, the committee will make a report on the situation to - the &os; Core Team. The Core Team may choose to issue a - public report of the incident.

    - -

    Appeals

    - -

    Only permanent resolutions (such as bans) may be appealed. To - appeal a decision of the CoC Committee, contact the &os; Core - Team at core@freebsd.org - with your appeal and the Core Team will review the case.

    +

    Reporting

    +

    The reporting process is documented at Code of Conduct Reporting + Instructions.

    Glossary

    Added: head/en_US.ISO8859-1/htdocs/internal/conduct-reporting.xml ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/en_US.ISO8859-1/htdocs/internal/conduct-reporting.xml Fri Dec 13 16:32:31 2019 (r53686) @@ -0,0 +1,142 @@ + + +]> + + + + &title; + + $FreeBSD$ + + + + +

    &os; Code of Conduct Reporting Instructions

    + +

    If you believe someone is violating the + code of conduct we ask + that you report it to the &os; Code of Conduct Committee by + emailing conduct@freebsd.org.

    + +

    All reports will be kept confidential whenever possible. We + strive to protect the identity and safety of reporters. In some + cases we may need to make a public statement of some form, in + which case we will use the minimum of details and identifying + information necessary to protect our community. In rare cases, + we may need to identify some of the people involved to comply + with the law or protect other potential victims. In these + cases, we will consult with the reporter to find out what their + wishes are and take them into account in our final decision. In + all cases, we will not directly or indirectly identify reporters + without their consent unless we see no other option.

    + +

    If you believe anyone is in physical danger, please notify + appropriate law enforcement first.

    + +

    In your report please include:

    + +
      +
    • Your name and contact info (so we can get in touch with you + if we need to follow up)
      • + +
    • Names (real, nicknames, and/or pseudonyms) of any + individuals involved. 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, tweet, or a + public IRC logger) please include a link and/or screen + shots.
      • + +
    • Any extra context you believe relevant 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 from the &os; Code of Conduct + Committee acknowledging receipt of your report within 48 + hours.

    + +

    The committee will meet as quickly as possible to review the + incident and determine:

    + +
      +
    • Whether an investigation is needed, including interviewing + additional parties or witnesses;
      • + +
    • What appears to have happened and;
      • + +
    • Whether the behavior constitutes a Code of Conduct + violation.
      • +
    + +

    If a member of the &os; Code of Conduct Committee is one of + the individuals included in the report they will recuse + themselves from handling the report.

    + +

    Once the working group has a complete account of the events + they will make a decision as to how to respond. Actions taken + may include:

    + +
      +
    • Nothing (for example, if we determine that no violation + occurred).
      • + +
    • If determined to be solely technical in nature or if it + falls outside the scope of the Code of Conduct, forwarding the + incident to the &os; Core Team
      • + +
    • A private reprimand from the working group to the + individual(s) involved.
      • + +
    • A public reprimand.
      • + +
    • An imposed vacation from &os; Project controlled spaces + (e.g. asking someone to "take a week off" from a + mailing list or IRC).
      • + +
    • A permanent or temporary ban from some or all &os; + Project controlled spaces (events, meetings, mailing lists, + IRC, etc.)
      • + +
    • A request for a public or private apology.
      • + +
    • A request to engage in mediation and/or an accountability + plan.
      • +
    + +

    We will do our best to 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 have determined our final action, we will contact the + original reporter to let them know what action (if any) we will + be taking. We will take into account feedback from the reporter + on the appropriateness of our response, but we do not guarantee + we will act on it.

    + +

    Finally, the committee will make a report on the situation to + the &os; Core Team. The Core Team may choose to issue a + public report of the incident.

    + +

    Appeals

    + +

    Only permanent resolutions (such as bans) may be appealed. To + appeal a decision of the CoC Committee, contact the &os; Core + Team at core@freebsd.org + with your appeal and the Core Team will review the case.

    + + + Modified: head/en_US.ISO8859-1/htdocs/internal/policies.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/policies.xml Fri Dec 13 14:44:59 2019 (r53685) +++ head/en_US.ISO8859-1/htdocs/internal/policies.xml Fri Dec 13 16:32:31 2019 (r53686) @@ -35,6 +35,7 @@ below, for more info.

    General Policies