@Andrew Wilkinson

@Ricardo Noriega De Soto

Red Hat

@Cindy Xing

@Rong Huang

China Unicom

@Chaoyu Zhang

@Srinivasa Addepalli

@Kuralamudhan Ramakrishnan (Deactivated)

Intel

@Jeff Brower

@Sukhdev Kapur @Tina Tsou (Deactivated)proxy

Juniper

@khemendra kumar

@thorking

InwinStack

@Mark Shan

@Peiying Huang

@Tide Wang

Phytium

@Ming Li

@Tina Tsou (Deactivated)

Arm

@Oleg Berzin

@Tina Tsou (Deactivated) proxy

@xinhuili

Salesforce

@Paul Carver

@Yanjun Chen

China Mobile Research Institute

@Peter Pouliot

Certification Program Overview

Overview of the different types of certification programs we have seen set up, including typical components (e.g. T&C, Agreement) and structure (WG).

Typical process:

-- establish what it means to be conformant

-- define a series of tests that user can run/submit to demonstrate conformance (can be self-tests)

Typical starting points:

-- Set up a conformance/certification working group

-- Have WG first focus on what are the things that we're wanting to have as categories of conformance (e.g. focused on a redistribution, plugins, compatible tools, etc.)

Votes on election topics

Voter Roll (proposed)

Bylaw Interpretation 

Email (proposed)

MyProfile page on LF

Brief Introduction about Arm CIs in open source communities and OpenLab

@Zhenyu Zheng

https://kunpengcompute.github.io/arm-landscape/

https://openlabtesting.org/

• API Sub-committee - Jeff Brower, Jane Shen (Co-Chair)

• CI, Blueprint Validation Lab sub-committee - Peter Pouliot, Robert Qiu (Co-Chair), Lincoln Lavoie (Lab Manager)

• Community Sub-committee – Ike Alisson

• Documentation Sub-committee - Ike Alisson

• Process, Project review – Biswajit De

• Security Sub-committee – Randy Stricklin (Chair)

• Technical Community - Doug Eng

• Upstream Sub-committee – Jim Xu, Swarup Nayak