-
Notifications
You must be signed in to change notification settings - Fork 262
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
improving support page #4196
improving support page #4196
Conversation
I'd like to suggest a few changes: Xen Orchestra runs in a controlled and verified environment, called XOA (Xen Orchestra virtual Appliance). Using XOA, grants you the option of professional support. Any account with a registered Xen Orchestra virtual Appliance can signup for one of our multiple support plans.
Higher tier support plans include faster ticket response times (and include additional features). Paid support plans and response times are based on the plan you have, plans can be reviewed here. |
Please make a PR after this one is merged or review the PR (but IDK if you can do it) |
docs/support.md
Outdated
@@ -24,6 +26,8 @@ We encourage you to give back to the community by assisting other users via thes | |||
|
|||
Lastly while Xen Orchestra is free and Open Source software, supporting and developing it takes a lot of effort. If you are considering using Xen Orchestra in production, please subscribe for one of our [professional support plans](https://xen-orchestra.com/#!/xo-pricing). | |||
|
|||
> Note: support from the sources is harder, because Xen Orchestra can potentially run on any Linux distro (or even FreeBSD and Windows!). Always try to double check that you followed the guide on how to [install it from the sources](https://xen-orchestra.com/docs/from_the_sources.html) before going further. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would change "followed the guide" to "followed our guide" to highlight the fact we cannot guarantee the outcome of the many 3rd party XO sources deployment scripts out there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would change "followed the guide" to "followed our guide" to highlight the fact we cannot guarantee the outcome of the many 3rd party XO sources deployment scripts out there.
A script should have nothing like a guide. . .
Run these commands in this order, is about all anything that I've seen states for "a guide".
Mine included.
Can't review without being asked too. That's why I commented. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Xen Orchestra runs in a controlled and verified environment, called XOA (Xen Orchestra virtual Appliance). Using XOA, grants you the option of professional support. Any account with a registered Xen Orchestra virtual Appliance can signup for one of our multiple support plans.
Let's remove the XOA s available in multiple plans . . . line jump straight to the bullets and then change this next line.
Higher tier support plans include faster ticket response times (and include additional features). Paid support plans and response times are based on the plan you have, plans can be reviewed here.
Last change is the Note section to state this
Note: Providing professional support for the source edition can be more difficult, because Xen Orchestra can potentially be run on any Linux distribution (even FreeBSD and Windows!). Always try to double check that you've followed the installation guide Installing from Source before requesting support.
Check list
Fixes #007
)CHANGELOG.unreleased.md
:${name} v${new version}
)Process
WiP:
(Work in Progress) if not ready to be merged