FRRouting Project Charter

THE LINUX FOUNDATION

Effective : April 3, 2017

This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the FRRouting Project (the “Project”) within The Linux Foundation. Contributors to the Project must comply with the terms of the Charter as well as any applicable policies of The Linux Foundation.

  1. Mission of the Project

    1. Advance, develop and support routing software that provides a suite of IP based routing and other control plane protocols.; and

    2. Host the technical governance of the Project.

  2. Technical Steering Committee

    1. The Technical Steering Committee (the “TSC”) shall be responsible for technical oversight of the Project.

    2. The Technical Steering Committee voting members shall consist of the Project’s Maintainers. At the inception of the project, the Maintainers of the Project will be published on the Project website frrouting.org.

    3. Technical Steering Committee meetings are intended to be open to the public, and can be conducted electronically, via teleconference, or in person.

    4. TSC projects generally will involve Contributors, Committers, and Maintainers:

      1. Contributors: anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project codebase.

      2. Committers: Contributors who have the ability to commit directly to a project’s main branch or other release branch of the Project’s repository.

      3. Maintainer: each lead developer on a project or system identified by the TSC. Each Maintainer shall also serve as the project or system’s representative on the TSC;

    5. Participation in the Project through becoming a Contributor, Committer, and/or Maintainer is open to all under the terms of this Charter.

    6. 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 and Committers to Committer and Maintainer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, Committers, and Maintainers, and create new roles, and publicly document any TSC roles, as it sees fit.

    7. The TSC shall elect a TSC Chair according to rules established by the TSC, who will preside over meetings of the TSC.

    8. Responsibilities: The TSC shall also be responsible for:

      1. coordinating the technical direction of the Project;

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

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

      4. communicating with external and industry organizations concerning Project technical matters;

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

      6. establishing community norms, workflows, or policies including processes for contributing (to be published on the Project website), issuing releases, and security issue reporting policies;

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

      8. coordinate any marketing, events, or communications with The Linux Foundation.

  3. TSC Voting

    1. While it is the goal of the Project to operate as a consensus based community, if any TSC decision requires a vote to move forward, the Maintainers shall vote on a one vote per Maintainer basis.

    2. Quorum for TSC meetings shall require two-thirds of all Maintainers. The TSC may continue to meet if quorum is not met, but shall be prevented from making any decisions at the meeting.

    3. Except as provided in Section 8.2.4 and 9.1, decisions by vote at a meeting shall require a two-thirds majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting shall require a two-thirds majority of all Maintainers.

    4. In the event a vote cannot be resolved by the TSC, any Maintainer shall be entitled to refer the matter to The Linux Foundation for assistance in reaching a decision.

  4. Antitrust Guidelines

    1. All participants in the Project shall abide by The Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy.

    2. All participants shall encourage open participation from any organization able to meet the participation requirements, regardless of competitive interests. Put another way, the community shall not seek to exclude any participant based on any criteria, requirements, or reasons other than those that are reasonable and applied on a non-discriminatory basis to all participants.

  5. Code of Conduct

    1. The TSC shall adopt a fair, reasonable, and non-discriminatory Project code-of-conduct, with approval from The Linux Foundation as outlined below.

    2. The Project will operate in a transparent, open, collaborative, and ethical manner at all times.

    3. The output of all Project discussions, proposals, timelines, decisions, and status will be made public and easily visible to all.

  6. Budget and Funding

    1. The TSC shall coordinate any budget or funding needs with The Linux Foundation. Organizations participating may be solicited to sponsor Project activities and infrastructure needs on a voluntary basis.

    2. The Linux Foundation shall have custody of and final authority over the usage of any fees, funds, and other cash receipts.

    3. Initially, the Project will not raise any funds and will be supported on a volunteer basis by the Project participants. In the event the Project does decide to solicit funding or more than one Project participant provides funding, a General & Administrative (G&A) fee will be applied by The Linux Foundation to any funds raised by the Project. The G&A fee shall equal 9% of the Project’s first $1,000,000 of gross receipts and 6% of the Project’s gross receipts over $1,000,000. For the purposes of clarity, contributions to the Project of IP, personnel, time, and infrastructure are not subject to the G&A fee.

    4. Under no circumstances shall The Linux Foundation be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt purpose of The Linux Foundation.

  7. General Rules and Operations. The Project shall be conducted so as to:

    1. 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 The Linux Foundation in the open source software community;

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

    3. subject to available funds, engage The Linux Foundation for all Project press and analyst relations activities;

    4. upon request, provide information regarding Project participation, including information regarding attendance at Project-sponsored events, to The Linux Foundation; and

    5. coordinate with The Linux Foundation in relation to any websites created directly for the Project.

  8. Intellectual Property Policy

    1. The Project seeks to integrate and contribute back to other open source projects within the mission set forth in Section 1 above. Based on this goal for the Project, the development community will:

      1. conform to all license requirements of the open source projects leveraged by the Project (such projects, collectively, “Upstream Projects”); and

      2. maximize opportunities for compatibility with other projects that might be leveraged by the Project.

    2. Except as described in Section 8.3, all code contributions to the Project are subject to the following:

      1. All new inbound code contributions must also be accompanied by a Developer Certificate of Origin sign-off (http://developercertificate.org) that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the licenses expressly granted in the file only with respect to such contribution, with no limitation, estoppel, or effect on any other member of the Project;

      2. All outbound code will be made available under the GNU General Public License version 2 available at https://www.gnu.org/licenses/gpl-2.0.html.

      3. Contributed 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/).

      4. The TSC may approve the use of an alternative license for inbound or outbound contributions on an exception basis. To request an exception, please email dev@lists.frrouting.org describing the contribution, the alternative open source license(s), and the justification for inclusion in the Project. Exceptions shall only be approved by a three-quarters vote of the entire TSC.

    3. Upstream Project code contributions not stored within the Project’s main code repository shall comply with the contribution process and license terms for the applicable Upstream Project.

    4. Subject to available funds, the Project may engage The Linux Foundation to determine the availability of, and register, trademarks, service marks, which shall be owned by The Linux Foundation. Any Project-related domain names and trademarks will be owned by The Linux Foundation and any pre-existing Project-related domain names or trademarks shall be transferred to The Linux Foundation.

  9. Amendments

    1. This charter may be amended by a three-quarters vote of the entire TSC, subject to approval by The Linux Foundation.