bernhard: doc/www/src getting-involved.html.m4,1.1,1.2

[cvs at kolab.org]

Author: bernhard

Update of /kolabrepository/doc/www/src
In directory doto:/tmp/cvs-serv19771

Modified Files:
	getting-involved.html.m4 
Log Message:
Improved the getting-involved page a bit. Mainly replaced "project" with "community".


Index: getting-involved.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/getting-involved.html.m4,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- getting-involved.html.m4	18 May 2005 12:54:02 -0000	1.1
+++ getting-involved.html.m4	23 Nov 2007 17:05:14 -0000	1.2
@@ -4,37 +4,40 @@
 
 <h1>Getting Involved</h1>
 
-Kolab is an open project welcoming any type of helpful contribution!
-If you like, you can become an active member of the Kolab Groupware Project.
+Kolab is an open community welcoming any type of helpful contribution!
+If you like, you can become an active member.
 
 <p>
-Becoming a member of the Kolab Groupware Project is in fact fairly easy.
-Depending on your area of interest and level of expertise you may perhaps identify
-one of these items where you like to contribute:
+Becoming a member of the Kolab community is easy: Connect
+with us and just contribute!
+Pick something you like to do, here are some ideas:
 
 <ul>
-<li>Testing Kolab Server and/or Kolab Klients: report bugs and wishes
-    into our issue tracker
+<li>Help other to understand and run Kolab.
+<li>Testing Kolab Server and/or Kolab Clients: report bugs and wishes
+    into our issue tracker or the development mailinglist.
 <li>Report any trouble-shooting findings and other valuable information
     into the Kolab Wiki
 <li>Write/polish documentation: There is quite some documentation already,
     but largely unsorted. Ask on the devel-list for what you could do.
 <li>Consolidate information from the mailing lists into the Wiki.
-<li>Fix bugs on your own: the issue tracker has lots of open items.
+<li>Help to fix problems: the issue tracker has lots of open items.
     If you feel competent, pick one that lies in your realm and solve it.
-    Don't forget to let others know you are working on a bug (ie. assign
+    Don't forget to let others know you are working on an issue  (ie. assign
     it to yourself and change the status accordingly).
 <li>Improve our web-site. It always needs work.
-<li>...
+<li>Share your experiences! May they be good or bad.
+<li>Design some nice artwork to promote Kolab.
 </ul>
 
 In any case you should subscribe to at least one of the mailing lists
 and participate there. Don't be frustrated if some emails remain unanswered -
 sometimes the others are simply lacking time or it may slip out of
-intention. Just remind if no reaction occurs. And give answers yourself
-where you can ;-)
+intention. Just send a reminder after a few days. 
+And give answers yourself where you can. ;-)
 
 <p>
-Everyone who continously contributes to Kolab can get CVS write access.
+Everyone who continously contributes to Kolab can get write access
+to the software repository.
 
 m4_include(footer.html.m4)