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

February 26th, 2024 Community Meeting #191

Closed
qu1queee opened this issue Feb 22, 2024 · 6 comments
Closed

February 26th, 2024 Community Meeting #191

qu1queee opened this issue Feb 22, 2024 · 6 comments

Comments

@qu1queee
Copy link
Contributor

  • 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 Feb 22, 2024

@SaschaSchwarze0
Copy link
Member

v0.13:

@SaschaSchwarze0
Copy link
Member

v0.13

  • Documentation sync
    • Adam: we should do a sync, if necessary manually
    • Adam: will check with RedHat information developers
  • Dependencies:
    • Sascha has opened an issue for Build -> Adam: versions there make sense
    • Adam: need an issue for Operator to update the versions as well -> Adam will open it
    • Sascha: will open issue for CLI
  • Blog Post
    • Content-wise: Beta API, maybe the vulnerability scanning
  • CLI
    • Adam: we may need deprecation when we remove things, maybe we then have some conversion-style thing in the CLI as well -> Sascha: for me it sounds like aliases
    • Adam: with things like Dockerfile removed, we require parameters support, minimum: single value, then arrays, last configmap / secret values -> should be a separate issue, Sascha will create it
    • Adam: but should not block v0.13

Release branching

  • SHIP is merged
    • Adam: will spike a little bit in my own fork

Vulnscan not part of Alpha

  • With the Beta controller reconciling things, do we stop adding new features to the Alpha CRDs ?
    • Adam/Sascha: yes, let's keep new features in Beta

Ayush: how to address shipwright-io/operator#181 ?

  • The code needs to check if the cluster role and cluster role binding shipwright-build-webhook exist, and delete them if they exist (or simply issue a delete and ignore the NotFound error)
  • Will be a general mechanism that we delete old things, more could be coming in the future

Most Valuable Contributor

  • Adam will send an email. Nominations can come in until Friday. Nominees will be shared in next week's community meeting. Then voting happens.

/done

@SaschaSchwarze0
Copy link
Member

/close

@openshift-ci openshift-ci bot closed this as completed Feb 26, 2024
Copy link

openshift-ci bot commented Feb 26, 2024

@SaschaSchwarze0: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@adambkaplan
Copy link
Member

Shipwright Most Valuable Contributor nomination form: https://forms.gle/x6H2RiKovajQSVLx6

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