| Time | Item | Who | Notes |
|---|
| Official security support policy on releases |
| Security team needs - How many releases from now has to be supported? (3-4 releases or less?)
- Priority/Risk will likely factor into this as well.
- Also a matter of capacity
- Should be raised to the PC → Axel can bring this with a paper/proposal to the PC - not yet.
- Probably want to bring this to the TC as well at some point, even if only for awareness.
- WOLFcon session?
- Axel will produce a paper that outlines that problem by next weeks meeting.
- Chris to ask his stakeholders about TAMU needs - not specifically, but has started to have some conversations
- https://docs.google.com/document/d/1Un5OlutEh7M2p3AzxE8g20NmdeEhrC0KCNkfd_QLkRw
- Continue discussion from slack... Spring Boot LTS
- We need to communicate the expectation better - e.g. add something to the platform release notes indicate how long P1 security issues will be backported to that release.
- As long as we upgrade to the latest LTS release of Spring Boot in each flower release, we should be in decent shape - only ~1 mo. where we're running a version of Spring boot that's no longer supported.
- Note that we're currently a bit behind with this, even if we upgrade edge modules, etc. in a Lotus HF, kiwi and Juniper will be running older, unsupported versions for some period of time. Going forward we'll need to be diligent about this to avoid getting into this situation again.
- Update? Have we added anything to the MG release notes?
- Not yet... Craig McNally will refresh his memory on what we agreed to at previous meetings and will send out a strawman message in the slack channel for review.
Today: - Textproposal:
Morning Glory will receive security fixes for critical issues until Orchid is released (est. Spring 2023).
Detailed information on particular issues will be provided by the security team. With this release there will be no other security hotfixes on Kiwi.
|
5 min | Update on | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | FOLIO-3317 |
|---|
|
| Axel | - Axel Dörrer Should be removed from week to week agenda and Axel will monitor for progress and report back
- MODEUS-139 has been moved to the next sprint
- Axel Dörrer waiting to hear back from Ann-Marie B. about the data-import ticket ... maybe target Nolana?
Today: - Defer update until next week since Axel Dörrer is out todayLeipzig Devs mentioned that filling up memory can not only be solved by a limit on uploads. It also should consider multiple simultainous uploads as scenario.
- Axel Dörrer to check back with dev what other possibilities of implementation could be.
|
| 5-10 min | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | RMB-902 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | OKAPI-1081 |
|---|
|
| Team | Notes from previous weeks: Discussions are ongoing, currently blocked on a decision being made. - Document the options on the wiki to facilitate these discussions and the decision making process.
- By this group? By the TC?
- How do we constrain the module names? If so, where/how?
- Various restrictions: Postgres, Hosting infrastructure (Kubernetes/ECS/etc.)
- What about the tenantId restrictions?
- Also part of the above discussion/decision.
- Some design choices have been suggested.
- Julian Ladisch to raise awareness of Tenant Id and Module Name Restrictions via posting to #sys-ops and #development slack channels
- Conversation is still in progress, there has been feedback from several people
- In general, it seems most agree with the proposal
- Maybe some minor adjustments are needed.
Today: | 5-10 min | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | STCLI-190 |
|---|
|
| Team | Notes from previous weeks: There's a PR that hasn't' moved in a while... What's the status? How do we move this forward? Was there another PR against stripes-testing? - ui-test:94 Was merged, a problem was reported, leading to this being reverted.
- Appears to be an environmental problem.
- The JIRA is now unassigned... it isn't clear who has the ball here.
- Added a comment to STCLI-190 tagging Khalilah, Ryan, and Zak
- This PR has been reverted because of issues with the included changes of kopy version. The idea is to exclude the kopy changes by now to move forward with this.
- Last week:
- No movement, but a PR should be coming soon.
- Conversations are ongoing within the Stripes Arch. group.
- Maybe replace kopy with something else that's better maintained
- Maybe roll our own replacement
Today: - Merged this week.
- Zak updated kopy version (one major version)
- Conversation is still in progress
- Might be adressed in TC
|
| 5-10 min | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MSEARCH-357 |
|---|
|
| Team | have we heard anything from the mod-search devs on this? Is it possible to use the openSearch client, or possibly make it configurable which client is used?
Today: - Seems to be possible to migrate to OpenSearch. Might be moved higher in the Spitfire Backlog
|
| 5-10 min | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODEXPW-67 |
|---|
|
/ | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODEXPS-109 |
|---|
|
/ | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | FOLIO-3448 |
|---|
|
| Team | Has there been any progress here? Last week it was noted that there was a slack conversation started about this. Need to check in on Oleksandr Bozhko's progress (he's was investigating the problem.Today: - no news in the last 7 days... Craig McNally to nudge him and see where this stands.
Today: - Open PR on FOLIO-3448 (Documentation as a warning for developers)
- Craig McNally to check if a new Jira has to be created for that and push on that
|
| 5 min | edge-lti-courses | Team | edge-lti-courses has been unmaintained since July 2021. Open Jiras: | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| columnIds | issuekey,summary,created,updated,assignee,priority,status |
|---|
| columns | key,summary,created,updated,assignee,priority,status |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | key in (MODCR-81, MODCR-80, MODCR-78) |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
|
TodayLast updates: - No real news here... Erin N. mentioned that she'll raise this with the staff at Duke. Maybe someone there can support these modules.
Today:
- Let's give it another week and then we might consider to move this out of the folio repo since there is no maintainer
|
* | Review the Kanban board. | Team | - There are several JIRAs on our board that haven't moved in a long time (well over a year in some cases...)
- Do we want to possibly close these as won't do?
- Craig McNally to look into how we can sort the board by last updated date, making it easier to see what's been lingering
|