# Participants: - David G. - Jahia - Kevan J. - Jahia - Jonathan S. - Jahia - Jérome B. - Jahia - Jean-Baptiste O. - Unomi / Karaf - Serge H. - Inoyu - Francois G. - Jahia
# Agenda - Round table and introduction - Next release - Project roadmap and backlog - Q&A / General discussion items # Meeting minutes We started the meeting with a reminder that the goal of this meeting is to provide a regular point to discuss project status, not to make decisions. Decisions are tracked via Jira and the mailing list. We then continued with a discussion/reminder regarding community practices for projects within the Apache Foundation (more details here: https://community.apache.org/newcommitter.html and here: https://www.apache.org/dev/pmc.html#committer-management). The team was informed that it was not necessary to be a committer to contribute on Unomi Jira ticket. Jean-Baptiste informed the team about upcoming changes in Apache Karaf around resolves and the feasibility if Apache Unomi is interested, of backporting these to the version currently used by Unomi. I will let Jean-Baptiste provide more details. Regarding the Apache Unomi codebase, no releases are currently planned for the short term. However, a minor release might be triggered depending on the progress of the stories mentioned below. As mentioned in the previous meeting minutes, Serge continued working on supporting the OpenSearch client. This integration will be done in parallel with the existing Elasticsearch client and will not introduce breaking changes. Good progress was made and should soon reach a PoC stage (Ticket: UNOMI-828). Serge also mentioned some early work/thoughts around introducing the ability for Unomi itself to become multi-tenant to reduce the operating cost of Unomi environments. David noted that some work took place in 2023 (released with Unomi 2.2) to reduce the number of Elasticsearch indices and that it is already possible to mutualize Elasticsearch instances (multiple Unomi instances going toward a common Elasticsearch environment). David mentioned that Unomi itself is pretty lightweight and that there might be limited cost benefits in mutualizing. To be continued... François mentioned that on Jahia's side, three items would potentially some work: - UNOMI-851: The Elasticsearch client currently used in Apache Unomi includes a vulnerable version of jackson-dataformat. Although Unomi itself is not affected this triggers alerts by automated security scanning systems. Addressing this would require an upgrade to v7.15+ of the client but there are uncertainties regarding the license of recent versions of that library (documentation says Apache 2, source code says Elastic. François opened a ticket with Elasticsearch for clarification (https://github.com/elastic/elasticsearch/issues/112827) - UNOMI-852: The team would like to integrate more useful data in Unomi production logs when events are rejected (such as the type of the event), but there are concerns about exposing Unomi to log injection if this was done “as-is”. Jahia (the product) implemented a mechanism whose logic could be ported to Unomi. If implementation succeeds, the team will look into improving logs when events are rejected. - The team is also discussing improvements that could be made to reduce the load on Unomi nodes when regular cleanup operations are done. When such an operation happens, the node executing it might become unresponsive. The team will investigate and determine the next improvement steps (in Unomi or somewhere else). The team also discussed potential opportunities for improving developer experience when developing tests (Cypress was mentioned by Serge) in replacement of the existing tests. There are no clear priorities on that front as the existing tests are stable. Cypress being initially a UI browser-based testing framework, François mentioned that there might be other modern solutions being a better fit for API-only testing. No clear next steps were identified. # Next release Apache Unomi 2.6.0 - release date not planned yet # Next meeting Next meeting: Thursday October 10, 2024 - 9AM CET (morning slot): https://us02web.zoom.us/j/85252119410
