Versions Compared

Old Version 25

changes.mady.by.user Joe Pearson

Saved on

compared with

New Version 26

changes.mady.by.user Joe Pearson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

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


Features are released iteratively as testable units are completed.
Agent releases happen every Thursday.

Upcoming work:

Project maturity:

  • All Working Group Chairs will identify backup/replacement and begin training
  • All WG repos will list MAINTAINERS and keep updated
  • Add two or more project Partners this year (which will also dilute IBM's influence on the TSC)
  • Add/recruit more non-IBM Contributors to all WGs

Community growth:

  • Develop ties with Eclipse SDV, contribute code demonstrating CD/CD pipeline for workload placement decisions
  • Work with AgStack Foundation (LF Ag) on open vision models for crop ID
  • Grow ORRA by adding edge networking and security features, new use cases

Document that it is being used in POCs.

Meets

Demonstrate a substantial ongoing flow of commits and merged contributions.

Meets

Insights Link

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

Meets

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

...

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

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.


Link to TSC page on wiki.  Current composition is:

  • IBM - 5 (71%)
  • AccuKnox - 1  (14%)
  • mimik Technologies - 1 (14%)

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

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.


  • Governance - high level description of goals
  • Community - organizational structure, roles, process
  • Contributions - feature requests & lifecycle process
  • Release - feature releases & roadmap **TBD**

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.



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.

.



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


Mainsail, Turnium, IBM, Intel, Samsung, DLR (Rhineland-Palatinate), AgriRegio Projekt, AccuKnox, mimik, Scale Computing, Boston Dynamics, Promare, Intensivate, expeer

...