dave-parachute/mike

A fork betting that Mike OSS should be installable by a lawyer, not just an engineer.

Early and quiet: no substantive divergence from upstream, with a couple of documentation proposals from a single burst of activity in mid-2026 and nothing since.

View on GitHub →

This is Mike, reframed for the person who'd actually use it in a law practice. @dave-parachute installed Mike OSS by walking through the setup himself - as a lawyer rather than a developer - and used that experience to propose a rewrite of the onboarding documentation aimed at the friction points first-time, non-technical installers hit.

The work here is about the front door, not the engine. The bet is that Mike's biggest gap isn't a missing feature but a setup path written by engineers for engineers, and that closing that gap widens who can adopt it. If you're evaluating Mike for a firm where the people installing it aren't the people who write code, this is the fork thinking about you.

It hasn't diverged from upstream in substance yet - the contributions are proposed documentation revisions rather than shipped product changes. Click through to GitHub if you want to read the proposals themselves.

What's in it

Direction

personas

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

📝 Smooth the README onboarding for non-engineer installers 0 commits minor change

Threads of work (detailed view)

1 thread have been distilled into posts.

Pull requests (detailed view)

2 PRs touch this fork — inbound (filed against it) or outbound (filed from it). State icons match the editorial dashboard.

⛔ Closed without merge (2)