[GRASSweb-list]markus: web help-wanted.html,1.3,1.4

grass at intevation.de grass at intevation.de
Fri Nov 7 04:13:09 EST 2003


Author: markus

Update of /grassrepository/web
In directory doto:/tmp/cvs-serv20209

Modified Files:
	help-wanted.html 
Log Message:
extended

Index: help-wanted.html
===================================================================
RCS file: /grassrepository/web/help-wanted.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- help-wanted.html	27 Nov 2002 09:05:09 -0000	1.3
+++ help-wanted.html	7 Nov 2003 09:13:06 -0000	1.4
@@ -2,7 +2,7 @@
 <html>
 <head>
    <DEFANGED_meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <DEFANGED_meta name="Author" content="GRASS Development Team, ideas from GNU Octave">
+   <DEFANGED_meta name="Author" content="MN/GRASS Development Team, inspired by GNU Octave">
    <DEFANGED_link rel="stylesheet" type="text/css" href="sitestyle.css">
    <title>GRASS: Help wanted!</title>
 </head>
@@ -22,38 +22,42 @@
 Spare time? Nothing to do?
 <p>
 There are a number of ways that you can contribute to help make GRASS a
-better GIS system. Perhaps the most important way to contribute is to write
-high-quality code for solving new problems, and to make your code freely
-available for others to use.  For inspiration, we have a wish-list of
+better GIS system. Perhaps the most important way to contribute is to <b>write
+high-quality code for solving old and new problems</b>, and to make your code freely
+available for others to use. For inspiration, we have a wish-list of
 <a href=http://intevation.de/rt/webrt?q_sort=area&q_reverse=1&q_queue=grass>projects</a>
-and feature requests.
+and feature requests. Just pick a task from the list. It may be a good idea to
+send a small posting to a <a href=support.html>GRASS mailing list</a> to
+announce you activities (maybe someone will join you!).
 </p>
 
-<p> If you've written a useful function or module for GRASS that you would
-like to make available for others to use, please post it to the <a
-href="support.html#grass5_list">GRASS 5 developers</a> mailing list.  Messages
-sent to this list will be seen by the GRASS maintainers, and will be
-considered for inclusion in future releases of GRASS. The messages are also
-<a href="support.html#grass5_list">archived</a>, so even if the code is not
-included in a future release, it will remain available for others to use.
+<p> If you've <b>already written</b> a useful function or module for GRASS that you
+would like to make available for others to use, please post it to the <a
+href="support.html#grass5_list">GRASS 5 developers</a> mailing list. GRASS standard
+code should be written in ANSI-C. Messages sent to this list will be seen by the 
+GRASS maintainers, and will be considered for inclusion in future releases of GRASS.
+The messages are also <a href="support.html#grass5_list">archived</a>, so even if 
+the code is not included in a future release, it will remain available for others to use.
 </p>
 
 <p> If you find GRASS useful, consider <a href="commercial.html">providing
-additional funding</a> to continue its development.  Even a modest amount of
+additional funding</a> to continue its development. Even a modest amount of
 additional funding could make a significant difference in the amount of time
-that its author can devote to development and support. </p>
+that its author can devote to development and support.</p>
 
-<p> If you cannot provide funding or contribute code, you can still help
-make GRASS better and more reliable by <a
-href="bugtracking/bugreport.html">reporting any bugs</a> you find in the latest
-code and by offering suggestions for ways to improve GRASS. Also updates to
-the GRASS manual pages are welcome as well as suggestions for the web pages
-(see contact address at bottom).
+<p> If you are not a programmer and cannot provide funding or contribute code,
+you can still help make GRASS better and more reliable by 
+<a href="bugtracking/bugreport.html">reporting any bugs</a> you find in the 
+latest version and/or by offering suggestions for ways to improve GRASS. 
+The GRASS Development Team appreciates to hear from you!</p>
+
+<p> Also <b>updates to the web pages</b> or to the GRASS <b>manual pages</b> 
+are welcome. Just use the contact address at bottom or our <a href="bugtracking/bugreport.html">bugtracking system</a>.
 </p>
 
 <!-- FOOTER -->
 <hr>
-<DIV ALIGN=right>&copy; 2002 GRASS Development Team<br>
+<DIV ALIGN=right>&copy; 2002-2003 GRASS Development Team<br>
 <a href="mailto:weblist at grass.itc.it">Comments</a> about this page | <a href="faq/index.html">FAQ</a> | <a href="download.html">Download</a> | <a href="support.html">Support</a> | <a href="gdp/index.html">Docs</a>  | <a href="grassdevel.html">Programming</a> | Back <a href=index.html>HOME</a><br>
 <i>Last change:
 $Date$





More information about the grass-web mailing list