steid

@jamesgill /

steid/plans/ROADMAP.md
4.6 KBCode·Blame·Raw
ab7fea9chore: plans setup1mo
1# Steid
2
3The source of truth for everything in a developer's or organization's portfolio.
4
5## Vision
6
7Steid is a developer/org identity and portfolio platform. It's where you host your
8code, your writing, your projects — everything you do, in one place, under your
9control.
10
11Git repos are a core feature, not the whole product. Blogs, documentation, project
12showcases, and anything else a dev or org wants to present lives here too.
13
14Personal-first, but organizations can collaborate on it.
15
16**What makes it different from Gitea/Forgejo:** those are GitHub clones scaled down.
17Steid is portfolio-first — the profile page is the product, and repos are one kind of
18thing that appears on it. That framing should win any tie-break.
19
20## Core Principles
21
22- **Fast** — Rust, minimal overhead
23- **Reliable** — correct first, then optimize
24- **Personal-first** — great for a single dev, scales to orgs
25- **Identity-centric** — everything is built around who you are (user/org); auth is
26 designed in from day one, not bolted on
27
28## Stack
29
30Starting intent, not settled decisions. Each one gets a record in
31[decisions/]decisions/ when it's actually made and confirmed in this build.
32
bd48b4bdocs: serve git over smart HTTP, reorder roadmap portfolio-first1mo
33| Concern | Choice | Decision |
34|---|---|---|
35| Web framework | Topcoat (tokio-rs) ||
36| Git transport | smart HTTP via `git http-backend` | [0001]decisions/0001-git-over-http-not-ssh.md |
37| Git auth | personal access tokens over HTTP Basic | [0001]decisions/0001-git-over-http-not-ssh.md |
38| Crate layout | single crate ||
39| Ownership | personal org owns repos ||
aaefaabfeat: root handles, grouped routes, reserved-handle denylist1mo
40| URLs | root handles, grouped routes | [0004]decisions/0004-root-handles-grouped-routes.md |
bd48b4bdocs: serve git over smart HTTP, reorder roadmap portfolio-first1mo
41| Database | SQLite via sqlx ||
ab7fea9chore: plans setup1mo
42
43Architecture and conventions: [architecture.md]architecture.md.
44
45## Milestone Ladder
46
bd48b4bdocs: serve git over smart HTTP, reorder roadmap portfolio-first1mo
47A from-scratch rebuild on Topcoat. Much of this was built and verified end-to-end in a
48previous attempt — see [progress.md]progress.md. Treat that code as reference, not as
49a baseline.
ab7fea9chore: plans setup1mo
50
51| # | Milestone | Status |
52|---|---|---|
bd48b4bdocs: serve git over smart HTTP, reorder roadmap portfolio-first1mo
53| 0 | **Skeleton** — Topcoat app boots, config, one page, SQLite wired | done |
076dbc9docs: close milestone 1, open milestone 21mo
54| 1 | **Identity, thin** — claim on first run, login, session | done |
c50d9adfeat: profile settings with flash feedback25d
55| 2 | **Profile page**`/{handle}` as the real profile | done |
2eb8681docs: put git next, plan the repo model24d
56| 3 | **Repo model** — records + bare repos on disk | active |
57| 4 | **Git over HTTP**`git http-backend`, PATs for auth | not started |
58| 5 | **Repo browsing** — tree, blob, commit log | not started |
59| 6 | **Writing** — posts, markdown | not started |
bd48b4bdocs: serve git over smart HTTP, reorder roadmap portfolio-first1mo
60| 7 | **Identity, full** — multi-user, orgs, invites, registration policy | not started |
61| 8+ | Projects/showcases · issues & PRs · SSH transport · federation | not started |
62
63`/api` is not a milestone. It's a standing practice: every milestone that adds a use
64case exposes it under `/api` where that makes sense. An API isn't a feature, it's a
65second surface on work already being done — and having a third consumer keeps the use
66case layer honest.
67
68### Why this order
69
70The vision calls Steid portfolio-first, but every previous ladder put portfolio behind
71four milestones of git plumbing. Across two attempts and ~6,000 lines, Steid has
72shipped identity, repo records, clone, push, and key auth — and not one portfolio
73feature. Attempt #2 ended with all the git infrastructure working and nothing that
74distinguishes it from Gitea.
75
2eb8681docs: put git next, plan the repo model24d
76The differentiator therefore shipped early: the profile page is milestone 2, not
77milestone 6. Full multi-user identity stays deferred to 7 — personal-first means one
78user, and there is nothing to collaborate on until there is something worth
79collaborating on.
80
81**Git moved ahead of writing after milestone 2 shipped**, deliberately reversing the
82original order. Two reasons. The profile has a Repositories section that a visitor
83expects to be full, and a gitforge whose repo list is permanently empty is its own kind
84of wrong. And git-over-HTTP is the least-understood work left — everything else is CRUD
85over SQLite, while that is pack data streamed through a subprocess — so learning what
86Topcoat makes awkward is worth more now than after three more features are stacked on
87top.
88
89The risk being run knowingly: disappearing into protocol work is what ended both
90previous attempts. Milestone 3 is deliberately small and ships something visible on the
91profile; if milestone 4 starts to sprawl, that is the signal to bank it and go back to
92writing.
ab7fea9chore: plans setup1mo
93
94**One numbering scheme.** The previous attempt kept two (a roadmap ladder and a
95separate build log with conflicting numbers) and they drifted apart within three
96milestones. If the plan changes, edit this table — don't start a second list.
97
bd48b4bdocs: serve git over smart HTTP, reorder roadmap portfolio-first1mo
98The active milestone is broken into steps in [current.md]current.md.