Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3098

Confirm how to refer to third party IDEs within Dev Spaces, and how/where to document licenses

XMLWordPrintable

    • False
    • None
    • False

      As we move away from Eclipse Theia / Che-Theia as the default editor in Dev Spaces, we need to consider how we will refer to default and optional editors available to be used from within our product.

      We need to make sure we're compliant with license terms when rebuilding/repackaging 3rd party vendors' content.

      Specifically:

      • Dockerfile name / description
      • container name / description / artifact

      Do we need to include additional license files in the IDE container(s), beyond stating the license terms in the Dockerfile?

      Right now the current/planned IDE list for Dev Spaces 3.1 includes:

      • Eclipse Theia
        • EPL v2

      So when referring to these, can we call them "idea" and "vscode" ? Or do we need to refer to them with their full product names?

      Some examples of where the IDE name appears:

      Results:

      name: che-incubator/che-code/insiders
displayName: VS Code - Open Source
description: Microsoft Visual Studio Code - Open Source IDE for Eclipse Che

      and

      name: che-incubator/che-code/insiders
displayName: VS Code - Open Source
description: Red Hat OpenShift Dev Spaces with Microsoft Visual Studio Code - Open Source IDE

        1. image-2022-09-07-15-09-41-779.png
          51 kB
          Nick Boldt
        2. image-2022-09-07-23-32-42-853.png
          8 kB
          Nick Boldt
        3. screenshot-1.png
          120 kB
          Nick Boldt
        4. screenshot-2.png
          12 kB
          Nick Boldt
        5. screenshot-3.png
          8 kB
          Nick Boldt
        6. screenshot-4.png
          17 kB
          Nick Boldt

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: