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

Abierto
  • ¿Algo no está bien?
#65 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
android, rust
Área
mobile

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
11
Forks
1
Merge medio
9 h 48 min
PR fusionados (30 d)
13

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aliasfoxkde/FireCraft

Todos los issues de aliasfoxkde/FireCraft

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.