COC content into policies

.github/docker-build-pdf.sh

@@ -133,10 +133,11 @@ function to_policy_pdf() {
 }
 
 # Convert all policies to PDF
+to_policy_pdf code-of-conduct "Code of Conduct"
 to_policy_pdf conflict-of-interest "Conflict of Interest"
 to_policy_pdf dissolution-policy "Dissolution"
 to_policy_pdf ip-policy "Intellectual Property"
-to_policy_pdf trademark-policy "Trademark"
 to_policy_pdf succession-plan "Continuity and Administrative Access"
+to_policy_pdf trademark-policy "Trademark"
 
 # TODO: to_policy_pdf privacy "Privacy"

.mlc_config.json

@@ -14,7 +14,7 @@
       "replacement": "{{BASEURL}}/"
     },
     {
-      "pattern": "^https://.*\\.?website/?",
+      "pattern": "^https://.*\\.?website/?$",
       "replacement": "{{BASEURL}}/"
     }
   ],

GOVERNANCE.md

@@ -58,7 +58,7 @@ We welcome all forms of contribution, from code improvements to documentation an
 [cf-decision-making]: ./bylaws/decision-making.md
 [cfab]: ./bylaws/cf-advisory-board.md
 [cfc]: ./bylaws/cf-council.md
-[coc]: ./CODE_OF_CONDUCT.md
+[coc]: ./policies/code-of-conduct.md
 [contrib]: ./CONTRIBUTING.md
 [membership]: ./bylaws/cf-membership.md
 [records]: ./bylaws/notice-records.md

bylaws/cf-council.md

@@ -63,6 +63,6 @@ The Chairperson orchestrates regular CFC meetings, ensuring leadership in discus
 
 The CFC may establish committees to manage specific areas of responsibility. While delegating tasks to these committees, the CFC retains ultimate oversight and decision-making authority.
 
-[coc-reports]: ../CODE_OF_CONDUCT.md#handling-reports-and-escalations
+[coc-reports]: ../policies/code-of-conduct.md#handling-reports-and-escalations
 [coi-policy]: ../policies/conflict-of-interest.md
 [MEMBERS.yaml]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml

policies/README.md

@@ -8,7 +8,7 @@ The CF is committed to complying with all applicable laws and regulations relate
 ## Index of CF Policies
 
 - [Bylaws](../bylaws/README.md)
-- [Code of Conduct](../CODE_OF_CONDUCT.md)
+- [Code of Conduct](./code-of-conduct.md)
 - [Conflict of Interest Policy](./conflict-of-interest.md)
 - [Continuity and Administrative Access Policy](./succession-plan.md)
 - [Intellectual Property Policy](./ip-policy.md)

policies/code-of-conduct.md

@@ -0,0 +1,277 @@
+---
+status: draft
+---
+# The Commonhaus Foundation Code of Conduct
+
+Welcome to the Code of Conduct (CoC) for the Commonhaus Foundation (CF). This document reflects our dedication to fostering a respectful, inclusive, and collaborative environment. It sets the standards for behavior expected in our community and provides a framework for addressing and resolving issues in a fair and respectful manner.
+
+- [Our Code of Conduct](#our-code-of-conduct)
+  - [Member Expectations](#member-expectations)
+  - [Report an issue](#report-an-issue)
+  - [Respond to a CoC issue](#respond-to-a-coc-issue)
+  - [Escalate an issue](#escalate-an-issue)
+  - [Code of Conduct Panel](#code-of-conduct-panel)
+- [Handling Reports and Escalations](#handling-reports-and-escalations)
+  - [Conflict of Interest](#conflict-of-interest)
+  - [Reports to `report@mailing-list`](#reports-to-reportmailing-list)
+  - [Reports to `coc-escalation@mailing-list`](#reports-to-coc-escalationmailing-list)
+- **Contributor Covenant Code of Conduct**
+  - [Our Pledge](#our-pledge)
+  - [Our Standards](#our-standards)
+  - [Enforcement Responsibilities](#enforcement-responsibilities)
+  - [Scope](#scope)
+  - [Enforcement](#enforcement)
+  - [Enforcement Guidelines](#enforcement-guidelines)
+    - [Correction](#correction)
+    - [Warning](#warning)
+    - [Temporary Ban](#temporary-ban)
+    - [Permanent Ban](#permanent-ban)
+  - [Attribution](#attribution)
+
+[MEMBERS.yaml]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml
+[cc-dm]: ../bylaws/decision-making.md
+
+## Our Code of Conduct
+
+The CF has adopted the [Contributor Covenant v2.1][v2.1] as its CoC (full text [below](#contributor-covenant-code-of-conduct)).
+
+- The CoC applies to all foundation activities.
+- New projects must adopt this CoC within 3 months of joining the foundation.
+
+A CoC is meaningful only [when it is effectively enforced][moz-coc].
+Having a unified CoC allows for consistent enforcement and better support across all CF projects.
+
+[moz-coc]: https://medium.com/mozilla-open-innovation/how-were-making-code-of-conduct-enforcement-real-and-scaling-it-3e382cf94415
+
+### Member Expectations
+
+All participants in CF projects are bound by the principles outlined in this Code of Conduct.
+
+Members of CF and CF project contributors are expected to be respectful of different viewpoints and work collaboratively with one another. Some general guidelines include:
+
+- Admit and work to correct mistakes. Aim to remediate first, and then discuss. If other members of the team express concerns about actions, acknowledge their concerns by stopping the actions in question and discuss within the team (the CFC, the CoCP, or CF project members) to come to a common agreement.
+- Treat all community members with respect, consideration, and highest standards of ethical conduct. Avoid preferential treatment. Criticize ideas rather than people. Discuss any concerns in person whenever possible.
+- Build trust by keeping your promises. The corollary: don't over-promise.
+- Demonstrate a willingness to listen and learn from others. Provide an example of ownership, stewardship, and inclusiveness that everyone can follow.
+
+If you're interested in an introduction to diversity, inclusion, and unconscious bias, consider these resources:
+
+- [Inclusive Speaker Orientation (Linux Foundation)][2]
+- [Inclusion at Scale in the Mozilla and Kubernetes Open Source Communities (The New Stack)][3]
+- [We See You! Reaching Diverse Audiences in FOSS][4]
+
+[2]: https://training.linuxfoundation.org/training/inclusive-speaker-orientation/
+[3]: https://thenewstack.io/inclusion-at-scale-in-the-mozilla-and-kubernetes-open-source-communities/
+[4]: https://medium.com/mozilla-open-innovation/we-see-you-reaching-diverse-audiences-in-foss-4e83efc86425
+
+#### Leadership Expectations
+
+There are further expectations for members of leadership teams including the CFC.
+
+When decisions are made within the established guidelines and policies of CF projects, *those in leadership roles have a responsibility to uphold and respect the decision even if they disagree with it*. Should the leader be unwilling or unable to do so, then they should resign their leadership position.
+
+This does not mean that decisions are set in stone. CF projects and the CFC are always able to revisit decisions at a later time.
+
+### Report an issue
+
+- Each CF project is free to implement enforcement of the CoC using processes appropriate for the size and scope of the project. CoC enforcement processes and contact methods must be defined in the projects' `CODE_OF_CONDUCT.md`.
+- For CF repositories that do not specify their own `CODE_OF_CONDUCT.md`, send your report to `report@mailing-list`. The CFC will receive these reports.
+
+Confidentiality is of utmost importance. We also understand that the person reporting the issue (**reporter**) may not be the individual directly affected or harmed (**target**). In such cases, communication will primarily be with the reporter unless the target explicitly gives permission. Personal details of the reporter (and the target if they differ) will not be disclosed without permission.
+
+- The CF *prohibits retaliation* against individuals who report concerns in good faith.
+
+### Respond to a CoC issue
+
+Each complaint will be reviewed and investigated, and will result in a response that is deemed necessary and appropriate to the circumstances.
+
+An issue should be created for each report in a private repository listed in its `CODE_OF_CONDUCT.md`. It should capture the report, discussion and final conclusion. Personal information is confidential. The report should NOT contain identifying details of the reporter.
+
+Access to the private repository should be restricted to individuals charged with resolving CoC reports. Individuals or groups with access to the private repository will be clearly stated in the `CODE_OF_CONDUCT.md`.
+
+**Confidentiality:** Given that membership to groups like the CFC or the CoCP have finite terms, members reviewing CoC reports agree to treat all reports as confidential, even after their term is finished.
+
+### Escalate an issue
+
+We expect most reports to be handled by the processes put in place by a project or the CFC.
+
+The CF maintains the CoCP to manage escalation when a reporter (a) believes that a report to a member project or the CFC has not been properly handled, or (b) does not feel comfortable reporting an issue through the standard process.
+
+Email `coc-escalation@mailing-list` to escalate an issue to the CoCP. The CoCP will meet to review submitted reports as described in [CF CoC procedures](#reports-to-reportmailing-list).
+
+### Code of Conduct Panel
+
+The CoCP is a foundation-wide team composed of the CFC Chairperson and 4 elected individuals who are not members of the CFC.
+
+CoCP members serve for two year terms. CF contributors and members from the broader community can be nominated to the CoCP.
+CoCP members should consider objectivity and diversity of experience and perspective when electing CoCP members.
+
+Members of the CoCP will be documented in the `cocp-panel` [MEMBERS.yaml][] attribute.
+
+## Handling Reports and Escalations
+
+This section describes the process and roles for handling Code of Conduct (CoC) reports and escalations for both the CFC and the CF Code of Conduct Panel (CoCP).
+
+### Conflict of Interest
+
+Any member of the CFC or CoCP who is involved in the report must recuse themselves from the discussions.
+
+### Reports to `report@mailing-list`
+
+All members of the CFC are subscribed to the `report@mailing-list` mailing list.
+
+We understand that the person reporting the issue (**reporter**) may not be the individual directly affected or harmed (**target**). In such cases, communication will primarily be with the reporter unless the target explicitly gives permission.
+
+1. **Acknowledgement:** Upon receipt of a report, a CFC member acknowledges it, confirming receipt to the reporter or target.
+2. **Point of Contact:** If no response has been sent by the next CFC meeting, the CFC Chairperson will ensure a CFC member is designated as the primary point of contact.
+3. **Information Gathering:** All relevant information is collected and centralized for review.
+4. **Discussion:** The gathered information is discussed to contextualize the facts and opinions.
+5. **Determination:** A consensus is reached on the appropriate response using the standard [CFC decision-making process][cc-dm].
+6. **Communication of Resolution:** The resolution is shared with the reporter or target. Feedback loops can continue until concerns have been adequately addressed. Absence of feedback within 7 days means resolution acceptance.
+7. **Finalization:** The agreed resolution is implemented.
+
+### Reports to `coc-escalation@mailing-list`
+
+All members of the CoCP are subscribed to the `coc-escalation@mailing-list` mailing list.
+
+The CoCP will follow the same overall procedure as the CFC, with the following changes:
+
+- **Point of Contact:** The CFC Chairperson will ensure a member of the CoCP is identified as the main point of contact either through email or scheduling a meeting for the CoCP.
+- **Communication of Resolution:** When an appropriate response has been determined by the CoCP, the proposed action is discussed with leaders of the relevant group (the CFC or the CF project). If the leadership representatives expresses concerns then the contact person will bring these back to the CoCP members for further discussion. This cycle can continue until the CoCP members reach consensus that the leadership representatives concerns have been adequately addressed.
+
+---
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+---
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

policies/ip-policy.md

@@ -74,10 +74,11 @@ This policy will be reviewed periodically to ensure it remains relevant and effe
 
 For questions or clarifications on this policy, please contact `legal@mailing-list`.
 
+[IP Policy]: ../policies/ip-policy.md
 [amendment process]: ../bylaws/amendments.md
-[cfc]: ../GOVERNANCE.md#commonhaus-foundation-council "CF Council"
-[standard website footer]: ../templates/website-footer.md "CF website footers"
+[cfc]: ../bylaws/cf-council.md "CF Council"
+[standard website footer]: https://github.com/commonhaus/foundation-draft/blob/main/templates/website-footer.md "CF website footers"
 [CC BY 4.0]: http://creativecommons.org/licenses/by/4.0/ "Creative Commons Attribution 4.0 International License (CC BY 4.0)"
 [MIT]: https://opensource.org/license/mit/ "The MIT License"
 [DCO]: http://developercertificate.org/
-[code-copyright]: https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code
+[code-copyright]: https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code

policies/succession-plan.md

@@ -56,7 +56,7 @@ This policy may undergo periodic reviews and updates to cater to the evolving ne
 For questions or clarifications on this policy, please contact `legal@mailing-list`.
 
 [amendment process]: ../bylaws/amendments.md
-[GOVERNANCE.md]: ../GOVERNANCE.md
-[CONTRIBUTING.md]: ../CONTRIBUTING.md
+[GOVERNANCE.md]: https://github.com/commonhaus/foundation-draft/blob/main/GOVERNANCE.md
+[CONTRIBUTING.md]: https://github.com/commonhaus/foundation-draft/blob/main/CONTRIBUTING.md
 [GOV-TPL]: https://github.com/commonhaus/foundation-draft/blob/main/templates/GOVERNANCE.md
 [CONTRIB-TPL]: https://github.com/commonhaus/foundation-draft/blob/main/templates/CONTRIBUTING.md