2024-07-08 Meeting notes
- Craig McNally
- Ingolf Kuss
- Jenn Colt
Date
Attendees
- Craig McNally
- Jenn Colt
- Maccabee Levine
- Jason Root
- Florian Gleixner
- Marc Johnson
- Tod Olson
- Ingolf Kuss
- Patrick Pace (Unlicensed)
- Taras Spashchenko
- VBar
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 1 min | Scribe | All | Jason Root is next, followed by Jakub Skoczen Reminder: Please copy/paste the Zoom chat into the notes. If you miss it, this is saved along with the meeting recording, but having it here has benefits. |
| 5-10 min | Liaison Updates |
| |
| 5 min | RFC Retro | All | We had a productive retrospective last week, Several discussion topics were identified, which we need to allocate some time for... Retro Board: https://easyretro.io/publicboard/dY8fCRqguiSDP3wtvSLhNzlULdM2/1cf104bb-6aa4-4eb3-a878-0f9f1e235436 It's probably worth reviewing if you weren't present. Using this Wed time slot to discuss. |
| 1 min | Upcoming Meetings | All |
|
| 5-10 min | TCR Board Review | All |
|
| 5 min | Technical Council Sub-Groups Updates | All | Static Code Analysis: Have not met the last 2 weeks - no news. Ingolf Kuss may revive in August, maybe by the 12th? Dev Documentation: Jeremy we believe will want to continue to meet. Meeting with David C next week |
| 1 min | RFCs | All | Reminder(s)
|
| 1 min | Developer Advocate Update | Patrick Pace (Unlicensed) | Waiting on permissions issue with Geo Management Services Board. Proposed structure for developer documentation update forthcoming |
| 1 min | Decision Log | All | Need to log decisions for the following: (see above)
|
| Time Permitting | All | Check Recurring Calendar Orchid has not been moved from Active to Archived | |
| 5-10 min | Reference Data Upgrade | In the Sys Ops SIG meeting the topic of Reference Data Upgrades came up. The SIG thinks that the solution of this problem for mod-inventory-storage is not enough, but that this problem needs to be solved in a general way, for all modules. There has been a long discussion 3-4 years ago about how FOLIO should handle reference data upon upgrades. See these links for background:
Notes: Marc Johnson points out he remembers a difference set of formal processes for this from the previous subgroup Jason R. asks if the issue is that you cannot specify per-module what type of data to load, or that no matter what is specified the upgrade process overrides it Marc mentions that the proposal to correct this by Vince is a very involved and complex workflow. There has been no developer resources allocated to correct this issue and address the proposal No easy solution to this problem because the original default data is lost to time and change Will reach out to Julian Ladisch when he returns | |
| 5 min | PR Templates | Maccabee Levine | Maccabee Levine took an action item last week to follow up with dev community about PR templates. Any update? Circle back on this, discuss next steps with the developer who raised this in next Monday's meeting |
| NA | Zoom Chat | Here are the notes: Jeremy rolling off TC doesn't necessarily mean he was dropping the subgroups. Worth asking. 11:10:48 From Ingolf Kuss to Everyone: Ok. I will make sure to include him in the Group. 11:18:07 From Marc Johnson to Everyone: IIRC Jakub is out for the whole of July 11:30:09 From Ingolf Kuss to Everyone: https://folio-org.atlassian.net/wiki/x/wxdN 11:42:09 From Craig McNally to Everyone: My recollection is that the proposal on the screen was approved by the TC (years ago), and stalled on finding someone to do a POC. 11:44:28 From Craig McNally to Everyone: Eureka does not solve this problem. 11:45:07 From Marc Johnson to Everyone: Reacted to "My recollection is t…" with 👍 11:45:08 From Ingolf Kuss to Everyone: Let's find a solution which is agnostic to Eureka / Okapi or whatever 11:45:33 From Craig McNally to Everyone: In Eureka, we don't have OKAPI's install endpoint (or OKAPI at all), but instead we have manager services which provide similar functionality (e.g. enable these applications for this tenant). That results in the module _tenant API calls, which is where reference and sample data is loaded. 11:45:38 From Marc Johnson to Everyone: Reacted to "In Eureka, we don't …" with 👍 11:46:46 From Marc Johnson to Everyone: What Jason describes is similar to what I recall EBSCO doing and what the proposal attempts to systematise 11:50:41 From Craig McNally to Everyone: It would be helpful to have someone who's involved in that work join us and describe the approach they're taking in circuliation 11:50:54 From Ingolf Kuss to Everyone: For mod-circulation-storage, there are currently two Jira issues which are being worked on, one for the Poppy release, the other one for the Quesnelia release: https://folio-org.atlassian.net/browse/CIRCSTORE-517 https://folio-org.atlassian.net/browse/CIRCSTORE-516 11:52:08 From Marc Johnson to Everyone: Reacted to "It would be helpful …" with 👍 |
Topic Backlog | ||
| Decision Log Review | All | Review decisions that are in progress. Can any of them be accepted? rejected? |
| Translation Subgroup | All | Since we're having trouble finding volunteers for a subgroup, maybe we can make progress during a dedicated discussion session? |
| Communicating Breaking Changes | All | Currently there is a PoC, developed by Maccabee Levine, of a utility to catalog Github PRs that have been labeled with the "breaking change" label. We would like to get developer feedback on the feasibility of this label being used more often, and the usefulness of this utility. |
| Officially Supported Technologies - Upkeep | All | Previous Notes:
Stripes architecture group has some questions about the Poppy release. Zak: A handshake between developers, dev ops and the TC. Who makes that decision and how do we pass along that knowledge ? E.g. changes in Nodes and in the UI boxes. How to communicate this ? We have a large number of teams, all have to be aware of it. TC should be alerted that changes are happening. We have a couple of dedicated channels for that. Most dev ops have subscribed to these channels. How can dev ops folk raise issues to the next level of community awareness ? There hasn't been a specific piece of TC to move that along. Craig: There is a fourth group, "Capacity Planning" or "Release Planning". Slack is the de facto communication channel. There are no objections to using Slack. An example is the Java 17 RFC. Craig: The TC gets it on the agenda and we will discuss it. The TC gets the final say. Marc Johnson: We shouldn’t use the DevOps Channel. The dev ops folks have made it clear that it should only be used for support requests made to them. Jakub: Our responsibility is to avoid piling up technical debt. Marc: Some set of people have to actually make the call. Who lowers the chequered flag ? Craig: It needs to ultimately come to the TC at least for awareness. There is a missing piece. Capacity Planning needs to provide input here. Marc: Stakeholders / Capacity Planning could make that decision. Who makes the decision ? Is it the government or is it some parts of the body ? Marc: the developers community, the dev ops community and sys ops are involved. For example the Spring Framework discussion or the Java 17 discussion. But it was completely separate to the TC decision. It is a coordination and communication effort. Marc: Maybe the TC needs to let go that they are the decision makers so that they be a moderating group. Jakub: I agree with Marc. But we are not a system operating group. Dependency management should be in the responsibility of Release management. There are structures in the project for that. Jason Root: I agree with Jakub and with Marc also. Policies should drive operational/release/support aspects of Folio. Jason Root: If the idea of “support” is that frameworks are supported, then of course the project should meet that. Marc Johnson Craig: This is a topic for the next Monday session. Craig to see if Oleksii Petrenko could join us to discuss the process for updating the officially supported technologies lists. |
| Dev Documentation Visibility | All | Possible topic/activity for a Wednesday session: Discuss/brainstorm:
|
| API linting within our backend modules | All | https://folio-project.slack.com/archives/CAQ7L02PP/p1713343461518409 |
| PR Templates | All | https://folio-project.slack.com/archives/CAQ7L02PP/p1713445649504769 Hello team, Small request to consider. Regarding pr templates.
What I suggest is that, pr template shouldn't be any instructions, because most developer who are creating pr have already understand the rules. If we put just two section into template, it will encourage developers to write more about their work and that lead to knowledge sharing among developers. |
| Java 21 | All | https://folio-project.slack.com/archives/CAQ7L02PP/p1713445764285349 Is Tech Council considering to update to java 21, I head good things from Netflix engineering teams about Garbage collector |
| Proposed Mod Kafka | All | https://folio-project.slack.com/archives/CAQ7L02PP/p1714471592534689 Mike Taylor Proposal. If and only if a FOLIO instance is running Kafka, it should insert and enable a module called mod-kafka, which consists entirely of a module descriptor that says it provides the interface kafka. The purpose is so that other modules can use the standard <IfInterface> and similar tools to determine whether they should attempt Kafka operations. Rationale: the FOLIO ILS depends absolutely on Kafka, but other uses of the platform will not. One such example: a dev platform that includes only mod-users, used as a source of change events for Metadb. |