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

Compare with Current View Page History

« Previous Version 7 Next »

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 the Wiki. 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
  • 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 stages below)
  • 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.


III. Stages - Definitions & Expectations

Every Foundation project has an associated maturity level. Proposed Foundation projects should state their preferred maturity level. Projects of all maturities have access to Foundation resources.

All Foundation projects may attend TAC meetings and contribute work regardless of their stage.


At Large Projects (formerly 'Sandbox')

Definition

At Large projects are projects which the TAC believes are, or have the potential to be, important to the ecosystem of Top-Level Projects or the Edge ecosystem as a whole. They may be early-stage projects just getting started, or they may be long-established projects with minimal resource needs. The At Large stage provides a beneficial, neutral home for these projects in order to foster collaborative development and provide a path to deeper alignment with other Foundation projects via the graduation process.

Examples

  1. New projects that are designed to extend one or more Foundation projects with functionality or interoperability libraries.
  2. Independent projects that fit the Foundation mission and provide potential for a novel approach to existing functional areas (or are an attempt to meet an unfulfilled need).
  3. Projects commissioned or sanctioned by the Foundation.
  4. Any project that realistically intends to join the Foundation Growth or Impact  Level Stages in the future and wishes to lay the foundations for that transition.

Expectations

End users should evaluate At Large projects with care, as this stage does not set requirements for community size, governance, or production readiness. At Large projects will receive minimal marketing support from the Foundation. Projects will be reviewed on an annual basis; they may also request a status review by submitting a report to the TAC.

Acceptance Criteria

To be considered for the At Large Stage, the project must meet the following requirements:

  • 2 TAC sponsors to champion the project & provide mentorship as needed
  • A presentation at an upcoming  meeting of the TAC
  • Adherence to the Foundation IP Policy
  • Upon acceptance, At Large projects must list their status prominently on website/readme


  • No labels