spinframework / spinframework/spin
Deprecate support for WAGI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
WAGI is rarely used and imposes a large maintenance burden on Spin. I propose that we make the breaking change of deprecating support for WAGI. Some discussion around this has already happened in this Slack thread in the CNCF Slack.
Ivan raised a good point in the thread that we should be cautious about WAGI usage in downstream Spin hosted services. It would make sense to encourage those to deprecate WAGI first before we eventually deprecate WAGI in Spin.
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
The issue names no files, tests, or entry points. Start by reviewing the linked Slack discussion and assessing WAGI usage in downstream Spin hosted services; done means establishing a deprecation plan for those services before deciding how support should be deprecated in Spin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100