I realize that I'm coming to this discussion late, and I'm just a peanut here...
It seems that there is already a good deal of project branding that the community does not want to abandon. It is true that ASF Java projects use org.apache.project as their brand, and I do not believe that ASF will allow org.kie.something to be released as an ASF project. With this in mind, there are projects that don't release artifacts under their PMC names. Example: Java Data Objects is part of the DB PMC but has its own brand: org.apache.jdo is the package name. Its github code repository is db-jdo and its github site repository is db-jdo-site. If the branding is to be maintained, i see no problem with keeping the existing brand while marking the project as an ASF project. Each of these projects could retain its own github repository under the ASF github umbrella. The PMC would have its own web site that would link to the project web sites. For example: org.apache.drools github kie-drools and kie-drools-site org.apache.jbpm org.apache.sonataflow org.apache.kogito org.apache.kie.tools These package names might be easier to deal with than trying to insert kie into everything, especially since "kie" is not a well-known brand of its own right now. In order for this to work, the original projects would have to donate their brands to ASF. I understand that this is not a problem. Good luck with all of this! Craig > On Oct 19, 2023, at 10:47, ricardo zanini fernandes <ricardozan...@gmail.com> > wrote: > > We have org.drools, org.jbpm, hence org.sonataflow. Can't we keep this > ubiquity? org.kie.apache.sonataflow is too large, IMO. If we go for > org.apache.sonataflow, then maybe renaming everything else to follow the > same pattern? > > > On Thu, Oct 19, 2023 at 2:30 PM Jason Porter <lightguar...@apache.org> > wrote: > >> I'm +0 on this. >> >> If we're going to rename it to SonataFlow, should we not make it >> org.apache.kie.sonataflow or something similar under the Apache name? >> >> On 2023/10/19 12:42:53 ricardo zanini fernandes wrote: >>> Friends, >>> >>> Since we moved from "Kogito Serverless Workflow" to "SonataFlow" project >>> I'd like to propose a naming change to those artifacts targeting 10.x. >>> >>> Some are *only* related to SW which is implementation specifics. We can >>> change to SonataFlow, for example: >>> >>> Description Extension Target >>> Runtime development tools for SonataFlow >>> org.kie.kogito:kogito-quarkus-serverless-workflow-devui >>> org.sonataflow:sonataflow-quarkus-devui >>> SonataFlow Add-On - Includes OpenApi Client, the Process engine, and >>> Knative Eventing capabilities >>> org.kie.kogito:kogito-quarkus-serverless-workflow >>> org.sonataflow:sonataflow-quarkus >>> >>> Another renaming is targeting Kogito Quarkus Add-Ons to KIE Quarkus >> Add-Ons >>> for generic proposes (works for SonataFlow, jBPM, Drools, etc). For >> example: >>> >>> Description Extension Target >>> KIE Data Index Infinispan Add-On >>> org.kie.kogito:kogito-addons-quarkus-data-index-infinispan >>> org.kie:kie-addons-quarkus-data-index-infinispan >>> KIE Data Index In-memory Add-On >>> org.kie.kogito:kogito-addons-quarkus-data-index-inmemory >>> org.kie:kie-addons-quarkus-data-index-inmemory >>> >>> There are also jBPM specifics, which I propose: >>> >>> Description Extension Target >>> jBPM Add-On for e-mail support on Human Tasks. >>> org.kie.kogito:kogito-addons-quarkus-mail >> org.jbpm:jbpm-addons-quarkus-mail >>> >>> To keep things simple for now, we can refrain from renaming namespaces, >> but >>> GAV is important since we are moving to 10.x., so we start fresh. >>> >>> If we agree, I can keep a spreadsheet with all the renames and share it >>> with the community. >>> >>> Cheers! >>> >>> -- >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org >> For additional commands, e-mail: dev-h...@kie.apache.org >> >> Craig L Russell c...@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org For additional commands, e-mail: dev-h...@kie.apache.org
