...
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 | Henry Lau (HP), Joe Pearson (IBM), Trevor Conn (Dell), Leding Li (Baidu), and Peter Moonki (Samsung) | |
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. | EdgeX is an Apache 2.0 license project. We require all contributions comply with this license agreement as stated in our Wiki below. https://wiki.edgexfoundry.org/pages/viewpage.action?pageId=21823866 Our TSC recently added a policy recently to review new libs, modules, etc. brought into the project to insure anything we use (or is used indirectly by modules we bring in) is compliant with this license. https://wiki.edgexfoundry.org/display/FA/Vetting+Process+for+3rd+Party+Dependencies We also conduct code scans regularly (with each PR) for any license compliance issues. | |
Upon acceptance, At Large projects must list their status prominently on website/readme | Posted on our wiki at the page below. https://wiki.edgexfoundry.org/display/FA/EdgeX+Foundry+Project+Wiki |
...
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. | Our current TSC is comprised of members from Intel, Canonical, IOTech, 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. | 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. | 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). |
| |
Adopt the Foundation Code of Conduct. | 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. | Project Examples of these documents can be found in our main repository https://github.com/edgexfoundry/edgex-go Additionally, 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 | |
Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website). | We have a list of adopters and uses, but not on an Adopters markdown file on a repository. We do highlight Our main repository contains the Adopter document (see https://github.com/edgexfoundry/edgex-go/blob/main/ADOPTERS.md) We also highlight user, 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:Website. edgexin-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. |
Additional Information Requested from All Projects
...