You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Statement on Mission and Vision

The LF Edge Foundation has been formed to create a unified community for Open Source Edge that

  • fosters cross-industry collaboration across IOT, Telecom, Enterprise and Cloud ecosystems
  • enables organizations to accelerate adoption and the pace of innovation for edge computing
  • seeks to facilitate harmonization across Edge projects

The vision of LF Edge is that our software & projects will enable rapid productization of Edge platforms by supplying the necessary building blocks (and/or frameworks, reference solutions) to facilitate integration and interoperability for Edge Computing across Telecom Service Providers, Cloud Providers, IOT & Enterprises.

Driving from these principles, LF Edge has defined a set of criteria both for Projects looking to be hosted by the Foundation, as well as the levels of maturity each Project will be categorized against.

Project Induction Process

The Technical and Board governance of LF Edge have defined a policy which describes how an open source project can formally join the LF Edge Foundation, hereinafter referred to as the "Foundation", via the Project Proposal Process. It describes the Stages a project may be admitted under and what the criteria and expectations are for a given stage, as well as the acceptance criteria for a project to move from one stage to another. It also describes the Annual Review Process through which those changes will be evaluated and made.

Project progression - movement from one stage to another - allows projects to participate at the level that is most appropriate for them given where they are in their lifecycle. Regardless of stage, all Foundation projects benefit from a deepened alignment with existing projects, and access to mentorship, support, and foundation resources.

Credit: The LF Edge Project Induction Process leverages best practices set forth by the OpenJS Foundation and CNCF.

Introduction

This governance policy sets forth the proposal process for projects to be accepted into the Foundation. The process is the same for both existing projects which seek to move into the Foundation, and new projects to be formed within the Foundation.

Project Proposal Requirements

Projects must be proposed on this Wiki. Please leverage the Project Proposal Template available here, adding new proposals below this tab. A full set of instructions on how to add new Proposals have been posted here.

Note: New page creation on the LF Edge Wiki will require a LF ID. If you do not have one already, you may create one at https://identity.linuxfoundation.org/.

Project proposals submitted to the Foundation must provide the following information to the best of their ability:

  • name of project
  • project description (what it does, why it is valuable, origin and history)
  • statement on alignment with Foundation charter mission and LF Edge taxonomy
  • statement on project synergy with existing projects under LF Edge
  • link to current Code of Conduct
  • sponsor from TAC, if identified (a sponsor helps mentor projects)
  • project license
  • source control (GitHub by default)
  • issue tracker (GitHub by default)
  • external dependencies (including licenses)
  • release methodology and mechanics
  • names of initial committers, if different from those submitting proposal
  • briefly describe the project's leadership team and decision-making process
  • preferred maturity level (see Project Stages: Definitions and Expectations)
  • list of project's official communication channels (slack, irc, mailing lists)
  • link to project's website
  • links to social media accounts
  • existing financial sponsorship
  • infrastructure needs or requests
  • project logo in svg format (see https://github.com/lf-edge/lfedge-landscape#logos for guidelines)


Project Acceptance Process

  • Projects are required to present their proposal at a TAC meeting
  • The TAC may ask for changes to bring the project into better alignment with the Foundation (adding a governance document to a repository or adopting a more stringent Code of Conduct, for example).
  • The project will need to make these changes in order to progress further.
  • Projects get accepted via a 2/3 supermajority vote of the TAC and a majority vote of the Governing Board.
  • The proposal document will be finalized as a project charter. This charter document must be included in the project's main repository.
  • The TAC will determine the appropriate initial stage for the project. The project can apply for a different stage via the review process.


  • No labels