[evolvis-commits] r12778: Small renames in contribution document

mirabilos at evolvis.org mirabilos at evolvis.org
Mon Feb 28 01:59:19 CET 2011


Author: mirabilos
Date: 2011-02-28 01:59:19 +0100 (Mon, 28 Feb 2011)
New Revision: 12778

Modified:
   trunk/gforge_base/evolvisforge-5.1/gforge/docs/docbook/docbook/contribution_guide/include/howto_contribute.xml
Log:
Small renames in contribution document

Modified: trunk/gforge_base/evolvisforge-5.1/gforge/docs/docbook/docbook/contribution_guide/include/howto_contribute.xml
===================================================================
--- trunk/gforge_base/evolvisforge-5.1/gforge/docs/docbook/docbook/contribution_guide/include/howto_contribute.xml	2011-02-28 00:59:17 UTC (rev 12777)
+++ trunk/gforge_base/evolvisforge-5.1/gforge/docs/docbook/docbook/contribution_guide/include/howto_contribute.xml	2011-02-28 00:59:19 UTC (rev 12778)
@@ -1,7 +1,7 @@
 <section id="cg_howto_contribute">
 	<title>How to contribute</title>
 	<para>
-		There are several ways to contribute to the Gforge project.
+		There are several ways to contribute to the FusionForge project.
 	</para>
 	<itemizedlist>
 		<listitem>
@@ -11,17 +11,17 @@
 			<para>You are willing to help develop new features. Give a look at the PM/Task Manager. The three subprojects (Todo, Documentation, Localization) lists the open tasks. You can pick up one of the open tasks and start working on it.</para>
 		</listitem>
 		<listitem>
-			<para>If you find a bug, submit a bug to the Bug tracker at <ulink url="http://gforge.org/tracker/?group_id=1">http://gforge.org/tracker/?group_id=1</ulink>. If you already solved the bug and are willing to share the fix with us, please add a patch to the bug.</para>
+			<para>If you find a bug, submit a bug to the Bug tracker at <ulink url="http://fusionforge.org/tracker/?group_id=6">http://fusionforge.org/tracker/?group_id=6</ulink>. If you already solved the bug and are willing to share the fix with us, please add a patch to the bug.</para>
 		</listitem>
 		<listitem>
-			<para>If you have developed some new feature, submit a patch to the patch manager of gforge. The submitted patch should follow the Coding and Templating standards described in this document.</para>
+			<para>If you have developed some new feature, submit a patch to the patch manager of fusionforge. The submitted patch should follow the Coding and Templating standards described in this document.</para>
 		</listitem>
 		<listitem>
-			<para>Documentation: there are some parts of Gforge that are not well documented. Refer to the Task Manager, Documentation subproject for a list of open tasks. You should write the documentation in the xdoc format as described in this section.</para>
+			<para>Documentation: there are some parts of FusionForge that are not well documented. Refer to the Task Manager, Documentation subproject for a list of open tasks. You should write the documentation in the docbook format as described in this section.</para>
 		</listitem>
 		<listitem>
-			<para>Localization: The user interface of gforge is now nearly completely localized. We need translators for the different languages.</para>
-			<para>If you like to translate gforge to a new, not listed language, you can refer to the Localization Howto document to see how to add a new language</para>
+			<para>Localization: The user interface of fusionforge is now nearly completely localized. We need translators for the different languages.</para>
+			<para>If you like to translate fusionforge to a new, not listed language, please contact us.</para>
 		</listitem>
 	</itemizedlist>
 </section>
\ No newline at end of file



More information about the evolvis-commits mailing list