svn commit: r840128 - in /websites/staging/stanbol/trunk/content: ./ development/index.html

[bu...@apache.org]

Author: buildbot
Date: Fri Nov 30 13:05:57 2012
New Revision: 840128

Log:
Staging update by buildbot for stanbol

Modified:
    websites/staging/stanbol/trunk/content/   (props changed)
    websites/staging/stanbol/trunk/content/development/index.html

Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 30 13:05:57 2012
@@ -1 +1 @@
-1413162
+1415614

Modified: websites/staging/stanbol/trunk/content/development/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/development/index.html (original)
+++ websites/staging/stanbol/trunk/content/development/index.html Fri Nov 30 13:05:57 2012
@@ -113,12 +113,24 @@ followed by the Apache Stanbol project.<
 <li><a href="coding.html">Coding Standards</a></li>
 <li><a href="release-management.html">Release Management</a></li>
 </ul>
+<h2 id="discussions-decisions-and-tracking-new-features">Discussions, decisions and tracking new features</h2>
+<p>Everything has to be discussed on the dev mailing list prior to any
+implementation action. If it is not on the list, it did not happen.</p>
+<p>New features should be backed by JIRA issues that describe the goals,
+use cases and software design decisions, which are usually the result 
+of dev list discussions. It is much easier to refer to JIRA issues describing 
+the implementation details for further discussions and later reference. </p>
+<p>The dev list is not a good place for persistent information, but JIRA issues 
+can also be used as an initial form of documentation for new 
+features: add usage and test instructions to the JIRA issues once your features
+reaches a usable state, so that others can test them. This is a good way of
+evolving the features documentation, as you work on the implementation.</p>
 <h2 id="documentation">Documentation</h2>
-<p>A good documentation is nearly as important as the software itself. Here you
-can find information how to contribute to it.</p>
-<ul>
-<li><a href="website.html">Website Development</a></li>
-</ul>
+<p>As mentioned below, starting with JIRA issues that describe what you're doing and 
+how to use and test it is often good enough, and it's a good way to document things
+as you go.</p>
+<p>Once new features reach a somewhat stable state, it's good to document them on 
+the website. See <a href="website.html">Website Development</a> for more info.</p>
   </div>
   
   <div id="footer">