...
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. | Meets | Our current TSC is comprised of members from Intel, Canonical, IOTech, Kong, HP, Beechwoods, and VMWare. For names and details see: |
Have a documented and publicly accessible description of the project's governance, decision-making, and release processes. | Meets | Matters of project governance, decision making and process are covered in our project Wiki. The following pages outline our policies. Guidance for how to submit code contributions is defined here: https://wiki.edgexfoundry.org/display/FA/Contributor%27s+Guide and here: https://wiki.edgexfoundry.org/display/FA/Contributor%27s+Process Documentation on how our release process and what gets released is here: https://wiki.edgexfoundry.org/display/FA/Release+Process and some additional information on what is considered a release artifact is defined here: https://docs.edgexfoundry.org/1.2/design/adr/devops/0007-Release-Automation/ |
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. | Meets | Work group chairs automatically have committer rights to their work group repositories and nominate others as committers as spelled out in our governance here: https://wiki.edgexfoundry.org/pages/viewpage.action?pageId=21823860#Contributors,Committers&Maintainers-NominationandApprovalofMaintainersandCommitters
|
Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects). | Meets | Integration with Akraino ELIOT blueprint (tested using UNH lab) Incubation of Open Horizon project Use of EdgeX in HomeEdge and continued support of that project Working on Fledge connectors |
Adopt the Foundation Code of Conduct. | Meets | For any significant community meeting such as the TSC meetings or meeting where we are inviting outside community to speak or observe are always preceded by the code of conduct and anti-trust policy statements. To date, we have had no unacceptable behavior incidents that the project has been made aware of. |
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. | Needs improvement | Project governance and committer process is fully documented in our Wiki, but we do not have these in markdown pages (we have 102 repositories so where to put it?). We have no list of Emeritus committers. We can look to improve this with our Hanoi Release documentation. Existing governance and contributor pages are located on this page and its subpages: https://wiki.edgexfoundry.org/display/FA/Technical+Work+in+the+EdgeX+Foundry+Project And here: https://wiki.edgexfoundry.org/display/FA/Contributor%27s+Guide |
Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website). | Needs improvement | We have a list of adopters and uses, but not on an Adopters markdown file on a repository. We do highlight adopters and commercial interests of EdgeX on our Wiki. For example, this month we have featured an adopter series of presentations on the main page of the site. We also have an "EdgeX in Market" page here: https://www.edgexfoundry.org/edgex-in-market/ We can look to improve the adoption coverage in Github with this upcoming release and add more on adopters with the upcoming Website update. |
...