Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)

Yeah, we worked on documenting things like [design rationale](https://github.com/WebAssembly/design/blob/main/Rationale.md) in the early days, but haven't really kept it up with every proposal as we've added them. User benefit is of course different (as wasm would be mostly transparent to end users) but every proposal has to consider e.g. developer benefit as it goes through the phases. Usually when champions request phase advancement they make a presentation that covers the design and often includes use cases and benefit (especially in early stages) design rationale, notable changes, etc. Those are all posted publicly, so at bare minimum it would be pretty straightforward to collect those, with links to the meeting notes, somewhere more convenient. Maybe we could have champions do that when they advance to phase 4.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1002#issuecomment-2433783456
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1002/2433783456@github.com>