cncf/mentoring: the repository behind CNCF's mentorship programs

What cncf/mentoring actually is, and who it is for

The repository is the documentation home for the Cloud Native Computing Foundation's participation in mentoring programs. Its README states that the repository contains resources and information for the CNCF Mentoring Program, and that the program is designed to match experienced mentors with mentees who are interested in learning about cloud native technologies and contributing to open source projects in the ecosystem. That sentence is the whole scope. There is no service, no daemon and no library here.

The audience is narrow and specific. Mentees who want to apply to a CNCF-hosted project under LFX Mentorship, Google Summer of Code or Outreachy read the mentees folder for guidance on what is expected. Mentors read the mentors folder. Maintainers who want to propose a project read the programs folder, which the README describes as a list of programs for mentees to work on with their mentors. Governance questions route to the cncf-toc-mentoring-subproject folder, where the README says information about meetings, communication and activities can be found.

If you arrived expecting a mentoring platform, this is not it. The actual application and matching systems live elsewhere: the README links to mentorship.lfx.linuxfoundation.org for LFX Mentorship, summerofcode.withgoogle.com for GSoC, and outreachy.org for Outreachy. This repository is the CNCF-side paperwork around those platforms.

The repository layout and how the pieces link together

The top level holds .github/, CONTRIBUTING.md, LICENSE, LICENSE-CONTENT, README.md, and four content directories: cncf-toc-mentoring-subproject/, mentees/, mentors/ and programs/. Each content directory carries its own README, and the root README links into them with relative paths such as /mentors#readme and /programs#readme. That link style means the repository is meant to be read on GitHub or on a mirror that preserves the directory structure, not copied into a static site without rewriting paths.

The programs directory is the interesting one. The README presents a table mapping each program to its purpose and to a details folder: lfx-mentorship, summerofcode and outreachy. Those folders are described as holding details and historical data, which makes them the place to look for past project lists and timelines rather than the root README.

The split between LICENSE and LICENSE-CONTENT is worth noting. Two licence files at the top level suggest the repository distinguishes code licensing from content licensing, which is consistent with a repository that is mostly prose and tables. Anyone reusing the guidance pages in their own onboarding material should read both files rather than assuming the Apache-2.0 identifier covers everything in the tree.

The internship statistics table and what it does not tell you

The README includes a program statistics table covering 2017 through 2025, listing successful internships per year for each program. The numbers make the program mix visible. LFX Mentorship grows from 56 in 2020, when the table labels it CommunityBridge, to 127 in 2023, 134 in 2024 and 176 in 2025. Google Summer of Code sits in a much narrower band, between 6 and 16 per year across the whole period. Outreachy appears in most years with one or two. Google Season of Docs appears from 2020 to 2023 with two to four per year and then stops appearing in the table.

Read this as a description of program shape, not as a difficulty rating. The table counts completed mentorships, and the README does not state how many applications each year drew, how many projects went unfilled, or how the counts were compiled. The 2025 row shows LFX Mentorship at 176 and GSoC at 11, with a yearly total of 187; the arithmetic is consistent, but nothing in the README explains whether a mentorship that spans a calendar boundary is counted once or twice.

The most defensible reading is structural: LFX Mentorship is where most CNCF mentoring capacity sits, so a candidate deciding where to spend application effort should weight it accordingly. That is a conclusion about volume, and the table supports it directly.

Participation, conduct and where to ask questions

The README states that participation in the CNCF Mentoring Program is open to anyone who is interested in learning about cloud native technologies and contributing to open source projects in the ecosystem. It does not list prerequisites, prior contribution requirements or a selection process. Those details, if they exist, are in the per-program folders or on the external platforms, and the root README routes contact questions to a communications file inside the cncf-toc-mentoring-subproject folder rather than answering them inline.

Conduct is handled by reference. The README points to the CNCF Code of Conduct in the cncf/foundation repository and states that by participating in this project you agree to abide by its terms. There is no separate moderation policy in the root README.

A practical note for anyone opening an issue or pull request: CONTRIBUTING.md exists at the top level and the README does not summarise it. Read that file before proposing changes to the guidance pages, because the repository is a governance artifact where wording changes can affect how applicants interpret program rules.

There is nothing to install, so start by reading the right folder

This repository has no install step. The README gives no package, no build command and no runtime, and there are no releases to download. The way to use it is to clone it or browse it and read the folder that matches your role. Cloning gives you the full tree and the relative links intact.

git clone https://github.com/cncf/mentoring.git
cd mentoring
ls

After the clone you should see the top-level entries listed in the repository: .github/, CONTRIBUTING.md, LICENSE, LICENSE-CONTENT, README.md, cncf-toc-mentoring-subproject/, mentees/, mentors/ and programs/. If your goal is to apply, the mentees folder is the starting point the README names for guidance on being an effective mentee.

If your goal is to propose a project as a maintainer, the programs folder is the entry point, and the README table tells you which subfolder corresponds to the program you are targeting.

ls programs
ls programs/lfx-mentorship

The README describes the programs folder as a list of programs for mentees to work on with their mentors, and the table maps LFX Mentorship, Google Summer of Code and Outreachy to their details folders. What you should see after those two commands is the per-program documentation, including the historical data the README mentions. If a folder appears empty or missing on your checkout, check that you are on the default branch main, because the README's relative links assume that layout.

What this repository cannot do for you

The clearest limitation is that the repository does not accept applications and does not match anyone with a mentor. The README sends applicants to three external platforms, and the actual selection happens there. Reading every file in this repository will not tell you whether a particular project is open this cycle, because the README does not claim to be the live source for that; the table in the README is explicitly historical, covering 2017 through 2025.

A second limitation is documentation depth. The root README is short and mostly a routing table. It does not document the application timeline for any program, the stipend amounts, the evaluation criteria, or what happens when a mentorship is terminated early. For each of those, the README is silent, and the reader has to follow the links into the per-program folders or the external sites. Treating the root README as a complete guide will leave gaps.

The third case where this is the wrong resource: if you want mentoring that is not tied to CNCF or to these three programs, nothing here applies. The repository is scoped to CNCF's participation in LFX Mentorship, Google Summer of Code and Outreachy, and the guidance pages are written with those structures in mind.

How it relates to the platforms it points at

The natural comparison is with the program platforms themselves. LFX Mentorship, hosted at mentorship.lfx.linuxfoundation.org, is the Linux Foundation's mentoring initiative and is where applications, mentor listings and project terms live. The difference in approach is that the platform is transactional and current, while cncf/mentoring is documentary and archival. The platform tells you which projects are open now. This repository tells you how CNCF has framed mentoring, what the roles involve, and how many internships each program completed in each year from 2017 to 2025.

That division has a practical consequence. If you want to know whether a CNCF project is taking an LFX mentee this term, the repository's programs/lfx-mentorship folder is historical data, and the live answer is on the platform. If you want to understand what a CNCF mentor is expected to do before you volunteer, the mentors folder is the better source than the platform, which is built around listings rather than role guidance.

Google Summer of Code and Outreachy follow the same pattern: summerofcode.withgoogle.com and outreachy.org are the operational systems, and the corresponding folders here hold CNCF's own notes and history. The repository is a companion to those platforms, not a replacement for any of them.

Maintenance, licensing and what to check before relying on it

The repository is not archived, and its last push was on 2026-09-21, three days before this article's reference point, so the tree is being touched. There are no retrieved releases, which fits a repository made of Markdown and tables: versioning happens through commits to main, not through tagged artifacts. For a reader, that means there is no changelog to consult and no version to pin. If you cite a statistic or a rule from these pages, cite the commit you read it at.

Licensing is split across two files at the top level, LICENSE and LICENSE-CONTENT, alongside the Apache-2.0 identifier for the repository. The presence of a separate content licence suggests the prose and statistics may be governed differently from any code in the tree. This is a description of what the files are, not legal advice; if you plan to republish the guidance or the statistics table, read both files and decide for yourself.

The upgrade cost is effectively zero and also the main risk. Nothing breaks when the repository changes, but nothing warns you either. A page you quoted last cycle can be edited without a release note. Before pointing a new mentee or mentor at any specific page, open the file on the current main branch and confirm it still says what you expect.

Editorial conclusion

Adopt cncf/mentoring as a reference if you are applying to LFX Mentorship, GSoC or Outreachy through CNCF, or if you are a maintainer writing a project idea for one of those programs. Do not treat it as a tool: there is no package to install and no runtime to configure, only Markdown guidance and historical tables. Before relying on any page, open the programs/lfx-mentorship, programs/summerofcode or programs/outreachy README and check its current contents, because the top-level README only links to them and the repository carries no releases.

Frequently asked questions

Official sources

1. cncf/mentoring on GitHub
2. Issues
3. License: Apache-2.0
4. Project website
5. README