Page tree
Skip to end of metadata
Go to start of metadata



Completed by: Brett Preston, Linux Foundation

Submitted to TAC Mail List: 2020/06/22

Presented on TAC Weekly Call: 2020/07/01 (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

 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 - Technical Charter

Upon acceptance, At Large projects must list their status prominently on website/readme

 Meets

https://www.lfedge.org/projects/fledge/


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)

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

https://wiki.edgexfoundry.org/display/FA/Roadmap + Lorem Ipsum Community Growth Plan

Document that it is being used in POCs.

 Meets

Use Cases

Demonstrate a substantial ongoing flow of commits and merged contributions.

 Meets

https://lfanalytics.io/projects/lfedge%2Fedgex-foundry/dashboard

Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan.

 Meets

https://lfanalytics.io/projects/lfedge%2Fedgex-foundry/dashboard

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

https://wiki.edgexfoundry.org/display/FA/Open+Horizon+-+EdgeX+Project+Group


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), 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.

 Meets

https://wiki.edgexfoundry.org/pages/viewpage.action?pageId=329436

Have a documented and publicly accessible description of the project's governance, decision-making, and release processes.

 Meets

https://wiki.akraino.org/display/AK/Akraino+Technical+Community+Document

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

https://lfanalytics.io/projects/lfedge%2Fedgex-foundry/dashboard

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

https://wiki.edgexfoundry.org/display/FA/Open+Horizon+-+EdgeX+Project+Group

Adopt the Foundation Code of Conduct.

 Meets

https://lfprojects.org/policies/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.

 Meets

https://wiki.akraino.org/display/AK/Akraino+Technical+Community+Document#AkrainoTechnicalCommunityDocument-3.2.2CommitterLifecycle

Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website).

 Meets

https://www.edgexfoundry.org/edgex-in-market/

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

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.)

42
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.)A, B and C
How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.)Back on target. Global pandemic resulted in Release being pushed back by 1 month.
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?X, Y and Z
How can LF Edge help you achieve your upcoming goals?Are there any examples of Projects who have implemented X?
Do you think that your project meets the criteria for the next Stage?N/A
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.
Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available).Yes
  • No labels