Transcription

IEEE SA BOG Open Source Committee (OSCom)Operations ManualThis document, also referred to as the IEEE SA BOG Open Source Operations Manual, wasapproved by the IEEE Standards Association Board of Governors in November 2019.1 OSCom OrganizationOSCom is a committee authorized by the IEEE Standards Association (IEEE SA) Board ofGovernors (BOG) to provide guidance, oversight, and life-cycle management support for IEEEOpen Source Projects, including IEEE Open Source Projects incorporated into IEEE standards.OSCom operates in an open, transparent, and community-driven fashion. OSCom works incooperation with the IEEE Open Source Community Manager and IEEE staff who establishdetailed operations and maintenance policies and procedures for the IEEE Open Source Platformand IEEE Open Source Projects.This Operations Manual sets forth the policies and procedures for OSCom activities and oversightof IEEE Open Source activities.1.1 OSCom ResponsibilitiesOSCom shall be responsible for the following: Approving Official IEEE Open Source Project activity; Developing and maintaining this Operations Manual; Reviewing and recommending updates to the Terms of Use for the IEEE Open SourcePlatform; Reviewing and approving a Maintainers Manual providing policies, technicalrequirements, and procedures for the use of Contributors, Project leads, maintainers, andother volunteers involved in IEEE Open Source Projects; Advising and assisting the IEEE Open Source Community Manager and IEEE staff insupporting IEEE Open Source Projects and the IEEE Open Source Platform; Serving as a mandatory coordination body to the IEEE SA Standards Board (SASB) tosupport governance of IEEE Open Source Projects incorporated into IEEE standards; Coordinating with the IEEE Technical Activities Board (TAB), and other IEEEorganizational units, to support governance of more general IEEE Open Source Projects; Supporting the IEEE SA’s marketing and business plans surrounding its Open Sourceofferings as determined by the IEEE SA BOG Focus Area for Market Incubation andBusiness Acceleration.1.2 Organization and MembershipOSCom shall have a Chair, Vice Chair, and at least three other members to serve for a term of oneyear, or until replaced. All members shall be members of IEEE SA and IEEE. Officers andmembers may serve for no more than three consecutive terms. All members are appointed by theIEEE SA BOG.Page 1of 10

In addition, the Open Source Community Manager, or another IEEE staff member as designatedby the Managing Director of Standards, shall serve, ex officio without vote, as the Secretary.1.2.1 OSCom ChairThe OSCom Chair is designated by the IEEE SA President from the appointed members.Responsibilities of the OSCom Chair or designee shall include: Establishing and maintaining OSCom policies and procedures; Setting agendas and chairing meetings; Representing OSCom for the purpose of reporting to the IEEE SA BOG or collaboratingwith the SASB, TAB, and other IEEE organizations.1.2.2 OSCom Vice ChairThe committee shall elect the Vice Chair from among the members of OSCom. The Vice Chairshall fulfill responsibilities as designated by the Chair, and shall assume the duties of the Chair ifthe Chair is unavailable.1.3 Governing DocumentsOSCom is governed by the following documents listed in order of precedence:1.2.3.4.5.6.7.8.9.New York State Not-for-Profit Corporation LawIEEE Certificate of IncorporationIEEE ConstitutionIEEE BylawsIEEE PoliciesIEEE Board of Directors ResolutionsIEEE Standards Association (IEEE SA) Operations ManualIEEE SA Board of Governors ResolutionsThe OSCom Operations Manual (this document)IEEE Open Source Projects incorporated into IEEE standards are also subject to the IEEE SASBpolicies and procedures.Robert’s Rules of Order Newly Revised (RONR) is the recommended guide on questions ofparliamentary procedure not addressed in these procedures.2 IEEE Open Source ConceptsOpen Source is a digital work for which the human-readable source code is available—in thepreferred form for making modifications—for use, study, re-use, modification, enhancement, andre-distribution by the users. Open Source applies to software and hardware, which may includecomputer code, hardware designs, data, documentation, documents, and other digital objects.The IEEE Open Source Platform consists of the code and document repositories, licenserepositories, communication forums, Project management systems, and related administrative andend-user tools maintained by IEEE for the purpose of hosting Open Source Projects together withthe associated governance mechanisms, support mechanisms, and other services offered toparticipants, users, and consumers of Open Source Projects.Page 2of 10

An IEEE Open Source Project is a Project that is authorized to use the IEEE Open SourcePlatform in accordance with this Operations Manual.There are five categories of IEEE Open Source Projects:1. Individual Projects—Projects that are maintained and managed by an individual who mayaccept contributions from others.2. Group Projects—Projects maintained and managed by a group of individuals ororganizations. Such Projects will typically have multiple maintainer(s), committers, etc.3. Official IEEE Open Source Projects—Open Source Projects authorized by OSCom tocreate official IEEE Open Source Releases or products.4. IEEE Open Source Projects incorporated into IEEE standards—Official IEEE Open SourceProjects operating in conjunction with an SASB authorized standards Project.5. Joint IEEE Open Source Projects—Official IEEE Open Source Projects that are operatingin conjunction with another IEEE Board or Organizational Unit and are also subject to thepolicies and procedures of that Board or Organizational Unit.An IEEE standard incorporates Open Source if it normatively or informatively incorporates anofficial IEEE Open Source Release developed by an IEEE Open Source Project in accordance withthe PAR for that standard.An official IEEE Open Source Release is a release of an Official IEEE Open Source Project.An Open Source License is a license under which an Open Source work is released that definesthe rights third parties have to the Open Source work and the terms under which the Open Sourcework may be used.An IEEE Contributor License Agreement (CLA) is an agreement with IEEE, signed by aContributor for personal contributions or by an authorized person on behalf of an organization thatdefines intellectual property rights in contributions made by the Contributor or representatives ofthe organization.3 IEEE Open Source Roles and ResponsibilitiesThe following roles are established to engage in activities for the IEEE Open Source Platform andProjects.3.1IEEE Staff RolesThe IEEE Open Source Community Manager is an IEEE SA staff role that leads the technicalguidance and support to IEEE Open Source Projects. The IEEE Open Source Community Managercontrols the management and operation of the IEEE Open Source Platform.The IEEE Open Source Community Manager or designee shall be responsible for a MaintainersManual, approved by OSCom, which shall be hosted on the IEEE Open Source Platform as anOfficial IEEE Open Source Project.The IEEE Open Source Community Manager provides guidance (directly and through theMaintainers Manual) to parties interested in initiating and conducting IEEE Open Source Projects,on: Access to the use of the IEEE Open Source Platform;Page 3of 10

The use of tools (IEEE or not) used to develop and maintain IEEE Open Source Projects; License agreements, including Open Source licenses and Contributor licenses [inconjunction with IEEE SA Intellectual Property Rights (IPR) Manager, and IEEE Legaland Compliance]; Requirements for a complete release package, including documentation, and Security, configuration management, verification and validation, testing requirements,release, branding, and distribution processes and tools on the Platform.The Maintainers Manual shall establish criteria for the vitality of Projects and for engaging withProjects to maintain their vitality and for taking actions, which may include deprecating, archiving,and terminating Projects when they become dormant.The IEEE Open Source Community Manager supports the SASB and its committees by providingor verifying information required for the initiation, governance, and review of IEEE Open SourceProjects incorporated into IEEE standards.3.1.2 Intellectual Property Rights ManagerThe IEEE SA Intellectual Property Rights (IPR) Manager is an IEEE staff role responsible formanaging Intellectual Property (IP) matters associated with Open Source Projects.The IEEE SA IPR Manager is responsible for the following: Evaluating new Open Source licenses, in conjunction with IEEE Legal and Compliance,for acceptance by OSCom; Recommending new Open Source licenses for IEEE Open Source Projects; Coordinating with and seeking necessary approvals from IEEE SASB for updates toexisting approved CLA templates; Working with the IEEE Open Source Community Manager to verify that contributions toIEEE Open Source Projects meet IEEE intellectual property requirements, includingverification that proper CLAs are in place; Supporting the SASB and its committees by providing or verifying information requiredfor the initiation, governance, and review of Open Source licenses and IEEE Open SourceProjects incorporated into IEEE standards.3.1.3 OSCom AdministratorAn OSCom Administrator is an IEEE SA staff role that supports the operations of OSCom.3.2 IEEE Volunteer Roles3.2.1 IEEE Open Source Project LeadAn IEEE Open Source Project Lead is responsible for the vitality, organization, development,evaluation, operation, security, and maintenance of an IEEE Open Source Project. An IEEE OpenSource Project Lead is an individual, or person designated by a technical organization associatedwith the Project as the official point of communication with OSCom and the IEEE Open SourceCommunity Manager on behalf of the IEEE Open Source Project. The IEEE Open Source ProjectLead may delegate specific responsibilities to an alternate IEEE Open Source ProjectRepresentative. For IEEE Open Source Projects incorporated into IEEE standards, the IEEE OpenSource Project Lead shall be an Officer of the Standards Committee or Working Group responsiblefor the Project.Page 4of 10

3.2.2 ContributorA Contributor is any person who submits any material to an IEEE Open Source Project, whetheras an individual or on behalf of an organization. Material may include, but is not limited to, OpenSource works, comments, and marketing materials. IEEE membership is not required to be aContributor. Every Contributor is required to obtain an IEEE account that requires agreeing to theIEEE Code of Conduct. Every contribution shall be associated with the IEEE account of itsContributor.3.2.3 MaintainerA Maintainer has authority to commit (save changes) to the IEEE code and document repositoryassociated with an IEEE Open Source Project. An IEEE Open Source Project shall have at leastone Maintainer, who may be the IEEE Open Source Project Lead. Maintainers shall be familiarwith and follow the policies and procedures in the Maintainers Manual. Maintainer responsibilitiesinclude committing code, releasing code, and managing the access controls on the IEEE OpenSource Project’s repository. Maintainers may assign Committers who have the ability to commitcode to a Project. For IEEE Open Source Projects incorporated into IEEE standards, Maintainersand Committers shall be members of the Standards Committee or Working Group responsible forthe Project, or affiliated with an entity member of such Working Group. Maintainers for IEEEOpen Source Projects incorporated into IEEE standards shall also be IEEE members of any gradeand a member of IEEE SA. Maintainers for Official IEEE Open Source Projects shall be IEEEmembers of any grade.3.2.4 IEEE Open Source Project Peer ReviewersIEEE Open Source Project peer reviewers, who are familiar with an IEEE Open Source Project’sfunctions, may be invited by the OSCom Community Manager or designee to perform a codereview or evaluate the security, usability, performance, or other aspects of a planned release of anOpen Source Project that is not an IEEE Open Source Project incorporated into IEEE standards(these IEEE Open Source Projects are reviewed under the Standards Association balloting andPublic Review processes of the SASB.)4 OSCom Meetings4.1 Quarterly MeetingsThe OSCom Chair shall schedule meetings of OSCom at least quarterly by teleconference withscreen sharing capabilities or face-to-face. Meetings (except for Executive Sessions) shall be opento all. Dates for meetings shall be announced at least thirty calendar days in advance and the initialagendas should be posted at least seven calendar days in advance. Meetings for urgent purposes,including executive sessions, may be called by the OSCom Chair or designee with at least tencalendar days’ notice.In its meetings or through electronic ballot, OSCom may take the following actions: Approve or inactivate IEEE Open Source Projects (other than IEEE Open Source Projectsincorporated into IEEE standards); Approve or inactivate IEEE Open Source Projects incorporated into IEEE standards inconjunction with the SASB; Approve the initial release and subsequent major releases of the Maintainers Manual;Page 5of 10

Advise on changes to the OS Platform, its Terms of Use, or operating procedures.OSCom members shall review requests to initiate or inactivate IEEE Open Source Projects andshall have the ability to vote for or against a request. OSCom shall have at least 14 calendar daysto make comments, shared with other OSCom members, before a vote. The OSCom Chair mayextend this period.The OSCom Administrator shall take minutes of each meeting. Minutes of meetings shall bepublished to meeting participants within 30 calendar days of the end of the meeting.4.2 Executive SessionExecutive sessions shall be limited to sessions in which sensitive personnel, legal, or businessissues are discussed. The OSCom Chair may invite individuals with information germane to anexecutive session to participate in designated portions of the executive session. Persons otherwisepermitted to participate in an executive session may be removed by the committee for reasons ofconflict of interest or for other reasons determined by IEEE Legal and Compliance.4.3 Quorum and VotingA quorum is defined as 50% or greater of the OSCom members. If a quorum is not present at ameeting, actions may be taken subject to confirmation by letter or electronic ballot. Actions shallbe approved by a majority of those voting. Proxy voting is not permitted.For votes cast by electronic mail, majority consent of those participating, provided a majority ofthe voting members of the committee respond, shall be required to approve an action takenwithout a meeting. The action and written confirmations shall be filed with the minutes.5 IEEE Open Source Project ManagementThe procedures for Project approval and Open Source approval are different when the Project isan IEEE Open Source Project incorporated into IEEE standards. Management of IEEE OpenSource Projects incorporated into IEEE standards is the responsibility of the SASB, coordinatingwith OSCom for the Open Source components of the IEEE standard.5.1 Open Source Project Initiation and ApprovalAny individual or entity may request to use the IEEE Open Source platform for a purpose relatedto IEEE objectives. An organization, or group of individuals and organizations, may request to setup a group Project on the IEEE Open Source Platform by application to the IEEE Open SourceCommunity Manager. The IEEE Open Source Community Manager and IEEE SA IPR Managershall review requests and should provide feedback within ten working days. Requests for initiatingOfficial IEEE Open Source Projects are then forwarded to OSCom for review and approval, whichtakes a minimum of 14 calendar days.Pilot Projects operating on the IEEE Open Source Platform before approval of this OperationsManual do not require further OSCom approval.The IEEE Open Source Community Manager may set up space on the IEEE Open Source Platformfor the operation of a Project prior to approval of the Project by OSCom. However, the Projectmay not have official public Open Source Releases prior to OSCom approval.Page 6of 10

5.1.1 Requesting an Official IEEE Open Source ProjectAn IEEE Open Source Project seeks authorization to become an Official IEEE Open SourceProject by posting a request on the IEEE Open Source Platform. The request shall include: A title and description of the Project;The name and contact information of the IEEE Open Source Project Lead;Selection of a single Open Source license and associated CLAs;An indication of how the Project will be governed (see 5.1.2);A description of the relationship of the Project to known Open Source;Agreement to adhere to the Terms of Use for the IEEE Open Source Platform (see 6.1);An indicator of whether the IEEE Open Source Project is intended to be incorporated intoan IEEE standard associated with an IEEE SA Project Authorization Request (PAR)submitted to the New Standards Committee of the IEEE SASB (NesCom) or an existingIEEE standards Project previously approved for Open Source development. IEEE Open Source Projects incorporated into IEEE standards shall agree to anapplicable set of Terms and Conditions (T&Cs). Authorization of an IEEE Open Source Project incorporated into IEEE standards shallrequire that any associated PARs have been assigned a standards designation.5.1.2 Project GovernanceProject governance is needed to make decisions on the Project and to ensure responsibility forconformance with the IEEE Open Source Platform administrative, technical, security, andlicensing requirements. Some possible sources of IEEE Open Source Project governance are thefollowing: A single individualAn external organizationA closed set of individuals or organizationAn identified set of active Contributors, using a democratic processA subgroup of an IEEE Technical Organization, such as a Standards Committee orWorking GroupA consensus-driven process in which any materially interested party may participate A single individualAn external organizationA closed set of individuals or organizationsAn identified set of active Contributors, using a democratic processA subgroup of an IEEE Technical Organization, such as a Standards Committee orWorking GroupA consensus-driven process in which any materially interested party mayparticipateItems that shall be addressed in IEEE Open Source Project governance include, but are not limitedto, who is the Project lead; who may contribute to the Project; how merge requests are handled;how the Maintainers, Committers, and IEEE Open Source Project peer reviewers are admitted tothe Project and authorized; and how and when releases are evaluated, reviewed and agreed. Projectgovernance may include a process for external, public, or other review prior to release.Page 7of 10

The IEEE Open Source Community Manager will provide samples of governance policies andprocedures, as part of the Maintainers Manual, that can be used or adapted by IEEE Open SourceProjects. The governance policies and procedures of an Official IEEE Open Source Project shallbe publicly available.The governance of IEEE Open Source Projects incorporated into IEEE standards is detailed in theIEEE SA Standards Board Bylaws and the IEEE SA Standards Board Operations Manual andapproved policies and procedures of its Standards Committees and Working Groups.5.2 Open Source Evaluation, Approval, and Release5.2. Initial CommitAn initial commit is the process of uploading a software package for the first time to the IEEEOpen Source Platform. Initial commits for Official IEEE Open Source Projects will be reviewedfollowing Maintainers Manual guidelines.For Official IEEE Open Source Projects, peer reviewers may review the initial commit if requestedby OSCom or the IEEE Open Source Community Manager, and their feedback will be used toinform the IEEE Open Source Community Manager or designee’s decision on whether to acceptor reject an initial commit to the repository.5.2.2 Peer ReviewThe IEEE Open Source Community Manager shall develop procedures for initiating andconducting peer review as part of an Official IEEE Open Source Project and shall publish themthrough the Maintainers Manual. Peer reviewed releases or products may indicate that they havebeen peer reviewed when publicized.The peer review process for IEEE Open Source Projects incorporated into IEEE standards isperformed during the Standards Association balloting and Public Review processes of the SASB.5.2.3 Planned ReleasesAll intellectual property and Contributor License Agreement (CLA) requirements shall be metprior to initial release or planned releases where the IEEE Open Source Project’s artifacts are madepublicly available.A release is the process by which a software package is made available. An IEEE Open SourceRelease is a release that has been developed through an approved IEEE process and is publicizedas an Official IEEE Release. IEEE Open Source Releases require the approval of the Project andthe IEEE Open Source Community Manager or designee.5.3 Review of IEEE Open Source ProjectsOSCom shall periodically review Official IEEE Open Source Projects for viability, at least everythree years. OSCom may request status reports from the OSCom Administrator to assist in thisreview.5.4 Inactivation of an IEEE Open Source ProjectAn IEEE Open Source Project that does not follow its approved governance procedures may bewarned, suspended, or inactivated (terminated) by OSCom. IEEE Open Source Projects may bePage 8of 10

suspended or inactivated, for example, due to unavailability of resources, security issues, or lackof Project oversight, maintenance, or technical viability.A request to inactivate an IEEE Open Source Project may be made by the IEEE Open SourceProject Lead, IEEE technical organization overseeing the Project (such as a Standards Committeeor Working Group), OSCom member, or the IEEE Open Source Community Manager. A requestshall include reasons for inactivation and recommended disposition of the Project artifacts, as wellas the consequences of inactivation or continued availability. The inactivation request shall beforwarded to the IEEE Open Source Community Manager, IEEE SA IPR Manager, IEEE OpenSource Project Lead, related IEEE Technical Organization (as applicable), and OSCom forcomments. After comments are received, an OSCom meeting shall be held to consider inactivation,which shall require a majority of OSCom members for quorum and a majority vote of OSCom forany action to be taken. Inactivation of an IEEE Open Source Project incorporated into IEEEstandards and archiving of its software shall additionally require approval of the SASB.Open Source software artifacts of inactivated Projects may be archived (removed fromunauthorized access), or transferred to another IEEE Open Source Project or IEEE Open SourceProject incorporated into IEEE standards.6 Terms of Use and Appeals6.1 Terms of UseOSCom shall provide a set of Terms of Use for the IEEE Open Source Platform. IEEE Legal andCompliance is responsible for reviewing and approving the Terms of Use for the IEEE OpenSource Platform. All users of the IEEE Open Source Platform shall agree to and adhere to all IEEEpolicies and procedures, including but not limited to the Terms of Use for the IEEE Open SourcePlatform, the IEEE Code of Ethics and IEEE Code of Conduct (whether or not the user is an IEEEor IEEE SA member), IEEE Nondiscrimination Policy, and all applicable laws and regulations.Access privileges of any user may be suspended or removed in response to violations of any IEEEpolicies.All Committers to IEEE Open Source Projects, particularly Maintainers, shall comply with theIEEE Maintainers Manual.6.2 AppealsPersons who have directly and materially affected interests and who have been, or couldreasonably be expected to be, adversely affected by an Open Source Project within the IEEE’sjurisdiction, or by the lack of action on any part of OSCom or the IEEE Open Source CommunityManager, shall have the right to appeal procedural actions or inactions, provided that the appellantshall have first exhausted the appeals procedures of any relevant IEEE committee or bodyresponsible for the policies and procedures of the IEEE Open Source Project before filing theprocedural appeal with OSCom.OSCom shall not provide an appeals process to resolve a disagreement about a technical decision.Any person dissatisfied with a technical decision shall follow the procedures of the body that hasmade the decision to provide input on the technical decision, including, but not limited to, makinga technical comment during the applicable comment submission and/or balloting period.Page 9of 10

OSCom shall not consider any claim that (i) is based solely on ethical considerations; (ii) does notseek to amend or reverse a decision of a relevant body; or (iii) does not recommend remedial actionor recommends remedial action not allowed by current IEEE policies and procedures. Theappellant shall be advised to bring ethical claims to the attention of the IEEE Ethics and MemberConduct Committee or the IEEE SA Standards Conduct Committee, as appropriate.The OSCom Chair and Vice Chair shall act as the OSCom Appeal Officers. The OSCom Chairshall select three members of OSCom to serve as the OSCom Appeals Panel. Members of theOSCom Appeals Panel shall serve until a new OSCom Appeals Panel is appointed. The OSComChair may appoint a new member of the OSCom Appeals Panel to replace a current member whois deemed to be conflicted.The appeals procedure for OSCom shall follow the procedures found in 5.8 of the IEEE SAStandards Board Operations Manual, except applied to OSCom and the OSCom Appeal Officersand OSCom Appeals Panel as described in this clause.7 Licenses and Contributor License AgreementsAll IEEE Open Source Projects on the IEEE Open Source Platform shall provide Open Sourcesoftware or hardware subject to an IEEE approved Open Source license.All Contributors to IEEE Open Source Projects shall submit appropriate IEEE CLAs, either entityCLAs or individual CLAs, that map to the IEEE approved Open Source license. IEEE CLAs areintended to protect the interests of IEEE, support IEEE’s business models, and support IEEE OpenSource development.7.1 List of Approved Open Source Licenses and Contributor License AgreementsThe IEEE SA IPR Manager shall maintain a set of Open Source licenses and CLAs that areapproved for general IEEE Open Source Projects and shall indicate which are approved for IEEEOpen Source Projects incorporated into IEEE standards. This list and the text of the licenses andCLAs shall be made publicly available. The list shall indicate which Contributor LicenseAgreements are approved for use with each approved Open Source license.An IEEE Open Source Project may request to use a license that is not on the approved list. Anysuch license shall be submitted to the IEEE Open Source Community Manager for review by theIEEE SA IPR Manager and shall not be used until it is approved by IEEE.7.2 Identification of License and Contributor License AgreementsThe Open Source License and CLAs to be used by an IEEE Open Source Project shall be identifiedin the request for authorization. OSCom shall verify that the licenses and CLAs are on an approvedlist.7.3 Required Notifications and ApprovalsAn IEEE Open Source Project shall notify the IEEE Open Source Community Manager and IEEESA IPR Manager whenever it wishes to change the Open Source license it uses for all or some ofits Open Source software and shall not make such change until the change is approved by OSCom.Page 10of 10

Open Source is a digital work for which the human-readable source code is available—in the preferred form for making modifications—for use, study, re-use, modification, enhancement, and re-distribution by the users. Open Source