Maintenance Documentation

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

• Issue triage (No one is doing this now)
  • 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 (@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 (@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 (now also for areas) management (now is done by all maintainers)
  • 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
• Facilitating the community meetings and keeping the notes up to date (@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