Page tree

Versions Compared

Key

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

...

Stage 1 Criteria (from the PLD)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations

 (var)Meets

The typical IP Policy for Projects under the LF Edge Foundation is Apache 2.0 for Code Contributions, Developer Certificate of Origin (DCO) for new inbound contributions, and Creative Commons Attribution 4.0 International License for Documentation. Projects under outside licenses may still submit for consideration, subject to review/approval of the TAC and Board.

 (var) Meets

Apache 2.0, DCO, CCA4.0 - Technical Charter

Upon acceptance, At Large projects must list their status prominently on website/readme

 (var)Meets

https://www.lfedge.org/projects/fledge/

...

Stage 2 Criteria (from the PLD)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Development of a growth plan (to include both roadmap of projected feature sets as well as overall community growth/project maturity), to be done in conjunction with their project mentor(s) at the TAC.

 (var)Meets

https://wiki.edgexfoundry.org/display/FA/Roadmap + Lorem Ipsum Community Growth Plan

Document that it is being used in POCs.

 (var)Meets

Use Cases

Demonstrate a substantial ongoing flow of commits and merged contributions.

 (var)Meets

https://lfanalytics.io/projects/lfedge%2Fedgex-foundry/dashboard

Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan.

 (var)Meets

https://lfanalytics.io/projects/lfedge%2Fedgex-foundry/dashboard

Demonstrate evidence of, or a plan for, interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects).

 (var)Meets

https://wiki.edgexfoundry.org/display/FA/Open+Horizon+-+EdgeX+Project+Group

...

Criteria

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

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.

 (var)Meets

https://wiki.edgexfoundry.org/pages/viewpage.action?pageId=329436

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

 (var)Meets

https://wiki.akraino.org/display/AK/Akraino+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.

 (var)Meets

https://lfanalytics.io/projects/lfedge%2Fedgex-foundry/dashboard

Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects).

 (var)Meets

https://wiki.edgexfoundry.org/display/FA/Open+Horizon+-+EdgeX+Project+Group

Adopt the Foundation Code of Conduct.

 (var)Meets

https://lfprojects.org/policies/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.

 (var)Meets

https://wiki.akraino.org/display/AK/Akraino+Technical+Community+Document#AkrainoTechnicalCommunityDocument-3.2.2CommitterLifecycle

Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website).

 (var)Meets

https://www.edgexfoundry.org/edgex-in-market/

...