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