Jump to content

Roadmap

From wikicells
Revision as of 07:48, 28 May 2026 by Randy (talk | contribs) (Seed load)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Hello World phase

Goal: a self-hosted Wikibase running at a real domain, populated with this project's own architectural decisions as a wikified table — demonstrating cell-as-wiki and schema-as-wiki on real project content from day one.

Step Description Status
1 Scaffold repo layout + bootstrap docs ✅ Done
2 infra/docker-compose.yml (Wikibase Suite) ✅ Done
3 infra/config/Extensions.php (federation + CC0 + user groups) ✅ Done
4 seed/schema.yaml + seed/open-questions.tsv ✅ Done
5 seed/pages/ (Main_Page, About, ...) ⏳ In progress
6 bots/seed_load.py (idempotent seed loader) ⏳ Pending
7 infra/config/traefik-dynamic.yml + deployment recipe ✅ Done
8 User: provision VPS, register domain, first deploy ⏳ User action

User actions blocking public deployment

  • Register a domain
  • Provision a VPS (≥ 4 GB RAM recommended for Elasticsearch + Blazegraph headroom)
  • Point DNS at the VPS
  • Set admin credentials in infra/.env on first boot

Steps 1–7 do not depend on these — they all run locally on Docker Compose.

Post-Hello-World phases

Phase A — CellHistory extension
Custom MediaWiki extension surfacing per-statement edit history as a first-class UI. The principal engineering investment of this project — it's the gap between Wikibase and our "every cell is a wiki" requirement.
Phase B — Bots and export
bots/wikidata_sync.py (curated import/export with Wikidata) and bots/export_mirror.py (scheduled wiki → markdown mirror for offline / GitHub-search discoverability).
Phase C — TrustGraph extension
Stake-and-slash vouching system per Trust Model. Weeks of work; meaningfully more complex than CellHistory.
Phase D — Oversight policy
Document the appeal process for RevisionDelete and suppression; establish the audit trail; train initial oversighters.
Phase E — Federation hardening
Scheduled RDF dump publishing; SPARQL endpoint hardening; QuickStatements push-to-Wikidata workflow for notable facts.
Phase F — User's specific site (Goal ii)
The particular wikified-database site the user originally intended, implemented on the now-mature infrastructure.
Phase G — Adoption packaging (Goal i)
Turn infra/ + extensions/ + bots/ + seed/ into a forkable deployment template other organizations can adopt with minimal setup.

The full decision log is maintained as wikified data — see the Architectural decision class page once the seed loader has populated the data.