2024-06-10 Meeting notes

Date

10 Jun 2024

Attendees

Discussion items

Time	Item	Who	Notes
1 min	Scribe	All	Florian Gleixner is next, followed by Marc Johnson 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	Maccabee Levine Tod Olson Jakub Skoczen Craig McNally Jenn Colt	CC: Maccabee Levine is not here. No meeting today due to the virtual member meeting. PC: Tod Olson is not here today, no PC meeting last week RMS Group: Jakub Skoczen is not here today Security Team: Craig McNally nothing new. New member(s) are on the way to join. Tri-council Application Formalization: Jenn Colt Second half of discussion in the sysops group not yet
1 min	Upcoming Meetings	All	12 Jun 2024 - Dedicated Discussion - Topic TBD 17 Jun 2024 - Regular TC Meeting 19 Jun 2024 - Dedicated Discussion - Topic TBD - probably cancel due to holidays 24 Jun 2024 - Regular TC Meeting 26 Jun 2024 - Dedicated Discussion - Topic TBD 01 Jul 2024 - Regular TC Meeting - New Co-Chair 03 Jul 2024 - Dedicated Discussion - Topic TBD Due to holidays, we start a thread in tc-internal discussing the topics
1 min	TCR Board Review	All
5 min	Technical Council Sub-Groups Updates	All	TCR Process Improvements: Nothing new. Static code analysis: Jeremy and Ingolf met. Draft for requirements. Some more people are invited for the meeting this week Developer Documentation: Second meeting last week. Progressing well. Foundational stuff mainly atm.
1 min	RFCs	All	Application Formalization: When will we do the final review? we dont have a quorum today. We try next monday. The following Monday 17 Jun 2024
1 min	Action Items	Jeremy Huff	Jeremy Huff: Reach out to the PC concerning TCR-41
5- 10 min	Developer Advocate Service Board Preview	Patrick Pace	Patrick will demonstrate the new Jira Service board for interfacing with the Developer Advocate, to solicit feedback from the TC. https://folio-org.atlassian.net/jira/servicedesk/projects/DA Permissions need to be set up to be public usable Portal is configured (but not yet accessible) Integration in Slack will be tested Email can be sent which will create a issue
10-15 min	Application Formalization RFC	Craig McNally	We will begin the final review of the Application Formalization RFC: https://github.com/folio-org/rfcs/pull/34
5 min	SHL and NLA Dedicated Discussion Topics Review	All	2024-06-05 - SHL and NLA Dedicated Discussion Topics Monthly or quaterly meeting could be good Additional Europe-Asia timeslot would be good - probably 3am or 6am EST
1 min	Decision Log	All	Nothing new
Time Permitting	Officially Supported Technologies (OST)	All	Standing agenda item to review/discuss any requested or required changes to officially supported technology lists Today: Quesnelia OST move tag from ACTIVE to ARCHIVED Create Sunflower OST from Ramsons. Apply "Policies and Reasoning" in a extra meeting.
NA	Zoom Chat		Jenn Colt: 2024-06-10 Meeting notes There was no PC last week Yeah still only 5 Yes!

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: 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.
API linting within our backend modules	All	https://folio-project.slack.com/archives/CAQ7L02PP/p1713343461518409 Hello team, I would like to discuss API linting within our backend modules. Some time ago, we transitioned our linting process from Jenkins to GitHub Actions as outlined in https://folio-org.atlassian.net/browse/FOLIO-3678. I am assuming that this move was done via some technical council decision. Please correct me if I'm wrong. In my observations, I've found two problems: Schema linting does not occur if the schemas are in YAML format. There are issues with resolving some deeper references during API linting. Although I'm unsure about how to improve the existing linting implementations within Folio, I propose to consider an open-source solution that handles OpenAPI linting effectively and allows us to define custom rules. For your reference: https://stoplight.io/open-source/spectral A test of this solution can be found in this PR: https://github.com/folio-org/mod-search/pull/567. The same PR also provides an example of custom rule definition: https://github.com/folio-org/mod-search/pull/567/files#diff-d5da7cb43c444434994b76f3b04aa6e702c09e938de09dbc09d72569d611d9ab.Also, by employing 'Spectral', I discovered AsyncAPI (https://www.asyncapi.com/en), an API design tool similar to OpenAPI but for asynchronous interactions. I suggest that we consider using AsyncAPI in FOLIO to generate documentation for Kafka interactions.
PR Templates	All	https://folio-project.slack.com/archives/CAQ7L02PP/p1713445649504769 Hello team, Small request to consider. Regarding pr templates. From my perspective, pr template is not good idea. Even the biggest open source projects that are contributed by many people don't have any pr template. Currently what we have for acq modules https://github.com/folio-org/mod-orders-storage/blob/master/PULL_REQUEST_TEMPLATE.md These pr template is inconsistent in different teams. 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 https://www.infoq.com/presentations/netflix-java/ (edited)
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.

Date

Attendees

Action Items