cncf/glossary
The CNCF Cloud Native Glossary Project aims to define cloud native concepts in clear and simple language, making them accessible to anyone — whether they have a technical background or not (https://glossary.cncf.io).
In plain words
Only 13 outside PRs in the last four months, too few to rate. More than half of outside PRs got no reply.
Outside PRs merged
Not enough data
3 merged, 1 closed, 9 still open
Closed without merging (1)
First human reply
Mostly unanswered
median of 13 outside PRs, 8 unanswered
Outside PRs opened 30 to 120 days ago, so each has had time to be answered. A figure needs at least 5 pull requests, otherwise it reads "Not enough data". How this is calculated · A number looks wrong?
Your first steps here
If you have never contributed to this project, do these in order.
- 1
Read the contributing guide
It says how to set the project up and what the maintainers expect in a pull request.
Open the guide - 2
Find something small
No first issue is free right now. Look for a typo, a missing test or an unclear error message, or ask where help is wanted.
Browse open issues - 3
Know where to ask
Questions go to the project's slack, or on the issue itself. Not in private messages.
Open it - 4
Open a small pull request
Link the issue in it. Too few outside pull requests here to say how long a reply takes.
What happens to an outside pull request
Every pull request opened by someone outside the core team, 30 to 120 days ago.
- Opened by outsiders13100%
- Got a human reply538%
- Merged323%
Time to first reply
After 2 days, 23% of outside PRs had a reply from a person. After a week, 31%. Bots do not count.
The last 52 weeks
Outside pull requests opened each week, and how many of them have been merged.
Starter issues
Issues labelled for beginners, with their real state. Available means open, unassigned, no linked pull request, nobody has claimed it in the last 14 days, and it was updated in the last 60 days.
- Available
- 0
- Claimed
- 1
- Has a pull request
- 2
- Stale
- 0
- Has a pull request[ru] Localize `Service` into Russian#3334
- Has a pull request[ru] Localize `Portability`#3265
- Claimed[es] A report to track and reflect updates of English content#3222
Issue replies: first human reply in Not enough data (median of 5 issues).
When replies arrive
All maintainers counted together. Shown only when at least 3 people replied in the last 90 days, so it never describes one person.
Replies are most likely between 22:00 and 01:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 7 |
| 01:00 | 3 |
| 02:00 | 4 |
| 03:00 | 6 |
| 04:00 | 6 |
| 05:00 | 6 |
| 06:00 | 5 |
| 07:00 | 3 |
| 08:00 | 1 |
| 09:00 | 1 |
| 10:00 | 1 |
| 11:00 | 3 |
| 12:00 | 7 |
| 13:00 | 6 |
| 14:00 | 2 |
| 15:00 | 0 |
| 16:00 | 1 |
| 17:00 | 3 |
| 18:00 | 3 |
| 19:00 | 3 |
| 20:00 | 3 |
| 21:00 | 2 |
| 22:00 | 7 |
| 23:00 | 11 |
How to start
- Contributing guidefound
- Code of conductfound
- Issue templatesfound
- Dev container for one-step setupfound
- No CLA or sign-off requirement was found.
Where the project talks
Activity
- Commits, 90 days
- 52
- Releases, 12 months
- 0
- Active maintainers
- 13
- Last push
- 9 Oct 2026
Stack
Badge and feed
Two ways to use these figures outside this page.
For maintainers: a README badge
Shows newcomers how quickly this project answers and how often it merges. Paste the line into your README; the badge updates with the index.
[](https://contributable.vercel.app/repo/cncf/glossary)[](https://contributable.vercel.app/repo/cncf/glossary)For contributors: follow new issues
Add the feed to a feed reader (Feedly, Inoreader, Thunderbird) and you hear about new free starter issues here without checking the site.
https://contributable.vercel.app/feed/repo/cncf/glossaryFor developers: every figure on this page as JSON at /api/v1/repos/cncf/glossary.
Similar repositories
Same main language (Go Template), most shared frameworks and topics first, then the faster reply.
Helm charts for Gen3 Deployments
- First reply
- 27 h