Attendees & Representation

TAC Members and Project representatives should mark their attendance below 

Agenda

• Check Action Items & Topic Requests (Backlog)

• Duranta Candidate Review

• Community Elections

  • Introducing new TAC Members

• Community Technical Events

• Planning discussion

  • RAN

  • AI

  • Security

• Any Other Topics

Duranta Update

Sagar provided an update on the Duranta project, which aims to host the OpenAirInterface (OAI) RAN and UE codebase. Key points include:

• License Transition:

  • Successfully completed license change on March 27th from OAI Public License 1.1 to a more generic version

  • Main source code now uses CSSL (Collaborative Standard Software License, similar to Apache 2)

  • Documentation uses CC BY 4.0, orchestration uses MIT license

  • Corporate CLA finalized; individual CLA and Easy CLA integration still pending

• Code Migration:

  • Target date: mid-May (subject to potential technical charter changes)

  • Will include complete RAN stack (CU, DU), UE stack, and supporting components

  • OAI GitLab repository will become a mirror only; all development will occur in Duranta GitHub repo

• Current Status:

  • TSC meetings held weekly (Tuesdays) with 3-4 regular attendees

  • First pre-release demo completed at ORAN face-to-face meeting in February

  • Currently being used in Open6G hackathon with 30-40+ PhD students

  • Development continues in OAI repository until migration

• Next Steps:

  • Release source code to Duranta GitHub repository

  • Migrate Jenkins CI from GitLab to GitHub

  • Add appropriate CI tests for sandbox and candidate stages (including OpenSSF badging)

Doug clarified that OAI will become a contributor within Duranta rather than maintaining a separate project, with OAI continuing CICD activities and serving as initial committer leaders.

There was a discussion about maintainers and committers focused on clarifying roles and governance:

• Role Clarification:

  • Sagar distinguished between contributors (who create and submit code) and committers/maintainers (who review and approve pull requests to the main branch)

  • Tony emphasized that committers serve as quality gates, verifying code standards and ensuring code fits within the framework

• Governance Recommendations:

  • Olaf suggested adding a governance.md file to precisely define roles and responsibilities, beyond the existing contributing.md

  • Muddasar recommended establishing three key objectives in governance documentation:

    • Quality assurance: Separate entities for code production vs. review

    • Review process: Formal sign-off procedures before code enters main branch

    • Traceability: Maintaining logs and artifacts for forensic purposes

• Best Practices:

  • Tony suggested disallowing self-committing (contributors cannot approve their own code)

  • Muddasar recommended Sagar review Tony's checklist and bestpractices.dev for process development

  • Doug confirmed the TSC will determine committers, initially populated by experienced OAI contributors

• Current Structure:

  • Doug noted OAI has internal checks and balances, though formal documentation needs enhancement

  • The project aims to leverage Linux Foundation expertise to improve code quality, security, and diversify participation

New TAC members introductions

• @Douglas Knisely

  • Has been on the LFN board for a while

  • Over 10 years of experience making open source work, especially in areas associated with industry standards

  • Background in industry standards

  • Currently very active in ORAN Alliance and AIRAN

  • Qualcomm is ramping up engagement with open source in the networking area

  @Tony Hansen

  • 45 years with AT&T

  • Long-time software developer with security focus

  • Former committer and contributor in ONAP

  • 7-8 years on ONAP security subcommittee

  • Member of TSC for Open Source Security Foundation's best practices badge (bestpractices.dev)

  @Murat Parlakisik

  • Nearly 30 years in telecom, mostly networking

  • Experience spanning telecommunications, cloud, and AI integration

  • 5 years working on Amazon/AWS and Kubernetes

  • Contributing to open source since OpenDaylight, focusing on software-defined networking

  • Currently contributing to networking and AI-based open source communities

  @Vratko Polak

  • Attended specifically for the AI usage discussion

  • Initiated AI discussions within the FDIO project

@Matt Watkins AI and tools Discussion

• Matt Watkins from the Release Engineering team discussed AI tooling usage and policies at LF:

  Current AI Tools & Usage:

  • Team uses GitHub Copilot with access to Anthropic's Claude models (Sonnet and Opus 4.6)

  • AI significantly increases development productivity, enabling "more with less"

  • Copilot code reviews are now mandated on some GitHub organizations

  • AI catches trivial and complex mistakes before human review

  Key Challenges:

  • Human code review time is the limiting factor as AI-generated code volumes increase

  • Reviewer workload becoming harder despite improved code quality

  • Douglas raised concerns about token costs and budget constraints for projects

  Best Practices:

  • Co-authored-by strings are mandated in commits created/co-authored by AI for traceability

  • Multiple development cycles with AI occur before human review

  • AI particularly effective for generating test suites and improving code coverage

  • Tony noted AI can help achieve 100% test coverage (vs. previous 50-60% struggles)

  Policy & Legal Considerations:

  • Olaf raised questions about copyright for AI-generated code and CLA/DCO sign-offs

  • Matt acknowledged legal review of approved tools (Google Gemini, Anthropic) but needs to review latest guidance

  • Group agreed to schedule a dedicated session for deeper discussion on AI policies and project use cases

  Pricing/Access:

  • LF has enterprise subscriptions with Anthropic (recently expanded to all IT staff)

  • Access to 1 million token window models with some usage limits

  • Unclear if/when project communities will get access

Future Agenda Item-

• StratoWeave Candidate presentation/annoucement - April