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