October 21th, 2024 Community Meeting

[qu1queee]

• Please add a topic in this thread and add a link to the GitHub issue associated with the topic.
• Please make sure you give folks enough time to review/discuss the topic offline on GitHub before coming into the meeting
• (optional) Paste the image of an animal 😸

[qu1queee]

• Move out of issues for Community meeting, in favor of a shared document (.e.g google drive doc)
• Update on Meetings invites.
• On Snyk usage.

[prb112]

Please share the link here when it's official - I follow along weekly.

[adambkaplan]

Ideas for improving (and documenting) the backlog refinement process.

[SaschaSchwarze0]

To be able to manage our releases, I created shipwright-io/build#1694 a while ago to start getting an overview which vulnerabilities our latest release has. Do we want that? I had planned to PR it on operator and CLI as well if so.

[qu1queee]

Meeting minutes:

• On community meetings:
  • for a single document, do we want anonymous user to have right permissions?
  • how do we handle permissions, as if today, anyone in a github issue can comment.
  • in google docs, an anonymous user can make a comment, visible to someone, that can accept the comment.
  • @qu1queee to experiment with the google doc approach
• On calendar invites via LFX Meetings:
  • Sounds interesting, and easier to manage.
  • On mailing list, we currently use something from RH OSPO.
• On Snyk
  • Next steps: Interprate the Snyk findings, decide how to address or ignore.
• On Refinement meeting improvements
  • Next steps: Open a hackmd or github discussions, bring ideas.
• Vuln check - announce for review
• Onboarding slack bot - unclear how to do. May need to reach out to k8s/CNCF contributor experience groups.

[adambkaplan]

Welcome/onboarding slack bot: #250