Support-tier vocabulary: release pages use five values, the Board Support Rules define four different ones
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- ドキュメント
- 明瞭さ
- おおむね明確
- 活発さ
- 静か
- 技術スタック
- markdown
調査の方向性
Read the Board Support Rules and the homepage’s “Which hardware is supported?” section, then compare their labels with the “Board status changes” sections in docs/releases/*.md. The issue also points to scripts/generate-release-doc.py in armbian/armbian.github.io for how release labels are produced. Done means the open vocabulary questions have human decisions and the homepage explanation matches the agreed terminology.
索引モデルが issue の本文から書いたものです。
説明
Blocking a homepage cleanup: the homepage explains three support tiers, generated release pages emit five different labels, and User-Guide_Board-Support-Rules.md — the source of truth — defines a fourth set. A reader who lands on /releases/26.8/ and sees
panther-x2: Standard support → EOS
has no way to map that onto the three buttons the homepage explains.
I stopped rather than invent definitions, per the brief. This needs a human decision before the homepage section can be rewritten.
Every distinct value found in generated release pages
From the "Board status changes" section of docs/releases/*.md (25.2 → 26.8). The generator (scripts/generate-release-doc.py in armbian/armbian.github.io) derives these from the config/boards/<board>.<ext> file extension in armbian/build:
| Label rendered | config/boards extension |
Boards on that extension today (armbian/build@79a3cc4) |
Defined in Board Support Rules? |
|---|---|---|---|
Standard support |
.conf |
142 | ✅ Yes — "Standard Support" |
CSC |
.csc |
216 | ⚠️ Only historically — named as a former status folded into "Community maintained" |
EOS |
.eos |
31 | ⚠️ Only historically — same sentence |
WIP |
.wip |
0 | ⚠️ Indirectly — the page calls this tier "Staging" and mentions WIP only in prose |
TV box |
.tvb |
14 | ❌ Not defined anywhere. The FAQ discusses TV boxes, but not as a support tier |
The three vocabularies, side by side
Homepage (/) |
Board Support Rules | Generated release pages |
|---|---|---|
| Platinum Support | Platinum Support | (never appears) |
| Standard Support | Standard Support | Standard support |
| Community maintained | Community maintained | CSC, EOS |
| (absent) | Staging | WIP |
| (absent) | (absent) | TV box |
What needs deciding
TV box/.tvbhas no definition at all. Is it a support tier, or a hardware category that happens to share the extension slot? Either it gets a section in the Board Support Rules, or the release generator should stop rendering it as a tier.CSCandEOSare live values, not historical ones. The Rules page says "Community maintained ... represents combined former CSC ... and EOS", butarmbian/buildstill has 216.cscand 31.eosboard files and the generator still emits both labels distinctly. Either the Rules page is out of date, or the generator should collapse both to "Community maintained".WIPvsStaging. Same tier, two names. Pick one for both places.Platinum Supportappears on the homepage and in the Rules but has noconfig/boardsextension, so it can never show up in a release page. Worth saying so explicitly on the homepage.
Once decided
The homepage "Which hardware is supported?" section should be updated to match the Rules page and cross-link to it, so the release pages' vocabulary is reachable from the tier explanation. That is a small follow-up PR — it just needs the answers above first.
/cc @armbian/documentation
- 主要言語
- Python
- スター
- 237
- フォーク
- 210
- 平均マージ
- 2時間 58分
- マージ済み PR(30日)
- 117
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
armbian/documentation のほかの issue
-
document bootscript templating対応中かも @swastiktawate が 3 日前に担当しました。 オープン
難易度 3/5 1〜2日 初心者へのやさしさ 20/100
armbian/documentation#844 ·
メンテナーはふだん 1 日以内に返信
-
document how to run a quick test via qemu / incus対応中かも @swastiktawate が 3 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 38/100
armbian/documentation#661 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
armbian/documentation の issue をすべて見る
似ている issue
-
hive size:simple
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
jxxghp/MoviePilot#7531 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
marimo-team/marimo#12027 ·
メンテナーはふだん 1 日以内に返信
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
painted-porch/marcus#977 ·
メンテナーはふだん 1 日以内に返信