Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CF Membership Bylaws: membership roles & dues #38

Merged
merged 1 commit into from
Dec 1, 2023
Merged

CF Membership Bylaws: membership roles & dues #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
64 changes: 43 additions & 21 deletions bylaws/cf-membership.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,39 +8,61 @@ It describes eligibility and requirements for different types of membership for

## Project Membership

We evaluate projects based on ownership, activity, usage, and originality. To be considered, projects must:
Joining the CF as a project member involves a few key steps:

- 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].
- **Eligibility**: Projects must be original or substantial forks, demonstrating recent activity and significant usage. We value innovation and active community engagement.

Project Leaders can submit an application for their project to join the Commonhaus Foundation.
*TBD: Link to process for submitting a project to join*
- **Application Process**: Project leaders are invited to submit a comprehensive application outlining the project’s goals, current status, community size, and how it aligns with the CF’s mission *(TBD: Application link)*. The [CF Council][cfc] (CFC) will review each application, and may ask for further information or clarification.

### Project Leaders and Code Owners
- **Approval and Onboarding**: We provide onboarding support and resources to help integrate new projects seamlessly into our ecosystem.

Project Leaders and Code Owners play a crucial role in steering CF projects, shaping the foundation's future. Responsibilities include:
## Project Leaders and Code Owners

- Holding write permissions in project repositories (managed through the `CODEOWNERS` file).
- Full voting rights and automatic eligibility for CFC positions.
Project Leaders and Code Owners are the pillars of their projects and the CF at large.

Further Reading: [About code owners][owners].
- **Responsibilities**: Managing access to project repositories and steering project direction and development. They ensure their projects adhere to CF policies, and collaborate with the CFC to ensure policies remain relevant and reduce procedural burden.
- **Membership and Voting Rights**: Project leaders and code owners are automatically eligible for CF membership, with voting rights and eligibility for CFC positions.

[owners]: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
**Code Owners**: The Code Owners for a repository should be managed through `CODEOWNERS` files. To learn more about this role, see [About Code Owners](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)

## 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:
General membership in the CF is open to all who share our mission and are eager to contribute.

- Repository contributions: code, documentation, design work.
- Community management, advocacy, or forum participation.
- Active participation in elections.
- **How to Become a Member:** Get involved! Whether it’s coding, writing documentation, participating in community management, or advocating for the CF, your active involvement for three months earns you voting rights.
- **Applying for Membership:** Share your intent through a formal application *(TBD: Criteria and form)*. The CFC reviews each application, assessing contributions and alignment with CF values.

*TBD: Criteria and link to application form for general members*
**Decisions and Transparency:** Our review process is transparent. Declined applicants receive explanations and can appeal. Our aim is always to be fair and act in the best interest of the CF community.

### Membership Termination and Resignation
## Membership Dues and Renewal

- **Voluntary Resignation:** Members can resign by notifying the CFC through a designated channel (e.g., email/form).
- **Revocation of Membership:** The CFC 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.
While the CF thrives on the passion and contributions of its members, nominal membership dues play a small but vital role in sustaining our operations.

[ip-policy]: ../policies/ip-policy.md
- **The Role of Dues:** These nominal fees support administrative tasks to ensure the smooth functioning of the CF.
- **Annual Renewal:** The initial payment of dues and the annual renewal process reaffirms your commitment to CF values and agreement to abide by its policies.

Your involvement in the CF, whether as a project member, a leader, or a general member, shapes the future of open-source innovation. We value each contribution and encourage active participation in our diverse and vibrant community.

## Inactive or Retired Members

Life happens, and we understand that. Members may choose to step back or retire, and we respect that decision.

- **Voluntary Resignation:** Members can choose to retire at any time, transitioning to an emeritus or inactive role while remaining part of our community.
- **Inactivity:** Members who are inactive for more than 12 months will transition to an inactive status. They can reactivate their membership by contacting the CFC.

Inactive members (of any type) do not have the right to vote in CFC elections and are ineligible for membership in the CFC.

## Suspension and Revocation of Membership

The CFC may suspend or revoke the membership of any member that is found to be in violation of CF policies or acting against the best interests of the CF community.

- **Suspension:** The CFC may suspend a member for up to 90 days, during which the member may not participate in CF activities or vote in CFC elections.
- **Revocation:** The CFC may act to revoke or suspend CF membership if it believes (in good faith) that the member is engaging in willful misconduct or harming the best interest of the CF and its members.

These situations will be recorded as violations of the [Code of Conduct][coc] and handled as per the [Code of Conduct Resolution process][coc-reports].

The decision to revoke or suspend membership is made by a supermajority vote of the CFC. The member in question will be notified of the decision and the reasons for it.

[cfc]: ./cf-council.md
[coc]: ../policies/code-of-conduct.md
[coc-reports]: ../policies/code-of-conduct.md#handling-reports-and-escalations
Loading