Versions Compared

Old Version 2

changes.mady.by.user Deepak Kataria

Saved on

compared with

New Version 3

changes.mady.by.user Tina Tsou

Saved on

Key

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

...

The Impact Stage is for projects that have reached their growth goals and are now on a self-sustaining cycle of development, maintenance, and long-term support. Impact Stage projects are widely used in production environments and have large, well-established project communities with a number of contributors from at least two organizations.

Project Stages Mapping: Criteria and Data

Stage 3: Impact Stage (formerly 'Top-Level')

Criteria

Data

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.


Have a documented and publicly accessible description of the project's governance, decision-making, and release processes.


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.


Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between 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.


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.




Examples

  1. Projects that have publicly documented release cycles and plans for LTS.
    1. Akraino has had one public releases to date (R1 release) with a second release (R2 targeted for November 30, 2019).  See Akraino Releases.
    2. Akraino's LTS policy is outlined here:  
  2. Projects that have themselves become platforms for other projects.
    1. Akraino is today being used in a number of proof-of-concept projects and commercial products.
    2. Some noted examples include:
  3. Projects that are able to attract a healthy number of committers on the basis of its production usefulness (not simply 'developer popularity').
    1. To date, Akraino has over X contributors; Y active contributors in the month of September 2019 alone
    2. Since Nov 1, 2018, there were almost Z commits.  Last month (August 2019), there were W commits.  These commits were made by contributors from many companies to include (list companies
  4. Projects that have several, publicly known, end-user deployments.
    1. The Akraino user community is globally diverse with contributions in September coming from the US, China, and Europe. 
    2. Provide graphic
    3. In addition to the commercial and open source products cited above, companies A, B, C and others have products or deployments under way or being developed.

...