Community meeting August 17th Agenda

[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 :)

• Paste the image of an animal :)

[sbose78]

#196

[sbose78]

Also, I'll provide an overview of the community-operator release process.

[zhangtbj]

Cool! 👍

One more issue is about Copyright for all codes: #336

[SaschaSchwarze0]

Encourage engineers to provide their opinion in Build controller handling of service account can lead to failing build runs and other artifacts #337.

[qu1queee]

Next steps, related to #196:

• @adambkaplan or @sbose78 to ask with OSPO around Add Copyright information in all codes #336
• move existing redhat build into https://github.com/shipwright-io
• fix CI after the migration.
• set project roles
• shipwright.io should be reserved by OSPO
• we want to have buildv2 in https://github.com/operator-framework/community-operators/ , so that is accessible from https://operatorhub.io/
• we will use https://quay.io/organization/shipwright for hosting images of the new repo.

@SaschaSchwarze0 all to provide some thoughts on #337

[adambkaplan]

@sbose78 update on image repos:

1. I have reserved docker.io/shipwrightio as an org. docker.io/shipwright was taken
2. I have likewise reserved quay.io/shipwrightio in case we want to keep org names aligned.

[zhangtbj]

Cool and Cheers!

So we already moved the repo here officially and start using this shipwright-io repo for issues and PRs, correct?