Maintenance Documentation¶

For this repo to stay healthy, we need to make sure that we are doing regular maintenance. This includes:

Issue Triage¶

• Review newly created/updated issues (bugs and questions) and try to find assignees
• Ensure issues don't get stale and eventually get fixed/answered
• Use community meeting for sync and help

CI Flakes Triage¶

Owner: @npinaeva

• Review newly created/updated flakes and try to find assignees
• Ensure flakes don't get stale and eventually get fixed
• Review/find reviewers for the CI flake fixes
• Use community meeting for sync and help

Release Tracking and Management¶

Owner: @tssurya

• Define target date for the next release, add Milestone and track the progress of the release
• Share updates on the release progress in the community meetings
• Track the scope of the release as we get closer to the release date and make sure we are on track to meet the release goals
• Cut the release and share the release notes with the community

Members and Contributors Management¶

All maintainers, including area maintainers, are responsible for this.

• Ensure that we have the right people with the right permissions in the repo and in the org
• Remove stale members and contributors
• Add new members and contributors (follow the process defined in the GOVERNANCE file)

Project Healthcheck¶

No one is doing this now

• Close stale PRs and issues (we have stale label)
• Delete stale branches

Community Meetings¶

Owners: @npinaeva and @tssurya

• Facilitate the meetings and ensure that we are having productive discussions and that we are making progress on the topics discussed
• Ensure that we are taking notes during the meetings and sharing them with the community