ChrisTitusTech / ChrisTitusTech/warframe-linux
F03: P0: provenance and field contracts
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4
- Forks
- 1
- Avg merge
- 7m
- Merged PRs (30d)
- 4
Description
Go implementation tracking epic
Selected stack: Go + Wails v2 + React/TypeScript + SQLite. Implementation starts on the next machine. Each child below is a separate PR; do not implement this epic in one PR.
Child tasks
- F03a: License and reuse inventory
- Merged prerequisites: None.
- Acceptance: Maintainer records new-code license and copied-code notices; list reusable modules and source/data attribution; no blanket MIT claim or code migration before this decision.
- F03b: Provider schema and endpoint contract notes
- Merged prerequisites: F03a.
- Acceptance: Document supported Market endpoints/rank/platform semantics and synthetic inventory schema, quantities, unknowns, mastery/foundry field availability; list unavailable data explicitly.
Workflow
See TASKS.md, ROADMAP.md, and CONTRIBUTING.md. Aim for 100-400 handwritten changed lines per PR; split above 600 unless inseparable. Merge prerequisites before dependents. Update task evidence and this checklist after each completed PR. Close this epic only when every child passes; optional work can remain deferred.
All tasks are not started. Live game access and publication/merge actions follow the user's explicit authorization. The planning handoff does not claim runtime validation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with TASKS.md, ROADMAP.md, and CONTRIBUTING.md, then review the F03a license and reuse inventory before approaching F03b's provider contract notes. Treat each child as a separate PR; done means recording license and attribution decisions, documenting endpoint and schema semantics, and listing unavailable data with the checklist and task evidence updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, react, sqlite, typescript
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100