Skip to content

docs(mentoring): Add Mentoring Subproject charter#2220

Open
bupd wants to merge 1 commit into
cncf:mainfrom
bupd:mentoring-subproject-charter
Open

docs(mentoring): Add Mentoring Subproject charter#2220
bupd wants to merge 1 commit into
cncf:mainfrom
bupd:mentoring-subproject-charter

Conversation

@bupd

@bupd bupd commented Jul 2, 2026 •
edited
Loading

Copy link
Copy Markdown

Summary

Add Mentoring Subproject charter

The TOC Mentoring Subproject charter is based on the previous CNCF Mentoring that lived under TAG CS in https://github.com/cncf/tag-contributor-strategy/blob/main/mentoring/README.md

Todo

  • Create Mailing List for TOC Mentoring Subproject

@bupd bupd requested a review from a team as a code owner July 2, 2026 17:00
@github-actions github-actions Bot added needs-triage Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied) needs-kind Indicates an issue or PR that is missing an issue type or kind (a kind/foo label) labels Jul 2, 2026
@github-actions github-actions Bot added the needs-group Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied) label Jul 2, 2026
brandtkeller
brandtkeller reviewed Jul 2, 2026
View reviewed changes
Comment thread toc_subprojects/mentoring-subproject/charter.md Outdated
brandtkeller
brandtkeller reviewed Jul 2, 2026
View reviewed changes
Comment thread toc_subprojects/mentoring-subproject/charter.md Outdated
brandtkeller
brandtkeller reviewed Jul 2, 2026
View reviewed changes
Comment thread toc_subprojects/mentoring-subproject/charter.md Outdated
brandtkeller
brandtkeller reviewed Jul 2, 2026
View reviewed changes

@brandtkeller brandtkeller left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Appreciative of the update - minor nits as for syncing timing (may be best to defer mentioning them here at all and just point to upstream source of truth?

@bupd bupd force-pushed the mentoring-subproject-charter branch 2 times, most recently from c53c04f to b6c818a Compare July 2, 2026 17:18
@bupd

bupd commented Jul 2, 2026

Copy link
Copy Markdown
Author

@brandtkeller Thanks for the review and heads up. This should be ready now.

@bupd bupd force-pushed the mentoring-subproject-charter branch from b6c818a to b176720 Compare July 2, 2026 17:36
nate-double-u
nate-double-u reviewed Jul 2, 2026
View reviewed changes
Comment thread toc_subprojects/mentoring-subproject/charter.md Outdated
@bupd bupd force-pushed the mentoring-subproject-charter branch 2 times, most recently from b68ad19 to 1712ee7 Compare July 2, 2026 17:57
nate-double-u
nate-double-u reviewed Jul 2, 2026
View reviewed changes
Comment thread toc_subprojects/mentoring-subproject/charter.md Outdated
@nate-double-u

nate-double-u commented Jul 2, 2026

Copy link
Copy Markdown
Member

I've just been told that some of this info belongs in the other file (thx @riaankleinhans)

The idea is the Charter it just "what we do and by who's authority"

The README is the admin, slack, mailing list, meeting, leadership etc. https://github.com/cncf/toc/blob/readme-update-fork-2221/toc_subprojects/mentoring-subproject/README.md

Having the admin in two place will guarantee information drift in <12 months

That is why we have the tags.yaml. TAG had the "same" information in various states of truth in the past.

So we should move everything below line 44 into the README, via the tags.yml in #2222

@bupd @aliok
@nate-double-u @riaankleinhans @jberkus
docs(mentoring): add mentoring subproject charter
8e0f09b 
Co-authored-by: Ali Ok <aliok@redhat.com>
Co-authored-by: Nate W <natew@cncf.io>
Co-authored-by: Riaan Kleinhans <61125752+riaankleinhans@users.noreply.github.com>
Co-authored-by: Josh Berkus <jberkus@redhat.com>
Signed-off-by: Prasanth Baskar <bupdprasanth@gmail.com>
@bupd bupd force-pushed the mentoring-subproject-charter branch from 1712ee7 to 8e0f09b Compare July 2, 2026 23:02
@bupd

bupd commented Jul 2, 2026

Copy link
Copy Markdown
Author

I've just been told that some of this info belongs in the other file (thx @riaankleinhans)

The idea is the Charter it just "what we do and by who's authority"
The README is the admin, slack, mailing list, meeting, leadership etc. readme-update-fork-2221/toc_subprojects/mentoring-subproject/README.md
Having the admin in two place will guarantee information drift in <12 months
That is why we have the tags.yaml. TAG had the "same" information in various states of truth in the past.

So we should move everything below line 44 into the README, via the tags.yml in #2222

makes sense, updated it now, no duplicate data between tags.yaml and the charter.md

nate-double-u
nate-double-u approved these changes Jul 3, 2026
View reviewed changes

@nate-double-u nate-double-u left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Thanks @bupd

@nate-double-u nate-double-u removed needs-group Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied) needs-triage Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied) labels Jul 3, 2026
@nate-double-u nate-double-u added kind/docs Docs related changes or updates sub/mentoring TOC Mentoring Subproject triage/valid Issue or PR is valid with enough information to be actionable and removed needs-kind Indicates an issue or PR that is missing an issue type or kind (a kind/foo label) labels Jul 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@brandtkeller brandtkeller brandtkeller left review comments
@nate-double-u nate-double-u nate-double-u approved these changes

At least 2 approving reviews are required to merge this pull request.

Assignees

No one assigned

Labels

kind/docs Docs related changes or updates sub/mentoring TOC Mentoring Subproject triage/valid Issue or PR is valid with enough information to be actionable

Projects

CNCF TOC Board
Status: New
TAG Developer Experience
Status: No status
TAG Infrastructure
Status: No status
TAG Operational Resilience
Status: No status
TAG Security and Compliance
Status: No status
TAG Workloads Foundation
Status: No status

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@bupd @nate-double-u @brandtkeller