...
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 | Joe Pearson, IBM Randy Templeton, Intel Erik Nordmark, Zededa Anil Vishnoi, Red Hat |
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 |
Code repositories use Apache 2.0 Documentation uses CC-by-4.0 |
Upon acceptance, At Large projects must list their status prominently on website/readme | Meets | On https://www.lfedge.org/projects/openhorizon/
On https://github.com/open-horizon
Marketing website not yet launched, but will reference. |
...
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 | Features are released iteratively as testable units are completed. Upcoming work (Feature Requests):
Project maturity:
Community growth:
|
Document that it is being used in POCs. | Meets |
|
Demonstrate a substantial ongoing flow of commits and merged contributions. | Meets | Insights Link - opened a Jira ticket
|
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 |
|
...
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). | Needs Improvement | Link to TSC page on wiki. Current composition is:
Actively working to expand TSC voting membership outside of IBM. |
Have a documented and publicly accessible description of the project's governance, decision-making, and release processes. | Meets |
|
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 | See Insights links above. NOTE: Current Insights organization report not accurate. |
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 | See interoperability section above. |
Adopt the Foundation Code of Conduct. | Meets |
|
Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website). | Meets | Added Anylog/EdgeLake, atym.io, AgriLife (Texas A&M), ZHAW/Nephele Mainsail, Turnium, IBM, Intel, Samsung, DLR (Rhineland-Palatinate), AgriRegio Projekt, AccuKnox, mimik, Scale Computing, Boston Dynamics, Promare, Intensivate, expeer |
...
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) | We intend to advance to Stage Three when the project and our TAC Sponsors feel we're ready. At this point, the largest sticking point is increasing non-IBM contributions. Open Horizon should not be a single-source open-source project. |
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. | Insights Link |
How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.) | We feature a MAINTAINERS file in each repo, ex:
|
| 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.) | The most recent adoptions are:
|
| How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.) | Previous Goals:
|
| 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? | See the Stage Two Growth Plan above. |
| How can LF Edge help you achieve your upcoming goals? | We need some assistance with fundraising so we can offer LFX Mentorships and run hackathon events. |
| Do you think that your project meets the criteria for the next Stage? | Not quite yet. We need to diversify our TSC company representation. |
| Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.) | |
| Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available). | No |
Please review, and update if needed, your Project entry on the Existing Project Taxonomy page, modifying the Last Updated / Reviewed date in the header. | No changes needed. |
Please share a LFX security report for your project in the last 30 days |
...