Repository navigation
Define AF OSS tiers (naming and definitions) #10
Description
Purpose
Name and define the AF OSS adoption tiers, plus the criteria for placement and promotion between them. This anchors how every intake decision categorizes a project.
Current working model (2026-04-23 Tier Model)
| Tier | Working name | Definition | Examples |
|---|---|---|---|
| 1 | Foundation-Owned | Repo under agenticsorg; Foundation controls merge, CI, CLA |
community-projects, OIA-Model |
| 2 | Foundation-Endorsed | Repo stays with author; Foundation certifies CI, CLA, review SLA | ruflo, RuVector, RuView |
| 3 | Community-Associated | Listed in ecosystem, no guarantees (default state) | nagual-qe, agentic-qe, Video Sync, Summary Bot |
Open naming question
Proposed simplification: Owned / Endorsed / Affiliated (vs the current Foundation-Owned / Foundation-Endorsed / Community-Associated).
Also pending: a "rings of adoption" framing to remove the status-hierarchy connotation. Concentric model: inner ring (Owned) is AF at the center, outer ring (Affiliated) is AF-blessed but independent.
To decide
- Tier names: Owned / Endorsed / Affiliated, vs current names, vs rings-of-adoption framing.
- Precise definition of each tier.
- Placement criteria: how a project lands in a tier (default to repo location:
agenticsorgimplies Owned; author namespace implies Endorsed or Affiliated). - Promotion criteria: Affiliated to Endorsed adds CI + CLA + review SLA; Endorsed to Owned transfers the repo to
agenticsorg.
References
- 2026-04-23 Tier Model Diagram.
- Scope boundary: five containers (2026-05-13).
Activity
michaeloboyle commentedon Jun 3, 2026
All tiers open for discussion and renaming.
Attestation: command processed on issue #10
Attestation: command processed on issue #10
Attestation: command processed on issue #10
Attestation: command processed on issue #10
Attestation: command processed on issue #10