charter.md

Technical Charter (the "Charter")

**for **

**FinOps Project **a Series of LF Projects, LLC

Adopted August 5, 2020

This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the FinOps** **open source project, which has been established as **FinOps Project **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.

1. Mission and Scope of the Project

   1. The mission of the Project is to support the creation of tools and specifications around cloud financial management ("FinOps") and to spread the practices of FinOps across industries.

   2. 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.

2. Technical Advisory Council

   3. The Technical Advisory Council (the "TAC") will be responsible for all technical oversight of the open source Project. From the inception of the Project until the point in time that the TAC votes to transition to an alternative membership structure (such point in time the “Transition Point”), the TAC will have ten members determined as follows:

      1. three individuals selected by vote of the Governing Board of the FinOps Foundation Fund, a directed fund of the Linux Foundation (the “Directed Fund”);

      2. up to three seats for Premier Members of the Directed Fund, with each Premier Member having the right to appoint a representative to the TAC until such point in time as there are more than three Premier Members of the Directed Fund, after which the Premier Members will nominate and elect among themselves three members of the TAC;

      3. three individuals that are FinOps Practitioners, as defined in the funding charter of the Directed Fund, selected or elected via a method to be determined by the Governing Board.

      4. the remaining number of seats to be filled in a manner as determined by the TAC.

   4. 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 TAC may choose an alternative approach for determining the voting members of the TAC, and any such alternative approach will be documented in the CONTRIBUTING file. Any meetings of the Technical Advisory Council are intended to be open to the public, and can be conducted electronically, via teleconference, or in person.

   5. TAC projects generally will involve Contributors and Committers. The TAC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented:

      4. Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project;

      5. Committers are Contributors who have earned the ability to modify ("commit") source code, documentation or other technical artifacts in a project’s repository; and

      6. 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.

   6. 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.

   7. The TAC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Contributors to Committer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Committers, and create new roles, and publicly document any TAC roles, as it sees fit.

   8. The TAC may elect a TAC Chair, who will preside over meetings of the TAC and will serve until their resignation or replacement by the TAC.** **The TAC Chair, or any other TAC member so designated by the TAC, will serve as the primary communication contact between the Project and the Directed Fund.

   9. Responsibilities: The TAC will be responsible for all aspects of oversight relating to the Project, which may include:

      7. coordinating the technical direction of the Project;

      8. approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);

      9. organizing sub-projects and removing sub-projects;

      10. creating sub-committees or working groups to focus on cross-project technical issues and requirements;

      11. appointing representatives to work with other open source or open standards communities;

      12. establishing community norms, workflows, issuing releases, and security issue reporting policies;

      13. approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file) and coordinating with the series manager of the Project (as provided for in the Series Agreement, the "Series Manager") to resolve matters or concerns that may arise as set forth in Section 7 of this Charter;

      14. discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and

      15. coordinating any marketing, events, or communications regarding the Project.

3. TAC Voting

   10. While the Project aims to operate as a consensus-based community, if any TAC decision requires a vote to move the Project forward, the voting members of the TAC will vote on a one vote per voting member basis.

   11. Quorum for TAC meetings requires at least fifty percent of all voting members of the TAC to be present. The TAC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting.

   12. Except as provided in Section 7.c. and 8.a, decisions by vote at a meeting require a majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TAC.

   13. In the event a vote cannot be resolved by the TAC, any voting member of the TAC may refer the matter to the Series Manager for assistance in reaching a resolution.

4. Compliance with Policies

   14. This Charter is subject to the Series Agreement for the Project and the Operating Agreement of LF Projects. Contributors will comply with the policies of LF Projects as may be adopted and amended by LF Projects, including, without limitation the policies listed at https://lfprojects.org/policies/.

   15. The TAC may adopt a code of conduct ("CoC") for the Project, which is subject to approval by the Series Manager. In the event that a Project-specific CoC has not been approved, the LF Projects Code of Conduct listed at https://lfprojects.org/policies will apply for all Collaborators in the Project.

   16. When amending or adopting any policy applicable to the Project, LF Projects will publish such policy, as to be amended or adopted, on its web site at least 30 days prior to such policy taking effect; provided, however, that in the case of any amendment of the Trademark Policy or Terms of Use of LF Projects, any such amendment is effective upon publication on LF Project’s web site.

   17. All Collaborators must allow open participation from any individual or organization meeting the requirements for contributing under this Charter and any policies adopted for all Collaborators by the TAC, regardless of competitive interests. Put another way, the Project community must not seek to exclude any participant based on any criteria, requirement, or reason other than those that are reasonable and applied on a non-discriminatory basis to all Collaborators in the Project community.

   18. The Project will operate in a transparent, open, collaborative, and ethical manner at all times. The output of all Project discussions, proposals, timelines, decisions, and status should be made open and easily visible to all. Any potential violations of this requirement should be reported immediately to the Series Manager.

5. Community Assets

   19. LF Projects will hold title to all trade or service marks used by the Project ("Project Trademarks"), whether based on common law or registered rights. Project Trademarks will be transferred and assigned to LF Projects to hold on behalf of the Project. Any use of any Project Trademarks by Collaborators in the Project will be in accordance with the license from LF Projects and inure to the benefit of LF Projects.

   20. The Project will, as permitted and in accordance with such license from LF Projects, develop and own all Project GitHub and social media accounts, and domain name registrations created by the Project community.

   21. Under no circumstances will LF Projects be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt status or purpose, as applicable, of LFP, Inc. or LF Projects, LLC.

6. General Rules and Operations.

   22. The Project will:

       16. engage in the work of the Project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of LF Projects, LFP, Inc. and other partner organizations in the open source community; and

       17. respect the rights of all trademark owners, including any branding and trademark usage guidelines.

7. Intellectual Property Policy

   23. Collaborators acknowledge that the copyright in all new contributions will be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project.

   24. Except as described in Section 7.c., all contributions to the Project are subject to the following:

       18. All new inbound code contributions to the Project must be made using [the Apache License, Version 2.0, available at https://www.apache.org/licenses/LICENSE-2.0] (the "Project License").

       19. All new inbound code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TAC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license;

       20. All outbound code will be made available under the Project License.

       21. Documentation will be received and made available by the Project under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/).

       22. To the extent a contribution includes or consists of data, any rights in such data shall be made available under the [CDLA-Permissive 1.0 License].

       23. The Project may seek to integrate and contribute back to other open source projects ("Upstream Projects"). In such cases, the Project will conform to all license requirements of the Upstream Projects, including dependencies, leveraged by the Project. Upstream Project code contributions not stored within the Project’s main code repository will comply with the contribution process and license terms for the applicable Upstream Project.

   25. The TAC may approve the use of an alternative license or licenses for inbound or outbound contributions on an exception basis. To request an exception, please describe the contribution, the alternative open source license(s), and the justification for using an alternative open source license for the Project. License exceptions must be approved by a two-thirds vote of the entire TAC.

   26. Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file.

8. Amendments

   27. This charter may be amended by a two-thirds vote of the entire TAC and is subject to approval by LF Projects.