first of a all, thanks to the operaton Team on what you have already accomplished so far! The last Townhall meeting was quite insightful and in a good spirit. After Tims call to action regarding plugins I remembered an effort I began in January after beta-2.
Both are created by https://www.holunda.io (Open Source Projects of Holisticon AG). I have not contacted the original developers If they are interested to move their effort to operaton after Camunda CE is finally EOL.
Besides the keycloak plugin (already ported) and the bpmn-assert plugin (promoted to Camunda core recently) they are our last remaining community dependency. So I took the effort as preparation in order to be able to port some internal projects to operaton.
If you have projects depending on camunda-platform-7-mockito, just checkout the operaton branch of my forks and install them locally - for the time beeing. Let me know if there is interest to move the projects to the operaton umbrella.
That’s great, i guess it would make sense to adopt the camunda-bpmn-data first then. I think @kthoms knows Simon Zambrovski, perhaps he can ping him and inform him about our plans to fork the plugin.
Hi Lars, I followed you here because I think discussing the port in the camunda-hub is misleading.
It looks like you already did all the work required to run the mockito test tool against operaton, so what exactly do you need from me? Jan
To clarify: the mockito tool is currently hosted on the camunda community hub. For C7 we will probably fork this in the holunda-io group …
How would that solve porting to operaton? Does the operaton org provide a space for such community extensions? Happy to help, but as said above: Seems the work was done already.
I think the question is if you would like to maintain the Operaton port next (or as a successor) to the original Camunda 7 version. It would be much better for the mockito extension if you (the original authors) would continue to support, maintain and evolve it. I would happily contribute the work already done.
We can move the forked plugin to the Operaton GitHub organization, unless there’s a more suitable home for it.
The main idea behind the question was simply to check whether the original authors are still interested in maintaining it. If so, it might make sense to move it either to the holunda-io org or the Operaton org, depending on what’s preferred.