October 19th, 2020 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 😄

[qu1queee]

• Ship a v0.1.1 release, to include the clientsets for wider usage.
• Consider usage of Conditions also for the Build CRD

[qu1queee]

Community meeting:

• We should get a v0.1.1 release to include the new Build ClientSets, this will enable other projects to consume our resources(natively) and the availability of this will become more obvious.
• We spoke about the Conditions implementation for the BuildRun. Independently of the Conditions implementation, we seem to share a concern around leveraging the "error" messages when a BuildRun fails or similar.
  • We would like to enhance the Conditions that tekton TaskRun defines
  • As @HeavyWombat pointed out, we might also increase the validations we do in the Build controller, to avoid errors that could have been detected in advance.
  • @SaschaSchwarze0 also mentioned that we could extend the strategies, to add a new step to process the errors.
  • As starters we should just get the Conditions implementation done for the BuildRun and then enhance on the Error content. @qu1queee will be generating an implementation proposal in Move to Conditions instead of Status in the BuildRun #307
• We discussed [EP] Remote Artifacts #419 with @otaviof . We believe there is yet no consensus on the terminology around "remote artifacts" and the team will revisit the proposal again. @otaviof also mentioned that for the dependencies of the remote artifact, the proposal should have a better example, instead of the jar file.
• @adambkaplan asked for help with the review of https://github.com/shipwright-io/website/pull/12/files and that the sdk bump is on the works.

Please add any other relevant information.