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
{{ message }}
Repository navigation
TSC Meeting (10 Oct 2023) - Fixing builds, Upstream dependencies, stackstorm.com, Python difficulties, new OS support #125
Updating StackStorm dependencies and upstream CVEs (10mins)
The StackStorm's upstream dependencies need updating. Multiple projects : st2, st2chatops, st2web, orquesta, OS-level dependencies (docker). Identify dependencies to bump, update. Do we need to release a quick patch v3.8.1 afterwards before committing to a more involved v3.9.0?
Related: StackStorm project security initiatives/ideas/problems are tracked in a separated Github project: https://github.com/orgs/StackStorm/projects/25. Security-interested folks, driving the coordination on these topics would be welcome. Some of the security hardening topics were raised by Scott and Haven in the last meeting #124.
OS Support and Proposal to use Amazon Linux 2 as supported OS (10mins)
TLDR; Need to decide on the framework used for generating the stackstorn.com website from templates. Hugo - more popularity, experience by the TSC members (bus factor, maintenance burden), heavily used in DevOps/SRE repos for website generation (ex: Docker, Kubernetes). Eleventy, - Javascript/npm tool (we're moving away from Javascript where possible #8), but Dale has experience with it and can help with the migration.
Who is familiar with Evelenty or Hugo in the TSC and can assist/pair w Dale?
Future Python version (3.10) support issues, Pants builds (10mins)
See #103 as we're blocked to add new releases, new OSes having difficulties adding newer Python versions. @carlos@amanda11@cognifloyd to update on where we are, the direction and what kind of help is needed.
Community assistance wanted with adding the support for python v3.10.
I saw that you were looking for the build of the st2 project to be fixed. while reading through @guzzijones's PR from StackStorm/st2 #5995, that they fixed the tests in that PR. We could look at those updates for those changes.
@FileMagic Thanks for looking at that! Replied in your Slack thread.
Also, if there are CI fixes that are part of that PR, - makes sense to extract them first. Eg. fix the working master branch first thing.
Activity
mickmcgrath13 commentedon Oct 10, 2023
I'm excited to announce that we're doing a StackStorm training at the end of the month:
https://www.bitovi.com/events/stackstorm-training
nzlosh commentedon Oct 10, 2023
Minutes for the meeting are now available.
FileMagic commentedon Oct 10, 2023
I saw that you were looking for the build of the st2 project to be fixed. while reading through @guzzijones's PR from StackStorm/st2 #5995, that they fixed the tests in that PR. We could look at those updates for those changes.
dzimine commentedon Oct 10, 2023
as agreed I'll shadow @dalesmith as he uses Evelenty to update StackStorm.com per #123.
arm4b commentedon Oct 11, 2023
@FileMagic Thanks for looking at that! Replied in your Slack thread.
Also, if there are CI fixes that are part of that PR, - makes sense to extract them first. Eg. fix the working master branch first thing.
setswei commentedon Oct 17, 2023
Hey, I logged a PR to fix the builds on ansible-st2. Let me know if you need anything else. I added some details to the PR as to what was wrong.
arm4b commentedon Oct 18, 2023
Very helpful, thanks a lot @setswei