finos / finos/devops-automation

SDLC Framework WG Bi-weekly call - September 29th

Open
#271 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
79
Forks
20
PR merge metrics
No merged PRs in 30d

Description

## Date

Monday 29th SEIP 2025 - 1000 EST / 1500UK

## Untracked attendees

| Name | Firm | Comment |
| :--- | :--- | :------ |

## Meeting notices
- FINOS **Project leads** are responsible for observing the FINOS guidelines for [running project meetings](https://community.finos.org/docs/governance/meeting-procedures/). Project maintainers can find additional resources in the [FINOS Maintainers Cheatsheet](https://community.finos.org/docs/finos-maintainers-cheatsheet).

- **All participants** in FINOS project meetings are subject to the [LF Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), the [FINOS Community Code of Conduct](https://community.finos.org/docs/governance/code-of-conduct) and all other [FINOS policies](https://community.finos.org/docs/governance/#policies).

- FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

- FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

## Agenda

- [x] Convene, roll call, welcome new people
- [x] Approve previous meeting minutes
- [x] Review slide for all community call (@aaronsearle)
- [x] WOW: Should we use the DevOps SIG [project board](https://github.com/orgs/finos/projects/64/views/1) to track work?
- [x] WOW: Should we use the same tech stack as the ai readiness project? https://github.com/finos/ai-governance-framework/blob/main/DEVELOPMENT.md
- [x] Cover the repo at https://github.com/finos-labs/SDLC-Controls-Framework
- [x] Cover the previous week's workshop minutes (https://github.com/finos-labs/SDLC-Controls-Framework/issues/1)
- [x] AOB, Q&A & Adjourn (5mins)

## Decisions Made

- [x] We will create a project board and track issues in the [SDLC Controls repo](https://github.com/finos-labs/SDLC-Controls-Framework/issues)
- [x] We will use the same tech stack as the ai readiness project? https://github.com/finos/ai-governance-framework/blob/main/DEVELOPMENT.md
- [x] We will use the sdlc-framework@lists.finos.org mailing list for announcements.

## Action Items

- [ ] Document how to sign up for mailing list (@karlmoll)

### Zoom info

([https://zoom-lfx.platform.linuxfoundation.org/meeting/96292319760?password=a023f03e-c2aa-46fb-aae3-5d93c9d9664e](https://www.google.com/url?q=https://zoom-lfx.platform.linuxfoundation.org/meeting/96292319760?password%3Da023f03e-c2aa-46fb-aae3-5d93c9d9664e&sa=D&source=calendar&ust=1757777213776791&usg=AOvVaw0aXjuGuIloQBmqHhBtS7BM))

**Join Zoom Meeting**
- https://zoom.us/j/94904595244
- Meeting ID: 949 0459 5244
- Passcode: 545224
- Find your local number: https://zoom.us/u/aesEqmNODb

**Github Repo:** https://github.com/finos/devops-automation/

**Project Board:** https://github.com/orgs/finos/projects/33

**Mailing List:** Email devops-mutualization+subscribe@finos.org to subscribe to our mailing list

Contributor guide

Open the contributing guide

Research direction

Start with the Action Items section and the mailing-list details at the bottom of the issue. No target documentation file is named, so confirm the intended location and whether the existing subscription address is still valid. Done means the sign-up process is documented and linked from the appropriate project documentation.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.