Versions Compared

Old Version 1

changes.mady.by.user Deepak Kataria

Saved on

compared with

New Version 2

changes.mady.by.user Deepak Kataria

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Have a defined governing body of at least 5 or more members (owners and core maintainers), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer.
    • The Akraino TSC is currently made up of 15 members. The TSC Chair and Vice-Chair are elected by the TSC.
    • Representation on the TSC includes:
      • 1 from AT&T
      • 1 from ARM
  • Have a documented and publicly accessible description of the project's governance, decision-making, and release processes.
    • See various areas of the project's wiki to include
      • Charter
      • Technical Community Document
  • Have a healthy number of committers from at least two organizations. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project.
    • To date, Akraino has over X contributors; Y active contributors in the month of September 2019 alone
    • In the month of September 2019, there were almost Z commits.  These commits were made by contributors from many companies to include A, B, C
  • Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects).
    • Akraino can interoperate with EdgeX Foundry, which is the current level 3 project.
    • Akraino can also fit within other LF Edge Projects
  • Adopt the Foundation Code of Conduct.
  • Explicitly define a project governance and committer process. This is preferably laid out in a GOVERNANCE.md file and references a CONTRIBUTING.md and OWNERS.md file showing the current and emeritus committers.
    • See governance and committer process at
    • Significantly large contributions must go through the Contributors Process defined here: 
  • Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website)
  • Other metrics as defined by the applying Project during the application process in cooperation with the TAC.
  • Receive a supermajority vote from the TAC and a majority vote of the Governing Board to move to Impact stage. Projects can move directly from At Large to Impact, if they can demonstrate sufficient maturity and have met all requirements.

...