Rename extension, update assets & documentation

[celanthe]

Hi Gunnar,

I hope today finds you well! This issue is being opened to ask if you would be open to renaming your extension on GitHub to reference Camunda Platform 7 rather than Camunda BPM after its release on April 12th, 2022. (For example: camunda-platform-7-keycloak) This change will also likely impact any screenshots you have in the README that reference Camunda BPM or previous versions of Camunda Platform, and this will likely need to also be updated throughout the repo's documentation as a whole. You can also make use of Shields.io badges to indicate which version of Camunda your extension is compatible with.

While it is not a requirement that you rename your extension to align with Camunda Platform 7, we would greatly appreciate it if you could make these changes, and merge them anytime after April 12th, 2022.

if you have any questions or require any assistance, please do not hesitate to reach out to @camunda-community-hub/devrel! :)

[VonDerBeck]

Hi @celanthe, thanks for the request. Even though this is not my top priority at the moment, I will find time to work on it around the end of April / beginning of May. Until then I will use the Camunda 7 badge. Does this also fit for you?

[akeller]

Hi @VonDerBeck - Rin has moved on from Camunda. Your timeline makes sense to me and hopefully the badge will help others users understand how to use your extension for now. Thanks!

[mary-grace]

hi @VonDerBeck - I just wanted to check in to see if I can help move this along in any way.

[VonDerBeck]

Hi @mary-grace,

thanks for asking. Sorry that I haven't taken care about that in the last weeks. I'm honest, there is a "too much projects" exception on my side... But it's a good time to start that soon. On my side there is one question, I'd like to have answered:

• renaming this extension to e.g. camunda-platform-7-keycloak means to rename / move the whole repository as well
• who is going to do that? I'm not the one who has the rights to do so
• what is happening with the old link https://github.com/camunda-community-hub/camunda-bpm-identity-keycloak/? Will there be an automatic redirect?

The procedure for renaming the repository then would be:

1. I create a separate branch, where I prepare the internals of this extension, update artifact names, documentation, etc.
2. After this is working, someone of you is going to give the community extension a new home
3. We use the prepared branch as new master

Any suggestions?

Kind regards Gunnar

[berndruecker]

Howdy Gunnar - hope you are well? I will go ahead and rename the repo right away - and yes - all traffic for the old URL will be automatically redirected (and even git pull/push continue to work for the old URL), so there should not be any friction caused by this. I think this is already a good start independent of renaming artifact id's or the like.

+1 for creating a branch to do your changes - let me know if you need some review or the like...

[VonDerBeck]

@berndruecker : 👍 Faster than the police allows 👍

[VonDerBeck]

Now waiting for release. See #99

[VonDerBeck]

Closing this issue - artifacts seem to be already available on Maven Central.

[berndruecker]

Thanks @VonDerBeck

[mary-grace]

Thanks for handling this so quickly, to both of you! :)