Hi -
There is precedence for allowing drools.org to continue.
We did that with openoffice.org and groovy-lang.org. Both of these had a long
history prior to incubation.
The KIE podling would need to make the case for drools.org to continue.
Also, please work to get that website into compliance
To the best of my knowledge, all relevant domains have already been
donated, and Brian Proffitt has been directly involved in coordinating
this effort.
Some of the package prefixes listed - such as org.uberfire and
com.ait.lienzo - are tied to legacy components that are no longer
actively develope
Would it be possible to consider getting the drools.org domain donated
to the ASF and https://www.drools.org/ to be redirected to Drools
pages on https://kie.apache.org?
The KIE tools repo has so many different package prefixes. Would it be
possible to cut down on them by moving some of them to or
The impact on KIE would be significant if we were required to change
core package names like org.drools.
Drools is one of the most widely adopted rule engines in the
enterprise space. Core components such as drools-compiler, a
dependency used in virtually every Drools-based application, have been
Hi PJ
By default, the package names should start with org.apache.
However, I remember we accepted (exceptional) other package name for
existing projects joining the incubator as it impacts the existing
community. I would consider more as a "transition" period.
Regards
JB
On Wed, Jul 2, 2025 at 1
HI,
In general, a podling should use org.apache.Foo package names, but we have made
exceptions in the past for projects that were already in use and where the
change would greatly impact their user community.
Kidn Regards,
Justin
-
