+1 from me, this should simplify the future developments

On Wed, 2026-03-25 at 12:26 +0530, Rishiraj Anand wrote:
> +1 to consolidate all codebases into a single, unified repository.
> This
> approach is more sensible and eventually makes it significantly
> easier for
> new developers to understand, navigate, and contribute effectively.
> 
> On Wed, 25 Mar 2026 at 02:50, ricardo zanini fernandes <
> [email protected]> wrote:
> 
> > Thanks, +1
> > 
> > On Tue, Mar 24, 2026 at 3:42 PM Alex Porcelli <[email protected]>
> > wrote:
> > 
> > > Sorry for being late to the party, as I've been heads-down
> > > prioritizing
> > the
> > > 10.2.0 release.
> > > 
> > > +1 for this proposal, it looks great.
> > > 
> > > This feels like a natural evolution of earlier proposals [1][2]
> > > that were
> > > both approved but unfortunately never materialized.
> > > 
> > > I hope this time we can execute on it. Having been involved in
> > > all Apache
> > > KIE releases and having firsthand experience with the fragility
> > > of our
> > CI,
> > > especially the release process, I'm genuinely excited about the
> > > idea of
> > > simplification.
> > > 
> > > Count 100% on me.
> > > 
> > > [1]
> > > https://lists.apache.org/thread/drojdtvz6xx1zo35ggjm75xdngnfcl21
> > > [2]
> > > https://lists.apache.org/thread/c09l9xq0d8jz7th6k23gf5svoky06955
> > > 
> > > Alex
> > > 
> > > On Tue, Mar 24, 2026 at 1:24 PM Kennedy Bowers
> > > <[email protected]>
> > wrote:
> > > 
> > > > Thanks for the proposal, Tiago, +1 from me. The streamlined
> > > > structure
> > > > makes a lot of sense and should help lower the barrier for
> > contributors.
> > > > Happy to help out with the restructuring or wherever needed.
> > > > 
> > > > On 2026/03/23 08:08:55 Tibor Zimányi wrote:
> > > > > Thanks, +1.
> > > > > 
> > > > > Best regards,
> > > > > Tibor
> > > > > 
> > > > > Dňa po 23. 3. 2026, 8:21 nicolas.heron
> > > > > <[email protected]>
> > > > napísal(a):
> > > > > 
> > > > > > When the project had so many repo o nkiegroup it became
> > > > > > impossible
> > to
> > > > > > contribute as a non full time contributor
> > > > > > before on svn : drools, jbpm, optaplanner and guvnor =>
> > > > > > easy
> > > > > > So I vote in favor of less git repositories
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > Le vendredi 20 mars 2026 à 15:42, Thiago Lugli <
> > [email protected]
> > > > 
> > > > a
> > > > > > écrit :
> > > > > > 
> > > > > > > I appreciate this change.
> > > > > > > 
> > > > > > > As someone in the community for a little while, mainly
> > > > > > > working on
> > > > > > > kie-tools, I find contributing to upstream repositories
> > > > > > > daunting
> > > > right
> > > > > > > now because it's not easy to spot potential downstream
> > > > > > > impacts.
> > > This
> > > > > > > change will improve that.
> > > > > > > It would even simplify the way we build Drools and Kogito
> > > > > > > in the
> > > > > > > kie-tools repository.
> > > > > > > 
> > > > > > > Thanks for the proposal, Tiago!
> > > > > > > 
> > > > > > > On Fri, Mar 20, 2026 at 6:52 AM Yeser Amer
> > > > > > > <[email protected]>
> > > wrote:
> > > > > > > > 
> > > > > > > > Hi,
> > > > > > > > 
> > > > > > > > Thanks for laying this out — the proposal makes sense
> > > > > > > > to me.
> > The
> > > > more
> > > > > > we work with the current structure and development model,
> > > > > > the
> > clearer
> > > > it
> > > > > > becomes that we need a unified approach moving forward. A
> > > > > > leaner
> > > > 10.3.x+
> > > > > > stream and a simplified repository structure will
> > > > > > definitely help
> > > > > > contributors be more effective.
> > > > > > > > Count me in for supporting this direction. I’m
> > > > > > > > available to
> > help
> > > > with
> > > > > > any difficulties we might encounter along the way and to
> > > > > > surface
> > and
> > > > > > address any potential issues as we move through the
> > > > > > process.
> > > > > > > > 
> > > > > > > > Yeser
> > > > > > > > 
> > > > > > > > On 2026/03/19 18:53:32 Tiago Bento wrote:
> > > > > > > > > Hi all,
> > > > > > > > > 
> > > > > > > > > As we make progress towards the 10.2 release, I’d
> > > > > > > > > like to
> > > > propose a
> > > > > > > > > refreshed development
> > > > > > > > > stream focused on Drools, jBPM, and Kogito — 10.3.x+.
> > > > > > > > > 
> > > > > > > > > This leaner stream would be developed in the `main`
> > > > > > > > > branch
> > but
> > > > > > giving it a
> > > > > > > > > distinct name
> > > > > > > > > (10.3.x+) marks it as a milestone in Apache KIE.
> > > > > > > > > 
> > > > > > > > > Borrowing ideas from the original proposal for a duo-
> > > > > > > > > repo
> > > > structure,
> > > > > > here’s
> > > > > > > > > what it would look
> > > > > > > > > like:
> > > > > > > > > 
> > > > > > > > > - A “new” `kie` repository from renaming `drools`
> > > > > > > > > (gotta keep
> > > > the 6k
> > > > > > > > > stars!), incorporating
> > > > > > > > > `drools`, `optaplanner`, `kogito-runtimes`, and
> > `kogito-apps`,
> > > > minus
> > > > > > > > > SonataFlow modules
> > > > > > > > > - `kie-tools` continue as is, minus DashBuilder,
> > > > > > > > > YaRD, and
> > > > SonataFlow
> > > > > > > > > packages
> > > > > > > > > - `kie-examples` from a renamed `kogito-examples`,
> > > > > > > > > with a
> > > > > > development cycle
> > > > > > > > > detached from
> > > > > > > > > `kie` and `kie-tools`
> > > > > > > > > - `kie-website` unchanged
> > > > > > > > > - `kie-docs` unchanged
> > > > > > > > > - PR checks and release automations re-written for a
> > > click-button
> > > > > > release
> > > > > > > > > process and a local-
> > > > > > > > > first development setup
> > > > > > > > > 
> > > > > > > > > The community would continue to have access to
> > > > > > > > > DashBuilder,
> > > > YaRD, and
> > > > > > > > > SonataFlow via the
> > > > > > > > > 10.2.x branch.
> > > > > > > > > 
> > > > > > > > > The 10.3.x+ stream would bring a refreshed structure
> > > > > > > > > to
> > Apache
> > > > KIE,
> > > > > > reduce
> > > > > > > > > barriers for new
> > > > > > > > > contributors, and allow for existing contributors to
> > > collaborate
> > > > more
> > > > > > > > > efficiently.
> > > > > > > > > 
> > > > > > > > > Regards,
> > > > > > > > > 
> > > > > > > > > Tiago Bento
> > > > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > ---------------------------------------------------------------
> > > > ------
> > > > > > > > To unsubscribe, e-mail: [email protected]
> > > > > > > > For additional commands, e-mail:
> > > > > > > > [email protected]
> > > > > > > > 
> > > > > > > 
> > > > > > > 
> > > -----------------------------------------------------------------
> > > ----
> > > > > > > To unsubscribe, e-mail: [email protected]
> > > > > > > For additional commands, e-mail: [email protected]
> > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > > 
> > -------------------------------------------------------------------
> > --
> > > > > > To unsubscribe, e-mail: [email protected]
> > > > > > For additional commands, e-mail: [email protected]
> > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > > ---------------------------------------------------------------
> > > > ------
> > > > To unsubscribe, e-mail: [email protected]
> > > > For additional commands, e-mail: [email protected]
> > > > 
> > > > 
> > > 
> > 

Reply via email to