svn commit: r863693 - in /websites/staging/gora/trunk/content: ./ contribute.html

[bu...@apache.org]

Author: buildbot
Date: Thu May 30 02:28:55 2013
New Revision: 863693

Log:
Staging update by buildbot for gora

Modified:
    websites/staging/gora/trunk/content/   (props changed)
    websites/staging/gora/trunk/content/contribute.html

Propchange: websites/staging/gora/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 30 02:28:55 2013
@@ -1 +1 @@
-1484568
+1487708

Modified: websites/staging/gora/trunk/content/contribute.html
==============================================================================
--- websites/staging/gora/trunk/content/contribute.html (original)
+++ websites/staging/gora/trunk/content/contribute.html Thu May 30 02:28:55 2013
@@ -130,25 +130,26 @@ We encourage open discussion and open de
 on the <a href="./mailing_lists.html">mailing lists</a> and <a href="https://issues.apache.org/jira/browse/GORA">Jira issues</a>.</p>
 <p>Simply put, gora needs you help to move forward. Like all open source projects, you can help gora in several ways:</p>
 <ul>
-<li>Bug reporting: No software is bug-free. So please report any issues that arise while using 
+<li><strong>Bug reporting</strong>: No software is bug-free. So please report any issues that arise while using 
   Gora by commenting on an existing bug, or opening a new bug report. You can search, 
   and create new bug reports <a href="https://issues.apache.org/jira/browse/GORA">here</a>.</li>
-<li>Feature Request: Gora should be driven further by feature requests from the community. 
+<li><strong>Feature Request</strong>: Gora should be driven further by feature requests from the community. 
   Reporting ideas for improvement on existing features and new features can help the 
   developers to re-arrange priorities for the project. Use the 
   <a href="https://issues.apache.org/jira/browse/GORA">issue tracker</a> for reporting feature 
   requests, or mention your idea at the dev@ mailing list.</li>
-<li>Developing Patches: We of course welcome patches from the community. 
+<li><strong>Developing Patches</strong>: We of course welcome patches from the community. 
   If you find an issue you want to fix, create the issue, develop the patch 
-  and attach the patch to the issue.</li>
-<li>Sharing Use Cases: You can share how you use gora in your projects. We
+  and attach the patch to the issue. You can see some of the <strong>newbie</strong> issues 
+  <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%2012311172%20AND%20labels%20%3D%20newbie">here</a></li>
+<li><strong>Sharing Use Cases</strong>: You can share how you use gora in your projects. We
   also encourage users to add thier use cases to our <a href="./poweredby.html">PoweredBy</a> page.</li>
-<li>Contributing Documentation: You can also contribute to the ongoing documentation 
+<li><strong>Contributing Documentation</strong>: You can also contribute to the ongoing documentation 
   effort of the project by editing <a href="https://cwiki.apache.org/confluence/display/GORA/Index">wiki pages</a>, 
   improving javadocs or writing blog posts. You can also answer user questions at the <a href="./mailing_lists.html">mailing lists</a>.</li>
-<li>Spreading the word: We encourage you to share your feedback on gora with us and 
+<li><strong>Spreading the word</strong>: We encourage you to share your feedback on gora with us and 
   with others, by tweeting, blogging, etc.</li>
-<li>Participating in GSoC: As a community and project, Gora has a successful record
+<li><strong>Participating in GSoC</strong>: As a community and project, Gora has a successful record
   in participating in <a href="https://developers.google.com/open-source/soc/">Google Summer of Code</a>.
   As a community we greatly encourage students to engage in such efforts. </li>
 </ul>