Skip to content

Home

Jump to bottom
Ying Xie edited this page Jan 6, 2026 · 27 revisions

The sonic-mgmt repository is part of the SONiC project. This repository primarily supports:

  • SONiC testbed deployment
  • SONiC feature testing

This wiki is the central hub for documentation, ownership, and collaboration guidelines for sonic-mgmt. It is designed to help contributors, maintainers, and community members navigate the test infrastructure, contribute effectively, and stay aligned on project priorities.

Code Owners

Code ownership is tracked in the .github/CODEOWNERS file.

For new pull requests, GitHub will automatically suggest or assign reviewers based on CODEOWNERS.

📘 Responsibilities of Code Owners

  • Review pull requests
  • Triage issues

✅ Self-Assigning Ownership

Contributors, active community members, and feature experts are encouraged to self-assign as feature owners. As a feature owner, you are expected to review pull requests and triage issues promptly. The goal is to ensure timely reviews, merges, and issue resolution. Repository maintainers may adjust feature ownership as needed to maintain project health and responsiveness.

To self-assign as a code owner, submit a PR updating .github/CODEOWNERS. Having multiple owners per feature area is encouraged.

💻 PR & Issue Routing

  • PR Authors: Refer to .github/CODEOWNERS to tag appropriate reviewers if one is not auto-assigned.
  • Issue Authors: Use the CODEOWNERS file to assign owners for triage and resolution.

📘 Guidelines

SONiC Test Subgroup Meeting

Regular community meetings are held by the SONiC test subgroup to discuss test-related topics.

Meeting links and schedules are available in the SONiC Community Meeting Calendar.

To accommodate global contributors, there are two meeting series:

  • West time zone: Every 4 weeks on Wednesday, 15:00–16:00 (UTC) - Link
  • East time zone: Every 4 weeks on Wednesday, 07:00–08:00 (UTC) - Link

Meeting frequency may increase based on topics and community needs. Always check the SONiC Community Meeting Calendar for the latest schedule.

Typical meeting topics include:

  • Test plan reviews
  • Issue triage
  • PR reviews
  • Community collaboration process improvements

How to book a topic: To reserve time for a topic like test plan review or specific discussion, please email the meeting hosts in advance. Reserved topics are discussed first; remaining time can be used for issue triage or PR reviews.

Current meeting hosts:

The community is considering adding more meeting hosts in the future.

If a topic is reserved, hosts will update the table below with the scheduled topic.

Date Host Topic
2026-01-22 07:00–08:00 (UTC)
2026-01-07 15:00–16:00 (UTC) Ying Xie (yinxi@microsoft.com) Issue triage
2025-12-24 07:00–08:00 (UTC)

[Marvell] MC-LAG PTF - Discussion on bring up of MCLAG PTF, 20 min
2025-12-10 15:00–16:00 (UTC)
2025-11-26 07:00–08:00 (UTC) Roy Sror (roysr@nvidia.com)

[Marvell] MC-LAG PTF - Discussion on bring up of MCLAG PTF, 20 min
[Alibaba, Yubin Lee] - The widespread application of vSONiC in Alibaba's development/testing scenarios, 40 min
2025-11-12 15:00–16:00 (UTC) Ying Xie (yinxi@microsoft.com) Issue triage
2025-10-29 07:00–08:00 (UTC) Xin Wang (xiwang5@microsoft.com)
2025-10-15 15:00–16:00 (UTC) Cancel - many community members are at OCP.
2025-10-01 07:00–08:00 (UTC) Roy Sror (roysr@nvidia.com) Cancelled due to public holiday.
2025-09-17 15:00–16:00 (UTC)
2025-09-03 07:00–08:00 (UTC) Xin Wang (xiwang5@microsoft.com) https://github.com/sonic-net/sonic-pipelines/pull/102 by Nvidia
2025-08-20 15:00–16:00 (UTC)
2025-08-06 07:00–08:00 (UTC) Roy Sror (roysr@nvidia.com)
2025-07-23 15:00–16:00 (UTC) Cancelled
2025-07-09 07:00–08:00 (UTC) Xin Wang (xiwang5@microsoft.com) Issue triage and PR review

Meeting minutes will be sent to the mailing list sonic-test@lists.sonicfoundation.dev Please refer to SONiC Test Subgroup Mailing List for how to subscribe.

Github ID - Email

Sometimes, discussions in Issues or Pull Request comments are not sufficient, and it becomes necessary to contact community members by email for further conversation. However, finding a community member's email address can be challenging. To make this easier, the table below tracks additional information about community members, such as GitHub ID, name, email address, company, and more. Sharing information beyond your GitHub ID is completely voluntary—please feel free to update the table if you are willing to share these details with the community.

Github ID Name Email Company Extra
wangxin Xin Wang xiwang5@microsoft.com Microsoft

Clone this wiki locally