fep: propose sig-os and sig-riscv as planned SIGs

fep/README.md

@@ -37,6 +37,8 @@ The following areas have been identified but lack Approvers; FEPs are reviewed d
 | `sig-tools` | Planned SIG | FlagRelease |
 | `sig-edge` | Planned SIG | Edge hardware |
 | `sig-architecture` | Planned SIG | Cross-module features, process changes |
+| `sig-os` | Planned SIG | OS-level packaging, distribution integration (openKylin, openEuler) |
+| `sig-riscv` | Planned SIG | Experimental RISC-V support — compile adaptation, dependency analysis |
 | `wg-embodied` | Incubating WG | FlagOS-Robo |
 | `wg-ai4s` | Incubating WG | FlagQuantum |
 

fep/README_CN.md

@@ -35,6 +35,8 @@ FEP (FlagOS Enhancement Proposal) 是 FlagOS 的特性管理机制。每个跨
 | `sig-tools` | 规划中 SIG | FlagRelease |
 | `sig-edge` | 规划中 SIG | 端侧硬件 |
 | `sig-architecture` | 规划中 SIG | 跨模块功能、流程变更 |
+| `sig-os` | 规划中 SIG | 操作系统打包、发行版集成（openKylin、openEuler） |
+| `sig-riscv` | 规划中 SIG | RISC-V 实验性支持 — 编译适配、依赖分析 |
 | `wg-embodied` | 孵化 WG | FlagOS-Robo |
 | `wg-ai4s` | 孵化 WG | FlagQuantum |
 

sigs/README.md

@@ -33,6 +33,8 @@ The following areas have been identified as important but no Chair candidate has
 | sig-tools | [_planned/sig-tools.md](_planned/sig-tools.md) | FlagRelease has external contributors |
 | sig-edge | [_planned/sig-edge.md](_planned/sig-edge.md) | Clear contributors and users emerge on the edge side |
 | sig-architecture | [_planned/sig-architecture.md](_planned/sig-architecture.md) | Held by TSC members concurrently; no standalone SIG for now |
+| sig-os | [_planned/sig-os.md](_planned/sig-os.md) | Wave 1 unified packaging (FEP-19) lands and a Chair candidate emerges |
+| sig-riscv | [_planned/sig-riscv.md](_planned/sig-riscv.md) | `riscv64` build experiments (FEP-34) land and a Chair candidate emerges |
 
 ## SIG Creation Process
 

sigs/_planned/sig-os.md

@@ -0,0 +1,16 @@
+# sig-os: OS Integration (Planned)
+
+## Reason for Deferred Activation
+
+The unified package integration work (FEP-19, [community#19](https://github.com/flagos-ai/community/pull/19)) is in its first implementation wave; no Chair candidate or standing member roster has been identified yet.
+
+## Planned Responsibilities
+
+- OS-level packaging for FlagOS repositories: Debian `.deb`, RPM `.rpm`, and PyPI wheel channels
+- FlagOS Nexus publishing (APT / YUM repositories at `resource.flagos.net`)
+- Distribution integration through the FlagOS SIGs in distribution communities (openKylin, openEuler)
+- Per-distribution install and runtime validation beyond the baseline matrix
+
+## Current Interim Arrangement
+
+The unified package integration FEP (FEP-19) is reviewed directly by the TSC per the bootstrap note in [fep/README.md](../../fep/README.md). Per-repository packaging PRs are reviewed by each module-owning SIG.

sigs/_planned/sig-riscv.md

@@ -0,0 +1,15 @@
+# sig-riscv: RISC-V Architecture Support (Planned)
+
+## Reason for Deferred Activation
+
+The RISC-V track is explicitly experimental (FEP-34, [community#34](https://github.com/flagos-ai/community/pull/34)); contributors are emerging around vendor backends (for example SpacemiT), but no Chair candidate or standing member roster has been identified yet.
+
+## Planned Responsibilities
+
+- `riscv64` compile adaptation across the FlagOS software stack
+- Dependency analysis and trimming for RISC-V availability
+- Coordination with vendor-specific RISC-V backends (owned by module SIGs, for example SpacemiT under sig-operator) and with OS-level packaging (sig-os)
+
+## Current Interim Arrangement
+
+The experimental support FEP (FEP-34) is reviewed directly by the TSC per the bootstrap note in [fep/README.md](../../fep/README.md). Experiment results land as merged PRs in the originating Flag* repositories.