vmware / vmware/photon

Additional restriction in Photon 5.0 EULA

Open
#1,617 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
3.2k
Forks
692
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

The Photon 5.0 EULA which applies to the Photon OVA and ISO includes a restriction which wasn't present in the Photon 4.0 EULA:

1.3. Restrictions. Customer may use the Offerings only for its internal use and for the benefit of its Affiliates. Affiliates may not use the Offerings. Customer may not resell or sublicense its rights to the Offerings. Customer may not use the Offerings in an application service provider, service bureau, hosted IT service, or similar capacity for third parties.

This appears to block the use case for the Photon OS OVA where a vSphere Remote Plugin has been packaged and distributed with the Photon OVA. This architecture is specifically recommended in VMWare's guide for developing remote plugins:

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere-sdks-tools/9-0/developing-remote-plug-ins-with-the-vsphere-client-sdk-8-0.html

Was the restriction erroneously added? If not, can you help me to understand the intention behind the update to the EULA and how we can continue to use the OVA.

Reproduction steps

Read the EULA

Expected behavior

Package and distribute a vSphere Remote Plugin with the Photon OS OVA

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the Photon 5.0 EULA restriction quoted in the issue and compare it with the Photon 4.0 EULA. Review the linked VMware guide for the vSphere Remote Plugin packaging model; the issue is done when maintainers clarify whether that use is permitted or document an approved alternative.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.