Hi William, thank you for the message. Could you please clarify, why a fork would be better than contributing to Dashbuilder directly in Apache KIE? I remember we moved to Apache with the intention to make contributions easier as there is a governance model etc. around.
Best regards, Tibor Dňa št 12. 12. 2024, 18:48 William Siqueira <wsiqu...@redhat.com> napísal(a): > Hello, > > My name is William and I was a Dashbuilder contributor. > > We have been working with Dashbuilder for a while and we have a roadmap for > quite a few improvements and we wanted to make some changes to its core, > also build new projects having dashbuilder as the core of it. > > Having this said, it would be great to fork dashbuilder core to a new > project so it can evolve independently. By Dashbuilder core I mean the > following packages: > > * dashbuilder: The actual core with GWT and Errai > * dashbuilder-components-*: Dashbuilder micro front-end components and its > APIs > > The new fork will have a friendly license, which means that you should be > able to continue using it by just pointing dashbuilder-client[1] to the > package from the new project. All the other projects dependent on > dashbuilder would continue working (Kubesmarts, vscode extension, > dashboards and so on) with little or no change. > > Kindly let me know your thoughts about this. > > Thanks! > > [1] > > https://github.com/apache/incubator-kie-tools/blob/main/packages/dashbuilder-client/package.json#L26 > > -- > > William Siqueira > > Software Engineer > > Red Hat > > <https://www.redhat.com> > > M: +55-12997070488 > <https://red.ht/sig> >
