You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Meeting minutes for TSC Meeting (01 Mar 2022): AWS follow-up, v3.7.0 preparation
Attendees:
Bradley Bishop
Ankur Signh
Eugen Cusmaunsa
Jacob Floyd
Amanda (amanda11)
Carlos (nzlosh)
AJ (guzzijones)
Saurav Kumar
AWS account ownership
Bradley Bishop of Encore Technology has talked internal about taking ownership of the StackStorm AWS Account (child) under the Encore Technology (parent) account.
A condition to Encore Technology taking on the StackStorm AWS account, they want to see a project plan outlining the actions the StackStorm project will take to reduce AWS operational costs.
AWS Actions
The TSC has agreed to create a Gtihub project board and fill in tasks that lead to the reduction of these costs.
Bradley is in contact with JP and will determine what day to day effort is required to manage an AWS parent account.
AJ (guzzijones) has been approved to work on StackStorm related work by his company and has offered to work on migrating API and documentation websites from AWS S3 to github pages.
Bradley offered his help with LDAP hosting in AWS if needed. Eugen suggested LDAP could be replaced with another authentication solution to help reduce AWS costs.
Bradley needs to determine how child/parent ownership works and long with other AWS details. He'd like to target mid to late June to carry out the AWS migration.
v3.7 Release Actions
Carlos (nzlosh) will be release assistant for v3.7
Carlos (nzlosh) will follow-up on issues #5152 #5143 and #4924 which are blocked in in progress.
March 2022 @StackStorm/tsc
1 hour
planned meeting: Tuesday,01 Mar 2022, 09:30 AM US Pacific
.See #33 for more info about how to join.
(TLDR; Zoom link: https://us02web.zoom.us/j/81082101702?pwd=N1V4TWdYRVQ4SXBsaFh1TFYvVDA0UT09)
Meeting host: @nzlosh
Meeting Agenda
StackStorm AWS account follow-up ~(20min)
31-July-22
, not31-March-22
as thought beforeStackStorm
v3.7.0
release preparation ~(40min)The text was updated successfully, but these errors were encountered: