Rename extension, update outdated assets and documentation

[celanthe]

This issue is being opened to inquire as to if you would be open to renaming your extension here on GitHub to reference Camunda Platform 7 rather than Camunda BPM. (For example: camunda-platform-7-plugin-stats This change would also likely impact any screenshots you have in the README that reference Camunda BPM or older versions of Camunda Platform, and would 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! :)

[akeller]

@falko @berndruecker Is this something either of you could update?

[akeller]

I added the C7 badge, but this is all I can commit to at this time.

[berndruecker]

I would actually archive this, as it is quite old and use cases should be possible by simply using Optimize in the meantime - unless @eklieme interjects

[akeller]

I'll leave you to follow up on this and archive if that's the best past forward. Thanks, @berndruecker!

[berndruecker]

@tobiasschaefer: Could you comment on this if we can archive it? I would follow lazy consensus and archive it next week if I don't hear back

[tobiasschaefer]

Hi @berndruecker ,

yes, please archive it. Camunda Optimize is superior now ;-)