spinframework / spinframework/spin
define what it means to archive a project in Spin
Open
Nobody has claimed this yet.
governance
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
relevant convo here: https://github.com/fermyon/spin/issues/2629#issuecomment-2361125110
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 by reading the linked conversation in issue #2629, especially the referenced comment, to understand the unresolved meaning of archiving a project in Spin. Done means the project’s archive semantics are explicitly defined and the resulting scope or implementation location is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100