Apologies, this should fix the formatting issues. Iceberg Community Sync (Recorded) - November 01 VIEW RECORDING: https://www.youtube.com/watch?v=1yljcXTAOuA Meeting Purpose:
Weekly Iceberg community sync up meeting to discuss recent developments, upcoming releases, and proposals. Key Takeaways - Logo update proposed to fix artifact issue - Release process improvements proposed to better track changes - Roadmap to be tracked in GitHub issues/projects rather than static site - Style guide adoption proposed to improve documentation consistency Topics: Logo Update - Brian noticed an artifact issue on some backgrounds where there is a hole/gap at the top of the iceberg logo - This was likely introduced during logo file transfers from Netflix - Brian has mockup to fix - needs PMC approval and then follow up with Apache Branding - Goal is better consistency and representation at Apache events Release Process Improvements - Brian proposed better tracking of user-facing changes between releases, to improve release notes and documentation - Could track changes in a release-specific PR, requiring committers to log changes there - Automation could also help generate a list of changes for the release manager - General agreement this could reduce gaps, but should avoid being too burdensome Roadmap Tracking - Currently roadmap is tracked statically on the Iceberg site - Brian proposes moving it to GitHub issues/projects since that's already part of existing process - Roadmap should be the source of truth - site could potentially embed or link to GitHub - General agreement to use GitHub issues/projects more formally for roadmap tracking Documentation Style Guide - Brian proposed adopting a style guide and using a linter like Vale to improve documentation consistency - Main goals are inclusive language, consistent grammar/conjugations, capitalization - General guidance to avoid being too strict or blocking contributions - Linter warnings could be fixed periodically rather than blocking merges - Follow up on dev@ thread for additional discussion Next Steps: - Create PR with proposed logo update - Start thread on dev@ list to discuss process improvements - Migrate roadmap tracking to GitHub - Follow up on style guide proposal on dev@ thread On Thu, Dec 7, 2023 at 4:48 PM Brian Olsen <bitsondata...@gmail.com> wrote: > > Key Takeaways 0:00 Introduction 11:07 Logo update proposed to fix artifact > issue 10:38 Release process improvements proposed to better track changes > 23:50 Roadmap to be tracked in GitHub issues/projects rather than static site > 35:15 Style guide adoption proposed to improve documentation consistency > Topics Logo update 11:47 Brian noticed an artifact issue on some backgrounds > where there is a hole/gap at the top of the iceberg logo 12:00 This was > likely introduced during logo file transfers from Netflix 12:07 Brian has > mockup to fix - needs PMC approval and then follow up with Apache Branding > 13:36 Goal is better consistency and representation at Apache events - > Release Process Improvements 10:51 Brian proposed better tracking of > user-facing changes between releases, to improve release notes and > documentation 11:08 Could track changes in a release-specific PR, requiring > committers to log changes there 21:23 Automation could also help generate a > list of changes for the release manager 22:18 General agreement this could > reduce gaps, but should avoid being too burdensome - Roadmap Tracking 24:27 > Currently roadmap is tracked statically on the Iceberg site 24:31 Brian > proposes moving it to GitHub issues/projects since that's already part of > existing process 25:01 Roadmap should be the source of truth - site could > potentially embed or link to GitHub 26:11 General agreement to use GitHub > issues/projects more formally for roadmap tracking - Documentation Style > Guide 35:15 Brian proposed adopting a style guide and using a linter like > Vale to improve documentation consistency 35:15 Main goals are inclusive > language, consistent grammar/conjugations, capitalization 38:59 General > guidance to avoid being too strict or blocking contributions 39:53 Linter > warnings could be fixed periodically rather than blocking merges 22:37 Follow > up on dev@ thread for additional discussion - Next Steps: - Create PR with > proposed logo update - 22:43 Start thread on dev@ list to discuss process > improvements - Migrate roadmap tracking to GitHub - Follow up on style guide > proposal on dev@ thread
