Page Comparison

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.

• The Akraino project has an "upstream first" policy. All Akraino Blueprints and Feature projects that contribute to upstream projects must complete the Upstream Dependency Matrix. The tables should be completed at project induction time (for new projects) and refreshed at release time (for existing projects). As of R4 and onward (Releases), in order to build a "stable Release" is a release which Downstream and Community can rebuild after a certain long period of time), Upstream will need to specify upstream repositories completely and with corresponding version/branch information. Also Upstream & Downstream Sub-committee (renamed in 2021) recommends to use tag instead of branch if possible.The list of each Blueprint Upstream Dependendency Matrix and Upstream Project information can be viewed at: https://wiki.akraino.org/display/AK/Upstream+Dependency+Matrix+and+Upstream+Project+Information?src=contextnavpagetreemode

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

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.

Within Akraino, there is currently

• more than 20 Blueprint (Integration) Projects (https://wiki.akraino.org/display and Feture Projects together /AK/Approved+blueprints?src=contextnavpagetreemode
• 4 Blueprint proposals (https://wiki.akraino.org/display/AK/Blueprint+Proposals?src=contextnavpagetreemode
• 10 Feature (aka Development) Projects
• For any Release, BP are required to submit the following (mandatory) list of documents, namely, 1. API Document, 2. Architecture Document, 3. Datasheet (summary) Document, 4. Installation Guide Document, 5. Release notes Document, 6. Test Document.

Document that it is being used in POCs.

Each Blueprint (Integration) project is required to submit the followng set of  Documents:

1. Architecure description, 2. API description, 3. Test description, 4. Installation Guide, 5. Test description. The deployment status of the Blueprint, being PoC, Demo or Commercial is presented/indicated in the Blueprint Architecture document.

Demonstrate a substantial ongoing flow of commits and merged contributions.

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.

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