Completed by: Mark Riddoch, Dianomic; Robert Raesemann, Raesemann Enterprises
Submitted to TAC Mail List: 2022/07/26
Presented on TAC Weekly Call: 2022/07/27 (Meeting Recording)
Below is a self-assessment submitted by the 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 2 and Stage 3 Projects also requested to complete this section, as PLD acceptance criteria requires meeting current as well as prior stage requirements
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 | |
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 | Apache 2.0, DCO, CCA4.0 - |
Upon acceptance, At Large projects must list their status prominently on website/readme | Meets | Fledge |
Stage 1 Projects, please skip to Additional Information Requested from All Projects
Stage 3 Projects also requested to complete this section
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 | See Roadmaps for the projected feature sets. The community growth and project maturity are discussed in the goals below. |
Document that it is being used in POCs. | Meets | There have been many PoCs and commercial deployments using Fledge, some are stated publicly. Some of the PoCs can be gleaned from various public commitments and event participation, such as: Fledge has a production deployment at Fledge has two new public uses cases that have been announced in 2021 and 2022: Fledge had three public use cases fully deployed and announced in 2020.
The Fledge Growth stage announcement also outlined partner, contributor, and user activity.
|
Demonstrate a substantial ongoing flow of commits and merged contributions. | Meets | https://insights.lfx.linuxfoundation.org/projects/lfedge%2Ffledge/dashboard;quicktime=time_filter_1Y |
Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan. | Meets | We are thrilled to say Fledge's community is scaling out and up. The Fledge project is maintained under LF Edge with a single TSC, branch and roadmap. However, the marketing and use of Fledge has expanded to two new open-source communities.
|
Demonstrate evidence of, or a plan for, interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (the ability to swap components between projects). | Meets | Joint Demo with Fledge and Akraino Blueprint family and Blueprint(s) See OSDU above Outreach EVE to LF Energy PoCs Completed EdgeX South plugin and testing |
Stage 2 Projects, please skip to Additional Information Requested from All Projects
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. | ||
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). |
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) | Advance to Stage 3 |
Include a link to your project’s LFX 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. | Total commits 13.64k, 63 submitters, and 103 Repos. Significant to the community are major industries and their system integrators contributing for their operations. Sebastion (Austrian Center for Digital Production) - Neuman Aluminum Raesemann Enterprises - JEA Kapsch - BRP/Rotax RTE and Swissgrid for themselves and LF Energy Nexcom for their transportation IoT solution Teledyne/FLIR for their IIoT gateway Aveva for their PI Historian |
How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.) | Maintainers Mark Riddoch - Dianomic Bill Hunt - Dianomic ashwin@dianomic.com - Dianomic Daniel Lazaro - AVEVA Sebastian Kropatschek - Austrian Centre for Digital Production Praveen Garg - Noida Labs Massimiliano Pinto - Dianomic |
| 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.) | There have been many PoCs and several commercial deployments using Fledge; some are stated publicly. Some of the PoCs can be gleaned from various public commitments and event participation, such as: Fledge has new public use cases announced in 2021 and 2022.
Fledge had three public use cases fully deployed and announced in 2020.
The Fledge Growth stage announcement also outlined partner, contributor and user activity
|
| How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.) |
|
| 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? | Goals for 2022
|
| How can LF Edge help you achieve your upcoming goals? | Market to industrial companies the virtues of open source in general. Market the virtues of Multi-cloud, Hybrid-cloud solutions to the OT market. Cooperate with LF Energy and OSDU in marketing and messaging Bring in more edge application and industrial equipment providers as members of LF Edge |
| Do you think that your project meets the criteria for the next Stage? | Project Stages: Definitions and Expectations
|
| Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.) | Sample Project had a kiosk at IOT SWC as well as ONES NA. Also participated in the LF Edge "On the Edge" webinar series. Speakers at conferences about OSS, IoT, and IIoT such as:
Work on the LF Edge user groups creation The LF Edge White paper |
| Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available). | |
Please review, and update if needed, your Project entry on the Existing Project Taxonomy page, modifying the Last Updated / Reviewed date in the header. | |
Please share an LFX security report for your project in the last 30 days. | https://security.lfx.linuxfoundation.org/#/a092M00001JWskWQAT/overview |