Versions Compared

Key

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

Table of Contents


Technical Advisory Council (TAC)

  1. The role of the TAC is to facilitate communication and collaboration among multiple Technical Projects. Technical oversight of each Technical Project is the responsibility of each Technical Project’s technical steering committee (or similar governance body).  The TAC will be responsible for:
    1. coordinating collaboration among Technical Projects, including development of an overall technical vision for the community;
    2. making recommendations to the Budget Committee of resource priorities for Technical Projects;
    3. electing annually a chairperson to preside over meetings, set the agenda for meetings, ensure meeting minutes are taken and who will also serve on the Governing Board as the TAC’s representative (the “TAC Representative”);
    4. creating, maintaining and amending project lifecycle procedures and processes, subject to the approval of the Governing Board; and
    5. such other matters related to the technical role of the TAC as may be communicated to the TAC by the Governing Board.
  2. The voting members of the TAC consist of:
    1. one representative appointed by each Premier Member; and
    2. one representative appointed by the technical oversight body (e.g., a technical steering committee) of each TAC Project (as defined herein).
  3. One representative of any Member may observe meetings of the TAC. Any committers from a TAC Project may observe meetings of the TAC. The TAC may change this at any point in time, including: (a) opening meetings to a broader community; (b) holding closed meetings; and (c) holding meetings open to the public.
  4. Any Technical Project can become a TAC Project through the approval of the Technical Project’s technical oversight body, the TAC (by a two-third’s vote), and the Governing Board. The TAC and the Governing Board may approve a project lifecycle policy that will address the incubation, archival and other stages of TAC Projects.
  5. The TAC representatives will elect a chair to preside over meetings, ensure minutes are taken and drive the TAC agenda with input from the TAC representatives.
  6. Only one Member that is part of a group of Related Companies (as defined in Section 9) may appoint a representative on the TAC.



TAC Principles

  1. We Are Project-Centric
  2. Projects Are Self-Governing
  3. No Kingmakers & One Size Does Not Fill All
  4. Not a Standards Body
  5. Above All We Want To Help Projects
  6. We Are An Open and Welcoming Community
  7. Projects Fit the Mission of LF Edge and Increase the Value To The Community



Members

CompanyTAC Voting Member
AMDKeesang SongArm
Tina TsouAVEVACharter CommunicationsMohammad Zebetian

Dianomic
EmersonDavid Denison
EquinixJustin DustzadehFlexnodeTarif Abboushi
Fujitsu
Huawei
IBM
Intel

Randall F Templeton Martin Kronberg

Red Hat

Anil Vishnoi

Vodafone

Guido GehlenNatalia Gorokhova

ZEDEDA, Inc.
Akraino Edge Stack (Stage 3 Project)

 Yin Ding (Google)

EdgeX Foundry (Stage 3 Project)

Brad Corrion (IOTech Systems)

Fledge (Stage 3 Project)Robert Raesemann 




Voting

In various situations, the LF Edge TAC shall hold a vote. These votes can happen on the phone, email, or via a voting service, when appropriate. TAC members can either respond "agree, yes, +1", "disagree, no, -1", or "abstain".

Per Section 8)c) of the LF Edge CharterExcept as provided in Section 16.a., decisions by vote at a meeting will require a simple majority vote, provided quorum is met. Except as provided in Section 16.a., decisions by electronic vote without a meeting will require a majority of all voting representatives.

Note, under Section 7)d): Any Technical Project can become a TAC Project through the approval of the Technical Project’s technical oversight body, the TAC (by a two-third’s vote), and the Governing Board.



Meeting Time

The TAC meets bi-weekly at 7am PT (find your local time here)



Projects

Previous TAC Calls - Meeting Slides and Recordings
01/OpenBao/0101/0403Open Horizon0409200403 2 Growth080924FIDO Device Onboard060420080923
Next Review DueProjectAcceptedLast ReviewedMaturity Level
04/29/25Akraino01/24/1905/29/24Stage 3 - Impact
10/04/24-Alvarium10/06/2110/04/23Stage 1 4 - At Large02/08/24Emeritus
-Baetyl08/05/1902/08/23Stage 1 4 - At LargeEmeritus
04/29/25EdgeLake04/29/2404/29/24Stage 1 - At Large
09/0625/2425EdgeX Foundry01/24/1909/0625/2324Stage 3 - Impact
0607/2824/2425eKuiper05/24/210607/2824/2324Stage 1 - At Large
0407/0524/2425EVE01/24/190407/0524/2324Stage 2 - Growth
04/17/25Fledge06/27/1904/17/24Stage 3 - Impact
-Home Edge01/24/1910/19/22Stage 4 - Emeritus
04/29/25InfiniEdge AI04/29/2404/29/24Stage 1 - At Large
06/04/25InstantX06/04/2406/04/24Stage 1 - At Large
11/20/25NanoMQ10/20/2311/20/24Stage 1 - At Large
11/06/25Nexoedge10/16/2311/06/24Stage 1 - At Large
-State of the Edge01/24/1912/02/20Stage 2 - Growth

Scheduled Community Presentations

If you're interested in presenting at a TAC call about your project, please refer to the LF Edge Projects, which includes instructions on how to submit a Project for TAC consideration

07/16/25Ocre07/16/2407/16/24Stage 1 - At Large
04/29/25OpenBao04/29/2404/29/24Stage 1 - At Large
04/03/25Open Horizon04/09/2004/03/24Stage 2 - Growth
09/11/25FIDO Device Onboard06/04/2009/11/24Stage 1 - At Large
-State of the Edge01/24/1912/02/20Stage 2 - Growth



Scheduled Community Presentations

If you're interested in presenting at a TAC call about your project, please refer to the LF Edge Projects, which includes instructions on how to submit a Project for TAC consideration



Previous TAC Calls - Meeting Slides and Recordings