AT:

• The EULA is included in the license book
  • txt file in the distros and docs
  • md file in the docs
• https://docs.camunda.org/manual/7.17/introduction/third-party-libraries/ has a new section for the webapps that informs specifically about the XLTS license. It either includes the EULA directly or links to the version on xlts.dev (to be clarified with Legal)
• https://docs.camunda.org/manual/7.17/introduction/licenses/#third-party-libraries is reworded for a better flow to https://docs.camunda.org/manual/7.17/introduction/third-party-libraries/
• The following pages link to https://docs.camunda.org/manual/7.17/introduction/third-party-libraries/ (to be decided: to we want to point out the XLTS license directly at the link locations?)
  • https://docs.camunda.org/enterprise/download/
  • https://docs.camunda.org/manual/7.17/introduction/downloading-camunda/
  • https://camunda.com/download/
  • https://camunda.com/download/enterprise/
  • https://hub.docker.com/r/camunda/camunda-bpm-platform/
  • To be decided: Do we want to inform about the third-party libraries at places where link directly to the artifacts? (e.g. https://docs.camunda.org/manual/7.17/installation/camunda-bpm-run/#installation-procedure and other installation guides, getting started guides, ...)
• https://github.com/camunda/camunda-bpm-platform/tree/master/webapps/ informs that building this project form source will use "old" AngularJS
• https://github.com/camunda/camunda-bpm-platform informs about third-party dependencies and links to https://docs.camunda.org/manual/latest/introduction/third-party-libraries/
• The release announcement message for the next patches at https://confluence.camunda.com/display/camBPM/Releases+-+Automation+Platform#ReleasesAutomationPlatform-NextPatches informs customers about the new third-party license
• Our release blog post template links to https://camunda.com/download/ instead of directly to the download center
• Legal has reviewed the changes