Re: [PROPOSAL] Move YARD into kie-drools repository

2025-07-04 Thread Gabriele Cardosi
Thanks Alex, Tony, Now I better understand, make sense. Thanks for the explanation. Best Gabriele Il giorno ven 4 lug 2025 alle ore 16:08 Alex Porcelli ha scritto: > The code in question, specifically the YARD runtime, has a development > history dating back to June 2022, which predates the

Re: [PROPOSAL] Move YARD into kie-drools repository

2025-07-04 Thread Toni Rikkola
For business use. The diver is really to have a one file rule definition. This can be used for scorecards, forming reporting data or data aggregation like I mentioned. For a product that could use this. There is one that I have been working on that allows me to set data collection on certain poin

Re: [PROPOSAL] Move YARD into kie-drools repository

2025-07-04 Thread Alex Porcelli
The code in question, specifically the YARD runtime, has a development history dating back to June 2022, which predates the migration of the codebase to the Apache Software Foundation. During that migration, other parts of the same effort, such as the YARD tooling, were brought into the KIE Tools r

Re: [PROPOSAL] Move YARD into kie-drools repository

2025-07-04 Thread Gabriele Cardosi
HI Alex, thanks for your explanation. Could you please help me understand better what you mean with: "This helps prevent potential legal concerns related to ownership, trademarks, and similar issues." The reason I'm asking is because, reading your explanation, my conclusion would be exactly the ot

Re: [PROPOSAL] Move YARD into kie-drools repository

2025-07-04 Thread Alex Porcelli
Thank you, Gabriele, for engaging and helping to evaluate the overall situation. Based on the repository history, with commits dating back to June 2022, this piece of code was likely overlooked during the migration to Apache. This seems plausible, given that other components, such as the YARD tool

Re: [PROPOSAL] Move YARD into kie-drools repository

2025-07-04 Thread Gabriele Cardosi
Hi Tony, many thanks for your answers, make sense! The only thing probably I've not been very clear about is the "driver" or business value, or whatever. I understand that currently the implementation is targeting scorecard, but my question was about the "need" of this other implementation, since

Re: [PROPOSAL] Move YARD into kie-drools repository

2025-07-04 Thread Toni Rikkola
Thank you for interest. Like I said this is a separate module that is easy to pick out if needed later. 1. Yes this is another way for defining and grouping rules. 2. org.kie.j2cl is actually something I need to remove. It comes from our j2cl dependencies that are mainly used by tooling. It wil

Re: [PROPOSAL] Move YARD into kie-drools repository

2025-07-04 Thread Gabriele Cardosi
Hi Tony, this seems an interesting feature, indeed. Anyway, as I mentioned in the past for other similar improvements, I think the main concern should be the evaluation of pros/cons, since we are already struggling to maintain the codebase as it is and this new implementation, inevitably, would inc

[PROPOSAL] Move YARD into kie-drools repository

2025-07-04 Thread Toni Rikkola
Hello, Summary: When we moved to KIE, YARD was still in experimental mode. We did move the editors and validation tooling (in kie-tools ATM), but runtime was left behind. I previously proposed adding YARD in, but it was seen as a risk for the up coming releases. Assignee: Me, Toni Rikkola

Re: Future Apache KIE releases seemed blocked

2025-07-04 Thread Toni Rikkola
I think this would be the case if the outside repository was not a reusable component, but specific for our needs. The linked mapper-xml project is used by the J2CL community. It was previously outside of KIE for this reason, but dragged in due to reasons and I can not remember the details. It

Re: Future Apache KIE releases seemed blocked

2025-07-04 Thread Alex Porcelli
My concern is that moving all GPL code into an outside repository maintained by a committer might not be the right solution, as it gives me the impression that we are using a shadow organization to solve issues. I'd be cautious with such an option. - Alex On Fri, Jul 4, 2025 at 3:57 AM Toni Rikk

Re: [HEADS UP] Direct merge to incubator-kie-docs

2025-07-04 Thread Alex Porcelli
Thank you for taking the lead on this, Toni! As you stated, it's fine to merge directly. Thank you for raising a PR in advance as a way to show what's coming. Next Tuesday (JULY, not June, 8th) sounds more than reasonable. On Fri, Jul 4, 2025 at 4:54 AM Toni Rikkola wrote: > > Hello, > > The go

[HEADS UP] Direct merge to incubator-kie-docs

2025-07-04 Thread Toni Rikkola
Hello, The goal is to move optaplanner docs to kie-docs with all the commit history data. Problem is GitHub does not support a merge with this many commits. When the same was done with for Drools Toshiya committed everything in small bits, but several of us said it would be OK to do one dire

Re: Future Apache KIE releases seemed blocked

2025-07-04 Thread Toni Rikkola
Any project using code from GPL becomes GPL. https://www.apache.org/licenses/GPL-compatibility.html However there is a linking exception. https://openjdk.org/legal/gplv2+ce.html https://en.wikipedia.org/wiki/GPL_linking_exception So the project maintained by Dmitrii is fine as a dependency, but i

Re: [DISCUSSION] Web site maintenance

2025-07-04 Thread Toni Rikkola
We need to do the same for optaplanner.org and jbpm.org. Apache requires us to have everything under kie.apache.org. Both of the websites have already been moved. Toni On 2025/07/04 01:40:16 Toshiya Kobayashi wrote: > Hi all, > > We have migrated the contents to kie.apache.org. > > I'm going