Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

June 10th, 2024 Community Meeting #209

Closed
qu1queee opened this issue Jun 7, 2024 · 5 comments
Closed

June 10th, 2024 Community Meeting #209

qu1queee opened this issue Jun 7, 2024 · 5 comments

Comments

@qu1queee
Copy link
Contributor

qu1queee commented Jun 7, 2024

  • 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
Copy link
Contributor Author

qu1queee commented Jun 10, 2024

@avinal
Copy link

avinal commented Jun 10, 2024

@adambkaplan
Copy link
Member

  • Upcoming conference CFPs: KubeCon NA, KubeCon India

@adambkaplan
Copy link
Member

@qu1queee
Copy link
Contributor Author

Meeting minutes:

  • On the Dependabot issue from @avinal . We had a good discussion on this, further extensions to the issue are:
    • Filter only on PRs related to a security issue
    • considering markdown folding for long lists of issues
  • On conferences:
    • KubeCon NA:
      • CFP: Closes on Sunday 13/14/15th
      • Idea is to have a maintainer talk for the Colocated TAG App delivery
    • KubeCon India:
    • Upcoming. @qu1queee can ask Nikhita for more information.
    • CD Mini Summit in Vienna at OSSummit EU.
  • On Build Scheduler Options SHIP
    • Adam is looking for feedback.
  • How to have a fixed cadence, independently of what we release, just release!
    • We need automation to have updates on projects like operator and cli after updates on Build. To create issues on this for CLI and Operator.
    • We need more issues for automation on Build, to release required branches, tags and trigger release notes creation, et. al.
  • On Issue 1615, we see this as an opportunity for new contributors to engage if they have the skill set. This is not something that must be done immediately, in general, this is more like a research item that can be discussed over time. We don't have the need for this change at the moment, but we are open to explore and consider additional technologies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants