WebAssembly / WebAssembly/WASI
Document WASI longevity expectations
Open
Nobody has claimed this yet.
P-clocks
S-inactive
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
We should capture the discussion the ideas in the discussion starting here in the main documentation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion linked from the issue, then locate the repository's main documentation. Capture the discussion's WASI longevity expectations there, with completion marked by the relevant ideas from the discussion being documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100