...
Presented on TAC Weekly Call: 2020/08/26 (Meeting Recording)
...
| Info |
|---|
Below is a self-assessment submitted by TSC Chair/Maintainers of the Project. Comments/questions/feedback is welcome either a) in the Comments at the bottom of the page or b) during the TAC call when information is presented |
...
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 | Meets | Henry Lau (HP) & Sean McGinnis (Dell) & Joe Pearson (IBM) |
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. | Meets | 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 | Meets | Posted on our wiki at the page below. https://wiki.edgexfoundry.org/display/FA/EdgeX+Foundry+Project+Wiki |
...
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. | Meets | We maintain a roadmap for the next 2 years and have a long term backlog that extends beyond that timeframe. The next couple of releases are documented with pages in our Wiki (and you can see past release roadmaps) here: https://wiki.edgexfoundry.org/display/FA/Roadmap. Minor fixes and enhancements are also captured in issues with each repository in Github. Github tags are used to label bugs from enhancement requests and when appropriate are associated with a specific target release (see https://github.com/edgexfoundry/edgex-go/issues for an example). |
Document that it is being used in POCs. | Meets | 5 companies recently announced use of EdgeX in their products. This includes Accenture (AIP+ product), ThunderSoft (TurboX), Jaingxing Intelligence (EdgeBox), and Tibco (Project Air) & HP (Engage Edge). Many of the company presentations to the EdgeX community can be found at the wiki site below. HP's announcement is found here: https://press.hp.com/us/en/blogs/2020/hp-unveils-hp-engage-edge.html IOTech Systems also provides a commercial implementation of EdgeX called Edge Xpert and uses that is several POC and customer projects around the globe. |
Demonstrate a substantial ongoing flow of commits and merged contributions. | Meets | Recorded and reported to the EdgeX TSC monthly. Most recent report: https://wiki.edgexfoundry.org/download/attachments/329436/July2020Stats.pdf?version=1&modificationDate=1596653219339&api=v2 180+ contributors globally ~ 30 contributors monthly ~ 1 to 4 new contributors a month ~ 140 commits a month |
Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan. | Meets | 6 successful project releases since April 2017 (2 each year) On track for another release (code named Hanoi) in fall of 2020 |
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). | 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 |
...
Additional Information Requested from All Projects | Supporting Data (if needed, include links to specific examples) |
|---|---|
Intention for the upcoming year (Remain at current stage OR advance towards the next Stage) | Remain |
Include a link to your project’s CommunityBridge Insights page. We will be looking for signs of consistent or increasing contribution activity. Please feel free to add commentary to add color to the numbers and graphs we will see on Insights. | https://lfanalytics.io/projects/lfedge%2Fedgex-foundry/dashboard |
How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.) | https://wiki.edgexfoundry.org/pages/viewpage.action?pageId=21823860 WG Chair are maintainers of their respective repositories with additional rights to nominate others (which often happens). Therefore we have at least 9 maintainers. Most WG Chairs nominate several maintainers to help with the workload of the incoming code reviews. For example, the main service repository has 28 maintainers/committers (see https://github.com/orgs/edgexfoundry/teams/edgex-go-committers/members). A small effort/repository may only have a few maintainers. |
| What do you know about adoption, and how has this changed since your last review / since you joined the current Stage? If you can list companies that are end users of your project, please do so. (Feel free to link to an existing ADOPTERS file if appropriate.) | We are learning about new adopters all the time. In addition to the companies that are participating in the construction of EdgeX, the following companies have announced (and presented) on EdgeX adoption: Accenture, ThunderSoft, HP, Jaingxing Intelligence, Tibco, Certis |
| How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.) | Met or exceeded goals. Nearing 7 million container downloads. New adopter stories have been a boost to the project. Regular releases for 3+ years - indicating stability to the marketplace |
| What are the current goals of the project? For example, are you working on major new features? Or are you concentrating on adoption or documentation? | Working on Hanoi release targeted for fall 2020. Details of the release can be found here: https://wiki.edgexfoundry.org/display/FA/Hanoi+Release Outside the software itself, the project has focused on:
|
| How can LF Edge help you achieve your upcoming goals? | Slack archive and creation of new user or adopter FAQs from specific tagged Slack messages |
| Do you think that your project meets the criteria for the next Stage? | We are at stage 3 |
| Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.) | Regular participation* in Hannover Messe, IOT SWC, IOT World and LF events. Our members speak frequently in live and virtual events all over the world. We have had 2 major Hackathon events (Chicago and recently one in China). We are working with Topcoder on an additional virtual event. (*) - pre-COVID |
| Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available). | Developed after our project launched. |
...