-
-
Notifications
You must be signed in to change notification settings - Fork 3
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 (10 Oct 2023) - Fixing builds, Upstream dependencies, stackstorm.com, Python difficulties, new OS support #125
Comments
I'm excited to announce that we're doing a StackStorm training at the end of the month: |
Minutes for the meeting are now available. |
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. |
as agreed I'll shadow @dalesmith as he uses Evelenty to update StackStorm.com per #123. |
@FileMagic Thanks for looking at that! Replied in your Slack thread. |
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. |
Very helpful, thanks a lot @setswei |
October 2023 @StackStorm/tsc
1 hour
meeting:Tuesday, 10 October 2023, 09:30 AM US Pacific / 06:30 PM EU CET
Meeting Agenda
Fixing the 🔴 broken st2 builds (help wanted, needs volunteers) (10mins)
WIP: Let's fix the builds (Updated 06 Nov):
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 involvedv3.9.0
?WIP: Let's fix security (Updated 06 Nov):
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)
See Add ability to use AL2 as base OS for Stackstorm (ST2) #6016. What's involved to add a new OS? What could be the blockers? @khushboobhatia01 able to assist on this? (the original issue was raised by her colleague?)
Other OS-level support topics:
Using Eleventy vs Hugo for stackstorm.com website templating (10mins)
We've migrated from Wordpress to GH static pages (Migrate StackStorm blog and CMS to GH Static Pages #76) for better security, allow community to add new content (blogs, website updates) via PR and TSC reviews/approval. It works as https://github.com/stackStorm/stackstorm.com -> stackstorm.com, but uses raw HTML which is harder to manage. Having a template engine for static HTML generation would be better (Hugo template for stackstorm.com #4, Enable Netlify integration (preview) #3) and these tasks were not finished.
Dale Smith proposed to Restart Static Site Migration Using Eleventy and CloudCannon #123.
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
orHugo
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
.The text was updated successfully, but these errors were encountered: