Plan: reviewing decks in the app, sent by mail

Aperta
#403 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
dart, flutter
Ambito
web-dev

Direzione di ricerca

Read docs/plans/deck-browser.md and the linked native-layers issue #392 first; this plan explicitly depends on that work. The issue describes a Pages deck browser, reviewer suggestions sent to Google Forms, Sheet rows becoming labelled issues, and a weekly canary, but leaves implementation details to its sub-issues. Done when every sub-issue is closed, each part has tests, and the plan is deleted.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

plan

Tracks docs/plans/deck-browser.md: reviewing decks inside the app, sent by mail. A reviewer turns reviewer mode on in Settings and the phone makes their rater code. They review on the screens that already show decks and cards, and send one review file per deck, in one mail with the code, to [email protected]. The hourly mail workflow (tools/mail_to_issues.py) opens one issue per review mail, with only the rater code and the languages. There is no Google Form, no Sheet and no Pages page for reviewing (owner, 2026-10-09). The owner reads the mail and the decks are updated with him.

Order: now, ahead of the native layers (owner, 2026-10-09): built on today's deck format, layer support added when #392 lands. Blocked by: nothing. The app side is PR #436 (feat/reviewer-mode). Parts: sign-off (#427), offensive-word ratings (#428), similarity confirmations (#429), rater codes (#430), review mail to issues (#407). Whether a public Pages deck browser survives is for the owner to decide (#404, #405); the form parts (#406, #408) are closed as superseded.

Done when every sub-issue is closed. Each part ships with its tests. Then close this issue and delete the plan from docs/plans/.


Generated by Claude Code

Lingua principale
Dart
Stelle
1
Fork
0
Merge medio
3h
PR unite (30g)
424

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aaronified/fluenough

Tutte le issue di aaronified/fluenough

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.