Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TSC Meeting (05 Apr 2022): Scalyr Monitoring, AWS cost reduction, v3.7.0 release #99

Closed
3 of 7 tasks
arm4b opened this issue Mar 30, 2022 · 2 comments
Closed
3 of 7 tasks
Assignees
Labels
TSC:meeting StackStorm Technical Steering Committee Meetings related topics

Comments

@arm4b
Copy link
Member

arm4b commented Mar 30, 2022

April 2022 @StackStorm/tsc 1 hour planned meeting: Tuesday, 05 Apr 2022, 09:30 AM US Pacific.

See #33 for more info on how to join.
(TLDR; Zoom link: https://us02web.zoom.us/j/81082101702?pwd=N1V4TWdYRVQ4SXBsaFh1TFYvVDA0UT09)

Meeting host: @cognifloyd

Meeting Agenda

Demo: migration to Scalyr monitoring for internal st2cicd infra by @Kami ~(10min)

TSC Meeting host rotation ~(5min)

  • Proposal: document in the Governance TSC Meeting host rotation

StackStorm AWS cost-reduction project ~(15min)

StackStorm v3.7.0 release preparation ~(20min)

ST2 Security/Maintenance Project ~(10min)

@arm4b arm4b added the TSC:meeting StackStorm Technical Steering Committee Meetings related topics label Mar 30, 2022
@cognifloyd
Copy link
Member

cognifloyd commented Apr 5, 2022

Meeting notes

Demo: migration to Scalyr monitoring for internal st2cicd infra by @Kami

Skipped. @Kami was unable to attend.

TSC Meeting host rotation

StackStorm AWS cost-reduction project

StackStorm v3.7.0 release preparation

Target master feature freeze date: 15 April 2022
Target release week: 18-22 April 2022

Highlight awesome recent contributions

TSC maintainers need to review these new contributors/maintainers:

ST2 Security/Maintenance Project

Things are improving:

  • All TSC members now have 2FA enabled
  • StackStorm-Exchange migrated to Github Actions with a much better security profile than how we managed things in CircleCI

Discussed "Require 2 reviews per PR for critical st2 repos"

  • Drawing the line between what is and is not critical is a sticky question. eg what about the st2-rbac repo where we include the master branch at release time?
  • Eugen defined "critical": The repos that build/push artifacts to PackageCloud (st2, st2chatops, st2-packages)
  • Agreed: Increase required reviews on st2 repo this month. Review in next TSC meeting.
    • @armab to increase required review count on st2 repo to 2.
  • Agreed: 2 reviews not required on docs repo for security. It would still be nice for quality control.
  • TSC members need to review things they are not familiar with to become more familiar and spread knowledge. But we also need to make sure someone else that knows that section of code also reviews it.
  • Several people noted that just increasing the required reviews count does not make those reviews actually focus on security. So, we need to document and build culture around including security in reviews.
  • Using Github's CODEOWNERS feature may be part of ensuring some people review key sections, but that's more for vision/performance of certain pieces, not necessarily for security.

Highlight issues for next meeting

  • Migrating AWS parent org
  • When to drop Python 3.6 / change OS Support matrix

Draft Agenda for next meeting on 03 May 2022

Demo: migration to Scalyr monitoring for internal st2cicd infra by @Kami ~(10min)

Plan migration of AWS parent org to Oncore ~(15min)

Discuss plan for dropping python 3.6 / OS support matrix ~(15 min)

  • Python 3.8 is not available in CentOS 7 without building/distributing our own.
  • Is there a way to divorce our requirements from OS platforms and focus more on supporting various python versions? (3.9, 3.10)

Recap on releasing v3.7.0 / Begin planning v3.8.0 ~(10 min)

  • How did the release go? Lessons learned?
  • Who is going to be release manager + assistant release manager for v3.8.0?

ST2 Security/Maintenance Project ~(10 min)

@cognifloyd cognifloyd self-assigned this Apr 5, 2022
@arm4b
Copy link
Member Author

arm4b commented Apr 5, 2022

Meeting attendees for the record.

TSC Meeting Host:

@StackStorm/maintainers & @StackStorm/contributors:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TSC:meeting StackStorm Technical Steering Committee Meetings related topics
Projects
None yet
Development

No branches or pull requests

2 participants