Skip to content

Charter.md

Latest commit

 

History

History
80 lines (61 loc) · 5.88 KB

Charter.md

File metadata and controls

80 lines (61 loc) · 5.88 KB

Technical Charter (the “Charter”) for OpenCHAMI a Series of LF Projects, LLC

1. Introduction

This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OpenCHAMI open source project, which has been established as OpenCHAMI a Series of LF Projects, LLC (the “Project”). LF Projects, LLC (“LF Projects”) is a Delaware series limited liability company. All contributors (including committers, maintainers, and other technical positions) and other participants in the Project (collectively, “Collaborators”) must comply with the terms of this Charter.

2. Mission and Scope of the Project

The mission of the Project is to steward the collaborative development and continuous evolution of cloud-like software to manage High Performance Computing capacity regardless of the size or deployment platform.

The scope of the Project includes collaborative development under the Project License (as defined herein) supporting the mission, including documentation, testing, integration, and the creation of other artifacts that aid the development, deployment, operation, or adoption of the open source project.

3. Technical Steering Committee (TSC)

The Technical Steering Committee (TSC) will be responsible for all technical oversight of the open source Project.

  • The TSC voting members are initially the Project’s Committers.
  • At the inception of the project, the Committers of the Project will be as set forth within the CONTRIBUTING file within the Project’s code repository.
  • The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the CONTRIBUTING file.
  • Any meetings of the TSC are intended to be open to the public and can be conducted electronically, via teleconference, or in person.

3.1 Roles within the TSC

TSC projects generally involve Contributors and Committers. The TSC may adopt or modify roles, documented in the CONTRIBUTING file.

  • Contributors: Anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project.
  • Committers: Contributors who have earned the ability to modify (“commit”) source code, documentation, or other technical artifacts in a project’s repository.
  • A Contributor may become a Committer by a majority approval of the existing Committers.
  • A Committer may be removed by a majority approval of the other existing Committers.

Participation in the Project through becoming a Contributor and Committer is open to anyone so long as they abide by the terms of this Charter.

3.2 Responsibilities of the TSC

The TSC will oversee all aspects of the Project, including:

  • Coordinating the technical direction of the Project.
  • Approving project or system proposals (e.g., incubation, deprecation, scope changes).
  • Organizing and removing sub-projects.
  • Creating sub-committees or working groups for cross-project issues.
  • Appointing representatives to work with other open source or open standards communities.
  • Establishing community norms, workflows, and security issue reporting policies.
  • Approving and implementing contribution policies (to be published in the CONTRIBUTING file).
  • Coordinating with the Series Manager to resolve matters as set forth in Section 7.
  • Managing project-related marketing, events, and communications.

4. TSC Voting

The Project aims to operate as a consensus-based community. If a vote is required:

  • Each TSC voting member has one vote.
  • Quorum requires at least 50% of all voting members.
  • Decisions at a meeting require a majority vote of those present, provided quorum is met.
  • Electronic votes require a majority vote of all voting members.
  • If a vote cannot be resolved, any voting TSC member may refer the matter to the Series Manager for assistance.

5. Compliance with Policies

This Charter is subject to the Series Agreement and Operating Agreement of LF Projects.

  • Contributors must comply with LF Projects’ policies: LF Projects Policies.
  • The TSC may adopt a Code of Conduct (CoC), subject to approval by the Series Manager. If not, the LF Projects CoC applies.
  • The Project must remain transparent, open, collaborative, and ethical at all times.

6. Community Assets

  • LF Projects will hold title to all trademarks used by the Project (Project Trademarks).
  • The Project will manage its own GitHub, social media accounts, and domain names.
  • LF Projects will not be expected to undertake actions that contradict its tax-exempt status.

7. General Rules and Operations

The Project will:

  • Engage professionally and maintain goodwill within the open source community.
  • Respect all trademark owners and branding guidelines.

8. Intellectual Property Policy

  • Copyright in all new contributions remains with the original author.
  • All new inbound code contributions must use the MIT License (MIT License).
  • All contributions must be accompanied by a Developer Certificate of Origin (DCO) (DCO).
  • All outbound code will be released under the MIT License.
  • Documentation will be available under Creative Commons Attribution 4.0 International License (CC-BY-4.0).
  • The Project will conform to all Upstream Project license requirements.
  • The TSC may approve license exceptions by a two-thirds vote.
  • Contributed files should use SPDX short-form identifiers for license information.

9. Amendments

This Charter may be amended by a two-thirds vote of the entire TSC, subject to LF Projects’ approval.