subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cmpil...@apache.org
Subject svn commit: r902217 - /subversion/site/publish/contributing.html
Date Fri, 22 Jan 2010 18:41:48 GMT
Author: cmpilato
Date: Fri Jan 22 18:41:47 2010
New Revision: 902217

URL: http://svn.apache.org/viewvc?rev=902217&view=rev
Log:
* site/publish/contributing.html
  Some tag/style tweaks, but also flesh out a couple of the remaining
  paragraphs.

Modified:
    subversion/site/publish/contributing.html

Modified: subversion/site/publish/contributing.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/contributing.html?rev=902217&r1=902216&r2=902217&view=diff
==============================================================================
--- subversion/site/publish/contributing.html (original)
+++ subversion/site/publish/contributing.html Fri Jan 22 18:41:47 2010
@@ -21,71 +21,104 @@
    the community.  Fortunately most of these require little more than
    an interest in Subversion and helping other members of the community.</p>
 
-<div class="h2" id="content" title="Help Others Learn">
+<div class="h2" id="educate" title="educate">
 <h2>Help Others Learn</h2>
+
 <ul>
-<li><strong>Participate in the mailing lists</strong>
-    <p>There are community <a href="mailing-lists.html">mailing lists</a>
you
-    can join to discuss Subversion. The lists are an excellent source for
-    users and contributors interested in having technical discussions,
-    answering questions, or resolving potential issues for newcomers.</p>
-</li>
-
-<li><strong>Promote Subversion</strong>
-    <p>Help promote Subversion by using your blog, Twitter, Facebook, or
-    submitting an article to your favorite local magazine. If you are a member
-    of a different open source community, why not mention Subversion on their
-    discussion forums or at conferences? If you love Subversion, don't hold
-    back - speak up&#33; The more developers use Subversion, the more bugs
-    will be caught, the more features will be added, the more visible the
-    project, and the more benefits the community will get&#33;</p>
-</li>
-
-<li><strong>Link to subversion.apache.org</strong>
-    <p>The success of any open source project depends on the number of people
-    who use the product and contribute back to the project. By linking to
-    subversion.apache.org, you can increase the chances of a new user or
-    contributor finding out about the project and joining the community.</p>
+<li><p style="font-weight: bold;">Participate in the mailing lists</p>
+    <p>There are community <a href="mailing-lists.html">mailing
+       lists</a> you can join to discuss Subversion. The lists are an
+       excellent source for users and contributors interested in
+       having technical discussions, answering questions, or resolving
+       potential issues for newcomers.</p>
+</li>
+
+<li><p style="font-weight: bold;">Promote Subversion</p>
+    <p>Help promote Subversion by using your blog,
+       <a href="http://twitter.com/" >Twitter</a>,
+       <a href="http://facebook.com/" >Facebook</a>, or submitting an
+       article to your favorite local magazine.  If you are a member
+       of a different open source community, why not mention
+       Subversion on their discussion forums or at conferences? If you
+       love Subversion, don't hold back &mdash; speak up!  The more
+       developers use Subversion, the more bugs will be caught, the
+       more features will be added, the more visible the project, and
+       the more benefits the community will get.</p>
+</li>
+
+<li><p style="font-weight: bold;">Link to subversion.apache.org</p>
+    <p>The success of any open source project depends on the number of
+       people who use the product and contribute back to the project.
+       By linking to <a href="http://subversion.apache.org"
+       >http://subversion.apache.org</a>, you increase the chances of
+       a new user or contributor finding out about the project and
+       joining the community.</p>
 </li>
 </ul>
-</div>
 
-<div class="h2" id="code" title="Contribute Code">
-<h2>Contribute Code</h2>
-<ul>
-<li><strong>File a bug report</strong>
-    <p>Bug reports take little time to file and are very helpful to
-    developers. This is one of the easiest contributions you can make. When
-    you discover a problem with Subversion, please report it. Our preference
-    as a community is to have you first report the bug to the <a
-    href="mailto:users@subversion.apache.org">users@subversion.apache.org</a>
-    mailing list so that other community members can provide some first-level
-    help and triage. Often times there may already be a solution or answer
-    to your problem.</p>
-</li>
+</div> <!-- #educate -->
 
-<li><strong>Help us triage existing bug reports</strong>
-    <p>Provide details on looking at open issues on issue tracker.
-    Describe what to do when a problem appears to no longer exist.
-    Lead into next item about creating reproduction recipes.</p>
-</li>
 
-<li><strong>Write a test or reproduction script</strong>
-    <p>Provide some reasons why writing a shell script to reproduce a problem
-    can help.  Maybe link to an example?</p>
-</li>
-
-<li><strong>Submit a patch</strong>
-    <p>Link to hacking and section on contributing patches, coding
-    conventions etc.</p>
-</li>
+<div class="h2" id="code" title="code">
+<h2>Contribute Code</h2>
 
-<li><strong>Become a committer and commit code directly</strong>
-    <p>Developers with a long history of submitting high-quality patches can
-    gain direct commit rights.</p>
+<ul>
+<li><p style="font-weight: bold;">File a bug report</p>
+    <p>Bug reports take little time to file and are very helpful to
+       developers.  This is one of the easiest contributions you can
+       make.  When you discover a problem with Subversion, please
+       report it.  Our preference as a community is to have you first
+       report the bug to the <a href="mailto:users@subversion.apache.org"
+       >users@subversion.apache.org</a> mailing list so that other
+       community members can provide some first-level help and triage.
+       Often times there may already be a solution or answer to your
+       problem.</p>
+</li>
+
+<li><p style="font-weight: bold;">Help us triage existing bug reports</p>
+    <p class="todo">Provide details on looking at open issues on issue tracker.
+       Describe what to do when a problem appears to no longer exist.
+       Lead into next item about creating reproduction recipes.</p>
+</li>
+
+<li><p style="font-weight: bold;">Write a test or reproduction script</p>
+    <p class="todo">Provide some reasons why writing a shell script to reproduce a
+       problem can help.  Maybe link to an example?</p>
+</li>
+
+<li><p style="font-weight: bold;">Submit a patch</p>
+
+    <p>The open-source adage "Patches welcome" may show up most
+       frequently as a thread-killing retort to mailing list trolls,
+       but at the heart of the statement are two quite genuine ideals:
+       software code doesn't write itself, and projects generally
+       really do want as many people as possible to help write that
+       code.  The Subversion project is no different.  We've accepted
+       and applied countless patch contributions, and we hope to
+       always have a constant stream of them.  If you're a developer
+       able to contribute in this way, take a cruise through our
+       <a href="docs/community-guide/">Subversion Community Guide</a>,
+       specifically the sections regarding
+       <a href="docs/community-guide/#patches">patch submissions</a> and
+       <a href="docs/community-guide/#conventions">coding conventions</a>,
+       and come join the fun!</p>
+</li>
+
+<li><p style="font-weight: bold;">Become a committer and commit code directly</p>
+    <p>Developers with a long history of submitting high-quality
+       patches can gain direct commit rights.  This is obviously
+       beneficial to the developer community &mdash; where quality
+       developers are concerned, "the more, the merrier"!  But never
+       underestimate how valuable this experience can be to you
+       personally
+       and <a href="http://onlamp.com/pub/a/onlamp/2005/07/14/osdevelopers.html"
+       >professionally</a>,
+       <a href="http://onlamp.com/pub/a/onlamp/2005/08/01/opensourcedevelopers.html"
+       >too</a>.</p>
 </li>
 </ul>
-</div>
+
+</div> <!-- #code -->
 
 <p>For more information about how to contribute, or to discuss your
    contribution with us, please contact <a



Mime
View raw message