Completed by:  Jiyong Huang, EMQ

Submitted to TAC Mail List:  YYYY/MM/DD

Presented on TAC Weekly Call:  2023/06/28 (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

Leding Li(Baidu)

jianguo zeng(Huawei)

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

website

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

See Feature Roadmap for the projected feature sets.

The community growth and project maturity are discussed in the goals below.

Document that it is being used in POCs.

Meets

Public use cases are documented on EMQ website Customer Success Stories | EMQ (emqx.com) 

Demonstrate a substantial ongoing flow of commits and merged contributions.

MeetsWe are mono-repo, here is the GitHub repo insights Pulse · lf-edge/ekuiper (github.com)

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

Meets

Exceed our expectation. Contributors doubled from last year.

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
  • EdgeX source/sink, use within EdgeX as rules engine.
  • Embed Baetyl MQTT configuration. Use within Baetyl.

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)

Advance towards the next 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.

LFX insights is setting up.

How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.)

4, from EMQ

For eKuiper, we are mono repo and do not have sub-groups. Maintainers means the people who have access rights to perform administrative functions on the eKuiper repo.

Contributors: 56 (double from last year)

Committers: 10

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

We have new adopters but not publicly available yet.




How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.)

We have four goals last year:

  1. Graduate to Stage 2 (progressing)

  2. Deliver on the 2022 Roadmap, about one release per quarter with new features. (Almost done. 4 releases with some changes of the content)

  3. Grow the number and diversity of contributors. (Done, double the contributors)

  4. Collaborate with more LF Edge projects and other open-source projects. (Done, continue to work closely with EdgeX. And new integration with EdgeWASM)

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?

We are working mainly on major new features and also try to promote adoptions.

  1. Graduate to Stage 2

  2. Deliver features regarding SQL, streaming and management. Plan and deliver v2.

  3. Grow the community with more contributors, PRs and discussions. 

  4. More documentations for use cases and scenarios.

How can LF Edge help you achieve your upcoming goals?
  • More exposure to companies globally.

  • Chances of outreach activities globally.

Do you think that your project meets the criteria for the next Stage?

See above.

Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.)

Conferences/meetups:

Jun 2022, Online, Opensource technology summit

Jun 25, 2022, Shenzhen, GIAC 

Jun, 2022, Virtual, Open Source Summit North America

EdgeX 2022 Q2 meetup

July 2022, Online, OpenInfra Dates China

Oct 2022, Online, COSCon

June 10, 2023, Shanghai, EdgeX Q2 meetup

June 17, 2023, Beijing, Smart Cloud Edge Collaboration Meetup

Seminars:

Intel AI training camp

EdgeX 2022 hackathon rules engine training

Others:

OSPP 2023

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.

Reviewed

Please share a LFX security report for your project in the last 30 days

Setting up
  • No labels