Hi all, I’d like to propose that we bring the current conversation around SpringBoot support in job-service to the mailing list.
While I understand the intention behind organizing a call to move the discussion forward, it’s important to remember that calls are not the primary medium for resolving decisions in Apache projects. We’ve used calls in the past, but there’s broad consensus now that the ML should be the main channel — for transparency, inclusiveness, and alignment with the Apache Way. In fact, we recently agreed to discontinue the Friday sync meetings for the same reason [1]. I’m not here to dive into the merits of the technical arguments just yet — though I see valid concerns from both perspectives. On one hand, the current implementation may seem overly complex and tightly coupled with Quarkus, which limits portability. On the other, any significant architectural change needs careful consideration, especially when it may affect alternative use cases like the SonataFlow deployment strategy. So rather than defaulting to a call, I suggest we use this thread to: - Surface and clarify the concerns - Explore how we can evolve the codebase to support SpringBoot at the highest quality standard - Ensure we do so without compromising other existing deployment strategies Let’s take full advantage of the mechanisms the community has in place: [DISCUSS], [PROPOSAL], and [VOTE]. If a call ends up being necessary to clarify something specific, it should still be initiated through the ML and the outcomes reflected on the ML. Looking forward to your thoughts. [1] https://lists.apache.org/thread/xpdvw24ytqojkx7kkbv8l9kp6scznlo3 - Alex --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org For additional commands, e-mail: dev-h...@kie.apache.org
