You've never seen a thorough design proposal? Typical commercial pre-wireframe research and proposal: https://web.stanford.edu/~eadolfo/cis-redesign/attachment

You've never seen a thorough design proposal? Typical commercial pre-wireframe research and proposal: https://web.stanford.edu/~eadolfo/cis-redesign/attachments/proposal-newsignature.pdf https://web.stanford.edu/~eadolfo/cis-redesign/attachments/p... More common in FOSS: https://github.com/openstreetmap/iD/issues/759 https://github.com/openstreetmap/iD/issues/759 https://github.com/stashapp/stash/issues/1549 https://github.com/stashapp/stash/issues/1549 https://github.com/newrelic/nr1-groundskeeper/issues/3 https://github.com/newrelic/nr1-groundskeeper/issues/3 https://github.com/creativecommons/creativecommons.github.io-source/issues/189 https://github.com/creativecommons/creativecommons.github.io... https://github.com/godotengine/godot-proposals/issues/1823 https://github.com/godotengine/godot-proposals/issues/1823 (from google searching for things like site:github.com "wireframes" "design" "proposal") > a) They have, b) it's definitely not rare, and c) it is an enormous time-drain and source of frustration for maintainers in the FOSS community. I can't claim to be omniscient but I've been a constant open source contributor for 10 odd years and heavy user for nearly 25 and I've never seen that, or even heard people complain about it, let alone enough to be an enormous problem. I've seen ill-conceived gripe lists, superficial 'lets make this look cool,' and 'this font sucks' type issues periodically. None of those are serious design proposals any more than "make everything faster" or "I hate when your program does x" or "I think we should get rid of this and make it in react" are serious development proposals. I'll happily put together a guide on cutting through bullshit UI change proposals if I could evaluate some issues/PRs for open source repos that constantly experience this problem.