T27-46 — Re-read the Android feasibility report and record the gate decision

オープン
  • 何か問題がありますか？
#65 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
38/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
android, rust
領域
mobile

調査の方向性

Read docs/research/android-feasibility.md against the dependency versions listed in Cargo.lock, then check the audit items in the campaign's P6 feasibility checklist. Record a dated approve or defer decision with its rationale and conditions in docs/decisions/. The work is done when the decision record exists and T27-47 is unblocked or formally closed; the issue says the ledger and execution board land with PR #12.

索引モデルが issue の本文から書いたものです。

説明

documentation release

T27 row: T27-46
Work package: RP-04 — Android feasibility spike and native port
Priority: P2
Status: READY

Objective

Re-read the Android feasibility report against the current dependency graph and record a written approve-or-defer decision, so the port is either authorized or explicitly declined on the record.

Acceptance criteria: The report is re-read against the current dependency graph and the accesskit + android-native-activity conflict is re-confirmed or resolved; a written approve/defer decision is recorded with its date, its rationale and its conditions.

Inputs

docs/research/android-feasibility.md; the current Cargo.lock (eframe 0.36.2, winit 0.30.13, android-activity 0.6.1, glow 0.17.0, glutin 0.32.3, boa_engine 0.20.0); docs/decisions/.

Authority

docs/tasks/T27-cross-platform-release.md — "Android is either verified as a real native app on an ARM64 device or explicitly deferred with a feasibility report"; the plan's non-goal that a native Android claim must not be made for a web wrapper.

Stopping condition

A decision record exists, and T27-47 is unblocked (approve) or formally closed (defer).

Verification

test -f docs/research/android-feasibility.md

Evidence and blockers

docs/research/android-feasibility.md exists on the board branch (it is not yet on main) and concludes "feasible with bounded work" — the GPU stack is glow-backed (EGL), not wgpu, and accesskit with android-native-activity forces GameActivity. Its disposition is "experimental": a feasibility finding, not a gate decision. Every item in the campaign's P6 feasibility checklist (re-read the report, audit the egui integration, the winit/event-loop dependencies, the accesskit conflicts, the NDK/SDK requirements, GameActivity integration, the document picker, touch interaction, lifecycle/resume, and the native architecture) is still unchecked.

Blocker: none — this row can start now.

Ledger: docs/tasks/T27-46-android-gate-decision.md and docs/release/EXECUTION-BOARD.md row T27-46 (these land with PR #12).
Campaign: docs/planning/release-compaign/Cross-Platform Releas.txt.

主要言語
Rust
スター
11
フォーク
1
平均マージ
9時間 48分
マージ済み PR（30日）
13

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

aliasfoxkde/FireCraft のほかの issue

aliasfoxkde/FireCraft の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。