Date: Fri, 29 Mar 2024 01:35:41 +0000 (UTC) Message-ID: <683106343.4023.1711676141054@a58c738ca285> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4022_417061121.1711676141054" ------=_Part_4022_417061121.1711676141054 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
These Operating Procedures sets forth the responsibilities and pro= cedures for technical contribution to, and oversight of, the ODIM open sour= ce project, which has been established as ODIM a Series of LF = Projects, LLC (the =E2=80=9CProject=E2=80=9D). LF Projects, LLC (=E2=80=9CL= F Projects=E2=80=9D) is a Delaware series limited liability co= mpany. All contributors (including committers, maintainers, and other techn= ical positions) and other participants in the Project (collect= ively, =E2=80=9CCollaborators=E2=80=9D) must comply with the t= erms of these Procedures.
The mission of the Project is to enable:
interoperability between infrastructure management products and of= ferings at the interface and data model level
coherent and consistent management of highly complex, heterogeneou= s, multi- vendor infrastructure environments
automated, efficient infrastructure deployment and operation at sc= ale, across multiple sites and geographies.
promotion, adoption and use of interfaces as the unifying approach= for management of heterogeneous compute, storage and network infrastructur= e 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 d= ocumentation, 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 =E2=80=9CTSC=E2=80=9D) will = be responsible for all technical oversight of the open source = Project.
The TSC voting members will be composed of technical representativ=
es, appointed by Participating Companies (as defined herein). Participating=
Companies may appoint one voting member to the TSC (each a =E2=80=9CTSC Member=E2=80=9D). Each Participat=
ing Company may also designate one alternate to act in place of
During the initial period of four Project releases or such other t= imeframe determined by the TSC (the =E2=80=9CInitial Period=E2= =80=9D), the number of TSC seats will be capped at a number on= e less that the number of Participating Companies at the inception of the P= roject multiplied by two (the =E2=80=9CLimit=E2=80=9D)<= span>. After the Initial Period the composition of the TSC will be as deter= mined by the TSC.
During the Initial Period, entities may become Participating Compa= nies by vote of the TSC which will base such decisions on objective and uni= form criteria intended to enable open participation, provided that the numb= er of Participating Companies may not exceed the Limit.
During or after the Initial Period the TSC may choose an alternati= ve approach for determining the composition of the TSC, and any such altern= ative approach will be documented on the Project=E2=80=99s web= site. The TSC may also raise the Limit by vote at any time. A= ny 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 Contributo= rs and Committers. The TSC may adopt or modify roles so long as the roles a= re documented on the Project=E2=80=99s web site. = Unless otherwise documented:
Contributors include anyone in the technical community that contri= butes code, documentation, or other technical artifacts to the Project;
Committers are Contributors who have earned the ability to modify = (=E2=80=9Ccommit=E2=80=9D) source code, documentation or other= technical artifacts in a project=E2=80=99s 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 wil=
l be as set forth on the Project=E2=80=99s web site
Participation in the Project through becoming a Contributor and Co= mmitter is open to anyone so long as they abide by the terms of these Proce= dures. Employment or affiliation with a Participating Company is not r= equired.
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 applica= ble, and (3) amend, adjust, refine and/or eliminate the roles of Contributo= rs, and Committers, and create new roles, and publicly document any TSC rol= es, as it sees fit.
The TSC may elect a TSC Chair, who will preside over meetings of t= he TSC and will serve until their resignation or replacement by the TSC.
Responsibilities: The TSC will be responsible for all aspects of o=
versight 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=E2= =80=99s scope);
organizing sub-projects and removing sub-projects;
creating sub-committees or working groups to focus on cross-projec= t technical issues and requirements;
appointing representatives to work with other open source or open = standards communities;
establishing community norms, workflows, issuing releases, and sec= urity issue reporting policies;
discussions, seeking consensus, and where necessary, voting on tec= hnical matters relating to the code base that affect multiple projects; and=
coordinating any marketing, events, or communications regarding th= e Project.
Definitions:
=E2=80=9CSubsidiaries=E2=80=9D 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;=
=E2=80=9CRelated Company=E2=80=9D 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 s= uch 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
=E2=80=9CRelated Companies=E2=80=9D are entities that= are each a Related Company of an entity.
=E2=80=9CParticipating Company=E2=80=9D is an entity,= including any of its Subsidiaries and Related Companies, that has the righ= t to appoint a voting member to the TSC. Organizations that are Related Com= panies will be treated as a single Participating Company.
TSC Voting
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 vot= ing members of the TSC to be present. The TSC may continue to meet if quoru= m 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 majorit= y vote of all voting members of the TSC.
In the event a vote cannot be resolved by the TSC, any voting memb= er 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 Proje= ct and the Operating Agreement of LF Projects. Contributors will comply wit= h the policies of LF Projects as may be adopted and amended by LF Projects,= including, without limitation the policies listed at https://lf= projects.org/policies/.
The TSC may adopt a code of conduct (=E2=80=9CCoC=E2=80=9D) for th= e Project, which is subject to approval by the Series Manager.= In the event that a Project-specific CoC has not been approved, the LF Pro= jects Code of Conduct listed athttps://lfprojects.org/policies will apply for = all Collaborators in the Project.
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, howeve= r, that in the case of any amendment of the Trademark Policy or Terms of Us= e of LF Projects, any such amendment is effective upon publication on LF Pr= oject=E2=80=99s web site.
All Collaborators must allow open participation from any individua= l or organization meeting the requirements for contributing under these Pro= cedures and any policies adopted for all Collaborators by the TSC, reg= ardless of competitive interests. Put another way, the Project community mu= st not seek to exclude any participant based on any criteria, requirement, = or reason other than those that are reasonable and applied on a non-discrim= inatory basis to all Collaborators in the Project community.
The Project will operate in a transparent, open, collaborative, an= d ethical manner at all times. The output of all Project discussions, propo= sals, timelines, decisions, and status should be made open and easily visib= le to all. Any potential violations of this requirement should be reported = immediately to the Series Manager.
Community Assets
LF Projects will hold title to all trade or service marks used by = the Project (=E2=80=9CProject Trademarks=E2=80=9D), whether ba= sed on common law or registered rights. Project Trademarks wil= l be transferred and assigned to LF Projects to hold on behalf of the Proje= ct. 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 acco= unts, 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 th= e 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 consist= ent with maintaining a cohesive community, while also maintaining the goodw= ill 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 contributi= ons will be retained by the copyright holder as independent works of author= ship 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 Proj= ect are subject to the following:
All new inbound code contributions to the Project must be made usi= ng the Apache License, Version 2.0, available athttps://www.apache.org/licenses/LIC= ENSE-2.0 (the =E2=80=9CProject License=E2=80=9D).= p>
All new inbound code contributions must also be accompanied by a D= eveloper Certificate of Origin (http://developercertificate.org) sign-off in= the source code system that is submitted through a TSC-approved contributi= on process which will bind the authorized contributor and, if not self-empl= oyed, 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 u= nder 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 rig= hts in such data shall be made available under the CDLA-Permissive 1.0 Lice= nse.
The Project may seek to integrate and contribute back to other ope= n source projects (=E2=80=9CUpstream Projects=E2=80=9D). In su= ch 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=E2=80=99s main code repository will comply with the contribution process and license terms for th= e 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 li= cense(s), and the justification for using an alternative open source licens= e 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 per= taining to the file.
Amendments
These procedures may be amended by a two-thirds vote of the entire= TSC.