OpenAN - LFN Onboarding as Candidate Project
OpenAN onboarding status. This page tracks the end-to-end onboarding of OpenAN as an LFN candidate project, populated from the OpenAN Onboarding Status Google Doc using the LFN Candidate Project Onboarding Status Template. Audience: LFN team (internal) and OpenAN founding members (China Mobile, Huawei).
About this template. This is a proposed format for tracking the end-to-end onboarding of any new LFN candidate project. It is a subpage of the existing DRAFT - LFN Candidate Project Data Template and is intended for review and feedback before adoption as the standard.
To use it for a new project: copy this page, replace placeholders (shown in <angle brackets>), and update each item's status as the project progresses.
About the Status Field
Each action item carries a status field. The values used in this template are native Confluence status lozenges. Once Yogi Status & Dropdown is approved on the LFN tenant, each lozenge can be replaced with a Yogi dropdown (type /yogi and select Onboarding Status in place of the lozenge) so any user can change the status inline without entering edit mode.
1. Project Overview
Mission
The name of the technical Project (which shall also be used to identify the Series established hereby) is "OpenAN" and the mission of the Project is to develop a suite of open-source projects for autonomous networks. It supports the development and deployment of telecom agents, enabling multi-vendor, cross-layer, and cross-domain integration, and accelerating the evolution of autonomous networks toward L4 and L5.
High-Level Description
OpenAN is an open source, vendor-neutral multi-agent collaboration framework for autonomous networks, providing the A2A-T SDK, registry, and orchestration components that enable telecom operators and vendors to deploy and coordinate AI agents across service and network layers.
One-Sentence Pitch
OpenAN is an open, vendor-neutral framework that accelerates the deployment of end-to-end closed-loop autonomous networks through multi-agent collaboration, industry-standard interfaces, and shared telecom knowledge, with the goal of accelerating the evolution of autonomous networks toward L4 and L5.
Project Vitals
Field | Value |
|---|---|
Project Name | OpenAN |
Project Creation Date | Originally launched March 2026, MWC-Barcelona |
Project License | Apache 2.0 |
Contributing Organizations | China Mobile, Huawei，ZTE， AsiaInfo (additional partners being invited) |
Primary Collaboration Tool | Zulip (LFN standard) plus LFX Zoom |
Top Technical Body (TAC Interface) | Technical Steering Committee (TSC) |
2. Formation Documents
Standard LF formation documents. Detailed content for each document is tracked separately; this section captures status only.
LF Technical Charter
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM, LF Formation Team, and Project Founders
Next Step: OpenAN Founders confirm the latest language as of May 31, 2026. Waiting on Formation Team approval.
Links: LF Technical Charter (Google Doc)
Comments:
LF Contribution Agreement
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF Formation Team, LF TCA/PM, and Project Founders
Next Step: Awaiting LF Formation team signature as of May 29, 2026
Links: Contribution Agreement (Google Doc)
Comments:
LF Series Agreement
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF Formation Team
Next Step: Executed by LF personnel; no action required from OpenAN founders.
Links: Series Agreement (Google Doc)
Comments:
3. Domains
Choose primary domain
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM, Project Founders
Next Step: Survey available domains, confirm trademark check with LF Trademark team, and select primary.
Comments:
Register primary domain under LF ownership
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM
Next Step: Register in PCC under LF ownership once selected.
4. Schedule and Milestones
LFN TAC Meeting Schedule
Prepare TAC presentation (LFN Candidate Project Onboarding)
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: Project Founders & LF TCA/PM
Next Step: None.
Links:
Comments:
TAC meeting: candidate approval
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM and LFN TAC
Next Step: TAC has given tentative approval, waiting on Series Agreement Signature.
Comments: The LFN TAC requires a 2 week review period after a project has been submitted for approval. Please make sure that is considered for any timeline considerations.
Release Plan
Open Source release: June 2026, DTW-Copenhagen.
Launch Innovations: December 2026, TM Forum IHPP.
Commercial Verification: 2027.
Seed Code Repositories
registry-center: https://gitcode.com/OpenAN/registry-center
orchestration-center: https://gitcode.com/OpenAN/orchestration-center
a2a-t-sdk: https://gitcode.com/OpenAN/a2a-t-sdk
Aspirational Roadmap
2026.3 MWC-Barcelona | 2026.6 DTW-Copenhagen | 2026.12 TM Forum IHPP | 2027 |
|---|---|---|---|
Kickoff (Launch). China Mobile and Huawei. | Seed Code Ready and Open-Sourced. Donate to LFN. | Launch Innovations. More Contributors. | Commercial Verification. Startup Member Review. |
5. Governance Structure
LFN projects follow the standard two-tier model: LFN Governing Board plus project TSC. Projects may also establish an End User Council or Marketing Advisory Council for business and operator-side stakeholders. These advisory bodies have no governance authority over the TSC or charter.
Project Roles
Field | Value |
|---|---|
TSC | TSC Chair, TSC Co-Chair, TSC Voting Members (Maintainers plus reserved founding-member seats for the initial period), Committers, Maintainers, Contributors. |
End User Council | Operator and enterprise stakeholders. Advisory role focused on commercialization, ecosystem development, and joint LFN presence at industry events (DTW, MWC, TM Forum IHPP). No governance authority over the TSC or charter. |
Role Assignment | Defined in the Technical Charter, GOVERNING.md, and CONTRIBUTING.md. |
Role Removal | Per TSC voting procedures defined in the Technical Charter. |
Current Role Holders | To be documented in CONTRIBUTORS.md once confirmed. |
Dispute Resolution | TSC majority vote, with escalation paths per the LF Technical Charter. |
Governance Evolution | Changes to the Technical Charter approved per LF Technical Charter procedures. |
Governance Action Items
Establish initial TSC membership
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: Project Founders & LF TCA/PM
Comments: Project Founders need to submit list of names/emails to LF TCA/PM to add to the committee
Define TSC Chair and Co-Chair
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: Project Founders, TSC, and LF TCA/PM
Next Step: Elect once TSC membership is confirmed.
Comments:
Establish Project Advisory Committee
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM with Project Founders
Next Step: Project Founders need to identify initial members, and confirm operating cadence (typically quarterly).
Comments:
Set up recurring TSC meeting cadence
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM. TSC
Next Step: Schedule once TSC membership is confirmed.
Comments:
Finalize Technical Charter
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM, LFN Executive Director, Project Founders
Next Step: Circulate draft for community and LF governance structure review.
Comments:
6. Branding & Communications
Logo Design Brief
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LFN Marketing Team, LF Creative Services, Project Founders
Next Step: Update the project leads that we can proceed with existing logo
Comments:
Logo concepts from LF Creative Services
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF Creative Services, LFN Marketing Team, LF TCA/PM, Founding Members
Next Step: Logo is finalized
Comments:
Review and select final logo
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: Project Founders, LFN Marketing Team
Next Step: Logo is finalized.
Comments:
Confirm logo asset transfer / creation under LFN ownership
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro,
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF Creative Services, LFN Marketing Team, LF TCA/PM
Next Step: Logo is finalized.
Comments:
Website
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF Creative Services, LFN Marketing Team, LF TCA/PM
Next Step: Initial Draft proposed at https://github.com/project-openan/project-openan.github.io/pull/1. Circulating for Input from LF Marketing Team and Project Founders.
Comments: Site Feedback can be added to the PR or to https://docs.google.com/document/d/1gF4WiUgG-EZ5POGosAUpgzYFJaE_nNPMjTPXKqn8qkc/edit?tab=t.0
Wiki space at lf-networking.atlassian.net
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM, TSC
Next Step: Create space and seed initial pages (TSC, home, governance).
Comments:
Mailing lists via Groups.io
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM, TSC
Next Step: Mailing Lists have been created in PCC. Groups.io is working on processing the domains.
Comments:
Zulip / Chat channel and contributor invitations
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF IT, LF TCA/PM, Founding Contributors, Founding Members, TSC
Next Step: Contributors can join https://linuxfoundation.zulipchat.com and join #lfn-openan* channels.
Comments:
7. Code and Repositories
Seed code migrates to the LFN GitHub organization. CLA migrates to LFN EasyCLA. The four governance documentation files (GOVERNING.md, CONTRIBUTING.md, CONTRIBUTORS.md, Contributor Agreement / EasyCLA setup) are tracked here because they live in the repositories.
Resolve access to existing repositories
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: Project Founders
Next Step: Confirm LF PM and LF IT have access to all source repos.
Comments:
Transfer repos to LFN GitHub organization
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: Project Founders, LF IT, LF TCA/PM
Next Step: Schedule migration after Technical Charter is finalized and FOSS scan is complete.
Comments:
Add to PCC (Project Control Center)
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM
Next Step: After GitHub transfer.
Comments:
Invite Linux Foundation Org
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM
Next Step: Assign thelinuxfoundation and the assigned LF PM after GitHub Creation.
Comments:
Assign repo ownership
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF TCA/PM, TSC
Next Step: Assign initial maintainers/contributors and the assigned LF TCA/PM after GitHub transfer.
Comments:
Run LF FOSS scan on seed code
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: LF FOSS Scan Team, LF TCA/PM
Comments: Scheduled to be complete by Jun 5, 2026
Add LICENSE.md to all repos
Phase: Status & Dropdown Yogi macro
Work State: Status & Dropdown Yogi macro
Ball in Court: Status & Dropdown Yogi macro
Blocking Dependency: Status & Dropdown Yogi macro
Owner: TSC