forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r230625 - /forrest/trunk/site-author/content/xdocs/committed.xml
Date Sun, 07 Aug 2005 03:38:09 GMT
Author: crossley
Date: Sat Aug  6 20:38:05 2005
New Revision: 230625

URL: http://svn.apache.org/viewcvs?rev=230625&view=rev
Log:
Add paragraph about onlist discussion.

Modified:
    forrest/trunk/site-author/content/xdocs/committed.xml

Modified: forrest/trunk/site-author/content/xdocs/committed.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/committed.xml?rev=230625&r1=230624&r2=230625&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/committed.xml (original)
+++ forrest/trunk/site-author/content/xdocs/committed.xml Sat Aug  6 20:38:05 2005
@@ -110,11 +110,16 @@
       nobody has any objection or anything to add. It is only if people 
       respond that you need to discuss further. Once the discussion reaches 
       consensus then coding can accelerate. Once you have implicit or explicit 
-      approval for your contribution just go ahead and do it. Be sure to 
+      approval for your contribution, just go ahead and do it. Be sure to 
       document what you have done whilst you are at it. Without 
       documentation (comments in code, mailing list discussion and user 
       docs) your code is next to useless - nobody knows it is there and 
       nobody knows how it works.</p>
+    <p>Online discussion is important for community building.
+      Offline discussion and one-to-one conversations deny the
+      community the chance to become involved and lead to solutions
+      that are not ideal. So please do as much discussion as possible
+      on the dev or user mailing list.</p>
     </section>
     <section id="references">
       <title>References</title>



Mime
View raw message