directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r929051 - in /websites/staging/directory/trunk/content: ./ contribute.html
Date Thu, 13 Nov 2014 11:19:18 GMT
Author: buildbot
Date: Thu Nov 13 11:19:17 2014
New Revision: 929051

Log:
Staging update by buildbot for directory

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

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Nov 13 11:19:17 2014
@@ -1 +1 @@
-1639301
+1639302

Modified: websites/staging/directory/trunk/content/contribute.html
==============================================================================
--- websites/staging/directory/trunk/content/contribute.html (original)
+++ websites/staging/directory/trunk/content/contribute.html Thu Nov 13 11:19:17 2014
@@ -173,6 +173,18 @@ These contributions, whether you think o
 <p>So, you consider contributing to our project. But how do you go about achieving
this? </p>
 <p>Well, it is as easy as pie. The first thing you need to do is to subscribe to one
of our mailing lists (see the overview below) and you are set to go to deliver your first
contribution: a posting there, about how great our product are, what you found missing, or
even the bug you're confronted with.
 You might even consider a more interactive approach and join the team on our irc channels.</p>
+<p>After you have had your first contribution over and done with, it stays easy. You
can:
+<em> reply to questions, and/or share your viewpoint on how to get issues resolved,
+</em> add to our FAQ or WIKI,
+<em> share your code and document patches through our issue management solution (JIRA),
+</em> evaluate bugs and proposed improvements provided by others in our team,
+* help with outlining and evaluating the future direction of our project and the development
iterations of our products.</p>
+<p>To make it a bit more explicit, we are looking for:
+<em> Source code and fixes contributions
+</em> Documentation assistance
+<em> Product and feature suggestions
+</em> Detailed and constructive feedback
+* Articles and white papers</p>
 <p>To begin with, we suggest you to subscribe to the <a href="mailing-lists-and-irc.html">Directory
Mailing Lists &amp; IRC</a> (follow the link for information on how to subscribe
and to access the mail list archives). Listen-in for a while, to see how others make contributions.</p>
 <p>Then you can :</p>
 <ul>



Mime
View raw message