Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Establish licensing approach for VA #10

Open
graybeal opened this issue Aug 9, 2019 · 3 comments
Open

Establish licensing approach for VA #10

graybeal opened this issue Aug 9, 2019 · 3 comments
Assignees
@graybeal @alexskr
Labels
documentation KB Aim1 Maintenance KB1 Mx:Docs/Ilities Virtual Appliance

Comments

@graybeal
Copy link

graybeal commented Aug 9, 2019

No description provided.

@graybeal
Copy link
Author

graybeal commented Aug 10, 2019 •
edited
Loading

Provided Terms and Privacy policies to Alex.

Decided at BP meeting 2019.08.10 that license acceptance would be required before VA can be accessed. Alex will implement this in AWS and (he believes) for the regular package.

Also decided in discussion with Alex 2019.08.09 that we should require an actual license key on startup of the system. This is documented in #11.

This ticket is just about the EULA/policies.

@graybeal
Copy link
Author

VMWare has click-to-agree in place with text John previously provided. Need to add new text to AWS click-through.

@graybeal
Copy link
Author

Licensing agreement for Amazon is a bit tricky. A generic one exists. To get our own custom, it might take some time.

@graybeal graybeal self-assigned this Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@graybeal graybeal

@alexskr alexskr

Labels
documentation KB Aim1 Maintenance KB1 Mx:Docs/Ilities Virtual Appliance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@graybeal @alexskr