Add the Common_Content files (they're essential for building, you know)

1 files changed, 77 insertions, 0 deletions

diff --git a/Common_Content/en-US/sect-Feedback.xml b/Common_Content/en-US/sect-Feedback.xml
new file mode 100644
index 0000000..b160dfd
--- /dev/null
+++ b/Common_Content/en-US/sect-Feedback.xml
@@ -0,0 +1,77 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+<section lang="en-US" id="sect-Feedback">
+    <title>Feedback</title>
+     <indexterm>
+        <primary>feedback</primary>
+         <secondary>contact information for this manual</secondary>
+
+    </indexterm>
+     <para>
+        We value feedback on our software as well as our documentation. Please find ways to contact us in this section.
+    </para>
+
+    <section id="sect-Feedback-Reporting_Bugs_in_Kolab">
+        <title>Reporting Bugs in Kolab</title>
+        <para>
+            Bug reports can be logged in our <ulink url="https://bugzilla.kolabsys.com">Bugzilla issue tracker</ulink>. Please bear in mind registration is required.
+        </para>
+        <para>
+            When reporting a bug, please prepare to provide the following information;
+        </para>
+        <para>
+            <itemizedlist>
+                <listitem>
+                    <para>
+                        Your platform, and if applicable, your distribution and the distribution version.
+                    </para>
+                </listitem>
+                <listitem>
+                    <para>
+                        The version(s) of the Kolab component(s) you are using.
+                    </para>
+                </listitem>
+                <listitem>
+                    <para>
+                        If a custom version is used, any options that may have specified during the build process.
+                    </para>
+                </listitem>
+            </itemizedlist>
+        </para>
+        <para>
+            provide some text on logging a new ticket in our bugzilla, information to provide, etc. Possibly mention the life cycle of a product version series.
+        </para>
+    </section>
+
+    <section id="sect-Feedback-Mailing_Lists">
+        <title>Mailing Lists</title>
+        <para>
+            For users of Kolab software, we run a public mailing list at <ulink url="https://lists.kolab.org/mailman/listinfo/kolab-users" />. To subscribe to the list, either click the aforementioned link and fill out the information requested, or send an email to <ulink url="mailto:kolab-users-subscribe@kolab.org">kolab-users-subscribe@kolab.org</ulink>.
+        </para>
+
+        <formalpara>
+            <title>Development Mailing List</title>
+            <para>
+                For developers of Kolab software, as well as general discussion on bugs and patches, we run a public mailing list at <ulink url="https://lists.kolab.org/mailman/listinfo/kolab-devel" />. To subscribe to the list and fill out the information requested, or send an email to <ulink url="mailto:kolab-devel-subscribe@kolab.org">kolab-devel-subscribe@kolab.org</ulink>.
+            </para>
+        </formalpara>
+
+        <section id="sect-Feedback-Mailing_Lists-Archives">
+            <title>Archives</title>
+            <para>
+                The archives of both the user support and development discussion mailing list are available through web archives.
+            </para>
+        </section>
+
+    </section>
+
+    <section id="sect-Feedback-IRC">
+        <title>IRC</title>
+        <para>
+            Refer to irc://irc.freenode.net/kolab here.
+        </para>
+    </section>
+
+</section>
+
+