Why does docker company not let more community developers continue the development and maintenance of swarm？
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
Why does docker company not let more community developers continue the development and maintenance of swarm, but let him die slowly？
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 swarmkit and asks about continued community development, but it does not identify a file, test, entry point, or specific code change. Start by reviewing the repository's current maintenance status and contribution guidance; the request would be complete only with a decided and actionable development scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100