Add OS maintenance strategy to documentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker
- Domain
- documentation
Research direction
Start by reading CONTRIBUTING.md and the discussion in related issue 2363, then inspect how the current Alpine and Debian images and architectures are represented in the repository. Done means the documentation explains inclusion, version and architecture lifecycle, defaults, and how changes during Node.js or operating system lifecycles are handled.
Written by the indexing model from the issue text.
Description
Suggestion
Extend the CONTRIBUTING document to describe the strategy for including and adding new images, either by adding text or referring to a separate new document.
This should reference:
- which operating systems are included (currently Alpine and Debian)
- how / when new operating system versions are added
- how / when operating system versions are removed
- how the default operating system version is set and maintained for a given Node.js release line
- how the default Node.js version is set and maintained for a given operating system selection
- how architectures will be added / maintained / removed
- if supported architectures change during the lifecycle of Node.js / operating system versions, describe how these will be handled
Related
- Dominant language
- Dockerfile
- Stars
- 8.6k
- Forks
- 2k
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 16
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.
More from nodejs/docker-node
-
build process docs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nodejs/docker-node#2564 · 2 comments ·
-
build process
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nodejs/docker-node#2437 ·
-
build process
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
nodejs/docker-node#2436 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nodejs/docker-node#1779 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nodejs/docker-node#1707 · 3 comments · 7 reactions ·
All issues in nodejs/docker-node
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
A11y ♿️
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
documentation improve or update documentation priority/low triage
Difficulty 2/5 Half a day Newbie friendliness 86/100
warpdotdev/docs#782 · 1 comment ·