September 14th, 2020 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 😄

[HeavyWombat]

For some of the work I did recently around build, I needed a way to quickly and easily create a bit of load. I ported one of our helper scripts into a Go program to be able to make it more convenient to use. At the moment, it supports creating n parallel buildruns by directly creating the respective kube resources (build, buildruns), including clean-up. It also has a mode to ramp up more and more parallel builds. So we were wondering if this tool is something that others might also find useful and that we would open-source into https://github.com/shipwright-io.

[adambkaplan]

• Logo - what do we like? Build logo icon Design #325
• CLI - agreement on name CLI #382
• Samples - Organize samples #366

Source: https://en.wikipedia.org/wiki/Penguin#/media/File:South_Shetland-2016-Deception_Island%E2%80%93Chinstrap_penguin_(Pygoscelis_antarctica)_04.jpg

[HeavyWombat]

With regards to #387, it was @SaschaSchwarze0 that brought up the good question whether we should not just add the tags, but actually create the client code into our project. It seems Tekton is doing it like that.

[qu1queee]

Would like to discuss #368

[zhangtbj]

Also would like to know if there is any new update for shipwright build controller for OpenShift

[qu1queee]

Meeting minutes:

• @HeavyWombat will share more examples on the performance tool and also a proposal around this in this repository. See proposals format
• @adambkaplan to get another round of logos where we can get something that illustrates more the fact that we are "building" something. The ship latest logo in general is well perceived by the team.
• @otaviof to open a new proposal around the name for the "build" CLI. See proposals format
• We discussed around how to implement Organize samples #366 and ideas around it. @adambkaplan will generate
• We discussed around the implementation of gen-code vs dynamic go client. Generated code is preferred based on https://www.openshift.com/blog/kubernetes-deep-dive-code-generation-customresources , and therefore Add genclient tags to build resources #387 . The blog have a nice explanation on how this works.
• We decided to close Move the vendor folder into a new repo under the shipwright umbrella #368 while is not a polemic topic in the team, and there is no disadvantage so far on having this. @sbose78 can you pls add some context on the three points you think we should validate before we remove the /vendor dir in the future?