Completed by: Trevor Conn, Dell Technologies
Submitted to TAC Mail List: YYYY/MM/DD
Presented on TAC Weekly Call: YYYY/MM/DD (Meeting Recording)
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: At Large Projects
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 | ||
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 |
Upon acceptance, At Large projects must list their status prominently on website/readme | Meets |
Stage 1 Projects, please skip to Additional Information Requested from All Projects
Stage 2: Growth Stage
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) |
|---|---|---|
| Demonstrate regular project leadership (typically TSC) meetings. Project leadership should meet monthly at a minimum unless there are extenuating circumstances (ex: holiday period) | ||
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. | ||
Document that it is being used in POCs. | ||
Demonstrate a substantial ongoing flow of commits and merged contributions. | ||
Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan. | ||
Demonstrate a willingness to work with (via interoperability, compatibility or extension) other LF Edge projects to provide a greater edge solution than what can be done by the project alone. |
Stage 2 Projects, please skip to Additional Information Requested from All Projects
Stage 3: Impact Stage
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) | ||
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. | ||
Establish a security and vulnerability process which at a minimum includes meeting ("Met" or "?") all OpenSSF best practices security questions and SECURITY.md. | ||
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
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 at current stage |
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. | |
How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.) | 5 active, all from Dell |
| 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.) | No active adoption by third parties at this time. As described to TAC, integration efforts with other LF-Edge projects are in process. |
| 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? |
|
| How can LF Edge help you achieve your upcoming goals? | When we complete the LF-Edge integrated POC, we would appreciate the opportunity to socialize our efforts through conferences, podcast, etc. |
| Do you think that your project meets the criteria for the next Stage? | No |
| 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. | |
Please share a LFX security report for your project in the last 30 days | Alvarium Security Overview |