Engineering Project Board
The Engineering project is the working board for this repository. It was set up in #392. This page records the field conventions and views so the board stays useful as issues come and go.
Membership
Every open issue in this repository goes on the board, with one deliberate exception: issues explicitly deferred to a later phase in the #280 implementation plan (currently #467, Android) may stay off until their phase starts.
Fields
Every open item carries a value for all four fields below. An item missing one of them is a gap to fix, not a valid state.
| Field | Type | Values and meaning |
|---|---|---|
| Status | Single select | Draft (needs a design loop, a decision, or an unblock step first) / Ready (workable now without further input) / In progress / In review (PR open) / Done |
| Priority | Single select | 1 workable now, 2 needs a design loop or an unblock step first, 3 deferred or later phase |
| Area | Text | Domain of the work. Reuse an existing value before inventing a new one: Documents, Grammar, Verbs, Decks, Profile, Mobile, Audio, Content, Cross-cutting, Operations, Process, Chat, Billing, LLM, Design, Research |
| Group | Single select | Engineering / Marketing / Operations — org-wide field for cross-group coordination. Almost everything in this repository is Engineering |
Estimate (hrs) and Actual (hrs) are optional number fields used when a task has been scoped.
Views
Views can only be created and edited in the GitHub UI (the API has no mutations for them), so their configuration lives here as the reference:
| View | Layout | Configuration | Purpose |
|---|---|---|---|
| By Status | Board, columns = Status | Filter is:open, sort Priority asc (1, workable now, first) |
Day-to-day kanban |
| By Area | Table, grouped by Area | Fields: Title, Assignees, Status, Linked PRs, Sub-issues progress | Where open work concentrates |
| Epics | Table | Filter is:open has:sub-issues-progress |
Umbrella issues such as #280 at a glance |
| Shipped | Table | Filter is:closed, sort Closed desc |
Cheap changelog for review |
A fifth view, “Groups overview” (board with columns = Group, no filter), becomes worth creating once Marketing or Operations items exist in meaningful numbers.
Workflow
- New issue: add it to the board and set all four fields immediately.
- Opening a PR for an issue: move the issue to
In review. - Merging: GitHub automation moves closed issues to
Done. - Field edits are scriptable via
gh api graphql(updateProjectV2ItemFieldValue); Area takes atextvalue, the other three take asingleSelectOptionId.