These Operating Procedures sets forth the responsibilities and procedures for technical contribution to, and oversight of, the ODIM open source project, which has been established as ODIM 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 these Procedures.
The mission of the Project is to enable:
interoperability between infrastructure management products and offerings at the interface and data model level
coherent and consistent management of highly complex, heterogeneous, multi- vendor infrastructure environments
automated, efficient infrastructure deployment and operation at scale, across multiple sites and geographies.
promotion, adoption and use of interfaces as the unifying approach for management of heterogeneous compute, storage and network infrastructure environments across different data center locations.
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.
Technical Steering Committee
The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project.
The TSC voting members will be composed of technical representatives, appointed by Participating Companies (as defined herein). Participating Companies may appoint one voting member to the TSC (each a “TSC Member”). Each Participating Company may also designate one alternate to act in place of each Participating Company’s primary TSC Member in the event that the primary TSC Member is unavailable. At the inception of the Project, the Participating Companies are those entities listed on the Project’s web site as such.
During the initial period of four Project releases or such other timeframe determined by the TSC (the “Initial Period”), the number of TSC seats will be capped at a number one less that the number of Participating Companies at the inception of the Project multiplied by two (the “Limit”). After the Initial Period the composition of the TSC will be as determined by the TSC.
During the Initial Period, entities may become Participating Companies by vote of the TSC which will base such decisions on objective and uniform criteria intended to enable open participation, provided that the number of Participating Companies may not exceed the Limit.
During or after the Initial Period the TSC may choose an alternative approach for determining the composition of the TSC, and any such alternative approach will be documented on the Project’s web site. The TSC may also raise the Limit by vote at any time. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person.
The Project and its sub-projects generally will involve Contributors and Committers. The TSC may adopt or modify roles so long as the roles are documented on the Project’s web site. Unless otherwise documented:
Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project;
Committers are Contributors who have earned the ability to modify (“commit”) source code, documentation or other technical artifacts in a project’s repository; and
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.
At the inception of the Project, the Committers of the Project will be as set forth on the Project’s web site.
Participation in the Project through becoming a Contributor and Committer is open to anyone so long as they abide by the terms of these Procedures. Employment or affiliation with a Participating Company is not required.
The TSC 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 TSC roles, as it sees fit.
The TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC.
Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Project, which may include:
coordinating the technical direction of the Project;
approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);
organizing sub-projects and removing sub-projects;
creating sub-committees or working groups to focus on cross-project technical issues and requirements;
appointing representatives to work with other open source or open standards communities;
establishing community norms, workflows, issuing releases, and security issue reporting policies;
discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and
coordinating any marketing, events, or communications regarding the Project.
“Subsidiaries” means any entity in which an entity owns, directly or indirectly, more than fifty percent of the voting securities or membership interests of the entity in question;
“Related Company” means any entity which controls or is controlled by an organization or which, together with an entity, is under the common control of a third party, in each case where such control results from ownership, either directly or indirectly, of more than fifty percent of the voting securities or membership interests of the entity in question; and
“Related Companies” are entities that are each a Related Company of an entity.
“Participating Company” is an entity, including any of its Subsidiaries and Related Companies, that has the right to appoint a voting member to the TSC. Organizations that are Related Companies will be treated as a single Participating Company.
While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis.
Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting. Decisions made at a meeting require a majority vote of all voting members in attendance at that meeting.
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 TSC.
In the event a vote cannot be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution.
Compliance with Policies
These procedures are 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/.
The TSC 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 athttps://lfprojects.org/policies will apply for all Collaborators in the Project.
All Collaborators must allow open participation from any individual or organization meeting the requirements for contributing under these Procedures and any policies adopted for all Collaborators by the TSC, 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.
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.
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.
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.
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.
General Rules and Operations.
The Project will:
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
respect the rights of all trademark owners, including any branding and trademark usage guidelines.
Intellectual Property Policy
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.
Except as described in Section 7.c., all contributions to the Project are subject to the following:
All new inbound code contributions to the Project must be made using the Apache License, Version 2.0, available athttps://www.apache.org/licenses/LICENSE-2.0 (the “Project License”).
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 TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license;
All outbound code will be made available under the Project License.
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/).
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.
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.
The TSC 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 TSC.
Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file.
These procedures may be amended by a two-thirds vote of the entire TSC.