January 25th, 2021 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 smile 😸

[qu1queee]

• Follow-ups from last community session. January 11, 2021 Community Meeting #528 (comment)
• Shipwright/Build Roadmap 2021: https://docs.google.com/document/d/1yd7h7iN4yVGr910X1WcaveeIs6fNt9mPTklk8yGEmHE/edit?usp=sharing
  

[HeavyWombat]

Thoughts on pure refactoring work: The Go Reports card shows that we have some functions with high cycle count (basically a lot of if, switch, and for constructs). Reducing the gocyclo count of functions will lead to more readability and helps new contributors when touching the code base the first time. What are our thoughts on that? Nice? Waste of time? Feedback highly appreciated.

Source: https://en.wikipedia.org/wiki/Sea_cucumber

[HeavyWombat]

With regards to PR #538, should we make sanity checks such as spell checking, Go linter mandatory by adding it as a GitHub Action?

Source: https://www.reddit.com/r/FallenOrder/comments/f3uko0/4k_oggdo_bogdo/

[adambkaplan]

Regarding roadmap, I prepared this slide deck. I think @qu1queee and I are more or less on the same page.

https://docs.google.com/presentation/d/1TJXIloUyhxU608x36jKRxR7bNL28T7jvg724HnhKA3s/edit?usp=sharing

[qu1queee]

Meeting minutes:

• Linter Makefile target to become mandatory per PR. We need an issue for this. @HeavyWombat could you help driving this one?
• For the gocyclo validations, we should eventually fix this, but this is not a priority neither something to enforce on a PR basis.
• We went through RoadMap 2021 . Community is encouraged to revisit this document and to provide feedback. We briefly discuss this document, mainly around:
  • 2020 leftovers and what we need to finish, in order to ship a v0.3.0 release.
  • 2021 must-have´s, this goes around different topics, like Security,Maintenance, Features, CLI, Docs, etc.
• We discuss the usage of operator-sdk, where we see a value on reducing it. Currently it is mainly used for e2e tests, so we would like to have a different approach here that does not require it. @SaschaSchwarze0 could you help creating such issue please?
• We need an issue to track the automation of releases shipment. @qu1queee to do this. @zhangtbj fyi.
• @sbose78 to help us to make the community calls public. We have a related PR open.
• We discuss that the intention of a CLI is to abstract as much as possible the usage of the Build API, and to provide more features on top, like retrieving logs. @sbose78 pls add more info if needed.

[qu1queee]

Im closing this issue, I generated new issues based on #535 (comment) . Thanks all.