svn commit: r972382 - in /websites/staging/community/trunk/content: ./ gettingStarted/101.html

[bu...@apache.org]

Author: buildbot
Date: Sat Nov 14 10:39:16 2015
New Revision: 972382

Log:
Staging update by buildbot for community

Modified:
    websites/staging/community/trunk/content/   (props changed)
    websites/staging/community/trunk/content/gettingStarted/101.html

Propchange: websites/staging/community/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Nov 14 10:39:16 2015
@@ -1 +1 @@
-1696907
+1714300

Modified: websites/staging/community/trunk/content/gettingStarted/101.html
==============================================================================
--- websites/staging/community/trunk/content/gettingStarted/101.html (original)
+++ websites/staging/community/trunk/content/gettingStarted/101.html Sat Nov 14 10:39:16 2015
@@ -154,10 +154,21 @@
 <li><a href="/gettingStarted/101.html">101.html</a></li>
 </ul>
    <hr>
-    <h1 id="where-do-i-start">Where do I start?</h1>
+    <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="where-do-i-start">Where do I start?<a class="headerlink" href="#where-do-i-start" title="Permanent link">&para;</a></h1>
 <p>If you have no idea where to start with your engagement with an Apache project 
 this is the page for you.</p>
-<h3 id="finding-the-right-project">Finding the right project</h3>
+<h3 id="finding-the-right-project">Finding the right project<a class="headerlink" href="#finding-the-right-project" title="Permanent link">&para;</a></h3>
 <p>The key to working on projects at Apache (and any open source for that matter)
 is to have a personal reason for being involved. You might be trying to solve 
 a day job issue, you might be looking to learn a new technology or you might 
@@ -174,7 +185,7 @@ level projects" but are still developing
 start "lurking". Read the mails that come through the list. Initially you will not
 understand what people are talking about, but over time you will start to
 pick up the language, objectives, strategies and working patterns of the community.</p>
-<h4 id="finding-an-issue-to-work-on">Finding an issue to work on</h4>
+<h4 id="finding-an-issue-to-work-on">Finding an issue to work on<a class="headerlink" href="#finding-an-issue-to-work-on" title="Permanent link">&para;</a></h4>
 <p>If you are trying to satisfy a specific technical problem then you already know
 what you want to work on, but if you are looking for something useful to do in
 order to participate in an ASF project then the projects issue/bug tracker is your 
@@ -188,7 +199,7 @@ with the label "GSoC" or "mentor", these
 manageable for someone new to the ASF and their project. The community has
 also indicated that they are willing to help someone work on those issues
 through our <a href="/newbiefaq.html#NewbieFAQ-AbouttheApacheMentoringProgramme">mentoring program</a>.</p>
-<h2 id="joining-the-community">Joining the community</h2>
+<h2 id="joining-the-community">Joining the community<a class="headerlink" href="#joining-the-community" title="Permanent link">&para;</a></h2>
 <p>once you have identified an issue you would like to tackle its time to join the 
 projects mailing list (if you haven't already) and get started.</p>
 <p>Remember, community members usually happy to help, but they have to get something
@@ -201,13 +212,12 @@ mentor you. See our <a href="/mentorprog
 <p>Alternatively you can dive straight in and work with the community. Since you've 
 been lurking on the lists for a while by the time you have got to this point you
 should have a feel for how to get involved, so go for it.</p>
-<h1 id="further-reading">Further Reading</h1>
-<div class="codehilite"><pre><span class="o">*</span> <span class="n">Some</span> <span class="n">common</span> <span class="n">questions</span> <span class="n">are</span> <span class="n">answered</span> <span class="n">in</span> <span class="n">our</span> <span class="p">[</span><span class="n">FAQ</span><span class="p">][</span>5<span class="p">]</span>
-<span class="o">*</span> <span class="n">To</span> <span class="n">learn</span> <span class="n">more</span> <span class="n">about</span> &quot;<span class="n">The</span> <span class="n">Apache</span> <span class="n">Way</span>&quot; <span class="n">of</span> <span class="n">developing</span> <span class="n">software</span> <span class="n">see</span> <span class="n">the</span>
-</pre></div>
-
-
-<p>foundations <a href="http://apache.org/foundation/how-it-works.html">How It Works</a> pages.</p>
+<h1 id="further-reading">Further Reading<a class="headerlink" href="#further-reading" title="Permanent link">&para;</a></h1>
+<ul>
+<li>Some common questions are answered in our <a href="/newbiefaq.html">FAQ</a></li>
+<li>To learn more about "The Apache Way" of developing software see the 
+foundations <a href="http://apache.org/foundation/how-it-works.html">How It Works</a> pages.</li>
+</ul>
   </div>
   
   <footer class="footer" align="center">