Skip to end of banner

Go to start of banner

2024-01-10 - Officially Supported Technologies

Skip to end of metadata

Created by Craig McNally, last modified on Jan 10, 2024

Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Date

10 Jan 2024

Attendees

Discussion items

Time	Item	Who	Notes
1 min	Scribe	All	Jenn Colt is next, followed by Florian Gleixner, then Jeremy Huff 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	Distributed vs Centralized Configuration	Florian Gleixner	Present abstract for RFC: https://github.com/folio-org/rfcs/pull/23 This RFC is about configuration options in FOLIO. It describes where to put configurations. The goal is to drop mod configuration due to security. It proposes favoring distributed configuration over the centralized configuration. It proposes that mod-configuration should not be used until the R release. The RFC suggests that a some exceptions might be made for centralized configuration. The RFC lays out a timing for migration. Tod: Central configuration could be used in cases where modules do not have storage. E.G. z39.50 or other edge modules. Craig: That is a good point, and the UI consumes these configu
5-10 min	Go programming language for backend development	Jakub Skoczen / Mike Taylor	Present abstract for RFC: https://github.com/folio-org/rfcs/pull/25
*	Officially Supported Technologies Upkeep	All	Some items on this page are accompanied by specific versions or version ranges, while others are not. Discuss whether or not we want to make this more consistent, or at least make it more clear when a version should be specified. The primary concern likely has to do with how these pages are expected to be used. There are at least a few different use cases includes, but not limited to: During the TCR process to verify that the module under review isn't introducing new technologies, or incompatible versions of technologies already on the list. To track/plan upgrades of dependencies to ensure we're using supported versions (security implications) ...
NA	Zoom Chat

Topic Backlog
Decision Log Review	All	Review decisions which 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	Since we're having trouble finding volunteers for a subgroup, maybe we can make progress during a dedicated discussion session?
Officially Supported Technologies - Upkeep	All	Previous Notes: A workflow for these pages. When do they transition from one state to another. Do we even need statuses at all ? 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 Some group needs to inform OleksAii when a relevant policy event occurs. These documents effectively ARE the manifestation of the policy. 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: Ideas for the type of developer-facing documentation we think would be most helpful for new developers How we might bring existing documentation up to date and ensure it's consistent etc.

Action Items

No labels