[TOC Meeting][Public] 2025-02-18

[mrbobbytables]

Host: @angellk
Note Taker: @TheFoxAtWork

Recurring Items

• LF Antitrust Policy
• Review Open Votes (REMINDER: Check both Issues AND PRs)
• Review & Assign projects in moving levels backlog
• Review TOC Work Board

Agenda

• TAG Reboot status ~5 mins
• Archive and health of review
• https://github.com/cncf/toc/blob/main/process/archiving.md
• Understand which move to archive vote, timeline, and projects that are just unhealthy and need next steps
• Code of Conduct PR: Proposed Code of Conduct Updates for January 2025 foundation#941

TOC Members in Attendance

• @TheFoxAtWork
• @angellk
• @kgamanji
• @kevin-wangzefeng
• @dims

[TheFoxAtWork]

TOC work board - review async, and private meeting to deep dive and clean up.

TAG Reboot - nothing raised, still moving forward.

Archive and health of review -

• if a project has a release, understanding if its delayed or not happening, is it regularly occurring? ensuring spec projects dont get arbitrarily pulled in.
• https://all.devstats.cncf.io/d/53/projects-health-table?orgId=1 Click "show inactive" <-- this is how we built out the current list for review.
• We should improve the archive process to clarify timeliness of engagement. recommend 1 month for health response window.
• @kgamanji will proxy the health of projects listing to the End User TAB, @dims will shoot a message out on the TOC mailing list. this is intended to get understanding of where the project is at, is it active, is it maintained and if so who by, are people using it? Should we have a central resource, similar to adopter interviews, so we can ask these questions of the end user community.
  • The TOC has identified the following list of projects in need of a health/activity check up, we're requesting your assistance in answering the following questions:
    • Are you familiar with this project?
    • Do you know if the project is active, perhaps outside of github?
    • Do you know if it is maintained and if so who is maintaining it?
    • Are you using or do you know someone who is using the project?
  • We keep the health response window open for one-month, to allow projects to provide the TOC with context around their health or inactivity before the TOC makes a determination to vote for archive or to provide a roadmap back to health for the project.
• we will also need a mechanism to indicate a "check-up" for status on open Health issues that are still being worked.
• Share on the maintainer list, mention opportunity to self-archive. add this to the archiving.md

CoCC PR - every TOC member needs to review the PR.

Actions:

• The https://github.com/cncf/toc/blob/main/process/archiving.md file needs updated with the following:
  • define the health response window as 1 month to receive input from the project, end users, other maintainers, and community members regarding the project's health and activity.
  • Document the TOC process for conducting health of and archive - this means notifying the end user TAB, the TOC mailing list, and the maintainers list of the projects requesting a health response.
  • Document how a project may self-archive.
• Establish a "check-in" status for health of project issues that completed a health response window, but were not determined to be feasible for archive as they are working to return to a healthy and active state.