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

Compare with Current View Page History

« Previous Version 24 Next »

DRAFT - UNDER REVIEW

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
  • high level assessment of 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)
  • trademark status


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