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.

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

Update EULA re http->https and abstract liability to paid subscription amount #83

Closed
phillxnet opened this issue Nov 7, 2021 · 0 comments · Fixed by #84
Closed

Update EULA re http->https and abstract liability to paid subscription amount #83

phillxnet opened this issue Nov 7, 2021 · 0 comments · Fixed by #84

Comments

@phillxnet
Copy link
Member

We currently use an http 'legal' link that is now https hosted due to:
rockstor/rockstor-core#2226
Plus we have a hard-coded liability amount: tie this to the first years paid subscription as that was the original intent with the currently given amount. This also allows us to vary our subscription for different countries/currencies in line with what may be appropriate going forward.

Note that these updates must also be reflected in our website repository as it, in turn, has a copy of the resulting EULA post edits performed by the installer build process.

phillxnet added a commit to phillxnet/rockstor-installer that referenced this issue Nov 8, 2021
…ockstor#83

Adds additional filters that were missed previously and updates the
copyright dates to be current and to catch some new Leap 15.3 dates.

Main change here is to remove a hard-coded $ amount re corner case
liability and replace with "1ST SUBSCRIPTION PAYED"; connecting this
amount to a subscription payment: the 1st in this case. It is postulated
that the original 50 dollars specified in our upstream is derived from
the earlier openSUSE box-set cost.
phillxnet added a commit that referenced this issue Nov 8, 2021
…nd_abstract_liability_to_paid_subscription_amount

Update EULA re https, abstract liability to sub amount & redo dates #83
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant