Skip to content

README.md

Latest commit

 

History

History
93 lines (69 loc) · 5.23 KB

README.md

File metadata and controls

93 lines (69 loc) · 5.23 KB
Raw

FlagOS SIG Overview

Bootstrap Phase SIGs (7)

SIG Modules Layer Meetings
sig-operator FlagGems, FlagAttention, FlagFFT, FlagSparse, FlagDNN, FlagBLAS, FlagTensor, FlagAudio L1 TBD
sig-compiler FlagTree L0 TBD
sig-network FlagCX L0 TBD
sig-framework PyTorch-Plugin-FL, vllm-plugin-FL, sglang-plugin-FL, TransformerEngine-FL, Megatron-LM-FL, verl-FL L2 TBD
sig-training FlagScale L3 TBD
sig-kernelgen KernelGen, KernelGenBench L3 TBD
sig-chip Datacenter chip adaptation (NVIDIA, Hygon, Iluvatar, MetaX, and 9 others — 13 total) — TBD

Incubating Working Groups (2)

WG Focus Area Promotion Criteria
wg-embodied Robotics ≥3 active Contributors + ≥1 demonstrable scenario
wg-ai4s AI for Science / Quantum Computing ≥3 active Contributors + paper or demo

Planned SIGs

The following areas have been identified as important but no Chair candidate has been found yet. They will be activated when conditions are met.

Area Charter Draft Activation Criteria
sig-benchmark _planned/sig-benchmark.md ≥2 people dedicated full-time to benchmark output
sig-documentation _planned/sig-documentation.md Docs virtual team delivers Getting Started + API Ref
sig-user-ecosystem _planned/sig-user-ecosystem.md GitHub Discussions MAU ≥50, external contributors ≥10
sig-release _planned/sig-release.md Release cadence increases, requiring a standing body
sig-agent _planned/sig-agent.md Skills module attracts active external contributors
sig-tools _planned/sig-tools.md FlagRelease has external contributors
sig-edge _planned/sig-edge.md Clear contributors and users emerge on the edge side
sig-architecture _planned/sig-architecture.md Held by TSC members concurrently; no standalone SIG for now
sig-os _planned/sig-os.md Wave 1 unified packaging (FEP-19) lands and a Chair candidate emerges
sig-riscv _planned/sig-riscv.md riscv64 build experiments (FEP-34) land and a Chair candidate emerges

SIG Creation Process

  1. Proposer submits a Charter draft + initial member list to TSC (PR to community repo)
  2. TSC votes within 2 weeks
  3. Upon approval, create directory structure, OWNERS file, and add to this index page
  4. Chair executes the SIG Launch Checklist

SIG Launch Checklist

After TSC approves a new SIG, the Chair must complete the following within 2 weeks.

GitHub

  • Create sigs/sig-xxx/ directory: README.md (Charter), OWNERS, meetings/
  • Request a SIG-specific GitHub label (sig/xxx) for tagging Issues and PRs
  • Update this page (sigs/README.md) with the SIG list and meeting calendar

Communication Channels

  • Create SIG WeChat group and set group notice (SIG name, meeting time, GitHub link)
  • If a mailing list is needed, contact TSC to create one (planned)
  • Post a SIG launch announcement in GitHub Discussions

Meetings & Recordings

  • Set a biweekly meeting time (staggered from TSC meetings), update the Meeting Calendar
  • Create a Bilibili / YouTube playlist for uploading meeting recordings
  • Publish the agenda before the first meeting (per the Meeting Operations Guide)

Community Participation

  • Chair and tech leads read the Moderation Guidelines
  • Give a SIG introduction at the next community all-hands (5-minute lightning talk)
  • Submit the first monthly brief to TSC (1 page, including meeting notes link and key progress)

Bootstrap Phase Simplification: Before the TSC is formed, the ZhongZhi FlagOS Community will assist the Chair with the checklist items involving WeChat groups, GitHub labels, Bilibili playlists, etc. GitHub label requests will be filed by TSC members on behalf of the SIG.

OWNERS Specification

Format of the OWNERS file in each SIG directory:

reviewers:
  # - sig-xxx-reviewers   ← references an alias in COMMUNITY/OWNERS_ALIASES

approvers:
  # - sig-xxx-approvers   ← references an alias in COMMUNITY/OWNERS_ALIASES

Use aliases instead of specific GitHub IDs: Each SIG's Reviewer and Approver teams are centrally defined in the community root OWNERS_ALIASES. When personnel change, only OWNERS_ALIASES needs updating — no need to modify individual module OWNERS files.

Do NOT fill OWNERS with TBD, placeholder, or unconfirmed individuals. Leave fields empty if no one is assigned.

Meeting Calendar

Time (UTC+8) Meeting Link
TBD TSC Meeting —
TBD SIG Meetings See individual SIG Charters