created new file moved in "Join Gnome" section copied in material from

  * gosfeedback.xml:
  created new file
  moved in "Join Gnome" section
  copied in material from gnome-feedback/C/gnome-feedback.xml Fixes #335968

1 files changed, 105 insertions, 0 deletions

diff --git a/gnome2-user-guide/C/gosfeedback.xml b/gnome2-user-guide/C/gosfeedback.xml
new file mode 100644
index 0000000..1d0faf2
--- /dev/null
+++ b/gnome2-user-guide/C/gosfeedback.xml
@@ -0,0 +1,105 @@
+  <appendix id="feedback">
+    <title>Feedback</title>
+    <para>This section contains information on reporting bugs in GNOME, making suggestions and comments about GNOME applications or documentation, and ways in which you can help GNOME.</para>
+    
+
+    <section id="feedback-bugs">
+    <title>Reporting Bugs</title>
+    <!-- NOTE TO TRANSLATORS: This section is material taken from gnome-desktop/desktop-docs/gnome-feedback/ Look for existing translations there before translating it all over again :) -->
+      <para>
+     If you have found a bug in one of GNOME applications, please
+   report it! Developers do read all the bug reports and try to fix
+   these bugs. Please try to be as specific as possible when
+   describing the circumstances under which the bug shows (what
+   commands did you enter? which buttons did you click?). If there were any
+   error messages, be sure to include them, too.  
+      </para> 
+      <para>
+	The easiest way to report bugs is by using <application>Bug
+	  Report Tool</application> (<command>bug-buddy</command>),
+	  available in the <guisubmenu>System Tools</guisubmenu> submenu
+	  of <guimenu>Applications</guimenu> menu. This utility will guide you
+	  through the bug reporting process; it will also
+	  automatically collect some information necessary for
+	  developers, such as versions of the operating system and
+	  libraries you are using. In the event that an application crashes, the <application>Bug
+	  Report Tool</application> will launch automatically.
+      </para>
+      <para>
+	You can also submit bugs and browse the list of known bugs by
+	connecting to the <ulink type="http"
+	url="http://bugzilla.gnome.org/">GNOME bug tracking
+	database</ulink>.  You will need to register before you can
+	submit any bugs this way — and do not forget to read
+	<ulink type="http"
+	url="http://bugzilla.gnome.org/bugwritinghelp.html">Bug
+	Writing Guidelines</ulink>. 
+      </para>
+      
+      <para>
+	Please note that some of GNOME applications are developed outside of GNOME, or by
+	commercial companies (these products are still free
+	software). For example, <application>Inkscape</application>, a
+	vector graphics application, is developed at <ulink type="http"
+	url="http://sourceforge.net/projects/inkscape/">SourceForge</ulink>. Bugs reports and
+	comments about these products should be directed to the
+	respective organization or company. If you are using <application>Bug Report
+	Tool</application>, it will automatically send bug reports to
+	the correct database.
+	</para>
+
+
+    </section>
+    <section id="feedback-wishlist"> 
+      <title>Suggestions and Comments</title> 
+      <!-- NOTE TO TRANSLATORS: This section is material taken from gnome-desktop/desktop-docs/gnome-feedback/ Look for existing translations there before translating it all over again :) -->      
+      <para> 
+	If you have a suggestion or want to request a new feature for
+      one of the applications, it can also be done using the bug
+      tracking database. Submit your suggestion as a bug report as
+      described in <xref linkend="feedback-bugs" /> and at the appropriate
+      step select <guilabel>Severity: Enhancement</guilabel>. 
+      </para>
+    </section>
+
+      <section id="feedback-docs">
+      <title>Documentation Comments</title>
+      <!-- NOTE TO TRANSLATORS: This section is material taken from gnome-desktop/desktop-docs/gnome-feedback/ Look for existing translations there before translating it all over again :) -->      
+
+      <para> If you found an inaccuracy or misprint in one of GNOME
+	documents, or have any comments or suggestions about
+	documentation, please let us know! The easiest way of doing so
+	is by submitting a bug report as explained before and
+	selecting <guilabel>Component: docs</guilabel> at appropriate
+	steps (or <guilabel>general</guilabel> if there is no
+	<guilabel>docs</guilabel> component). If your comment is about
+	general GNOME documentation (such as <citetitle>GNOME Users
+	Guide</citetitle>) rather than specific application manual,
+	select <guilabel>Product: gnome-user-docs</guilabel>.
+      </para>
+      <para>
+	Alternatively, you can just send your comments by email to the
+	<ulink type="http"
+	url="http://live.gnome.org/DocumentationProject">GNOME
+	Documentation Project</ulink> mailing list; our address is
+	<email>gnome-doc-list@gnome.org</email>. And by the way: if you are not
+	a developer but want to help GNOME —
+	<ulink type="http"
+	url="http://live.gnome.org/DocumentationProject/Join">join
+	the GDP</ulink> and help us  improve GNOME documentation.
+      </para>
+    </section>
+    <!-- NOTE TO TRANSLATORS: end of old material -->
+
+
+    <section id="joingnome">
+      <title>Joining the GNOME Project</title>
+      <para>We hope you enjoy using GNOME and that you find working with GNOME productive. However, there is always room for improvement.</para>
+      <para>GNOME invites you to join our free software community if you have some spare time. There are many different fields. GNOME needs programmers, but it also needs translators, documentation writers, testers, artists, writers, and more.</para>
+      <para>For more information on joining GNOME, please visit <ulink type="http" url="http://live.gnome.org/JoinGnome">http://live.gnome.org/JoinGnome</ulink>.</para>
+      <para>For more information on giving feedback on GNOME, such as bug reports, suggestions, and corrections to documentation, see the section on <ulink type="help" url="ghelp:gnome-feedback">Reporting GNOME Bugs</ulink>.</para>
+
+    </section>
+  
+
+  </appendix>