TSC Meeting (07 Dec 2021): New Contributors, v3.6.0 Recap, v3.7.0 Planning, EOY

[arm4b]

December 2021 @StackStorm/tsc 1 hour planned meeting: Tuesday, 07 Dec 2021, 09:30 AM US Pacific.
See #33 for more info about how to join.

TSC Meeting Host: @armab

Meeting Agenda

New Contributors

• @rush-skills Add Ankur Singh (@rush-skills) as a StackStorm Contributor st2#5449
• @khushboobhatia01 Add Khushboo Bhatia (@khushboobhatia01) as a Contributor st2#5450
• @xod442 Add Rick Kauffman (@xod442) as a Contributor st2#5452

Idea: rename repo stackstorm/discussions -> stackstorm/community?

Idea: 360 all-to-all anonymous TSC team feedback for 2021. Would it be helpful?

StackStorm v3.6.0 released!

• Release Manager: @winem & Release Assistant: @guzzijones to give a summary & recap about the finished release.
• Any post-release tasks, technical debt left?

StackStorm v3.7.0 preliminary release planning

• Release Manager & Assistant: WHO from @StackStorm/maintainers?
• Project & Roadmap: https://github.com/orgs/StackStorm/projects/23
  • EL8: py3.6 -> py3.8 upgrade
  • anything else?

Brainstorming: StackStorm Maintenance & Security

• Discuss security tasks/ideas in the project: https://github.com/orgs/StackStorm/projects/25

StackStorm moments of the year

• Think about an impactful fact or 👍 st2 moment that happened this year, share it with the team

---

^^ @StackStorm/tsc & @StackStorm/contributors

[arm4b]

Participants

Attendees:

• @StackStorm/maintainers: @armab @amanda11 @m4dcoder @winem @cognifloyd @nzlosh @guzzijones
• @StackStorm/contributors: @arms11 @rush-skills

Meeting Minutes

New Contributors

• Thanks, @rush-skills, @khushboobhatia01, @xod442 for their contributions, and welcome to the Community!
• @rush-skills introduced himself and highlighted the automation he does at @CERN and the use of StackStorm.

Idea: Rename repo stackstorm/discussions -> stackstorm/community

• Fact 1. The old forum.stackstorm.com was replaced with the new Github Q/A Discussions: https://github.com/StackStorm/st2/discussions.
• Fact 2. We use https://github.com/StackStorm/discussions/ for general technical discussions, RFC, TSC meetings, Design, Proposals, Roadmap.
• DECIDED: To avoid confusion with the Github Q/A Discussions (https://github.com/StackStorm/st2/discussions), we'll reame https://github.com/StackStorm/discussions/ to https://github.com/StackStorm/community/

Idea: 360 all-to-all anonymous TSC peer team feedback for 2021. Would it be helpful?

Meeting consensus: provide improvements feedback every time when needed depending on the situation or case. Shout-out to the community or TSC when someone does a great job.

StackStorm v3.6.0 released

• Per @winem, the release is technically out. Still needs a Blog Post announcement.
• Per @guzzijones, there's a pending CVE request awaiting confirmation from upstream. Blocking the Blog Post announcement.
• Based on the fresh bug report (Executions stuck with "requested" status) Executions can not be proceeded with errors in st2actionrunner and st2scheduler st2#5483, we might need v3.6.1 patch (fix: Executions can not be proceeded with errors in st2actionrunner and st2scheduler st2#5483).
  • TODO: @StackStorm/maintainers check the blast radius if the issue is present only with etcd coordination backend or it's an issue with default Redis backend as well?

StackStorm v3.7.0 preliminary release planning

• Project: https://github.com/orgs/StackStorm/projects/23
• Leftover from v3.6.0: Upgrade RabbitMQ #91. Only Puppet-st2 left. @rush-skills volunteered to help with the update: Install RabbitMQ from official repository puppet-st2#340
• Py 3.6 -> 3.8 update for EL8
• CentOS 8 EOL end 2021 #88 plan created by @amanda11
  • TBD: Agree which distro we'll use: RockyLinux or AlmaLinx or Oracle Linux as a replacement for CentOS8.
  • @StackStorm/tsc and @StackStorm/contributors will do the homework before the next TSC meeting to have opinions about the distro we'll use for producing EL8-compatible artifacts, as well as testing and CI/CD
• TODO next TSC meeting: Reiterate on v3.7.0 planning

Brainstorming: StackStorm Maintenance & Security

• Discuss the security enhancements around the StackStorm Open Source project: https://github.com/orgs/StackStorm/projects/25
  • Discussed: Migrate StackStorm blog and CMS to GH Static Pages #76 (moved to in progress)
  • Discussed: [RFC] Use Github Actions for StackStorm-Exchange CI and Maintenance #63 (moved to in progress)
• TODO next TSC meeting: Continue discussing and triaging ideas in https://github.com/orgs/StackStorm/projects/25

StackStorm moments of the year

The team highlighted some of the moments and memories from the year:

• A bummer of the year: @blag leaving the project
• A growing open-source community with new Maintainers, Contributors and Adoption
• Still not good, we can do better: time to review/merge for the community-contributed PRs
• Lots of Releases, Support, Bugfixes, Maintenance, and hard work TSC put together as a team
• @Kami doing one of the most significant performance speed-up impacts for the project
• Transition to the LF governance and the expansion of the ecosystem