November 9th Community Meeting

[zhangtbj]

• 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 smile

[qu1queee]

• Conditions implementation
• KubeCon EU
• Local Source Code support spikes (help wanted)
  

[otaviof]

#419 -- Multiple VCS repositories support.

[qu1queee]

Community meeting minutes:

• There is some ongoing work around spiking on "local source code" support for Shipwright Build. Tekton have an open issue around this. IBM folks will be working on the spike(new issue in the backlog tbd) . @gabemontero @otaviof to provide more insights on how this was implemented for openshift build v1. In general we consider doing our own implementation for this, instead of relying on Tekton(none native implementation so far). One thing to highlight is the strong dependency of this feature to the ongoing CLI dev efforts.
• Tekton recently added support for OCI bundles, see more info . This might be relevant for us, so something to take a look.
• We discussed around efforts for evangelize the project. @adambkaplan and @qu1queee to discuss a potential submission to KubeCon EU(single one just around the pitch of building container images with shipwright/build). @adambkaplan will be generating more content on this topic via different platforms, and checking if there is the option to get some demos in k8s communities.
• We discussed that the IBM folks will be working on the adoption of Conditions for BuildRun CRD, and other enhancements like secrets error messages distinction, plus the upcoming spike from @SaschaSchwarze0 around shrinking the Buildpacks strategy to a single step.
• There is some pending work around the v1.0 milestone and the post GA one. The idea is that everyone is on the same page with the expectation for both dev cycles. @adambkaplan @qu1queee to define a new meeting(weekly/biweekly) around cards definitions. We would like to discuss some of the issue in both milestones during next community meeting. @zhangtbj @qu1queee @SaschaSchwarze0 to take a look on the post GA ones in advance.
• We discussed [EP] Remote Artifacts #419 . We should get this one merge asap. One thing to keep in mind is that for the support of multiple git sources, we would require another EP, to finalize the details around how to do this. @otaviof please correct me if I say something wrong.