dave-parachute/mike
A fork betting that Mike OSS should be installable by a lawyer, not just an engineer.
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
- Onboarding for non-engineers README and setup revisions written for a lawyer installing Mike OSS, not a developer - targeting the friction a first-time, non-technical installer actually hits.
- Install-tested by its author @dave-parachute walked the setup himself as a first-time non-technical user, so the proposed changes come from real friction rather than guesswork.
Direction
personas
Activity
Threads of work (detailed view)
dave-parachute rewrites Mike's setup guide for lawyers, not engineers
An outside contributor installed Mike as a non-technical user, hit a wall at every step, and wrote down the fixes.
Pull requests (detailed view)
⛔ Closed without merge (2)
dave-parachute · opened 2mo ago · closed 2mo ago dave-parachute · opened 2mo ago · closed 2mo ago