Closed alex-hedley closed 10 months ago
@alex-hedley Do you mean Camunda 8? This would be a new repo. There was a community effort once started here: https://github.com/korthout/camunda-platform-rest-api - but I don't think it is actively maintained. We also discuss this matter internally at the moment if we shall/can provide a REST API for Camunda 8 (ping @akeller FYI)
I did.
Is it worth seeing if it can be moved over to the camunda-community-hub
org?
@korthout: WDYT - would it make sense to transfer the repo to the community hub (maybe renaming it to camunda-community-hub/camunda-platform-8-rest-client-java
to make it clearly distinguishable from this repo)?
@berndruecker I've let maintenance of https://github.com/korthout/camunda-platform-rest-api slip for two reasons:
@alex-hedley What additional value do you see as in moving the project over to the camunda-community-hub
? I'd like to understand what value this would provide before spending time on this. Please consider that this would require changes to the CI and release process and that this costs time to change and test. Would moving the project help you to use the project? If so, how? Would it help you to contribute to it? If so, how?
I'd also like to know whether users are actually interested in using this project, before spending more time on it. At the moment, there appears to be little interest. I cannot track actual usage, so I depend on community outreach for this knowledge. If there is actual interest, then I'd be happy to revive the project.
I guess visibility for one, if people are looking for Camunda stuff it seems to be the place to go. Might have more a seal of approval on it is on a semi-official org. It would allow for more maintainers as it's then not just a single user repo. Happy to help adding any issues/feature requests for the missing functionality so it's easier to track what is left to do? Maybe even create a Project board.
Has anyone started working on a v8? Would this be done in a new repo?