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