[2025-01-10] Meeting minutes

[porcelli]

• Hibernate dependency (LGPL)
  • Many individuals reached out to Hibernate team members, and the overall situation is that they are close to relicensing it.
  • It may still take a couple of months to have it fully sorted out
  • @porcelli also talked to Max Anderson from Quarkus. The next LTS is scheduled already if the new Hibernate can't make it... the worst case scenario is to have it by september-ish in the next LTS.
• 10.1.0 release
  • start a new release
  • @domhanak is wondering about 11 instead of 10, but it's fine either way
  • @baldimir suggested a cadence, @porcelli pointed out that before cadence he consider the stabilization of the release necessary. @baldimir has opened a thread to discuss.
• docs and websites
  • @domhanak argued that it he believes there's a general agreement to consolidate everything in a single place for docs and etc.
  • @porcelli pointed out that part of the docs discussion is define what technology to use, where to host, how to build and where to publish
    • there might have a little bit more discussions, as like the definition of a unified table of contents
  • @domhanak provided links for all existing docs sources are hosted: https://github.com/apache/incubator-kie-docs/tree/main-kogito https://github.com/apache/incubator-kie-kogito-docs https://github.com/apache/incubator-kie-drools/tree/main/drools-docs
• examples
  • quick solution by @domhanak:
    • patch current broken repo
    • update the examples to 10.0.0
    • branch a new stable and use 10.0.0
  • @gitgabrio agrees with @domhanak and suggested to get rid of the stable branch
  • @gitgabrio wants - in the near future - to understand as a group not as individuals - what's the purpose of the examples
    • @domhanak his experience those are used as quickstart
    • @baldimir also agrees on the quickstart
  • @domhanak getting started is not ideal; examples can contribute to it
  • @porcelli clarified the examples is a collection of issues - not only one.
    • he first expressed that he agrees to fix/patch the current 10.0.0 situation following @domhanak suggestion
    • he also described the problem with 2 components: consume and maintenance. he explained in voice what he wrote to ML.
  • @gitgabrio mentioned that the problem alex reference is a consequence of bad architecture and lack of clear direction... and before trying to fix anything a re-evaluation of the bigger picture and architecture should be done before doing anything else. He also suggested that maybe is the time to stop the world, if necessary, to make what he consider the important things.
  • @porcelli alex mentioned that it's fair to @gitgabrio consider that there's a bigger issue, but also mentioned that you cannot block a problem resolution, because there might be a bigger one. Apache way is to find compromises, and not shutdown discussions. It's expected that issues will continue be solved incrementally.
  • Discussion evolved to next topic
• Mono repo vs. poly repo
  • @baldimir don't think mono will happen
    • backend, frontend, containers, examples
  • @gitgabrio shared that he consider that most of the issues are a lack of proper architecture and organization and mono repo is not a solution
  • @porcelli touched lightly and shared he well know preference for mono repo, as we are apache kie and not different scattered components.
  • @porcelli also mentioned that the concept of 4 repos split by tech stack sounds right, but the devil is in the details. Like the devui jar's need depend on UI, and the UI do not have a -snapshot equivalent, etc...

---

Recording:

https://us06web.zoom.us/rec/share/YGMSiAVO-AgPc-lnFeY5xSzsJbnvIzitoKtNnBf0Ki_uiGzguiqOXmDmqjWv4A6a.J06yixLi9gE-BiyJ
Passcode: 5#FgVBiA