revoirsoftware wants Mike to scope bigger changes before they sprawl
A proposed planning template would give substantial product and architecture work a clearer starting point.
The proposal separates feature planning from ordinary bug reports, asking contributors to set out the problem, boundaries, alternatives, affected areas, measures of success and open questions before a larger change gets underway.
- A copy-and-paste planning template for substantial work.
- A matching GitHub issue option so that planning starts in the same place as other contributions.
- Contribution guidance on when a simple issue is enough and when fuller product thinking is needed.
The pull request was closed without merging, so this is a signal of how revoirsoftware thinks Mike could be governed, not a change to the project today.
So what Teams considering Mike for serious legal-product work should note the push for clearer decisions before complex changes reach the build stage.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?