From 6d4c1fe788234371e9dc41c4808e9f3aaa98e9e0 Mon Sep 17 00:00:00 2001 From: Erin Schnabel Date: Mon, 13 Nov 2023 21:32:14 -0500 Subject: [PATCH] Reframe governance into sections of bylaws - Introduce README in bylaws directory - Clearly include all documents as sections within a whole - Clarify language around how/where records are kept. --- CODE_OF_CONDUCT.md | 67 +++++----- GOVERNANCE.md | 136 +++++++++++++++------ README.md | 15 +-- bylaws/README.md | 53 ++++++++ bylaws/conflict-of-interest.md | 77 ++++++++++++ bylaws/ip-policy.md | 94 ++++++++++++++ bylaws/legal-compliance.md | 71 +++++++++++ {governance => bylaws}/succession-plan.md | 16 ++- {governance => bylaws}/trademark-policy.md | 69 ++++++----- {governance => bylaws}/website-footer.md | 0 governance/conflict-of-interest.md | 61 --------- governance/ip-policy-guidance.md | 42 ------- governance/ip-policy.md | 41 ------- 13 files changed, 488 insertions(+), 254 deletions(-) create mode 100644 bylaws/README.md create mode 100644 bylaws/conflict-of-interest.md create mode 100644 bylaws/ip-policy.md create mode 100644 bylaws/legal-compliance.md rename {governance => bylaws}/succession-plan.md (87%) rename {governance => bylaws}/trademark-policy.md (75%) rename {governance => bylaws}/website-footer.md (100%) delete mode 100644 governance/conflict-of-interest.md delete mode 100644 governance/ip-policy-guidance.md delete mode 100644 governance/ip-policy.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index e5d7a90..73a64e4 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -3,34 +3,41 @@ status: draft --- # The Commonhaus Foundation Code of Conduct -The Commonhaus Foundation (CF), and every project within it, needs a clear and enforced Code of Conduct (CoC) to foster a respectful and collaborative environment for all participants. - -1. **[Contact Info](#contact-information)**: Defines channels for project issues, foundation-wide concerns, and escalations. -2. **[Our CoC](#our-code-of-conduct)**: Adopts the Contributor Covenant v2.1 and outlines its scope and enforcement. -3. **[Member Expectations](#member-expectations)**: Details the behavior expected from members and leaders of the foundation. -4. **[Reporting](#report-an-issue)**: Describes the process for reporting CoC violations. -5. **[Responding to Issues](#respond-to-a-coc-issue)**: Provides a guide on handling and documenting CoC reports. -6. **[Escalation](#escalate-an-issue)**: Offers procedures when regular channels aren't effective or appropriate. -7. **[CoC Panel](#code-of-conduct-panel)**: Defines the role and composition of the Code of Conduct Panel. -8. **[Handling Reports](#handling-reports-and-escalations)**: Describes procedures for both regular and escalated CoC reports. +Welcome to the Code of Conduct (CoC) for the Commonhaus Foundation (CF). This document, forming **Section 8** of the CF [Bylaws][bylaws], 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. + +- [8.1 Contact information](#81-contact-information) +- [8.2 Our Code of Conduct](#82-our-code-of-conduct) + - [8.2.1 Member Expectations](#821-member-expectations) + - [8.2.2 Report an issue](#822-report-an-issue) + - [8.2.3 Respond to a CoC issue](#823-respond-to-a-coc-issue) + - [8.2.4 Escalate an issue](#824-escalate-an-issue) + - [8.2.5 Code of Conduct Panel](#825-code-of-conduct-panel) +- [8.3 Handling Reports and Escalations](#83-handling-reports-and-escalations) + - [8.3.1 Conflict of Interest](#831-conflict-of-interest) + - [8.3.2 Reports to `report@mailing-list`](#832-reports-to-reportmailing-list) + - [8.3.3 Reports to `coc-escalation@mailing-list`](#833-reports-to-coc-escalationmailing-list) +- [Contributor Covenant Code of Conduct](#contributor-covenant-code-of-conduct) +- [Attribution](#attribution) + + +[bylaws]: ./bylaws/README.md +[cfc]: GOVERNANCE.md#commonhaus-foundation-council "Commonhaus Foundation Council" +[cc-dm]: GOVERNANCE.md#decision-making-and-voting +[coc-reports]: #83-handling-reports-and-escalations +[cocp]: #825-code-of-conduct-panel "Code of Conduct Panel" +[membership]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml "Members" -## Contact information +## 8.1 Contact information -- **Project Issues:** Each CF project will define a `CODE_OF_CONDUCT.md`. For issues related to a project, start there. -- **Founation Issues:** Issues related to the CF should be sent to `report@mailing-list` for [review](#respond-to-a-coc-issue) by the [Commonhaus Foundation Council][cfc] (CFC). +- **Project-related Issues:** Each CF project will define a `CODE_OF_CONDUCT.md`. For issues related to a project, start there. +- **Foundation-wide Issues:** Issues related to the CF should be sent to `report@mailing-list` for [review](#823-respond-to-a-coc-issue) by the [Commonhaus Foundation Council][cfc] (CFC). - The CFC will follow [CF CoC procedures][coc-reports] when handling CoC reports. - Records will be kept in TODO-private-repository. Access to this repository is restricted to current CFC members. -- **Escalations:** [Escalations](#escalate-an-issue) should be sent to `coc-escalation@mailing-list` for review by the [Code of Conduct Panel (COCP)][cocp]. +- **Escalations:** [Escalations](#824-escalate-an-issue) should be sent to `coc-escalation@mailing-list` for review by the [Code of Conduct Panel (COCP)][cocp]. - 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. -[cfc]: 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]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml "Members" -[coc-reports]: #handling-reports-and-escalations - -## Our Code of Conduct +## 8.2 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)). @@ -40,7 +47,7 @@ The CF has adopted the [Contributor Covenant v2.1][v2.1] as its CoC (full text [ A CoC is meaningful only [when it is effectively enforced](https://medium.com/mozilla-open-innovation/how-were-making-code-of-conduct-enforcement-real-and-scaling-it-3e382cf94415). Having a unified CoC allows for consistent enforcement and better support across all CF projects. -### Member Expectations +### 8.2.1 Member Expectations All participants in CF projects are bound by the principles outlined in this Code of Conduct. @@ -65,7 +72,7 @@ When decisions are made within the established guidelines and policies of CF pro 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 +### 8.2.2 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. @@ -74,7 +81,7 @@ Confidentiality is of utmost importance. We also understand that the person repo - The CF *prohibits retaliation* against individuals who report concerns in good faith. -### Respond to a CoC issue +### 8.2.3 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. @@ -84,7 +91,7 @@ Access to the private repository should be restricted to individuals charged wit **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 +### 8.2.4 Escalate an issue We expect most reports to be handled by the processes put in place by a project or the CFC. @@ -92,7 +99,7 @@ The CF maintains the CoCP to manage escalation when a reporter (a) believes that 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][coc-reports] -### Code of Conduct Panel +### 8.2.5 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. @@ -101,15 +108,15 @@ CoCP members should consider objectivity and diversity of experience and perspec Members of the CoCP will be documented in the `cocp-panel` [MEMBERS.yaml][membership] attribute. -## Handling Reports and Escalations +## 8.3 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 +### 8.3.1 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` +### 8.3.2 Reports to `report@mailing-list` All members of the CFC are subscribed to the `report@mailing-list` mailing list. @@ -123,7 +130,7 @@ We understand that the person reporting the issue (**reporter**) may not be the 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` +### 8.3.3 Reports to `coc-escalation@mailing-list` All members of the CoCP are subscribed to the `coc-escalation@mailing-list` mailing list. diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 849e32f..5d5ad16 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -3,37 +3,76 @@ status: draft --- # Commonhaus Foundation Project Governance -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 +Welcome to the governance documentation for the Commonhaus Foundation (CF). + +This document is **Section 2** of [CF Bylaws][bylaws], outlines the structures, roles, and processes that guide our collaborative and open-source community. It's designed to ensure clarity, fairness, and inclusivity in our decision-making and community interactions. + +- [2.1 CF Membership and Roles](#21-cf-membership-and-roles) + - [2.1.1 Project Membership](#211-project-membership) + - [2.1.2 Project Leaders and Code Owners](#212-project-leaders-and-code-owners) + - [2.1.3 General Members](#213-general-members) + - [2.1.4 Membership Termination and Resignation](#214-membership-termination-and-resignation) +- [2.2 CF Council](#22-cf-council) + - [2.2.1 Composition and Membership](#221-composition-and-membership) + - [2.2.2 Tenure and Transition](#222-tenure-and-transition) + - [2.2.3 Apportioning Duties Among Council Members](#223-apportioning-duties-among-council-members) +- [2.3. CF Advisory Board](#23-cf-advisory-board) +- [2.4 Decision Making and Voting](#24-decision-making-and-voting) + - [2.4.1 General Decision Making](#241-general-decision-making) + - [2.4.2 Elections](#242-elections) +- [2.5 Record Keeping](#25-record-keeping) +- [2.6 Code of Conduct](#26-code-of-conduct) +- [2.7 Trademark Policy](#27-trademark-policy) +- [2.8 Contributing](#28-contributing) + +[bylaws]: ./bylaws/README.md +[coc]: ./CODE_OF_CONDUCT.md +[coc-reports]: ./CODE_OF_CONDUCT.md#handling-reports-and-escalations +[coi-policy]: ./bylaws/conflict-of-interest.md +[Trademark Policy]: ./bylaws/trademark-policy.md [MEMBERS.yaml]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml +[ip-policy]: ./bylaws/ip-policy.md +[records]: ./bylaws/legal-compliance.md#record-keeping +[contrib]: ./CONTRIBUTING.md + +## 2.1 CF Membership and Roles -## Table of Contents +### 2.1.1 Project Membership -- [Project Roles](#project-roles) -- [Commonhaus Foundation Council](#commonhaus-foundation-council) -- [Decision Making and Voting](#decision-making-and-voting) -- [Code of Conduct](#code-of-conduct) -- [Trademark Policy](#trademark-policy) -- [Contributing](#contributing) +We evaluate projects based on ownership, activity, usage, and originality. To be considered, projects must: -## Project Roles +- Be novel or a substantial fork of an existing project. +- Show recent activity and/or significant usage as measured by downloads from a central package repository (Maven Central, GitHub Packages, etc.). +- Comply with the [CF IP Policy][ip-policy]. -**Members:** CF Membership is open to anyone dedicated to our mission, whether through code, documentation, design, community management, or advocacy. Members are empowered to vote in Council elections, initiate proposals, and if inclined, pursue a Council seat. +Project Leaders can submit an application for their project to join the Commonhaus Foundation. +*TBD: Link to process for submitting a project to join* -- Membership application is straightforward, promoting inclusivity for all who align with our mission. Specifics of the process and member expectations will be provided. -- 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. +### 2.1.2 Project Leaders and Code Owners -**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. +Project Leaders and Code Owners play a crucial role in steering CF projects, shaping the foundation's future. Responsibilities include: -- Access: They have write permissions to the repository. -- Reference: Managed through the repository's `CODEOWNERS` file. +- Holding write permissions in project repositories (managed through the `CODEOWNERS` file). +- Full voting rights and automatic eligibility for Council positions. Further Reading: [About code owners](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners) -## Commonhaus Foundation Council +### 2.1.3 General Members + +General membership is open to anyone dedicated to our mission. Active members, contributing to CF or its projects within the past year, gain voting rights after three months. Contributions include: + +- Repository contributions: code, documentation, design work. +- Community management, advocacy, or forum participation. +- Active participation in elections. + +*TBD: Criteria and link to application form for individual members* + +### 2.1.4 Membership Termination and Resignation + +- **Voluntary Resignation:** Members can resign by notifying the Council through a designated channel (e.g., email/form). +- **Revocation of Membership:** The Council may dismiss members for behavior inconsistent with CF's mission or values. This process includes a review and an opportunity for the member to respond. + +## 2.2 CF 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. 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. @@ -47,28 +86,47 @@ Summaries of key decisions and discussions will be shared with the community to - **Concerns and Actions**: Members can voice concerns or propose actions by emailing `council@mailing-list` (TODO: or initiating a GitHub discussion, etc.). -### Composition and Membership +### 2.2.1 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](#2231-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. - **Eligibility**: Any member that has been active within the CF community for at least six months can run or be nominated. - **Elections**: Conducted annually, with every member entitled to one vote. -### Tenure and Transition +### 2.2.2 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. Upon completing their tenure, CFC members may seek re-election to extend their service, or step down. -#### Chairperson of the Council +#### 2.2.2.1 Resignation and Removal of Council Members + +- Council members wishing to resign must formally notify the Chairperson or the Council, with immediate cessation of their responsibilities and rights as Council members upon resignation. +- A Council member may be removed for misconduct, failure to perform duties, or consistent non-participation. + The removal process includes a fair review, an opportunity for the member to respond, and a decision made through a vote by the remaining Council members or a general membership vote. + +In the event of a vacancy, the Council will temporarily assign the duties of the vacated position to other members. A special election will then be held to fill the vacant council seat. + +### 2.2.3 Apportioning Duties Among Council Members + +The Council will decide the distribution of specific roles and responsibilities, such as Secretary and Treasurer duties, among its members. This ensures effective governance and leverages the strengths and interests of each Council member. + +- The **Secretary** is responsible for maintaining records, overseeing official correspondence, and managing organizational documentation. +- The **Treasurer** oversees the financial affairs of the Foundation, including budgeting and financial reporting. In cases where a Fiscal Host or Agent is used, the Treasurer will coordinate with them for accounting and financial management. + +#### 2.2.3.1 Chairperson of the Council The Chairperson orchestrates regular CFC meetings, ensuring leadership in discussions is evenly spread. They also oversee the proper handling of [Code of Conduct reports and escalations][coc-reports]. -## Commonhaus Foundation Advisory Board +#### 2.2.3.2 Committees and Delegation -The CF Advisory Board comprises representatives from organizations and companies that support the Commonhaus Foundation. It acts as a bridge between the CF and the broader tech industry, providing diverse insights and strategic guidance to inform the Council's decisions. +The Council may establish committees to manage specific areas of responsibility. While delegating tasks to these committees, the Council retains ultimate oversight and decision-making authority. + +## 2.3. CF Advisory Board + +The CF Advisory Board comprises representatives from organizations and companies that support the CF. It acts as a bridge between the CF and the broader tech industry, providing diverse insights and strategic guidance to inform the Council's decisions. The Advisory Board does not have decision-making authority but plays a crucial role in shaping the foundation's direction through advice and industry perspectives. The structure is designed to ensure robust representation and dialogue: @@ -84,9 +142,9 @@ The Advisory Board does not have decision-making authority but plays a crucial r An up-to-date list of Advisory Board representatives will be maintained in the `advisory-board` [MEMBERS.yaml][] attribute, fostering transparency and openness. -## Decision Making and Voting +## 2.4 Decision Making and Voting -### General Decision Making +### 2.4.1 General Decision Making True to Open Source roots, the CF ensures every member's voice is heard through the Lazy Consensus decision-making model. @@ -104,7 +162,7 @@ When seeking consensus, members should express objections or dissent as early as 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 +#### 2.4.1.1 Seeking consensus in meetings When an agenda item has appeared to reach a consensus the moderator will ask "Does anyone object?" as a final call for dissent from the consensus. @@ -114,7 +172,7 @@ The call for a vote must be seconded by a majority of the CFC or else the discus For all votes, a simple majority of all Voting CFC members for, or against, the issue wins. A Voting CFC member may choose to participate in any vote through abstention. -#### Seeking consensus on mailing lists +#### 2.4.1.2 Seeking consensus on mailing lists When seeking consensus in mailing lists, it is important to leave enough time (at least 72-hours) for everyone to read the email and respond with opinions and objections. @@ -126,7 +184,7 @@ CFC members should consider the following when drafting consensus-seeking email: It is customary for the initiator to post a summary once it appears that consensus has been reached, to ensure that their understanding is accurate. -### Elections +### 2.4.2 Elections 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. @@ -134,15 +192,19 @@ This approach allows members to rank candidates in order of preference, ensuring - [Voting using Elekto](https://elekto.dev/docs/voting/) - [Administering an Election using Elekto](https://elekto.dev/docs/administration/) -## Code of Conduct +## 2.5 Record Keeping + +The CF is committed to maintaining thorough and accessible records of its activities as documented in [Record Keeping][records]. + +## 2.6 Code of Conduct -All participants in the project are expected to adhere to the project's [Code of Conduct](CODE_OF_CONDUCT.md). Please ensure you are familiar with its guidelines and expectations, as it's essential for maintaining a positive and collaborative environment. +All participants in the project are expected to adhere to the project's [Code of Conduct][coc]. Please ensure you are familiar with its guidelines and expectations, as it's essential for maintaining a positive and collaborative environment. -## Trademark Policy +## 2.7 Trademark Policy -Commonhouse Foundation logos, icons, and domain names are protected by trademark rights. Usage of these trademarks must adhere to our [Trademark Policy](governance/trademark-policy.md). +CF logos, icons, and domain names are protected by trademark rights. Usage of these trademarks must adhere to our [Trademark Policy][]. -## Contributing +## 2.8 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). +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][contrib]. diff --git a/README.md b/README.md index b9ef07d..81da93b 100644 --- a/README.md +++ b/README.md @@ -16,8 +16,8 @@ We are dedicated to ensuring the long-term growth and stability of GitHub-style 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#basic-ip-requirements +[succession]: bylaws/succession-plan.md +[ip-policy]: bylaws/ip-policy.md ## Core Distinctions of CF @@ -46,10 +46,11 @@ We're not just a placeholder but a guide, assisting projects as they grow and, i ## CF's Focus and Vision -- **Prioritize Action:** We favor tangible outcomes over extended discussions, concentrating on: - - **Application Frameworks:** For efficient app development and deployment. - - **Libraries:** Essential tools that minimize application complexities. -- **Selective Alignment:** Not every project aligns with CF. While we respect the importance of *Specifications & Standards*, we do not engage in their definition or debate. This is a home for self-governing, code-centric projects. +**Prioritize Action:** We favor tangible outcomes over extended discussions, concentrating on: +- **Application Frameworks:** For efficient app development and deployment. +- **Libraries:** Essential tools that minimize application complexities. + +**Selective Alignment:** Not every project aligns with CF. While we respect the importance of *Specifications & Standards*, we do not engage in their definition or debate. This is a home for self-governing, code-centric projects. ## Community and Sponsorship @@ -64,4 +65,4 @@ CF is committed to inclusive growth, opening its doors to all individuals who sh - [Code of Conduct](CODE_OF_CONDUCT.md) - [Commonhaus Foundation Governance](GOVERNANCE.md) - [Succession Planning][succession] -- [IP Policy Guidance][ip-policy-guidance] +- [IP Policy][ip-policy] diff --git a/bylaws/README.md b/bylaws/README.md new file mode 100644 index 0000000..76ca25e --- /dev/null +++ b/bylaws/README.md @@ -0,0 +1,53 @@ +--- +status: draft +--- +# BYLAWS OF COMMONHAUS FOUNDATION + +Adopted [Insert Adoption Date] + +## Section 1. GENERAL + +### 1.1 Purposes + +The Commonhaus Foundation (CF) is dedicated to open-source innovation and collaboration. It is organized for the purpose of promoting common business interests and improving business conditions in the technology industry, qualifying it as exempt from Federal income tax under Section 501(c)(6) of the Internal Revenue Code of 1986 (or the corresponding provision of any subsequent Federal tax laws). + +Our nonprofit purposes are to: +1. Serve the community by facilitating collaboration between creators and consumers of CF projects. +2. Empower a diverse community of contributors to create, maintain, enhance, and secure vital open-source libraries and frameworks. +3. Foster and support the longevity of open-source projects through community collaboration and shared stewardship. +4. Promote the exchange of ideas and information within the technology community. +5. Support the common interests of businesses and professionals to improve the economic climate and business development of commercial enterprises in the technology sector. + +The CF will conduct activities lawful for a nonprofit corporation organized under the laws of the State of Florida and will operate as a tax-exempt entity in accordance with Section 501(c)(6) of the U.S. Internal Revenue Code, or the corresponding section of any future federal tax code. + +### 1.2 Nonprofit Status + +1. The CF is organized and shall be operated as a non-stock, nonprofit membership corporation under the laws of the State of Florida. +2. The CF shall be operated as a tax-exempt entity in accordance with Section 501(c)(6) of the U.S. Internal Revenue Code, or the corresponding section of any future federal tax code. + +### 1.3 Principal Office + +The CF may have offices either within or outside the Central Florida area (or anywhere throughout the State of Florida), as the [CF Council][] may designate or as the affairs of the CF may require from time to time. + +## 1.4 Authoritative Document Version + +The authoritative copy of these bylaws is maintained in a dedicated GitHub repository. This ensures transparency, version control, and accessibility. + +Official amendments and updates to these bylaws are documented and approved using issues and pull-requests against that repository. This process allows for clear tracking of changes and provides a definitive reference for the most current version of the document. + +## SECTIONS + +Please see the following sections: + +- Section 2. [GOVERNANCE](../GOVERNANCE.md) + - [Foundation Membership and Roles](../GOVERNANCE.md#foundation-membership-and-roles) + - [Commonhaus Foundation Council](../GOVERNANCE.md#commonhaus-foundation-council) + - [Decision Making and Voting](../GOVERNANCE.md#decision-making-and-voting) +- Section 3. [Legal and Compliance Policy](./legal-compliance.md) +- Section 4. [Conflict of Interest Policy](./conflict-of-interest.md) +- Section 5. [Continuity and Administrative Access Policy](./succession-plan.md) +- Section 6. [IP Policy](./ip-policy.md) +- Section 7. [Trademark Policy](./trademark-policy.md) +- Section 8. [Code of Conduct](../CODE_OF_CONDUCT.md) + +[CF Council]: ../GOVERNANCE.md#commonhaus-foundation-council \ No newline at end of file diff --git a/bylaws/conflict-of-interest.md b/bylaws/conflict-of-interest.md new file mode 100644 index 0000000..cbf9c82 --- /dev/null +++ b/bylaws/conflict-of-interest.md @@ -0,0 +1,77 @@ +--- +status: draft +--- +# Commonhaus Foundation Conflict of Interest Policy + +This document is **Section 4** of Commonhaus Foundation (CF) [Bylaws][bylaws] and establishes policies for identifying, disclosing, and managing conflicts of interest within the CF. + +[bylaws]: ./README.md + +This policy applies to all individuals with decision-making authority within the CF, including Council members and officers, and extends to project leaders and members when their interests may influence Foundation activities. + +- [4.1 Definition of Conflict of Interest](#41-definition-of-conflict-of-interest) + - [Examples](#examples) +- [4.2 Disclosing Potential Conflicts of Interest](#42-disclosing-potential-conflicts-of-interest) + - [4.2.1 Immediate Disclosure](#421-immediate-disclosure) + - [4.2.2 Annual Disclosure](#422-annual-disclosure) +- [4.3 Managing Conflicts](#43-managing-conflicts) +- [4.4 Transparency and Documentation](#44-transparency-and-documentation) +- [4.5 Prohibited Acts](#45-prohibited-acts) +- [4.6 Guidelines for Gifts and Hospitality](#46-guidelines-for-gifts-and-hospitality) +- [4.7 Training and Compliance](#47-training-and-compliance) +- [4.8 Procedures for Determining Compensation](#48-procedures-for-determining-compensation) +- [4.9 Review of Policy](#49-review-of-policy) + +## 4.1 Definition of Conflict of Interest + +A conflict of interest occurs when an individual's personal, professional, or financial interests could potentially interfere with or influence their decisions or actions on behalf of the CF. + +### 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. +- Relationship with another nonprofit competing for the same resources. +- Personal or business relationships affecting CF decisions. + +## 4.2 Disclosing Potential Conflicts of Interest + +### 4.2.1 Immediate Disclosure + +All individuals must disclose any potential conflict of interest as soon as it is recognized. This disclosure should be made to the CF Council or a designated point of contact. + +### 4.2.2 Annual Disclosure + +Each member of the CF Council and officers must provide an annual statement declaring any known potential conflicts of interest. + +## 4.3 Managing Conflicts + +Upon the disclosure of a potential conflict, the individual involved must abstain from participating in discussions or decision-making processes related to the matter. The CF Council will review the situation and determine the appropriate course of action. + +## 4.4 Transparency and Documentation + +All discussions and decisions related to conflicts of interest must be documented and included in the minutes of the CF Council meetings. + +## 4.5 Prohibited Acts + +The CF will not engage in transactions where there is a direct conflict of interest with a Council member, officer, or key person, unless it is in the best interest of the CF and has been thoroughly vetted and approved by the Council. + +## 4.6 Guidelines for Gifts and Hospitality + +Members should not accept gifts, favors, or hospitality that might appear to influence their decision-making or actions on behalf of the CF. + +## 4.7 Training and Compliance + +Members will be provided with information and training to understand and adhere to this policy. Failure to comply may result in corrective action, including potential removal from their position within the CF. + +## 4.8 Procedures for Determining Compensation + +When hiring staff or paying for contract work, the CFC 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. + +## 4.9 Review of Policy + +This policy will be reviewed periodically to ensure it remains relevant and effective. Any amendments will be approved by the CF Council. + +For questions or clarifications on this policy, please contact `legal@mailing-list`. \ No newline at end of file diff --git a/bylaws/ip-policy.md b/bylaws/ip-policy.md new file mode 100644 index 0000000..300328d --- /dev/null +++ b/bylaws/ip-policy.md @@ -0,0 +1,94 @@ +--- +status: draft +--- +# Commonhaus Foundation Intellectual Property Policy + +This document, forming **Section 6** of Commonhaus Foundation (CF) [Bylaws][bylaws], outlines our policies on intellectual property (IP) to guide contributors and safeguard the interests of our projects and community. + +[bylaws]: ./README.md +[cfc]: ../GOVERNANCE.md#commonhaus-foundation-council "CF Council" +[standard website footer]: ./website-footer.md "CF website footers" + +- [6.1 License Selection and Usage](#61-license-selection-and-usage) +- [6.2 Contributions](#62-contributions) + - [6.2.1 Documentation and Media Files](#621-documentation-and-media-files) +- [6.3 Collaborations and External Projects](#63-collaborations-and-external-projects) +- [6.4 Intellectual Property Rights](#64-intellectual-property-rights) +- [6.5 Implementing the IP Policy](#65-implementing-the-ip-policy) + - [6.5.1 Copyright Statements](#651-copyright-statements) +- [6.6 Obtaining an Exemption](#66-obtaining-an-exemption) +- [6.7 Policy Changes and Additional Requirements](#67-policy-changes-and-additional-requirements) + +## 6.1 License Selection and Usage + +CF projects can use any [open-source license approved by the Open Source Initiative](https://opensource.org/licenses/) (OSI). The CF is most familiar with the following four licenses, which can simplify the review process: + +- [The Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0) +- [The MIT License][MIT] +- [The 2-Clause BSD License](https://opensource.org/license/bsd-2-clause/) +- [The 3-Clause BSD License](https://opensource.org/license/bsd-3-clause/) + +Selection of other OSI-approved licenses is permitted but may require additional review by the [Commonhaus Foundation Council][cfc] (CFC). + +## 6.2 Contributions + +Code contributions should comply with the project's chosen license. + +Contributions are validated through a [Developer Certificate of Origin][DCO] (DCO) or a Contributor License Agreement (CLA), as determined by the project. + +### 6.2.1 Documentation and Media Files + +Projects should choose an appropriate license for documentation and media files, such as [CC BY 4.0][] or the project's primary license. + +All contributions must be clearly labeled with license information. + +## 6.3 Collaborations and External Projects + +When collaborating with external open-source projects ("Upstream Projects"): + +- Comply with the Upstream Project's licensing requirements. +- Prioritize compatibility +- Seek alternative license approvals from the CFC when necessary. + +## 6.4 Intellectual Property Rights + +CF membership does not grant or transfer intellectual property rights unless explicitly stated by this policy or a Project's license. + +## 6.5 Implementing the IP Policy + +Project leaders should ensure compliance with this policy and provide clear guidance to contributors. + +- Use the [standard website footer][] for member project websites, +- Ensure that contribution guidelines are updated and accessible, and +- (optionally) Maintain accurate copyright statements. + +### 6.5.1 Copyright Statements + +Using [copyright statements in your code][code-copyright] is a practice with mixed adoption. + +If your project wants to add copyrights to source code, we recommend one of the following: + +- Copyright <year of file creation> The XYZ Authors. +- Copyright <year of file creation> Contributors to the XYZ project. +- Copyright <year of file creation> The original author or authors. + +Updating the year after the file is created is unnecessary. + +Do not alter existing copyright lines unless you have the right to do so. + +## 6.6 Obtaining an Exemption + +If the [IP Policy][] doesn't cater to your project's needs, request special permission from the CFC. + +[Steps to request an exemption TBD] + +## 6.7 Policy Changes and Additional Requirements + +The CF Council reserves the right to modify this policy. Projects may have additional contribution requirements, provided they align with this policy and are clearly communicated to contributors. + +For detailed guidance on implementing this policy or for assistance, projects can contact `legal@mailing-list`. + +[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 diff --git a/bylaws/legal-compliance.md b/bylaws/legal-compliance.md new file mode 100644 index 0000000..249c256 --- /dev/null +++ b/bylaws/legal-compliance.md @@ -0,0 +1,71 @@ +--- +status: draft +--- +# Commonhaus Foundation Legal and Compliance Policy + +This document is **Section 3** of Commonhaus Foundation (CF) [Bylaws][bylaws]. It outlines the legal and compliance policies designed to ensure our operations are not only legally sound but also adhere to the highest ethical standards. + +- [3.1 Indemnification](#31-indemnification) +- [3.2 Record Keeping](#32-record-keeping) + - [3.2.1 Methods and Platforms](#321-methods-and-platforms) + - [3.2.2 Accessibility and Security](#322-accessibility-and-security) + - [3.2.3 Compliance and Management](#323-compliance-and-management) + - [3.3 Insurance](#33-insurance) +- [3.4 Liability](#34-liability) +- [3.5 Compliance with Laws and Regulations](#35-compliance-with-laws-and-regulations) +- [3.6 Amendments and Policy Updates](#36-amendments-and-policy-updates) +- [3.7 Contact for Queries](#37-contact-for-queries) + +[bylaws]: ./README.md + +## 3.1 Indemnification + +The CF commits to protecting its Council members, officers, and other key personnel against legal risks associated with their roles. In cases arising from their duties, we provide indemnification for expenses and liabilities, under the following conditions: + +- Protection excludes acts of willful misconduct or gross negligence. +- Those seeking indemnification must notify the Foundation promptly, enabling review and confirmation that the case aligns with our policy guidelines. + +## 3.2 Record Keeping + +The CF will maintain records of all activities for transparency and legal compliance. + +### 3.2.1 Methods and Platforms + +- **Digital Records:** Key documents such as meeting minutes, election information, and applications will be stored and versioned in GitHub repositories. +- **Legal Documents:** Essential legal documents and filings will be kept in both electronic and paper formats to ensure redundancy and compliance. + +### 3.2.2 Accessibility and Security + +- **Transparency:** Non-confidential records will be accessible to all members, fostering transparency. +- **Confidentiality:** Sensitive records will be securely stored, with restricted access to protect privacy. + +### 3.2.3 Compliance and Management + +- **Annual Reports** will be prepared and filed as per state and federal regulations, with accessibility as required by law. +- **Retention and Version Control**: Documents will adhere to legal requirements for retention periods and employ version control for historical accuracy. +- **Backup and Security:** Regular backups and robust security measures to safeguard digital records. + +### 3.3 Insurance + +**Decision-making:** The Commonhaus Foundation Council is responsible for evaluating and deciding on the insurance needs of the Foundation. This includes assessing the necessity and feasibility of various insurance coverages. + +**Types of Insurance:** The Council shall consider maintaining insurance policies appropriate for the Foundation’s activities and risks, such as Directors and Officers (D&O) Liability insurance, property insurance, and liability insurance for events. + +**Regular Review:** The insurance policies will be reviewed regularly, at least annually, to ensure they remain adequate and align with the Foundation's evolving needs and circumstances. + +## 3.4 Liability + +CF Council members and officers are not personally liable for actions undertaken in their official capacity, except in cases of willful misconduct or gross negligence. + +## 3.5 Compliance with Laws and Regulations + +The CF is committed to complying with all applicable laws and regulations related to nonprofit operations, intellectual property, employment, and other relevant domains. Regular policy reviews are conducted to ensure ongoing compliance. + +## 3.6 Amendments and Policy Updates + +- This policy is subject to periodic reviews and updates to align with evolving legal requirements and best practices. +- Amendments undergo a structured review and approval process, ensuring continuous compliance and relevance. + +## 3.7 Contact for Queries + +For questions or clarifications on legal and compliance matters, please contact `legal@mailing-list`. diff --git a/governance/succession-plan.md b/bylaws/succession-plan.md similarity index 87% rename from governance/succession-plan.md rename to bylaws/succession-plan.md index 74e97a8..13321ca 100644 --- a/governance/succession-plan.md +++ b/bylaws/succession-plan.md @@ -7,14 +7,22 @@ The Commonhaus Foundation (CF) understands the impact of reliable libraries and The CF aims to help projects address this vital concern. +This document is **Section 5** of Commonhaus Foundation (CF) [Bylaws][bylaws]. This policy articulates the foundation's need for administrative access to project resources and the principles that guide this requirement. +- [5.1 Policy Rationale](#51-policy-rationale) +- [5.2 Scope of Access and Intervention](#52-scope-of-access-and-intervention) +- [5.3 Commitment to Project Code Owners and the Community](#53-commitment-to-project-code-owners-and-the-community) +- [5.4 Policy Review and Updates](#54-policy-review-and-updates) + + +[bylaws]: ./README.md [GOVERNANCE.md]: ../GOVERNANCE.md [CONTRIBUTING.md]: ../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 +## 5.1 Policy Rationale Administrative access empowers the CF to: @@ -27,7 +35,7 @@ Administrative access empowers the CF to: 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. -## Scope of Access and Intervention +## 5.2 Scope of Access and Intervention **Limited Interference:** Although the CF maintains administrative access, every option to contact the current code owners will be made before we do so. Action will require a consensus of [X%] of the project's active contributors or CF Council members. @@ -35,7 +43,7 @@ For libraries under heavy use, we will encourage a "path of least disturbance" a **Transparent Communication:** Any exercise of administrative privilege by the CF will be recorded and communicated to the project code owners. -## Commitment to Project Code Owners and the Community +## 5.3 Commitment to Project Code Owners and the Community The CF respects each project's chosen governance model. This policy complements, and does not supersede, those models. We recommend projects define: @@ -52,6 +60,6 @@ Further Reading: - [Wrangling Web Contributions: How to Build a CONTRIBUTING.md](https://mozillascience.github.io/working-open-workshop/contributing/) - See [CONTRIBUTING.md][] and the [Project CONTRIBUTING.md template][CONTRIB-TPL] for examples. -### Policy Review and Updates +## 5.4 Policy Review and Updates This policy may undergo periodic reviews and updates to cater to the evolving needs of the CF and its projects. Project leaders and the community will be involved in and informed of any changes. diff --git a/governance/trademark-policy.md b/bylaws/trademark-policy.md similarity index 75% rename from governance/trademark-policy.md rename to bylaws/trademark-policy.md index 9564da7..502520c 100644 --- a/governance/trademark-policy.md +++ b/bylaws/trademark-policy.md @@ -3,23 +3,28 @@ status: draft --- # Commonhaus Foundation Trademark Policy Statement -This is a statement regarding the use and licensing of trademarks owned by the Commonhaus Foundation (CF) and used by CF projects. For purposes of this document, references to trademarks or marks include all trade and service marks and logos owned by the Commonhaus Foundation legal entity. +This document, forming **Section 7** of Commonhaus Foundation (CF) [Bylaws][bylaws], is a statement regarding the use and licensing of trademarks owned by the Commonhaus Foundation (CF) and used by CF projects. For purposes of this document, references to trademarks or marks include all trade and service marks and logos owned by the Commonhaus Foundation legal entity. -- [Trademark Definitions](#trademark-definitions-and-ownership) and [Ownership](#ownership-and-specific-project-trademarks) -- [Trademark usage guidelines](#trademark-usage-guidelines) -- [Guidelines for Commonhaus Foundation Trademarks](#guidelines-for-commonhaus-trademarks) - - [General Trademark Rules](#general-trademark-rules) - - [Specific Rules for Commonhaus Foundation Trademarks](#specific-rules-for-commonhaus-foundation-trademarks) - - [Visual Trademark Instructions](#visual-trademark-instructions) -- [Commonhaus Foundation Trademarks and Crowdfunding](#commonhaus-trademarks-and-crowdfunding) -- [Contact Us](#questions-comments-concerns) -- [Disclaimer](#disclaimer) +- [7.1 Trademark Definitions and Ownership](#71-trademark-definitions-and-ownership) + - [7.1.1 Ownership and Specific Project Trademarks](#711-ownership-and-specific-project-trademarks) +- [7.2 Trademark Usage Guidelines](#72-trademark-usage-guidelines) +- [7.3 Guidelines for Commonhaus Trademarks](#73-guidelines-for-commonhaus-trademarks) + - [7.3.1 General Trademark Rules](#731-general-trademark-rules) + - [7.3.2 Specific Rules for Commonhaus Foundation Trademarks](#732-specific-rules-for-commonhaus-foundation-trademarks) + - [7.3.3 Visual Trademark Instructions](#733-visual-trademark-instructions) +- [7.4 Commonhaus Trademarks and Crowdfunding](#74-commonhaus-trademarks-and-crowdfunding) +- [7.5 Questions, Comments, Concerns](#75-questions-comments-concerns) +- [7.6 Disclaimer](#76-disclaimer) +- [7.7 Modifications and Updates](#77-modifications-and-updates) +- [7.8 Attribution](#78-attribution) -## Trademark Definitions and Ownership +[bylaws]: ./README.md + +## 7.1 Trademark Definitions and Ownership The Commonhaus Foundation owns all CF trademarks, both registered and unregistered. A comprehensive list of registered trademarks, pending registrations, and trademarks in use can be found at https://trademark-list.website. -### Ownership and Specific Project Trademarks +### 7.1.1 Ownership and Specific Project Trademarks While all trademarks are owned by the Commonhaus Foundation, each CF project may have its own (unique) set of trademarks. These trademarks, along with any specific usage guidelines, will be documented in the project's `TRADEMARK.md` file. @@ -27,7 +32,7 @@ In case of any inconsistency between the rules in a project's `TRADEMARK.md` fil Member companies or projects that heavily rely on a specific trademark can request special permissions or rights from the CF to enforce or defend the trademark in situations where CF may not act. These permissions will be granted on a case-by-case basis and do not transfer overall ownership of the trademark. -## Trademark Usage Guidelines +## 7.2 Trademark Usage Guidelines This section explains how trademarks ensure consistent quality, and how you can use them without implying the endorsement of the Commonhaus Foundation. @@ -49,31 +54,31 @@ Proper use of Commonhaus Foundation trademarks by following these trademark usag Any use of or reference to Commonhaus trademarks that is inconsistent with this trademark policy, or use of marks that are confusingly similar to trademarks of the Commonhaus Foundation, is prohibited. All uses of Commonhaus Foundation trademarks, and all goodwill associated therewith, will inure solely to the benefit of the Commonhaus Foundation, and Commonhaus Foundation projects. -## Guidelines for Commonhaus Trademarks +## 7.3 Guidelines for Commonhaus Trademarks Understanding and respecting trademark rules are vital for preserving the integrity and recognition of a brand. These guidelines outline how to correctly use any trademark, especially those associated with the Commonhaus Foundation. -### General Trademark Rules +### 7.3.1 General Trademark Rules - **Nature of Use:** - - Trademarks should be used as adjectives followed by a generic noun, not as verbs or nouns. - - Avoid using trademarks in plural or possessive forms. - - Do not alter trademarks. This includes shortening, hyphenating, abbreviating, or breaking them into parts. + - Trademarks should be used as adjectives followed by a generic noun, not as verbs or nouns. + - Avoid using trademarks in plural or possessive forms. + - Do not alter trademarks. This includes shortening, hyphenating, abbreviating, or breaking them into parts. - **Domain and Design:** - - Trademarks must not form any part of domain names or product names. - - Do not incorporate trademarks into company logos or designs. + - Trademarks must not form any part of domain names or product names. + - Do not incorporate trademarks into company logos or designs. - **Trademark Notices:** - - Always provide a notice on the primary appearance of a trademark. - - Do not modify trademark symbols. For instance, ™ should not be altered to an ® without the owner's consent. If in doubt regarding a mark's registration, contact the Commonhaus Foundation. + - Always provide a notice on the primary appearance of a trademark. + - Do not modify trademark symbols. For instance, ™ should not be altered to an ® without the owner's consent. If in doubt regarding a mark's registration, contact the Commonhaus Foundation. -### Specific Rules for Commonhaus Foundation Trademarks +### 7.3.2 Specific Rules for Commonhaus Foundation Trademarks - **Correct Usage:** - - Use trademarks in their most up-to-date form. - - Ensure trademarks distinguish from surrounding text, e.g., by capitalizing or using distinct fonts. - - Mention that usage doesn't imply the foundation's endorsement unless explicitly stated. + - Use trademarks in their most up-to-date form. + - Ensure trademarks distinguish from surrounding text, e.g., by capitalizing or using distinct fonts. + - Mention that usage doesn't imply the foundation's endorsement unless explicitly stated. - **Prohibited Activities:** - Avoid generic usage of trademarks. @@ -88,7 +93,7 @@ Understanding and respecting trademark rules are vital for preserving the integr - **Approval:** - The Commonhaus Foundation has the discretion to review and decide on any trademark usage, even if not explicitly detailed in the policy. -### Visual Trademark Instructions +### 7.3.3 Visual Trademark Instructions To maintain the integrity of The Commonhaus Foundation's visual trademarks: @@ -98,7 +103,7 @@ To maintain the integrity of The Commonhaus Foundation's visual trademarks: - **Alterations:** Preserve the original logo. Avoid distortions, rotations, and other modifications. - **Background:** Ensure that the logo is set against contrasting backgrounds for visibility. -## Commonhaus Trademarks and Crowdfunding +## 7.4 Commonhaus Trademarks and Crowdfunding Want to use a Commonhaus trademark for crowdfunding? Here's what you need to know and do. @@ -123,13 +128,13 @@ To request permission to use a mark, please contact `trademarks@mailing-list`. Finally, if you are raising money through crowdfunding, be aware that you are not acting on behalf of the Commonhaus Foundation. It is your responsibility to know and follow all applicable laws. -## Questions, Comments, Concerns +## 7.5 Questions, Comments, Concerns We value input from our community in maintaining the integrity of the Commonhaus Foundation's trade and service marks. If you have questions with respect to these guidelines or to report concerns regarding the use or misuse of a trademark of the Commonhaus Foundation, or to obtain written permission for a proposed use of Commonhaus trademarks, contact `trademarks@mailing-list`. -## Disclaimer +## 7.6 Disclaimer We can't guarantee that our trademarks won't infringe on others, and we're not responsible for actions taken under this policy. If you use our trademarks, you'll have to defend us against any legal claims. @@ -137,11 +142,11 @@ We can't guarantee that our trademarks won't infringe on others, and we're not r - The Commonhaus Foundation does not warrant that any pending trademark applications for Commonhaus trademarks will result in any granted trademark protection. - The Commonhaus Foundation shall not be liable for any claims relating to user’s activities taken under the permissions granted by this policy. You (the user of Commonhaus Trademarks) hereby agree to indemnify, defend and hold the the Commonhaus Foundation and its contributors harmless against any such claims. -## Modifications and Updates +## 7.7 Modifications and Updates The Commonhaus Foundation may modify or update this Trademark Policy as needed. You are responsible for staying informed about the most recent trademark guidelines. -## Attribution +## 7.8 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). It is licensed under a Creative diff --git a/governance/website-footer.md b/bylaws/website-footer.md similarity index 100% rename from governance/website-footer.md rename to bylaws/website-footer.md diff --git a/governance/conflict-of-interest.md b/governance/conflict-of-interest.md deleted file mode 100644 index 1213415..0000000 --- a/governance/conflict-of-interest.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -status: draft ---- -# Commonhaus Foundation Conflict of Interest Policy - -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. -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 (CFC) and Advisory Board members, and extends to CF members and project leaders when their personal interests may influence Foundation activities. - -## Identifying Conflicts of Interest - -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. -- Relationship with another nonprofit competing for the same resources. -- Personal or business relationships affecting CF decisions. - -## Disclosing Potential Conflicts of Interest - -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 CFC immediately upon recognition. - -### Annual Disclosure - -You are required to submit an annual statement of potential conflicts, and for CFC members, also before your initial appointment. - -## Determining Whether a Conflict of Interest Exists - -The CFC, or a designated committee, will review disclosures to determine if a conflict exists. The involved individual will recuse themselves from the decision-making process. - -The CFC will consider whether the potential conflict might affect CF’s transactions or reputation and take appropriate action. - -## Procedures for Addressing a Conflict of Interest - -The CFC may gather facts from the involved party but will deliberate and decide on the matter in their absence. - -For transactions involving significant interests, the CFC will seek alternatives and require a consensus for approval, with all decisions being documented. - -## Minutes and Documentation - -The minutes of the CFC meetings will include details of discussions regarding conflicts, including names, interests, and the rationale for decisions. - -## Prohibited Acts - -CF will not make loans to any Council members, officers, or key persons. - -## Procedures for Determining Compensation - -When hiring staff or paying for contract work, the CFC 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. diff --git a/governance/ip-policy-guidance.md b/governance/ip-policy-guidance.md deleted file mode 100644 index b1d03ae..0000000 --- a/governance/ip-policy-guidance.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -status: draft ---- -# Commonhaus Foundation IP Policy Guidance - -This guide simplifies the [Commonhaus Foundation (CF) IP Policy][IP Policy] for easier implementation. - -[IP Policy]: ip-policy.md -[cfc]: ../GOVERNANCE.md#commonhaus-foundation-council "Commonhaus Foundation Council" -[standard website footer]: website-footer.md "Commonhaus Foundation website footers" - -## Basic IP Requirements - -1. **Licensing:** Refer to the [IP Policy][] for approved licenses. If your chosen license isn't listed, [seek an exemption](#obtaining-an-exemption). - -2. **Copyright Notices:** - We recommend one of the following: - - - Copyright <year of file creation> The XYZ Authors. - - Copyright <year of file creation> Contributors to the XYZ project. - - Copyright <year of file creation> The original author or authors. - - Do not alter existing copyright lines unless you have the right to do so. Updating the year after the file is created is unnecessary. - - Additional reading on [copyright statements in your code][code-copyright]. - -3. **Website Footer:** Ensure your project's website has the [standard website footer][]. - -4. **Contribution Licensing:** Projects can use either the [DCO][] or a Contributor License Agreement (CLA) for contributions. The chosen method should align with the project's governance and community preferences. - -## Obtaining an Exemption - -If the [IP Policy][] doesn't cater to your project's needs, request special permission from the [CF Council][cfc] (CFC). - -[Steps to request an exemption TBD] - -## Assistance - -For questions about this guidance or the [IP Policy][], contact `legal@mailing-list`. - -[DCO]: https://developercertificate.org -[code-copyright]: https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code diff --git a/governance/ip-policy.md b/governance/ip-policy.md deleted file mode 100644 index 729d83f..0000000 --- a/governance/ip-policy.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -status: draft ---- -# Commonhaus Foundation Intellectual Property Policy - -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”. - -[cfc]: ../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: - - [The Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0) - - [The MIT License][MIT] - - [The 2-Clause BSD License](https://opensource.org/license/bsd-2-clause/) - - [The 3-Clause BSD License](https://opensource.org/license/bsd-3-clause/) - - Other open source licenses require [Commonhaus Foundation Council][cfc] (CFC) approval. - -2. **Collaborations with Upstream Projects:** When collaborating with external open source projects (“Upstream Projects”), Projects must: - - - Comply with the Upstream Project's licensing requirements. - - Prioritize compatibility. - - Seek alternative license approvals from the CFC when necessary. - -3. **Contributions:** Unless approved by the CFC: - - - All code contributions must be under the Project Code License, validated by a [Developers Certificate of Origin (DCO)][DCO] or a Contributor License Agreement (CLA) (chosen by the Project). - - All documentation and media files should use a license chosen by the Project (for example, [CC BY 4.0][CC BY 4.0] or [MIT License][MIT]). - - License information should label all contributed files. - -4. **Policy Changes:** The CFC can modify this policy after notifying the Projects. - -5. **Additional Requirements:** Projects can have additional contribution requirements. - -6. **Intellectual Property Rights:** CF membership does not grant or transfer intellectual property rights unless explicitly stated by this policy or a Project's license. - -For detailed guidance on implementing this policy, refer to the [IP Policy Guidance][]. - -[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/