]> git.proxmox.com Git - pve-docs.git/blame_incremental - getting-help.adoc
Improve wording of getting help section for commercial support
[pve-docs.git] / getting-help.adoc
... / ...
CommitLineData
1Getting Help
2------------
3include::attributes.txt[]
4
5
6Proxmox VE Wiki
7~~~~~~~~~~~~~~~
8
9The primary source of information is the {pve}
10http://pve.proxmox.com[wiki]. It combines the reference documentaion
11with user contributed content.
12
13
14Community Support Forum
15~~~~~~~~~~~~~~~~~~~~~~~
16
17{pve} itself is fully open source, so we always encourage our users to
18discuss and share their knowledge using the
19http://forum.proxmox.com/[Community Support Forum]. The forum is fully
20moderated by the Proxmox support team, and has a quite large user base
21around the whole world. Needless to say that such a large forum is a
22great place to get information.
23
24Mailing Lists
25~~~~~~~~~~~~~
26
27This is a fast way to communicate via email with the Proxmox VE
28community
29
30* Mailing list for users:
31 http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user[PVE User
32 List]
33
34The primary communication channel for developers is:
35
36* Mailing list for developer:
37 http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel[PVE
38 development discussion]
39
40
41Commercial Support
42~~~~~~~~~~~~~~~~~~
43
44{proxmoxGmbh} also offers commercial
45http://www.proxmox.com/proxmox-ve/pricing[{pve} Subscription Service
46Plans]. System Administrators with a standard subscription plan can access a
47dedicated support portal with guaranteed reponse time, where {pve}
48developers help them should an issue appear.
49Please contact the mailto:office@proxmox.com[Proxmox sales
50team] for more information or volume discounts.
51
52
53Bug Tracker
54~~~~~~~~~~~
55
56We also run a public a public bug tracker at
57https://bugzilla.proxmox.com. If you ever detect a bug, you can file
58an bug entry there. This makes it easy to track the bug status, and
59you will get notified as soon as the bug is fixed.