diff --git a/BOOTSTRAPPING.md b/BOOTSTRAPPING.md index 675a6fc..06db7ff 100644 --- a/BOOTSTRAPPING.md +++ b/BOOTSTRAPPING.md @@ -5,7 +5,7 @@ status: draft This document outlines the interim procedures and commitments during the foundation's initial establishment phase. It provides guidelines for project commitments, ensuring mutual trust and flexibility until the foundation reaches a stable state. -[cc]: GOVERNANCE.md#commonhaus-council "Commonhaus Foundation Council" +[cc]: GOVERNANCE.md#commonhaus-foundation-council "Commonhaus Foundation Council" [cc-dm]: GOVERNANCE.md#decision-making-and-voting ## 1. Preliminary Commitments diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 8dbbdd4..66d8861 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -24,16 +24,15 @@ The Commonhaus Foundation (CF), and every project within it, needs a clear and e - The [CoCP][cocp] will follow [CF CoC procedures][coc-reports] when handling CoC reports and escalations. - Records will be kept in TODO-private-repository. Access to this repository is restricted to CoCP members. -[cc]: GOVERNANCE.md#commonhaus-council "Commonhaus Foundation Council" +[cc]: GOVERNANCE.md#commonhaus-foundation-council "Commonhaus Foundation Council" [cc-dm]: GOVERNANCE.md#decision-making-and-voting [cocp]: #code-of-conduct-panel "Code of Conduct Panel" -[membership]: MEMBERS.yaml +[membership]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml "Members" [coc-reports]: #handling-reports-and-escalations - ## 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 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. @@ -45,17 +44,16 @@ Having a unified CoC allows for consistent enforcement and better support across 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: +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. +- 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)](https://training.linuxfoundation.org/training/inclusive-speaker-orientation/) -- [Making product inclusion and equity a core part of tech (McKinsey & Company)](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/making-product-inclusion-and-equity-a-core-part-of-tech) - [Inclusion at Scale in the Mozilla and Kubernetes Open Source Communities (The New Stack)](https://thenewstack.io/inclusion-at-scale-in-the-mozilla-and-kubernetes-open-source-communities/) - [We See You! Reaching Diverse Audiences in FOSS](https://medium.com/mozilla-open-innovation/we-see-you-reaching-diverse-audiences-in-foss-4e83efc86425) @@ -69,18 +67,18 @@ This does not mean that decisions are set in stone. CF projects and the CFC are ### 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`. +- 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][cc] 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. +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. +- 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. +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`. @@ -96,10 +94,10 @@ Email `coc-escalation@mailing-list` to escalate an issue to the CoCP. The CoCP w ### 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. +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. +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][membership] attribute. @@ -113,7 +111,7 @@ Any member of the CFC or CoCP who is involved in the report must recuse themselv ### Reports to `report@mailing-list` -All members of the [CFC][cc] are subscribed to the `report@mailing-list` mailing list. +All members of the [CFC][cc] 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. @@ -127,9 +125,9 @@ We understand that the person reporting the issue (**reporter**) may not be the ### Reports to `coc-escalation@mailing-list` -All members of the [CoCP][cocp] are subscribed to the `coc-escalation@mailing-list` mailing list. +All members of the [CoCP][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: +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. @@ -155,23 +153,23 @@ diverse, inclusive, and healthy community. 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, +- 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 +- 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 +- 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, +- 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 +- Other conduct which could reasonably be considered inappropriate in a professional setting ## Enforcement Responsibilities @@ -268,4 +266,3 @@ For answers to common questions about this code of conduct, see the FAQ at [Mozilla CoC]: https://github.com/mozilla/diversity [FAQ]: https://www.contributor-covenant.org/faq [translations]: https://www.contributor-covenant.org/translations - diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 51a0da7..b8d4557 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -48,17 +48,17 @@ We might request further clarifications, changes, or provide feedback. ### 3. Address Feedback -If feedback is provided on your PR, please address it in a timely manner. +If feedback is provided on your PR, please address it in a timely manner. Once all feedback has been addressed, and the PR is approved, it will be merged into the main repository. ## A Note on Legal Matters -Given the nature of this repository, some changes or amendments might require legal review. +Given the nature of this repository, some changes or amendments might require legal review. We appreciate your patience as we ensure that all content aligns with the foundation's principles and legal considerations. -## Thank You! +## Thank You -Every contribution, be it small or large, helps us maintain and improve this repository. +Every contribution, be it small or large, helps us maintain and improve this repository. Your willingness to help is genuinely appreciated. For any questions or further information, don't hesitate to reach out to us. Happy contributing! diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 1bafe90..93b5690 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -3,12 +3,12 @@ status: draft --- # Commonhaus Foundation Project Governance -The Commonhaus Foundation (CF) is a collaborative space where contributors come together. +The Commonhaus Foundation (CF) is a collaborative space where contributors come together. While working in groups can present challenges, this document lays out the guidelines that foster unity and progress. [coc-reports]: CODE_OF_CONDUCT.md#handling-reports-and-escalations [coi-policy]: governance/conflict-of-interest.md -[MEMBERS.yaml]: MEMBERS.yaml +[MEMBERS.yaml]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml ## Table of Contents @@ -27,6 +27,7 @@ While working in groups can present challenges, this document lays out the guide - Active members, defined as those contributing to CF or its projects within the past year, are eligible for voting after three months of membership. Contributions include code, documentation, forum participation, issue resolution, and election involvement. **Code Owners:** The leaders and code owners for CF projects are members. Their project roles carry the responsibility of steering project direction, which includes a stake in shaping the foundation's future. Project Leaders are automatically eligible for Council positions, ensuring our projects' voices are prominently represented. + - Access: They have write permissions to the repository. - Reference: Managed through the repository's `CODEOWNERS` file. @@ -34,13 +35,13 @@ Further Reading: [About code owners](https://docs.github.com/en/repositories/man ## Commonhaus Foundation Council -The Commonhaus Foundation Council (CFC) is the governing body of the CF, responsible for overseeing financial allocations, satisfying fiscal responsibilities, and setting future plans that serve the collective interests of the community. +The Commonhaus Foundation Council (CFC) is the governing body of the CF, responsible for overseeing financial allocations, satisfying fiscal responsibilities, and setting future plans that serve the collective interests of the community. Council members must adhere to our [Conflict of Interest Policy][coi-policy] to ensure that personal or professional interests do not unduly influence their duties within the CF. -The Council convenes regularly and holds an Annual General Meeting (AGM) to review the annual report, financial status, and set future plans. -Special general meetings may be initiated with a defined agenda if proposed by at least a third of the Council members or by a significant fraction of the general members. +The Council convenes regularly and holds an Annual General Meeting (AGM) to review the annual report, financial status, and set future plans. +Special general meetings may be initiated with a defined agenda if proposed by at least a third of the Council members or by a significant fraction of the general members. -Agendas and schedules for these gatherings will be released in advance. +Agendas and schedules for these gatherings will be released in advance. Meetings open to the broader public are accessible to all members and interested observers. Summaries of key decisions and discussions will be shared with the community to ensure that all members are informed and can provide feedback. @@ -48,7 +49,7 @@ Summaries of key decisions and discussions will be shared with the community to ### Composition and Membership -The Council has a minimum of 3 elected members: 1 [Council Chairperson](#chairperson-of-the-council) and at least 2 members-at-large. +The Council has a minimum of 3 elected members: 1 [Council Chairperson](#chairperson-of-the-council) and at least 2 members-at-large. At least one-third of Council members are direct representatives from our projects, maintaining a strong voice for project needs and perspectives. To avoid any single entity's undue influence, no more than one Council member may represent any given company or legal entity. @@ -57,8 +58,8 @@ At least one-third of Council members are direct representatives from our projec ### Tenure and Transition -For continuity and stability, elections for Council members (including the Council Chair) are staggered. -In each election cycle, no more than two-thirds of Council seats will be up for reelection. +For continuity and stability, elections for Council members (including the Council Chair) are staggered. +In each election cycle, no more than two-thirds of Council seats will be up for reelection. Upon completing their tenure, CFC members may seek re-election to extend their service, or step down. #### Chairperson of the Council @@ -89,7 +90,7 @@ An up-to-date list of Advisory Board representatives will be maintained in the ` True to Open Source roots, the CF ensures every member's voice is heard through the Lazy Consensus decision-making model. -To quote the [Consensus definition](https://community.apache.org/committers/decisionMaking.html) from the Apache Foundation: +To quote the [Consensus definition](https://community.apache.org/committers/decisionMaking.html) from the Apache Foundation: > Consensus > @@ -101,7 +102,7 @@ To quote the [Consensus definition](https://community.apache.org/committers/deci When seeking consensus, members should express objections or dissent as early as possible to ensure there is time to discuss and address objections. -Every member, regardless of their role or contribution level, has an equal voice and is entitled to one vote in all decisions. +Every member, regardless of their role or contribution level, has an equal voice and is entitled to one vote in all decisions. #### Seeking consensus in meetings @@ -126,7 +127,7 @@ It is customary for the initiator to post a summary once it appears that consens ### Elections -For Council elections, CF adopts a preference-based voting system facilitated by [Elekto](https://elekto.dev/). +For Council elections, CF adopts a preference-based voting system facilitated by [Elekto](https://elekto.dev/). This approach allows members to rank candidates in order of preference, ensuring the elected representatives are the most broadly supported by the community, rather than simply the most popular. - [Voting using Elekto](https://elekto.dev/docs/voting/) diff --git a/README.md b/README.md index 5d8c29e..b9ef07d 100644 --- a/README.md +++ b/README.md @@ -2,34 +2,34 @@ status: draft --- -> 📝 Note: This repo is a draft to explore an idea. -> It tries to be reasonably thorough to convey the concept, but there are lots of holes and details to sort through, and none of it has undergone any kind of legal review. -> [Discussions](https://github.com/commonhaus/foundation-draft/discussions) are open and input is welcome! +> 📝 Note: This repo is a draft to explore an idea. +> It tries to be reasonably thorough to convey the concept, but there are lots of holes and details to sort through, and none of it has undergone any kind of legal review. +> [Discussions](https://github.com/commonhaus/foundation-draft/discussions) are open and input is welcome! > If you're willing to support this effort, please submit a PR to add yourself to [SUPPORTERS.yaml](https://github.com/commonhaus/foundation-draft/blob/main/SUPPORTERS.yaml). # The Commonhaus Foundation (CF) -The Commonhaus Foundation champions open-source innovation and collaboration. +The Commonhaus Foundation champions open-source innovation and collaboration. -We are dedicated to ensuring the long-term growth and stability of GitHub-style open-source projects through community collaboration and shared stewardship. Our mission is to empower a diverse community of contributors to create, maintain, enhance, and secure vital open-source libraries and frameworks. +We are dedicated to ensuring the long-term growth and stability of GitHub-style open-source projects through community collaboration and shared stewardship. Our mission is to empower a diverse community of contributors to create, maintain, enhance, and secure vital open-source libraries and frameworks. Our vision is to create a dynamic and inclusive community where developers, contributors, and users unite to drive the evolution of open-source libraries and frameworks. We aim to cultivate an ecosystem that thrives on collaborative innovation, bypassing the complexities of traditional governance models. [codehaus]: https://www.infoworld.com/article/2892227/codehaus-the-once-great-house-of-code-has-fallen.html [succession]: governance/succession-plan.md -[ip-policy-guidance]: governance/ip-policy-guidance.md#1-licensing +[ip-policy-guidance]: governance/ip-policy-guidance.md#basic-ip-requirements ## Core Distinctions of CF Drawing inspiration from [The Codehaus][codehaus], CF offers the right balance of support without overwhelming governance. -**Minimal Viable Governance:** CF embraces the "community-first" model prevalent in modern GitHub-style projects. +**Minimal Viable Governance:** CF embraces the "community-first" model prevalent in modern GitHub-style projects. While we provide foundational support, projects maintain their autonomy. -**Access to Funding:** We bridge the post-Kickstarter gap. +**Access to Funding:** We bridge the post-Kickstarter gap. CF aids projects in meeting governance requirements, paving the way for them to access platforms like GitHub Sponsors or fiscal hosts such as Open Source Collective. -**Future-ready Flexibility:** CF acknowledges the evolutionary nature of projects. +**Future-ready Flexibility:** CF acknowledges the evolutionary nature of projects. We're not just a placeholder but a guide, assisting projects as they grow and, if needed, transition to foundations with more rigorous governance. **Tailored for Established Projects:** CF is an ideal home for projects that already have a user base and are now seeking stability and growth without heavy governance overhead. @@ -65,4 +65,3 @@ CF is committed to inclusive growth, opening its doors to all individuals who sh - [Commonhaus Foundation Governance](GOVERNANCE.md) - [Succession Planning][succession] - [IP Policy Guidance][ip-policy-guidance] - diff --git a/governance/conflict-of-interest.md b/governance/conflict-of-interest.md index 99d59af..69b4d01 100644 --- a/governance/conflict-of-interest.md +++ b/governance/conflict-of-interest.md @@ -3,9 +3,9 @@ status: draft --- # Commonhaus Foundation Conflict of Interest Policy -As a nonprofit organization, CF is committed to the responsible stewardship of its resources. +As a nonprofit organization, CF is committed to the responsible stewardship of its resources. -This policy is designed to protect the interests of the Commonhaus Foundation (CF) when potentially beneficial actions or transactions might intersect with the private interests of a director, officer, or key person. +This policy is designed to protect the interests of the Commonhaus Foundation (CF) when potentially beneficial actions or transactions might intersect with the private interests of a director, officer, or key person. Additionally, it ensures compensation fairness for any staff or contractors hired by CF, which operates primarily as a volunteer organization. This policy applies to all individuals with decision-making authority within the CF ("you"), including CF Council and Advisory Board members, and extends to CF members and project leaders when their personal interests may influence Foundation activities. @@ -15,6 +15,7 @@ This policy applies to all individuals with decision-making authority within the A conflict of interest occurs when you have the potential to benefit financially or otherwise from an action taken or a transaction entered into by CF, or when you have an interest that could compromise your independence or objectivity. ### Examples + - Financial interest in any entity with which CF transacts. - Board membership, employment, or volunteer work with such an entity. - Personal gifts or loans from any entity dealing with CF. @@ -26,9 +27,11 @@ A conflict of interest occurs when you have the potential to benefit financially When in doubt, it is safer to disclose a potential conflict of interest. ### Immediate Disclosure + All potential conflicts should be disclosed to the designated official or office within the CF Council immediately upon recognition. ### Annual Disclosure + You are required to submit an annual statement of potential conflicts, and for CF Council members, also before your initial appointment. ## Determining Whether a Conflict of Interest Exists @@ -55,4 +58,4 @@ CF will not make loans to any Council members, officers, or key persons. When hiring staff or paying for contract work, the CF Council will reference industry standards to ensure compensation is fair and justified. The process will be transparent and fully documented. -All individuals will abstain from discussions or votes concerning their own compensation or that of those closely associated with them. \ No newline at end of file +All individuals will abstain from discussions or votes concerning their own compensation or that of those closely associated with them. diff --git a/governance/ip-policy-guidance.md b/governance/ip-policy-guidance.md index 6b2405c..e528374 100644 --- a/governance/ip-policy-guidance.md +++ b/governance/ip-policy-guidance.md @@ -6,7 +6,7 @@ status: draft This guide simplifies the [Commonhaus Foundation (CF) IP Policy][IP Policy] for easier implementation. [IP Policy]: ip-policy.md -[cc]: ../GOVERNANCE.md#commonhaus-council "Commonhaus Foundation Council" +[cc]: ../GOVERNANCE.md#commonhaus-foundation-council "Commonhaus Foundation Council" [standard website footer]: website-footer.md "Commonhaus Foundation website footers" ## Basic IP Requirements diff --git a/governance/ip-policy.md b/governance/ip-policy.md index b32bac2..b28ce07 100644 --- a/governance/ip-policy.md +++ b/governance/ip-policy.md @@ -5,7 +5,7 @@ status: draft The Commonhaus Foundation (CF) oversees multiple individual projects, referred to as “Projects”. Contributions to these Projects are governed by this policy and each Project's chosen license, known as the “Project Code License”. -[cc]: ../GOVERNANCE.md#commonhaus-council "Commonhaus Foundation Council" +[cc]: ../GOVERNANCE.md#commonhaus-foundation-council "Commonhaus Foundation Council" [IP Policy Guidance]: ip-policy-guidance.md "Commonhaus Foundation IP Policy Guidance" 1. **License Options:** Projects can select from approved licenses: diff --git a/governance/succession-plan.md b/governance/succession-plan.md index ea61d0b..74e97a8 100644 --- a/governance/succession-plan.md +++ b/governance/succession-plan.md @@ -5,14 +5,14 @@ status: draft The Commonhaus Foundation (CF) understands the impact of reliable libraries and frameworks on the broader tech community. Businesses run on applications built using these assets, and it is logical for them to do so. A retailer specializing in fish tanks shouldn’t need to understand low-level internet protocols. However, time brings change, and code owners, the nurturers of these invaluable tools, might pivot to new endeavors. In their absence, who ensures the continuity and security of these tools? -The CF aims to help projects address this vital concern. +The CF aims to help projects address this vital concern. This policy articulates the foundation's need for administrative access to project resources and the principles that guide this requirement. [GOVERNANCE.md]: ../GOVERNANCE.md -[GOV-TPL]: ../templates/GOVERNANCE.md [CONTRIBUTING.md]: ../CONTRIBUTING.md -[CONTRIB-TPL]: ../templates/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 ## Policy Rationale @@ -25,7 +25,7 @@ Administrative access empowers the CF to: **Artifact Updates:** Provide consistent access to updated project artifacts, even amidst maintainer hiatus. The CF may intervene in certain situations, but we will exhaust every option to contact the current code owners before we do so. -For libraries under heavy use, we will encourage a "path of least disturbance" approach to provide stability for applications relying on these libraries. +For libraries under heavy use, we will encourage a "path of least disturbance" approach to provide stability for applications relying on these libraries. ## Scope of Access and Intervention @@ -45,7 +45,8 @@ The CF respects each project's chosen governance model. This policy complements, - **Contribution guidelines:** Describe project build, test, and packaging instructions in `CONTRIBUTING.md`. Include criteria for contributions, versioning practices, and preferences in the event of an ownership transition. -Further Reading: +Further Reading: + - [About code owners](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners) - See [GOVERNANCE.md][] and the [Project GOVERNANCE.md template][GOV-TPL] for examples. - [Wrangling Web Contributions: How to Build a CONTRIBUTING.md](https://mozillascience.github.io/working-open-workshop/contributing/) diff --git a/governance/trademark-policy.md b/governance/trademark-policy.md index 3b40fcd..089fad4 100644 --- a/governance/trademark-policy.md +++ b/governance/trademark-policy.md @@ -35,7 +35,7 @@ Trademarks are used to provide assurance to the community of consistency with re This policy aims to strike a balance between two key interests: -1) Ensuring that trademarks remain reliable indicators of the qualities that they have been created to preserve and +1) Ensuring that trademarks remain reliable indicators of the qualities that they have been created to preserve and 2) Ensuring that community members are able to discuss Commonhaus Foundation and its projects and to accurately describe the relationship between the CF, CF projects, and the products and services offered by others. A trademark provides the owner with an exclusive right to authorize or control the use of the mark. @@ -103,7 +103,7 @@ To maintain the integrity of The Commonhaus Foundation's visual trademarks: Want to use a Commonhaus trademark for crowdfunding? Here's what you need to know and do. The Commonhaus Foundation recognizes that some projects may wish to use a project trademark when raising funds through crowdfunding platforms. -These activities are not official foundation efforts, even if they are coordinated by core participants from our projects. +These activities are not official foundation efforts, even if they are coordinated by core participants from our projects. Since crowdfunding operates externally to the Commonhaus Foundation, you must obtain permission before using a Commonhaus trademark on any crowdfunding page. In exchange for using the mark, the Commonhaus requires the administrator of the crowdfunding effort to adhere to these three policies: @@ -114,9 +114,9 @@ In exchange for using the mark, the Commonhaus requires the administrator of the 3. You must include the following disclaimer on the crowdfunding page, replacing [Project Name] with the name of the project whose logo you plan to use: -> "This crowdfunding page supports independent contributors of the [Project Name] open source project. -> The Commonhaus Foundation does not endorse, administer, or control this page. -> Donations made here will go directly to the individuals contributing to [Project Name], and not to the Commonhaus Foundation. +> "This crowdfunding page supports independent contributors of the [Project Name] open source project. +> The Commonhaus Foundation does not endorse, administer, or control this page. +> Donations made here will go directly to the individuals contributing to [Project Name], and not to the Commonhaus Foundation. > The [Project Name] marks are used under license from the Commonhaus Foundation for the open source community's benefit." To request permission to use a mark, please contact `trademarks@mailing-list`. @@ -143,7 +143,7 @@ The Commonhaus Foundation may modify or update this Trademark Policy as needed. ## Attribution -This work is inspired by [The OpenJS Foundation Trademark Policy](https://openjsf.org/wp-content/uploads/sites/84/2021/01/OpenJS-Foundation-Trademark-Policy-2021-01-12.docx.pdf). +This work is inspired by [The OpenJS Foundation Trademark Policy](https://openjsf.org/wp-content/uploads/sites/84/2021/01/OpenJS-Foundation-Trademark-Policy-2021-01-12.docx.pdf). It is licensed under a Creative Commons Attribution 4.0 International license (“CFC BY 4.0”, available at -https://creativecommons.org/licenses/by/4.0). \ No newline at end of file +). \ No newline at end of file diff --git a/templates/CODE_OF_CONDUCT.md b/templates/CODE_OF_CONDUCT.md index 501f044..0c1d86d 100644 --- a/templates/CODE_OF_CONDUCT.md +++ b/templates/CODE_OF_CONDUCT.md @@ -4,7 +4,7 @@ instructions: Replace [Project Name], update Contact information, delete YAML fr --- # [Project Name] Code of Conduct -[Project Name] has adopted the [Contributor Covenant v2.1][v2.1] as its Code of Conduct (CoC) and +[Project Name] has adopted the [Contributor Covenant v2.1][v2.1] as its Code of Conduct (CoC) and follows the [Commonhaus Foundation (CF) CoC][coc-policy] (included below). ## [Project Name] Contact information @@ -14,17 +14,17 @@ follows the [Commonhaus Foundation (CF) CoC][coc-policy] (included below). - Records will be kept in `PROJECT-private-repository` - [Escalations](#escalate-an-issue) should be sent to `coc-escalation@mailing-list` for review by the [Code of Conduct Panel (COCP)][cocp]. -[cc]: ../GOVERNANCE.md "Commonhaus Foundation Council - TODO: full path" -[cocp]: ../CODE_OF_CONDUCT.md#code-of-conduct-panel "Code of Conduct Panel - TODO: full path" -[coc-policy]: ../CODE_OF_CONDUCT.md "TODO: full path" -[coc-reports]: ../CODE_OF_CONDUCT.md#handling-reports-and-escalations "Handling CoC reports - TODO: full path" -[MEMBERS.yaml]: ../MEMBERS.yaml "Members - TODO: full path" +[cc]: https://github.com/commonhaus/foundation-draft/blob/main/GOVERNANCE.md#commonhaus-foundation-council "Commonhaus Foundation Council" +[cocp]: https://github.com/commonhaus/foundation-draft/blob/main/CODE_OF_CONDUCT.md#code-of-conduct-panel "Code of Conduct Panel" +[coc-policy]: https://github.com/commonhaus/foundation-draft/blob/main/CODE_OF_CONDUCT.md +[coc-reports]: https://github.com/commonhaus/foundation-draft/blob/main/CODE_OF_CONDUCT.md#handling-reports-and-escalations "Handling CoC reports" +[MEMBERS.yaml]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml "Members" --- ## 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 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. @@ -34,24 +34,24 @@ Having a unified CoC allows for consistent enforcement and better support across ### 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 other Commonhaus repositories, send your report to `report@mailing-list`. The [CFC][cc] will receive these reports. +- 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 other Commonhaus repositories, send your report to `report@mailing-list`. The [CF Council][cc] will receive these reports. ### 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. +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. +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. ### Escalate an issue -We expect most reports to be handled successfully by the processes put in place by a project or the [CFC][cc]. +We expect most reports to be handled successfully by the processes put in place by a project or the [CF Council][cc]. -The CF maintains the [CoCP][cocp] to manage escalation when a reporter (a) believes that a report to a member project or the [CFC][cc] has not been properly handled, or (b) does not feel comfortable reporting an issue through the standard process. +The CF maintains the [CoCP][cocp] to manage escalation when a reporter (a) believes that a report to a member project or the [CF Council][cc] 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. @@ -82,23 +82,23 @@ diverse, inclusive, and healthy community. 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, +- 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 +- 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 +- 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, +- 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 +- Other conduct which could reasonably be considered inappropriate in a professional setting ## Enforcement Responsibilities diff --git a/templates/GOVERNANCE.md b/templates/GOVERNANCE.md index 13fa603..4d1968f 100644 --- a/templates/GOVERNANCE.md +++ b/templates/GOVERNANCE.md @@ -7,8 +7,8 @@ instructions: Replace [Project Name], update Contact information, delete YAML fr This document outlines the governance model for [Project Name]. This governance model is designed to uphold the principles of transparency, open collaboration, and community involvement. -[cc]: ../GOVERNANCE.md#commonhaus-council "Commonhaus Foundation Council - TODO: full path" -[cdm]: ../GOVERNANCE.md#decision-making-and-voting "Commonhaus decision making - TODO: full path" +[cc]: ../GOVERNANCE.md#commonhaus-council "Commonhaus Foundation Council - TODO: full path" +[cdm]: ../GOVERNANCE.md#decision-making-and-voting "Commonhaus decision making - TODO: full path" ## Table of Contents @@ -29,7 +29,7 @@ Reference: [About code owners](https://docs.github.com/en/repositories/managing- This project follows The [Commonhaus decision making][cdm] process. -1. **Consensus-seeking (lazy consensus):** The project primarily aims for a consensus-based decision-making process, where maintainers and active contributors discuss and come to an agreement. +1. **Consensus-seeking (lazy consensus):** The project primarily aims for a consensus-based decision-making process, where maintainers and active contributors discuss and come to an agreement. 2. **Voting:** In situations where consensus cannot be reached, decisions may be made through a simple majority vote among the maintainers. 3. **Conflict Resolution:** If conflicts arise, maintainers are responsible for facilitating a resolution. The [Commonhaus Foundation Council][cc] can be asked to mediate the discussion, if necessary. @@ -44,4 +44,3 @@ The [Project Name] logos, icons, and domain names are protected by trademark rig ## Contributing We welcome all forms of contribution, from code improvements to documentation and design. For details on how to contribute and the process your contributions will follow, please read our [Contributing Guidelines](CONTRIBUTING.md). -