...
Completed by: @Ike Ike Alisson
Submitted to TAC Mail List: -
Presented on TAC Weekly Call: 2021/01/13 (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 | @Tina Tsou |
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 |
|
Upon acceptance, At Large projects must list their status prominently on website/readme | Meets | https://www.lfedge.org/projects/akraino/ |
...
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 | Within Akraino, there is currently
|
Document that it is being used in POCs. | Meets | Each Blueprint (Integration) project is required to submit the followng set of Documents:
|
Demonstrate a substantial ongoing flow of commits and merged contributions. | Meets | There had been 623 committs, by 62 contributors over 36 repositories. 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 | There have been more than 17.00K builds. https://insights.lfx.linuxfoundation.org/projects/lfedge%2Fakraino-edge-stack/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 | There are undertakings for high-level co-operation between Akraino ELIOT and EdgeX Foundry. There are also several cases for interaction/use of LF Edge EVE and Fledge (e.g. Akraino Blueprint IoT Camera maintenance Blueprint). Akraino API TSC Sub-committee is currently workingon assessing the room for potential co-operation among Akraino Blueprint and Development Projects as part of the Inter-operability Strategy for one of the Akraino Goals for 2021. |
...
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 for R4 with a preliminary infographic for New/Additional Rel. 4 Akraino Blueprints/Integration Projects:
|
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://insights.lfx.linuxfoundation.org/projects/lfedge%2Fakraino-edge-stack/dashboard |
How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.) | Maintainers are at Akraino Blueprint and Development project level and therein varies accordingly. |
| 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.) | This again varies among Akraino Blueprints and Development projects. |
| How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.) | The targets in terms of Blueprints evolvement/maturity via the above inidcated 4 (four phases) and adding new Blueprints/Development projects had been in line with the set for 2020 targets. |
| 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? | Teh The focus is on the coming Akraino R4 as wellas as outlining the type and use of APIs by all the Akraino Blueprints and Development Projects in order to outline a potential plan and scope for possible inter-operability among the Akraino Blueprints/Development Projects. |
| How can LF Edge help you achieve your upcoming goals? | LF Edge can provide an insight on synergy between existing Architectures e.g. 3GPP 5G SBA, ETSI MEC, TM Forum ODA LF ONAP and identify a Common Architecture Framework that all LF Edge Projects can follow and through compliance to that Common Architecture Framework achieve and inter-operatibility and scalability among the LF Edge Projects. |
| Do you think that your project meets the criteria for the next Stage? | Yes. Akraino Project is ready for Rel. 4. |
| Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.) | F2F Akraino TSC meeting in March 2020 and virtual F2F TSC Conference in September 2020 as well as participation at various Conferences as ONES and Edge Computing World and varios guest speakers from various Companies and SDOs as ETSI MEC, ETSI NFV, Verizon, Google, HPE, Telefonica. |
| Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available). | Akraino benefits from the following Getting started Project description.
https://wiki.akraino.org/display/~TapioTallgren/Getting+started+with+Akraino 2. Getting started with Akraino Project: Process, Project Review, recommend and Documentation Process, Project review and recommend sub-committee: Finalize request Templates for Blueprint and feature project, document to allow developers to get started. Develop and evolve the process by which blueprint and feature project proposals are reviewed, and ultimately approved with recommendation required documentation.Template 1 - Use case template, Template 2 - Blueprint family template, Template 3 - Blueprint species template |
...