community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r972556 [1/3] - in /websites/staging/community/trunk/content: ./ apache-extras/ calendars/ committers/ contributors/ events/ mentoring/ newcomers/ proposals/ speakers/
Date Mon, 16 Nov 2015 08:24:19 GMT
Author: buildbot
Date: Mon Nov 16 08:24:18 2015
New Revision: 972556

Log:
Staging update by buildbot for community

Removed:
    websites/staging/community/trunk/content/apache-extras/
Modified:
    websites/staging/community/trunk/content/   (props changed)
    websites/staging/community/trunk/content/boardreport.html
    websites/staging/community/trunk/content/calendars/conferences.html
    websites/staging/community/trunk/content/calendars/index.html
    websites/staging/community/trunk/content/comdevboardreports.html
    websites/staging/community/trunk/content/comdevboardresolution.html
    websites/staging/community/trunk/content/committers/consensusBuilding.html
    websites/staging/community/trunk/content/committers/decisionMaking.html
    websites/staging/community/trunk/content/committers/funding-disclaimer.html
    websites/staging/community/trunk/content/committers/index.html
    websites/staging/community/trunk/content/committers/lazyConsensus.html
    websites/staging/community/trunk/content/committers/voting.html
    websites/staging/community/trunk/content/contactpoints.html
    websites/staging/community/trunk/content/contributors/index.html
    websites/staging/community/trunk/content/events/small-events.html
    websites/staging/community/trunk/content/gsoc-admin-tasks.html
    websites/staging/community/trunk/content/gsoc.html
    websites/staging/community/trunk/content/guide-to-being-a-mentor.html
    websites/staging/community/trunk/content/index.html
    websites/staging/community/trunk/content/links.html
    websites/staging/community/trunk/content/localmentors.html
    websites/staging/community/trunk/content/mentee-ranking-process.html
    websites/staging/community/trunk/content/mentor-request-mail.html
    websites/staging/community/trunk/content/mentoring/experiences.html
    websites/staging/community/trunk/content/mentoringprogramme-icfoss-pilot.html
    websites/staging/community/trunk/content/mentoringprogramme.html
    websites/staging/community/trunk/content/mentorprogrammeapplication.html
    websites/staging/community/trunk/content/mentorprogrammeformaleducation.html
    websites/staging/community/trunk/content/newbiefaq.html
    websites/staging/community/trunk/content/newcomers/index.html
    websites/staging/community/trunk/content/newcommitter.html
    websites/staging/community/trunk/content/projectIndependence.html
    websites/staging/community/trunk/content/proposals/ZestProposal.html
    websites/staging/community/trunk/content/speakers/index.html
    websites/staging/community/trunk/content/speakers/slides.html
    websites/staging/community/trunk/content/speakers/speakers.html
    websites/staging/community/trunk/content/use-the-comdev-issue-tracker-for-gsoc-tasks.html

Propchange: websites/staging/community/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Nov 16 08:24:18 2015
@@ -1 +1 @@
-1714300
+1714524

Modified: websites/staging/community/trunk/content/boardreport.html
==============================================================================
--- websites/staging/community/trunk/content/boardreport.html (original)
+++ websites/staging/community/trunk/content/boardreport.html Mon Nov 16 08:24:18 2015
@@ -153,7 +153,18 @@
 <li><a href="/boardreport.html">BoardReport</a></li>
 </ul>
    <hr>
-    <p>Top-level projects report to the board once a quarter, Incubator podlings usually monthly. </p>
+    <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>
+<p>Top-level projects report to the board once a quarter, Incubator podlings usually monthly. </p>
 <p>The ASF Board currently meets on the
 third Wednesday of every month, and projects need to report well in advance of that, as reports are 
 reviewed before the meeting.</p>

Modified: websites/staging/community/trunk/content/calendars/conferences.html
==============================================================================
--- websites/staging/community/trunk/content/calendars/conferences.html (original)
+++ websites/staging/community/trunk/content/calendars/conferences.html Mon Nov 16 08:24:18 2015
@@ -154,7 +154,18 @@
 <li><a href="/calendars/conferences.html">Apache Conferences Calendar</a></li>
 </ul>
    <hr>
-    <p>This calendar lists events relating to The Apache Software Foundation and its projects. </p>
+    <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>
+<p>This calendar lists events relating to The Apache Software Foundation and its projects. </p>
 <p>This Calendar is maintained by the Apache Community Development Committee (ComDev), 
 to have your event listed considered for addition please mail <a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.
 Note that to be listed in this calendar events must conform to the <a href="http://www.apache.org/foundation/marks/events.html">Third Party Event Branding Policy</a>. </p>

Modified: websites/staging/community/trunk/content/calendars/index.html
==============================================================================
--- websites/staging/community/trunk/content/calendars/index.html (original)
+++ websites/staging/community/trunk/content/calendars/index.html Mon Nov 16 08:24:18 2015
@@ -153,11 +153,22 @@
 <li><a href="/calendars">Calendars</a></li>
 </ul>
    <hr>
-    <p>This calendar lists events relating to The Apache Software Foundation and its projects. </p>
+    <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>
+<p>This calendar lists events relating to The Apache Software Foundation and its projects. </p>
 <p>This Calendar is maintained by the Apache Community Development Committee (ComDev), 
 to have your event listed considered for addition please mail <a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.
 Note that to be listed in this calendar events must conform to the <a href="http://www.apache.org/foundation/marks/events.html">Third Party Event Branding Policy</a>. </p>
-<h2 id="upcoming-events">Upcoming events</h2>
+<h2 id="upcoming-events">Upcoming events<a class="headerlink" href="#upcoming-events" title="Permanent link">&para;</a></h2>
 <p><ul id="events">
  <li><i>List loading</i></li>
 </ul></p>
@@ -171,7 +182,7 @@ style="border: 0" width="800" height="60
 
 <script src="https://apis.google.com/js/client.js"></script>
 
-<h2 id="related-events">Related Events</h2>
+<h2 id="related-events">Related Events<a class="headerlink" href="#related-events" title="Permanent link">&para;</a></h2>
 <p>In addition to Official Apache Events, there are a wide range of other
 events which feature Apache projects and technologies. A list of upcoming
 <a href="http://www.apache.org/events/meetups.html">Apache related Meetups is available</a>, powered in part by <a href="https://svn.apache.org/repos/asf/comdev/tools/get_meetups">this script</a>

Modified: websites/staging/community/trunk/content/comdevboardreports.html
==============================================================================
--- websites/staging/community/trunk/content/comdevboardreports.html (original)
+++ websites/staging/community/trunk/content/comdevboardreports.html Mon Nov 16 08:24:18 2015
@@ -153,11 +153,22 @@
 <li><a href="/comdevboardreports.html">ComDevBoardReports</a></li>
 </ul>
    <hr>
-    <p>This page contains records of the Apache Community Development Project
+    <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>
+<p>This page contains records of the Apache Community Development Project
 board reports. The official record of these reports is the minutes of the
 appropriate board meeting, they are provided here for convenience.</p>
 <p><a name="ComDevBoardReports-Draftreportfornextmeeting"></a></p>
-<h1 id="draft-report-for-next-meeting">Draft report for next meeting</h1>
+<h1 id="draft-report-for-next-meeting">Draft report for next meeting<a class="headerlink" href="#draft-report-for-next-meeting" title="Permanent link">&para;</a></h1>
 <p>The following report is <em>incomplete</em> and <em>draft</em> only. It is being prepared
 for the next submission to the board. Submitted reports can be found
 further down the page.</p>
@@ -211,7 +222,7 @@ Actions:
 </div>
 
 <p><a name="ComDevBoardReports-SubmittedReports"></a></p>
-<h1 id="submitted-reports">Submitted Reports</h1>
+<h1 id="submitted-reports">Submitted Reports<a class="headerlink" href="#submitted-reports" title="Permanent link">&para;</a></h1>
 <div class="panel" style="background-color: #FFFFCE;border-style: solid;border-width: 1px;">
 <div class="panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;background-color: #F7D6C1;"><B>August 2012</B></div><div class="panelContent" style="background-color: #FFFFCE;"><pre>
 Status report for the Apache Community Development Project

Modified: websites/staging/community/trunk/content/comdevboardresolution.html
==============================================================================
--- websites/staging/community/trunk/content/comdevboardresolution.html (original)
+++ websites/staging/community/trunk/content/comdevboardresolution.html Mon Nov 16 08:24:18 2015
@@ -153,7 +153,18 @@
 <li><a href="/comdevboardresolution.html">ComDevBoardResolution</a></li>
 </ul>
    <hr>
-    <p>The Apache Community Development Project was created in November 2009.</p>
+    <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>
+<p>The Apache Community Development Project was created in November 2009.</p>
 <DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>Board Resolution Creating the Apache Community Development Project</B></DIV><DIV class="codeContent panelContent">
        Establish the Apache Community Development Project
 

Modified: websites/staging/community/trunk/content/committers/consensusBuilding.html
==============================================================================
--- websites/staging/community/trunk/content/committers/consensusBuilding.html (original)
+++ websites/staging/community/trunk/content/committers/consensusBuilding.html Mon Nov 16 08:24:18 2015
@@ -154,7 +154,18 @@
 <li><a href="/committers/consensusBuilding.html">Consensus Building</a></li>
 </ul>
    <hr>
-    <p>In some cases there is no obvious path to take, or you might be a new community, 
+    <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>
+<p>In some cases there is no obvious path to take, or you might be a new community, 
 or a new member of an existing community. In these cases people will often 
 need to build consensus by making proposals and eliciting responses.</p>
 <p>We want to avoid unnecessary discussion and the creation of significant
@@ -162,7 +173,7 @@ amounts of unnecessary mail that everyon
 That is not to say that we want to avoid constructive discussion. This is 
 the lifeblood of a successful project. However, many ASF projects adopt a 
 shorthand notation for showing support, or otherwise, for a proposal.</p>
-<h2 id="expressing-support-or-otherwise">Expressing support (or otherwise)</h2>
+<h2 id="expressing-support-or-otherwise">Expressing support (or otherwise)<a class="headerlink" href="#expressing-support-or-otherwise" title="Permanent link">&para;</a></h2>
 <p>First of all, it is important to understand that everyone is invited to express 
 their opinion of any given action or proposal. Apache projects are community 
 projects in which no single individual has more power than any other single 
@@ -183,7 +194,7 @@ to help implement"</li>
 like "+1000".</p>
 <p>The important thing is that this is not an exact science. It's just a shorthand 
 way of communicating strength of feeling.</p>
-<h2 id="consensus-building-is-not-voting">Consensus Building is Not Voting</h2>
+<h2 id="consensus-building-is-not-voting">Consensus Building is Not Voting<a class="headerlink" href="#consensus-building-is-not-voting" title="Permanent link">&para;</a></h2>
 <p>The confusing thing about this notation is that it is the same notation
 used in a formal vote. Knowing when something is a vote and when it is a 
 preference is important. It's easy to tell though, if the subject does not have 

Modified: websites/staging/community/trunk/content/committers/decisionMaking.html
==============================================================================
--- websites/staging/community/trunk/content/committers/decisionMaking.html (original)
+++ websites/staging/community/trunk/content/committers/decisionMaking.html Mon Nov 16 08:24:18 2015
@@ -154,7 +154,18 @@
 <li><a href="/committers/decisionMaking.html">Decision Making</a></li>
 </ul>
    <hr>
-    <p>The most important thing about engaging with any Apache project is that everyone
+    <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>
+<p>The most important thing about engaging with any Apache project is that everyone
 is equal. All people with an opinion are entitled to express that opinion and, where 
 appropriate, have it considered by the community.</p>
 <p>To some the idea of having to establish consensus in a large and distributed team 
@@ -163,18 +174,18 @@ set of simple processes to ensure things
 <p>In ASF projects we don't like to vote. We reserve that for the few things that need 
 official approval for legal or process reasons (e.g. a release or a new committer). 
 Most of the time we work with the consensus building techniques documented below.</p>
-<h2 id="lazy-consensus">Lazy Consensus</h2>
+<h2 id="lazy-consensus">Lazy Consensus<a class="headerlink" href="#lazy-consensus" title="Permanent link">&para;</a></h2>
 <p><a href="/committers/lazyConsensus.html">Lazy consensus</a> is the first, and possibly the most important, consensus building 
 tool we have. Essentially lazy consensus means that you don't need to get explicit
 approval to proceed, but you need to be prepared to listen if someone objects.</p>
-<h2 id="consensus-building">Consensus Building</h2>
+<h2 id="consensus-building">Consensus Building<a class="headerlink" href="#consensus-building" title="Permanent link">&para;</a></h2>
 <p>Sometimes lazy consensus is not appropriate. In such cases it is necessary to
 make a proposal to the mailing list and discuss options. There are mechanisms
 for quickly showing your support or otherwise for a proposal and 
 <a href="/committers/consensusBuilding.html">building consensus</a> amongst the community.</p>
 <p>Once there is a consensus people can proceed with the work under the <a href="/committers/lazyConsensus.html">lazy 
 consensus</a> model.</p>
-<h2 id="voting">Voting</h2>
+<h2 id="voting">Voting<a class="headerlink" href="#voting" title="Permanent link">&para;</a></h2>
 <p>Occasionally a "feel" for consensus is not enough. Sometimes we need to 
 have a measurable consensus. For example, when <a href="/committers/voting.html">voting</a> in new committers or 
 to approve a release. </p>

Modified: websites/staging/community/trunk/content/committers/funding-disclaimer.html
==============================================================================
--- websites/staging/community/trunk/content/committers/funding-disclaimer.html (original)
+++ websites/staging/community/trunk/content/committers/funding-disclaimer.html Mon Nov 16 08:24:18 2015
@@ -154,7 +154,18 @@
 <li><a href="/committers/funding-disclaimer.html">Funding campaign disclaimer</a></li>
 </ul>
    <hr>
-    <p>Some Apache committers have successfully run funding campaigns to work on their favorite Apache projects.</p>
+    <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>
+<p>Some Apache committers have successfully run funding campaigns to work on their favorite Apache projects.</p>
 <p>This is ok in principle but you have to make it clear that the campaign is your own thing, and avoid any confusion about the role of the 
 ASF and how its projects work.</p>
 <p>He's a nice example disclaimer used by one of our committers:</p>

Modified: websites/staging/community/trunk/content/committers/index.html
==============================================================================
--- websites/staging/community/trunk/content/committers/index.html (original)
+++ websites/staging/community/trunk/content/committers/index.html Mon Nov 16 08:24:18 2015
@@ -153,10 +153,21 @@
 <li><a href="/committers">Committers</a></li>
 </ul>
    <hr>
-    <p>Information that is useful to Apache committers is spread across the whole ASF site.
+    <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>
+<p>Information that is useful to Apache committers is spread across the whole ASF site.
 This page is intended to be an index of useful resources. This site is editable by 
 any Apache Committer, feel free to add anything useful here.</p>
-<h2 id="decision-making">Decision making</h2>
+<h2 id="decision-making">Decision making<a class="headerlink" href="#decision-making" title="Permanent link">&para;</a></h2>
 <p>Decisions in Apache projects are the result of:</p>
 <ul>
 <li>action</li>
@@ -171,7 +182,7 @@ responsibilities, it is necessary to cal
 <p>Each of these three approaches is described more fully on various foundation 
 and project sites. However, we've provided an initial introduction to <a href="/committers/decisionMaking.html">decision
 making</a> here on the community development site.</p>
-<h2 id="project-independence">Project independence</h2>
+<h2 id="project-independence">Project independence<a class="headerlink" href="#project-independence" title="Permanent link">&para;</a></h2>
 <p>While not all aspects of the Apache Way are practiced the same way by 
 all projects at the ASF, there are a number of rules that Apache 
 projects are required to follow – things like complying with PMC 
@@ -184,7 +195,7 @@ opportunity to contribute to and benefit
 of motivation or financial objectives. This is discussed in more detail
 in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
 <p><a name="Index-Assistingwithprojectmanagement"></a></p>
-<h2 id="development-processes">Development processes</h2>
+<h2 id="development-processes">Development processes<a class="headerlink" href="#development-processes" title="Permanent link">&para;</a></h2>
 <p>Each project in Apache is free to define its own development processes as 
 long as they respect our decision making, legal and independence requirements.
 However, over the many years that the ASF has existed many best practices have 
@@ -206,7 +217,7 @@ operate in ways that are largely similar
 </li>
 <li>[ASF Developer section sitemap][19]</li>
 </ul>
-<h2 id="assisting-with-project-management-and-marketing">Assisting with project management and marketing</h2>
+<h2 id="assisting-with-project-management-and-marketing">Assisting with project management and marketing<a class="headerlink" href="#assisting-with-project-management-and-marketing" title="Permanent link">&para;</a></h2>
 <p>There are many visible contributions of value in an Apache projects
 (documentation, testing, coding user support, design etc.), but there are
 also plenty of "back office" tasks that are necessary to maintain a healthy
@@ -218,7 +229,7 @@ activities, although non-committers can
 <li><a href="/newcommitter.html">Assessing and approving new committers</a></li>
 <li><a href="/boardreport.html">Board Reports</a></li>
 </ul>
-<h2 id="speaking-about-apache">Speaking about Apache</h2>
+<h2 id="speaking-about-apache">Speaking about Apache<a class="headerlink" href="#speaking-about-apache" title="Permanent link">&para;</a></h2>
 <p>We encourage all of our committers to speak about Apache Projects, 
 Technologies, and generally help to grow and enhance our community.
 For more information on getting started, see our 
@@ -228,7 +239,7 @@ For more information on getting started,
 and would be committers. For more information on what this program involves,
 and how to sign yourself up for it, please see the 
 <a href="/localmentors.html">Local Mentors</a> page.</p>
-<h2 id="other-resources">Other Resources</h2>
+<h2 id="other-resources">Other Resources<a class="headerlink" href="#other-resources" title="Permanent link">&para;</a></h2>
 <p>There is no shortage of useful resources for committers at Apache, 
 here are a few you might want to take a look at:</p>
 <ul>

Modified: websites/staging/community/trunk/content/committers/lazyConsensus.html
==============================================================================
--- websites/staging/community/trunk/content/committers/lazyConsensus.html (original)
+++ websites/staging/community/trunk/content/committers/lazyConsensus.html Mon Nov 16 08:24:18 2015
@@ -154,7 +154,18 @@
 <li><a href="/committers/lazyConsensus.html">Lazy Consensus</a></li>
 </ul>
    <hr>
-    <p>The concept of "Lazy Consensus" is very important in our project. Lazy
+    <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>
+<p>The concept of "Lazy Consensus" is very important in our project. Lazy
 Consensus means that when you are convinced that you know what the community
 would like to see happen you can simply assume that you already have consensus
 and get on with the work. You don't have to insist people discuss and/or
@@ -165,7 +176,7 @@ You just assume you have the communities
 to indicate disapproval. If you believe the community will support your action
 you can operate on lazy consensus as long as you are prepared to roll back 
 any work should a valid objection is raised.</p>
-<h2 id="avoiding-unnecessary-discussion">Avoiding Unnecessary Discussion</h2>
+<h2 id="avoiding-unnecessary-discussion">Avoiding Unnecessary Discussion<a class="headerlink" href="#avoiding-unnecessary-discussion" title="Permanent link">&para;</a></h2>
 <p>The key thing about lazy consensus is that it's easier for people to agree,
 by doing nothing, than it is to object, which requires an
 alternative to be proposed. This has two effects, firstly people are less 
@@ -177,7 +188,7 @@ of the project to watch what is happenin
 far down the road will cause upset, but objecting (or asking for clarification 
 of intent) early is likely to be greeted with relief that someone is watching
 and cares.</p>
-<h2 id="stating-lazy-consensus">Stating Lazy Consensus</h2>
+<h2 id="stating-lazy-consensus">Stating Lazy Consensus<a class="headerlink" href="#stating-lazy-consensus" title="Permanent link">&para;</a></h2>
 <p>Sometimes a member of the community will believe a specific action is the correct 
 one for the project but are not sure that there will be consensus. In these 
 circumstances they may not wish to proceed with the work without giving the 
@@ -191,7 +202,7 @@ around their proposal, nor are they requ
 supports their actions. However, this differs from assuming lazy consensus 
 since it allows space and time to <a href="/committers/consensusBuilding.html">express support or objections</a> and corrections to 
 the proposal before work begins. </p>
-<h2 id="silence-is-consent">Silence is consent</h2>
+<h2 id="silence-is-consent">Silence is consent<a class="headerlink" href="#silence-is-consent" title="Permanent link">&para;</a></h2>
 <p>People may choose to indicate their support for the actions taken with a +1 
 mail - quick and easy to read and reassuring for the implementer. However, 
 remember, in a lazy consensus world silence is the equivalent to support. This

Modified: websites/staging/community/trunk/content/committers/voting.html
==============================================================================
--- websites/staging/community/trunk/content/committers/voting.html (original)
+++ websites/staging/community/trunk/content/committers/voting.html Mon Nov 16 08:24:18 2015
@@ -154,21 +154,32 @@
 <li><a href="/committers/voting.html">Voting</a></li>
 </ul>
    <hr>
-    <p>Occasionally a "feel" for consensus is not enough. Sometimes we need to 
+    <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>
+<p>Occasionally a "feel" for consensus is not enough. Sometimes we need to 
 have a measurable consensus. For example, when voting in new committers or 
 to approve a release. </p>
-<h2 id="preparing-for-a-vote">Preparing for a Vote</h2>
+<h2 id="preparing-for-a-vote">Preparing for a Vote<a class="headerlink" href="#preparing-for-a-vote" title="Permanent link">&para;</a></h2>
 <p>Before calling a vote it is important to ensure that the community is given time to
 discuss the upcoming vote. This will be done by posting an email to the list
 indicating the intention to call a vote and the options available. By the time
 a vote is called there should already be <a href="/committers/consensusBuilding.mdtext">consensus in the community</a>. The vote 
 itself is, normally, a formality.</p>
-<h2 id="calling-a-vote">Calling a Vote</h2>
+<h2 id="calling-a-vote">Calling a Vote<a class="headerlink" href="#calling-a-vote" title="Permanent link">&para;</a></h2>
 <p>Once it is time to call the vote a mail is posted with a subject starting 
 with <strong>[VOTE]</strong>. This enables the community members to ensure they do not miss
 an important vote thread. It also indicates that this is not consensus building
 but a formal vote.</p>
-<h3 id="casting-your-vote">Casting Your Vote</h3>
+<h3 id="casting-your-vote">Casting Your Vote<a class="headerlink" href="#casting-your-vote" title="Permanent link">&para;</a></h3>
 <p>The notation used in voting is:</p>
 <ul>
 <li>+1 Yes I agree </li>

Modified: websites/staging/community/trunk/content/contactpoints.html
==============================================================================
--- websites/staging/community/trunk/content/contactpoints.html (original)
+++ websites/staging/community/trunk/content/contactpoints.html Mon Nov 16 08:24:18 2015
@@ -153,31 +153,42 @@
 <li><a href="/contactpoints.html">ContactPoints</a></li>
 </ul>
    <hr>
-    <p>If you need to contact the ASF about an official matter you should use the
+    <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>
+<p>If you need to contact the ASF about an official matter you should use the
 appropriate address below. These are publicly shareable email addresses
 that point to privately archived lists.  </p>
 <p><a name="ContactPoints-Trademarks"></a></p>
-<h3 id="trademarks">Trademarks</h3>
+<h3 id="trademarks">Trademarks<a class="headerlink" href="#trademarks" title="Permanent link">&para;</a></h3>
 <p>Any issues regarding trademarks, specific project names, or branding of the
 ASF and it's projects should go to 
 <a href="mailto:trademarks@apache.org">trademarks@apache.org</a></p>
 <p><a name="ContactPoints-PublicityandMarketing"></a></p>
-<h3 id="publicity-and-marketing">Publicity and Marketing</h3>
+<h3 id="publicity-and-marketing">Publicity and Marketing<a class="headerlink" href="#publicity-and-marketing" title="Permanent link">&para;</a></h3>
 <p>Any issues dealing with publicity, marketing, or any inquires from the
 press or analysts should go to 
 <a href="mailto:press@apache.org">press@apache.org</a></p>
 <p><a name="ContactPoints-FundraisingandSponsorship"></a></p>
-<h3 id="fundraising-and-sponsorship">Fundraising and Sponsorship</h3>
+<h3 id="fundraising-and-sponsorship">Fundraising and Sponsorship<a class="headerlink" href="#fundraising-and-sponsorship" title="Permanent link">&para;</a></h3>
 <p>Any issues dealing with fundraising, sponsorships, donations, or related
 finances should be sent to 
 <a href="mailto:fundraising@apache.org">fundraising@apache.org</a></p>
 <p><a name="ContactPoints-Legal"></a></p>
-<h3 id="legal">Legal</h3>
+<h3 id="legal">Legal<a class="headerlink" href="#legal" title="Permanent link">&para;</a></h3>
 <p>Specific legal questions that may need to be private, and require a
 response from the ASF's legal counsel to to 
 <a href="mailto:legal-internal@apache.org">legal-internal@apache.org</a></p>
 <p><a name="ContactPoints-Other"></a></p>
-<h3 id="other">Other</h3>
+<h3 id="other">Other<a class="headerlink" href="#other" title="Permanent link">&para;</a></h3>
 <p>For more information on these and other foundation lists see the <a href="http://www.apache.org/foundation/mailinglists.html">Mailing Lists</a>
  page.</p>
   </div>

Modified: websites/staging/community/trunk/content/contributors/index.html
==============================================================================
--- websites/staging/community/trunk/content/contributors/index.html (original)
+++ websites/staging/community/trunk/content/contributors/index.html Mon Nov 16 08:24:18 2015
@@ -153,12 +153,23 @@
 <li><a href="/contributors">Contributors</a></li>
 </ul>
    <hr>
-    <p>This page is intended for those people who are reasonably 
+    <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>
+<p>This page is intended for those people who are reasonably 
 comfortable with open source development models but need a helping hand finding 
 their way around The Apache Software Foundation and our way of developing software
 (commonly called "The Apache Way"). For those wishing to start from
 the very beginning we have a <a href="/newcomers/index.html">newcomers page</a> too.</p>
-<h2 id="project-independence">Project Independence</h2>
+<h2 id="project-independence">Project Independence<a class="headerlink" href="#project-independence" title="Permanent link">&para;</a></h2>
 <p>While not all aspects of the Apache Way are practiced the same way by 
 all projects at the ASF, there are a number of rules that Apache 
 projects are required to follow – things like complying with PMC 
@@ -170,7 +181,7 @@ environemnt in which all participants ar
 opportunity to contribute to and benefit from our software, regardless
 of motivation or financial objectives. This is discussed in more detail
 in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h2 id="from-contributor-to-committer">From contributor to committer</h2>
+<h2 id="from-contributor-to-committer">From contributor to committer<a class="headerlink" href="#from-contributor-to-committer" title="Permanent link">&para;</a></h2>
 <p>Anyone can be a contributor to an Apache project. Being a contributor simply means
 that you take an interest in the project and contribute in some way, ranging from asking
 sensible questions (which documents the project and provides feedback to developers)
@@ -186,7 +197,7 @@ committers, who have earned even more me
 development1 process used at the ASF, is that we value the community more than 
 the code. A strong and healthy community will be respectful and be a fun and 
 rewarding place. Strong code will evolve. </p>
-<h3 id="contributing-to-the-project-copdoc">Contributing to the Project - CoPDoC</h3>
+<h3 id="contributing-to-the-project-copdoc">Contributing to the Project - CoPDoC<a class="headerlink" href="#contributing-to-the-project-copdoc" title="Permanent link">&para;</a></h3>
 <p>The foundations of an Apache project and how the community contributes to it is 
 sometimes referred to by the acronym CoPDoC:</p>
 <ul>
@@ -195,7 +206,7 @@ sometimes referred to by the acronym CoP
 <li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
 <li>(C)ode - discussion goes nowhere without code</li>
 </ul>
-<h3 id="becoming-a-committer">Becoming a Committer</h3>
+<h3 id="becoming-a-committer">Becoming a Committer<a class="headerlink" href="#becoming-a-committer" title="Permanent link">&para;</a></h3>
 <p>There is nothing at The Apache Software Foundation that says you must write code 
 in order to be a committer. Anyone who is supportive of the community and works 
 in any of the CoPDoC areas is a likely candidate for committership.</p>
@@ -210,7 +221,7 @@ cooperatively with your peers.</p>
 <p>Some of those users become committers in their own right. Some will test code, 
 some will write documentation, some will do bug triage and some will write code.</p>
 <p>For more details see our "<a href="http://www.apache.org/foundation/how-it-works.html">How it works</a>" document.</p>
-<h2 id="questions-and-feedback">Questions and Feedback</h2>
+<h2 id="questions-and-feedback">Questions and Feedback<a class="headerlink" href="#questions-and-feedback" title="Permanent link">&para;</a></h2>
 <p>Feedback can be provided and questions asked by subscribing to our mailing
 list by sending a mail to 
 <a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribe you can send your mail to

Modified: websites/staging/community/trunk/content/events/small-events.html
==============================================================================
--- websites/staging/community/trunk/content/events/small-events.html (original)
+++ websites/staging/community/trunk/content/events/small-events.html Mon Nov 16 08:24:18 2015
@@ -154,7 +154,18 @@
 <li><a href="/events/small-events.html">Requirements for organizers of small Apache-related events</a></li>
 </ul>
    <hr>
-    <h1 id="approval-of-small-apache-related-events">Approval of small Apache-related events</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="approval-of-small-apache-related-events">Approval of small Apache-related events<a class="headerlink" href="#approval-of-small-apache-related-events" title="Permanent link">&para;</a></h1>
 <p>The Community Development PMC is responsible for assisting with the
 organisation and promotion of all Apache events. </p>
 <p>Organizers of Apache-related events need approval for using the

Modified: websites/staging/community/trunk/content/gsoc-admin-tasks.html
==============================================================================
--- websites/staging/community/trunk/content/gsoc-admin-tasks.html (original)
+++ websites/staging/community/trunk/content/gsoc-admin-tasks.html Mon Nov 16 08:24:18 2015
@@ -153,7 +153,18 @@
 <li><a href="/gsoc-admin-tasks.html">Gsoc-admin-tasks.html</a></li>
 </ul>
    <hr>
-    <p>A comprehensive guide to being the GSoC admins for the ASF</p>
+    <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>
+<p>A comprehensive guide to being the GSoC admins for the ASF</p>
 <p>List of duties:</p>
 <ol>
 <li>Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the

Modified: websites/staging/community/trunk/content/gsoc.html
==============================================================================
--- websites/staging/community/trunk/content/gsoc.html (original)
+++ websites/staging/community/trunk/content/gsoc.html Mon Nov 16 08:24:18 2015
@@ -153,11 +153,22 @@
 <li><a href="/gsoc.html">GSoC</a></li>
 </ul>
    <hr>
-    <p>Google is sponsoring the <a href="http://google-melange.appspot.com/gsoc/homepage/google/gsoc2015">2015 Summer of Code</a> and 
+    <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>
+<p>Google is sponsoring the <a href="http://google-melange.appspot.com/gsoc/homepage/google/gsoc2015">2015 Summer of Code</a> and 
 <a href="http://www.apache.org/">The Apache Software Foundation</a> (ASF) has been accepted as a mentoring organization. This page is your entry point to the ASF GSoC
 program.</p>
 <p><a name="GSoC-Students:readthis"></a></p>
-<h1 id="students-read-this">Students: read this</h1>
+<h1 id="students-read-this">Students: read this<a class="headerlink" href="#students-read-this" title="Permanent link">&para;</a></h1>
 <ul>
 <li>Learn <a href="http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page#whatis">about GSoC</a></li>
 <li>Decide if you are <a href="http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page#1._Are_there_any_age_restrictions_on">eligible</a>
@@ -175,7 +186,7 @@ to the projects you are interested in.</
 <li>If you do not see any interesting projects from the proposed ideas, we encourage you to contact one of the Apache Project's mailing list and propose a new idea. But these ideas have to be vetted on the project dev list. The ASF does not encourage and will not respond to your personal new open source project ideas which are unrelated to any Apache projects.</li>
 </ul>
 <p><a name="GSoC-ApplyingforGSoC"></a></p>
-<h3 id="applying-for-gsoc">Applying for GSoC</h3>
+<h3 id="applying-for-gsoc">Applying for GSoC<a class="headerlink" href="#applying-for-gsoc" title="Permanent link">&para;</a></h3>
 <p>Details are announced now and we are in the project discussion phase. We encourage you to discuss you application with the project community.</p>
 <p>In order to apply we ask that you create</p>
 <ul>
@@ -194,14 +205,14 @@ community.</p>
 with the community to ensure that you understand the needs of the project
 and the commitment you need to make to your mentors.</p>
 <p>Once open applications are made through the <a href="http://www.google-melange.com/">GSoC site</a></p>
-<h3 id="application-template">Application template</h3>
+<h3 id="application-template">Application template<a class="headerlink" href="#application-template" title="Permanent link">&para;</a></h3>
 <p><em>This is just a suggested template, feel free to add and remove sections as appropriate. Be brief, don't write a large essay!</em></p>
-<h4 id="about-me">About me</h4>
+<h4 id="about-me">About me<a class="headerlink" href="#about-me" title="Permanent link">&para;</a></h4>
 <p><em>What relevant experience have you got, including university, work and hobby activities?</em></p>
-<h4 id="background">Background</h4>
+<h4 id="background">Background<a class="headerlink" href="#background" title="Permanent link">&para;</a></h4>
 <p><em>What exists already? What is the identified need? What can you reuse, what needs to he replaced?</em></p>
 <p><em>Example: Apache Foo has already got support for HTTP client requests, but this does not work well with OAuth-based services. The main interface for requests can be reused, but this project proposes to replace the backend code with a modular approach based on Apache Bar.</em></p>
-<h4 id="design-description-of-work">Design / description of work</h4>
+<h4 id="design-description-of-work">Design / description of work<a class="headerlink" href="#design-description-of-work" title="Permanent link">&para;</a></h4>
 <p><em>Brief list of things you will do / create, in some rough chronological order.</em></p>
 <p><em>Show which bits are essential, and which are optional. Highlight what is new, what are modifications, and how your work fits into the existing architecture.</em></p>
 <p><em>Example:</em></p>
@@ -210,20 +221,20 @@ and the commitment you need to make to y
 <li><em>Develop JavaScript functions for browsing files (optional)</em></li>
 <li><em>Integrate with Apache Foo's request system (essential)</em></li>
 </ul>
-<h4 id="results-for-the-apache-community">Results for the Apache community</h4>
+<h4 id="results-for-the-apache-community">Results for the Apache community<a class="headerlink" href="#results-for-the-apache-community" title="Permanent link">&para;</a></h4>
 <p><em>Benefit of your work to Apache $Project users and developers. What will be the legacy of your work after you finish?</em></p>
-<h4 id="deliverables">Deliverables</h4>
+<h4 id="deliverables">Deliverables<a class="headerlink" href="#deliverables" title="Permanent link">&para;</a></h4>
 <p><em>Including milestones, components, documentation, tests.</em></p>
-<h4 id="scheduling">Scheduling</h4>
+<h4 id="scheduling">Scheduling<a class="headerlink" href="#scheduling" title="Permanent link">&para;</a></h4>
 <p><em>Not too detailed, but some milestones and checkpoints. Rough estimates per work item (weeks/days). Remember to leave time for slack and bugfixing!</em></p>
-<h4 id="other-commitments">Other commitments</h4>
+<h4 id="other-commitments">Other commitments<a class="headerlink" href="#other-commitments" title="Permanent link">&para;</a></h4>
 <p><em>Exams, part time work, holidays, lectures.</em></p>
-<h4 id="community-engagement">Community engagement</h4>
+<h4 id="community-engagement">Community engagement<a class="headerlink" href="#community-engagement" title="Permanent link">&para;</a></h4>
 <p><em>In particular with Apache $Project, including project mailing lists, wikis, issue trackers, test systems.</em></p>
 <p><em>This should show a rough understanding of working with open source communities. You should be engaged with the rest of the community both before coding start (e.g. to develop this proposal) and during the project.</em></p>
 <p><em>Include any planned user testing, prototypes, code review.</em></p>
 <p><a name="GSoC-ContactingtheASF"></a></p>
-<h2 id="contacting-the-asf">Contacting the ASF</h2>
+<h2 id="contacting-the-asf">Contacting the ASF<a class="headerlink" href="#contacting-the-asf" title="Permanent link">&para;</a></h2>
 <p>The ASF is not just one project, it is a federation of projects, see the
 lists at <a href="http://www.apache.org">http://www.apache.org/</a> and <a href="http://incubator.apache.org/">http://incubator.apache.org/</a>. Each of our
 projects has its own community of users, contributors and committers. GSoC
@@ -233,7 +244,7 @@ mentoring organisation) applies to a sin
 engage with that project community.</p>
 <p><a name="GSoC-ProspectiveASFmentors:readthis"></a>
 <a name="formentors"></a></p>
-<h1 id="prospective-asf-mentors-read-this">Prospective ASF mentors: read this</h1>
+<h1 id="prospective-asf-mentors-read-this">Prospective ASF mentors: read this<a class="headerlink" href="#prospective-asf-mentors-read-this" title="Permanent link">&para;</a></h1>
 <p>We are looking for as many interesting projects as we can come up with. For
 more info about mentoring, please read our <a href="guide-to-being-a-mentor.html">guide to being a mentor</a>
 .</p>
@@ -252,12 +263,12 @@ please be sure to add the labels "gsoc20
 automatically include them in our list of subjects. If your project does
 not use JIRA please contact dev@community.apache.org.  </p>
 <p><a name="GSoC-ASFGSoCTimeline"></a></p>
-<h1 id="asf-gsoc-2015-timeline">ASF GSoC 2015 Timeline</h1>
+<h1 id="asf-gsoc-2015-timeline">ASF GSoC 2015 Timeline<a class="headerlink" href="#asf-gsoc-2015-timeline" title="Permanent link">&para;</a></h1>
 <p>Below is a timeline of events for The Apache Software Foundation's
 involvement in GSoC. Unless otherwise stated deadlines are 24:00 UTC on the
 date indicated.</p>
 <p><a name="GSoC-StudentApplicationandSelection"></a></p>
-<h2 id="student-application-and-selection">Student Application and Selection</h2>
+<h2 id="student-application-and-selection">Student Application and Selection<a class="headerlink" href="#student-application-and-selection" title="Permanent link">&para;</a></h2>
 <ul>
 <li>2015-03-16 19:00 UTC: Student applications start</li>
 <li>2015-03-27 19:00 UTC: Student applications deadline</li>
@@ -266,21 +277,21 @@ date indicated.</p>
 <li>2015-04-27 19:00 UTC: Google announces accepted projects.</li>
 </ul>
 <p><a name="GSoC-GSocisunderway"></a></p>
-<h2 id="gsoc-is-underway">GSoc is underway</h2>
+<h2 id="gsoc-is-underway">GSoc is underway<a class="headerlink" href="#gsoc-is-underway" title="Permanent link">&para;</a></h2>
 <ul>
 <li>2015-05-25: Coding starts.</li>
 <li>2015-06-26 19:00 UTC: Midterm evaluations can be submitted</li>
 <li>2015-07-01: ASF mentors must have completed their midterm evaluations</li>
 </ul>
 <p><a name="GSoC-Winddown"></a></p>
-<h2 id="wind-down">Wind down</h2>
+<h2 id="wind-down">Wind down<a class="headerlink" href="#wind-down" title="Permanent link">&para;</a></h2>
 <ul>
 <li>2015-08-17: Soft pencils down date</li>
 <li>2015-08-21 19:00 UTC: Firm pencils down date. Final evaluations can be submitted</li>
 <li>2015-08-26: ASF mentors must have completed their final evaluations</li>
 </ul>
 <p><a name="GSoC-UsefulLinks"></a></p>
-<h1 id="useful-links">Useful Links</h1>
+<h1 id="useful-links">Useful Links<a class="headerlink" href="#useful-links" title="Permanent link">&para;</a></h1>
 <ul>
 <li><a href="http://www.google-melange.com/">Summer of Code home</a></li>
 <li><a href="http://www.google-melange.com/gsoc/events/google/gsoc2015">Official Google Summer of Code 2015 Timeline, FAQs</a></li>

Modified: websites/staging/community/trunk/content/guide-to-being-a-mentor.html
==============================================================================
--- websites/staging/community/trunk/content/guide-to-being-a-mentor.html (original)
+++ websites/staging/community/trunk/content/guide-to-being-a-mentor.html Mon Nov 16 08:24:18 2015
@@ -153,13 +153,24 @@
 <li><a href="/guide-to-being-a-mentor.html">Guide to being a mentor</a></li>
 </ul>
    <hr>
-    <p><a name="guidetobeingamentor-Submittingideastothementoringprogramme"></a></p>
-<h1 id="submitting-ideas-to-the-mentoring-programme">Submitting ideas to the mentoring programme</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>
+<p><a name="guidetobeingamentor-Submittingideastothementoringprogramme"></a></p>
+<h1 id="submitting-ideas-to-the-mentoring-programme">Submitting ideas to the mentoring programme<a class="headerlink" href="#submitting-ideas-to-the-mentoring-programme" title="Permanent link">&para;</a></h1>
 <p>All ASF projects are invited to submit their ideas for consideration in the
 ASF mentoring programme. Any Apache member and experienced committers can
 submit ideas via JIRA (if your project does not use JIRA you can <a href="use-the-comdev-issue-tracker-for-gsoc-tasks.html">use the Comdev Issue Tracker For GSoC Tasks</a>. We are looking for as many interesting projects as we can come up with. </p>
 <p><a name="guidetobeingamentor-Summary"></a></p>
-<h2 id="summary">Summary</h2>
+<h2 id="summary">Summary<a class="headerlink" href="#summary" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Add an issue to JIRA (if your project doesn't use JIRA contact dev@community.apache.org)</li>
 <li>use sub-tasks if necessary</li>
@@ -167,7 +178,7 @@ submit ideas via JIRA (if your project d
 <li>Label the main issue with "gsoc2011" if appropriate (these will show up at <a href="http://s.apache.org/gsoc2011tasks">http://s.apache.org/gsoc2011tasks</a>)</li>
 </ul>
 <p><a name="guidetobeingamentor-Detail"></a></p>
-<h2 id="detail">Detail</h2>
+<h2 id="detail">Detail<a class="headerlink" href="#detail" title="Permanent link">&para;</a></h2>
 <p>To ensure you JIRA issues are included in our list of mentored projects
 please add the label "mentor" to the issue. If you want it to be included
 in the Google Summer of Code lists also add the "gsoc" label. If you want
@@ -192,7 +203,7 @@ those project will automatically go ahea
 projects; the number of people able to mentor and the timing we will
 probably have to make a smaller selection.</p>
 <p><a name="guidetobeingamentor-Publicisingyourmentoredissues"></a></p>
-<h3 id="publicising-your-mentored-issues">Publicising your mentored issues</h3>
+<h3 id="publicising-your-mentored-issues">Publicising your mentored issues<a class="headerlink" href="#publicising-your-mentored-issues" title="Permanent link">&para;</a></h3>
 <p>You can link to the <a href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12315361">ASF wide list of issues</a>
  or you can create your own lists and feeds within your own website.</p>
 <p>Since your mentored issues are recorded alongside your normal issues you
@@ -202,14 +213,14 @@ out.</p>
 <p>If you have any cool ideas for using this data please let us know so we can
 share them with other projects (mail dev@community.apache.org)</p>
 <p><a name="guidetobeingamentor-Examples"></a></p>
-<h2 id="examples">Examples</h2>
+<h2 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12315360">Wookie GSoC Issues</a></li>
 <li><a href="https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-rss/12315360/SearchRequest-12315360.xml?tempMax=1000">Wookie RSS GSoC feed</a></li>
 <li><a href="https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12315360/SearchRequest-12315360.xml?tempMax=1000">Wookie XML GSoC feed</a></li>
 </ul>
 <p><a name="guidetobeingamentor-Stayingintouch"></a></p>
-<h1 id="staying-in-touch">Staying in touch</h1>
+<h1 id="staying-in-touch">Staying in touch<a class="headerlink" href="#staying-in-touch" title="Permanent link">&para;</a></h1>
 <p>All mentors <em>must</em> subscribe to mentors@apache.org, our list for
 coordinating mentor activities. </p>
 <p>Subscriptions to mentors will only be accepted from addresses known to
@@ -223,7 +234,7 @@ subscribe to dev@community.apache.org.</
 need to register with Google, see our <a href="gsoc.html">GSoC</a>
  page for more information.</p>
 <p><a name="guidetobeingamentor-Howmucheffortisinvolvedwithbeingamentor"></a></p>
-<h2 id="how-much-effort-is-involved-with-being-a-mentor">How much effort is involved with being a mentor</h2>
+<h2 id="how-much-effort-is-involved-with-being-a-mentor">How much effort is involved with being a mentor<a class="headerlink" href="#how-much-effort-is-involved-with-being-a-mentor" title="Permanent link">&para;</a></h2>
 <p>Most mentors spend between 3 and 5 hours per week with their students. Most
 of this time is spent encouraging them.</p>
 <p>Within the ASF we like to think that the whole project community will help
@@ -234,7 +245,7 @@ student and helping them deliver on thei
 <p>The <a href="http://en.flossmanuals.net/GSoCMentoringGuide">GSoC Mentoring Guide</a>
  has plenty of useful materials for mentors.</p>
 <p><a name="guidetobeingamentor-Anoteabouteligibility"></a></p>
-<h2 id="a-note-about-eligibility">A note about eligibility</h2>
+<h2 id="a-note-about-eligibility">A note about eligibility<a class="headerlink" href="#a-note-about-eligibility" title="Permanent link">&para;</a></h2>
 <p>If your project has any restrictions on who can participate (as is the case
 with Harmony for example) please be sure to clarify these with potential
 students as early as possible. It causes unnecessary confusion and

Modified: websites/staging/community/trunk/content/index.html
==============================================================================
--- websites/staging/community/trunk/content/index.html (original)
+++ websites/staging/community/trunk/content/index.html Mon Nov 16 08:24:18 2015
@@ -152,7 +152,18 @@
 <li><a href="/">Home</a></li>
 </ul>
    <hr>
-    <div class="hero-unit">
+    <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>
+<div class="hero-unit">
 <h2>Apache Community Development!</h2>
 <br>
 

Modified: websites/staging/community/trunk/content/links.html
==============================================================================
--- websites/staging/community/trunk/content/links.html (original)
+++ websites/staging/community/trunk/content/links.html Mon Nov 16 08:24:18 2015
@@ -153,23 +153,34 @@
 <li><a href="/links.html">Links</a></li>
 </ul>
    <hr>
-    <p>This is a collection of links to information that's relevant to the Apache Way and Open Source in general.</p>
+    <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>
+<p>This is a collection of links to information that's relevant to the Apache Way and Open Source in general.</p>
 <p>Note that most of these links point to websites that are outside of the control of the Apache Software Foundation. Please contact their respective 
 authors for more information or questions. General discussion on the dev@community.a.o list is fine of course.</p>
-<h1 id="books">Books</h1>
+<h1 id="books">Books<a class="headerlink" href="#books" title="Permanent link">&para;</a></h1>
 <ul>
 <li><a href="http://producingoss.com/">Producing Open Source Software</a> - by Karl Fogel</li>
 </ul>
-<h1 id="blog-posts">Blog posts</h1>
+<h1 id="blog-posts">Blog posts<a class="headerlink" href="#blog-posts" title="Permanent link">&para;</a></h1>
 <ul>
 <li><a href="http://grep.codeconsult.ch/2009/03/30/the-asf-is-the-switzerland-of-open-source/">Apache - the Switzerland of Open Source?</a> - by Bertrand Delacretaz</li>
 <li><a href="http://psteitz.blogspot.ch/2011/11/thinking-together.html">Thinking Together</a> - by Phil Steitz</li>
 </ul>
-<h1 id="slides">Slides</h1>
+<h1 id="slides">Slides<a class="headerlink" href="#slides" title="Permanent link">&para;</a></h1>
 <ul>
 <li><a href="http://www.apachecon.com/eu2007/materials/asf-intro-slides-eilebrecht.pdf">Behind the Scenes of the Apache Software Foundation</a> - by Lars Eilebrecht (PDF)</li>
 </ul>
-<h1 id="apache-community-members-websites-and-links">Apache community members websites and links</h1>
+<h1 id="apache-community-members-websites-and-links">Apache community members websites and links<a class="headerlink" href="#apache-community-members-websites-and-links" title="Permanent link">&para;</a></h1>
 <ul>
 <li><a href="http://theapacheway.com/">Shane's "the Apache Way"</a> - An Apache Way Primer by Shane Curcuru</li>
 <li><a href="https://delicious.com/bdelacretaz/opendevelopment">Bertrand's Open Development links</a> - a live collection of pointers to Open Development information</li>

Modified: websites/staging/community/trunk/content/localmentors.html
==============================================================================
--- websites/staging/community/trunk/content/localmentors.html (original)
+++ websites/staging/community/trunk/content/localmentors.html Mon Nov 16 08:24:18 2015
@@ -153,12 +153,23 @@
 <li><a href="/localmentors.html">LocalMentors</a></li>
 </ul>
    <hr>
-    <p>The Local Mentors project aims to allow people getting started in Apache
+    <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>
+<p>The Local Mentors project aims to allow people getting started in Apache
 (both within the <a href="mentoringprogramme.html">Formal Mentoring Program</a>
 , and everyone else) to meet up with existing Apache developers in their
 area.</p>
 <p><a name="LocalMentors-Why?"></a></p>
-<h1 id="why">Why?</h1>
+<h1 id="why">Why?<a class="headerlink" href="#why" title="Permanent link">&para;</a></h1>
 <p>When you're getting involved in a new open source project, it can be a little daunting. You engage in the mailing lists with people from all around the world. You solve bugs with people in different time zones. You develop patches with people from different languages and cultures. Perhaps you have a mentor (<a href="mentoringprogramme.html">Formal</a>
  or informal) from your project, but the chances area, they're a thousand
 miles away.</p>
@@ -180,7 +191,7 @@ committer near you, head to a cafe or pu
 have a chat. They probably won't know your project, but they'll hopefully
 know the rest!</p>
 <p><a name="LocalMentors-Ifyou'relookingforalocalmentor"></a></p>
-<h1 id="if-youre-looking-for-a-local-mentor">If you're looking for a local mentor</h1>
+<h1 id="if-youre-looking-for-a-local-mentor">If you're looking for a local mentor<a class="headerlink" href="#if-youre-looking-for-a-local-mentor" title="Permanent link">&para;</a></h1>
 <p>First up, make sure a local mentor's the right thing for you. The Local
 Mentoring project has different aims to the <a href="mentoringprogramme.html">Formal Mentoring Program</a>
 . If you're after someone who knows your project, or someone who's
@@ -202,7 +213,7 @@ discover that you can't find anyone near
 people near where you might visit in the future, or failing that, see if
 any other open source foundations or local groups have anything near you.</p>
 <p><a name="LocalMentors-HowexistingApacheCommitterscangetinvolved"></a></p>
-<h1 id="how-existing-apache-committers-can-get-involved">How existing Apache Committers can get involved</h1>
+<h1 id="how-existing-apache-committers-can-get-involved">How existing Apache Committers can get involved<a class="headerlink" href="#how-existing-apache-committers-can-get-involved" title="Permanent link">&para;</a></h1>
 <p>If you think you could spare the odd hour everyone once in a while, to sit
 down over a beer or a coffee and chat about Open Source and the Apache Way,
 then we'd love you to get involved! You're not signing up to a long-term

Modified: websites/staging/community/trunk/content/mentee-ranking-process.html
==============================================================================
--- websites/staging/community/trunk/content/mentee-ranking-process.html (original)
+++ websites/staging/community/trunk/content/mentee-ranking-process.html Mon Nov 16 08:24:18 2015
@@ -153,7 +153,18 @@
 <li><a href="/mentee-ranking-process.html">Mentee Ranking Process</a></li>
 </ul>
    <hr>
-    <p>This page describes the ranking process used by The Apache Software
+    <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>
+<p>This page describes the ranking process used by The Apache Software
 Foundation to evaluate mentee proposals.</p>
 <p>The ranking process is designed to ensure the most promising looking
 applicants are assigned a mentor with an ASF project. The goal is <em>not</em> to
@@ -166,9 +177,9 @@ as a potential mentor (you don't actuall
 <p>The instructions below described ranking proposals using the Google Summer
 of Code application.</p>
 <p><a name="MenteeRankingProcess-ScoringSystem"></a></p>
-<h1 id="scoring-system">Scoring System</h1>
+<h1 id="scoring-system">Scoring System<a class="headerlink" href="#scoring-system" title="Permanent link">&para;</a></h1>
 <p>Projects are ranked using a scoring system as follows:</p>
-<h2 id="pre-selection-phase-done-by-mentor-when-accepting-to-be-mentor-of-a-given-proposal"><em>Pre-Selection Phase</em> : done by mentor when accepting to be mentor of a given proposal</h2>
+<h2 id="pre-selection-phase-done-by-mentor-when-accepting-to-be-mentor-of-a-given-proposal"><em>Pre-Selection Phase</em> : done by mentor when accepting to be mentor of a given proposal<a class="headerlink" href="#pre-selection-phase-done-by-mentor-when-accepting-to-be-mentor-of-a-given-proposal" title="Permanent link">&para;</a></h2>
 <ul>
 <li>if the proposal is for a project you will be mentoring and you feel the
 proposal looks good enough for you to commit your time to it then click the
@@ -179,7 +190,7 @@ code-awards@a.o first. We encourage mult
 <p>Other community members are free to comment on proposals as they see fit.
 In the re-evaluation phase (see below) admins will use
 comments provided by mentors and community members.</p>
-<h2 id="selection-phase-done-by-mentor-during-ranking-time"><em>Selection Phase</em> : done by mentor during ranking time</h2>
+<h2 id="selection-phase-done-by-mentor-during-ranking-time"><em>Selection Phase</em> : done by mentor during ranking time<a class="headerlink" href="#selection-phase-done-by-mentor-during-ranking-time" title="Permanent link">&para;</a></h2>
 <p>All scoring is done in the Google Docs spreadsheet that was sent to
 code-awards@apache.org. Every Score must be followed by an explanation.
 DO NOT ADD SCORES IN MELANGE! Use integer numbers only!</p>
@@ -242,7 +253,7 @@ a score at or above the project ranked 3
 phase). Before progressing to the next phase admins will read all proposals
 either above or near the minimum score and ensure that there are no errors
 in this phase of ranking.</p>
-<h2 id="re-evaluation-done-by-admins-during-or-after-selection-phase"><em>Re-Evaluation</em> : done by admins during or after selection phase</h2>
+<h2 id="re-evaluation-done-by-admins-during-or-after-selection-phase"><em>Re-Evaluation</em> : done by admins during or after selection phase<a class="headerlink" href="#re-evaluation-done-by-admins-during-or-after-selection-phase" title="Permanent link">&para;</a></h2>
 <p>In this phase admins evaluate all proposals above the required score and
 others that are just below it. We check those just below the required score
 to ensure that the scores have been equally assigned across all proposals
@@ -261,7 +272,7 @@ community members to mark a proposal up
 <p>At the end of this phase there is a short window for the community to
 verify the admins work before the final selection is made.</p>
 <p><a name="MenteeRankingProcess-Whatarewelookingforinagoodproposal?"></a></p>
-<h1 id="what-are-we-looking-for-in-a-good-proposal">What are we looking for in a good proposal?</h1>
+<h1 id="what-are-we-looking-for-in-a-good-proposal">What are we looking for in a good proposal?<a class="headerlink" href="#what-are-we-looking-for-in-a-good-proposal" title="Permanent link">&para;</a></h1>
 <p>In general we much prefer new mentees to repeat mentees. The goal is to
 enable new people to learn about open source software development.</p>
 <p>In past years we have seen some consistent patterns in quality proposals:</p>
@@ -274,7 +285,7 @@ requests for more info)</li>
 addressing those weaknesses</li>
 </ul>
 <p><a name="MenteeRankingProcess-Warningsignsinabadproposal"></a></p>
-<h1 id="warning-signs-in-a-bad-proposal">Warning signs in a bad proposal</h1>
+<h1 id="warning-signs-in-a-bad-proposal">Warning signs in a bad proposal<a class="headerlink" href="#warning-signs-in-a-bad-proposal" title="Permanent link">&para;</a></h1>
 <ul>
 <li>no engagement with project community</li>
 <li>lack of understanding of what open source is and how it is developed</li>
@@ -282,7 +293,7 @@ addressing those weaknesses</li>
 <li>previous failures within the mentor programme</li>
 </ul>
 <p><a name="MenteeRankingProcess-Whathappensnext?"></a></p>
-<h1 id="what-happens-next">What happens next?</h1>
+<h1 id="what-happens-next">What happens next?<a class="headerlink" href="#what-happens-next" title="Permanent link">&para;</a></h1>
 <p>Towards the end of the ranking period Google will announce how many slots
 the ASF has been given. Shortly after that we will ask ASF committers to
 stop ranking and the ASF GSoC admins will work to adjust the rankings to
@@ -293,22 +304,22 @@ cut-off point. In this case the admins w
 projects to ensure that Google can assign awards as appropriate.</p>
 <p>For example, imagine that 7 is the number of points that causes the
 clustering, and we have the following projects ranked at 7:</p>
-<h1 id="a">A</h1>
-<h1 id="b">B</h1>
-<h1 id="c">C</h1>
-<h1 id="d">D</h1>
-<h1 id="e">E</h1>
+<h1 id="a">A<a class="headerlink" href="#a" title="Permanent link">&para;</a></h1>
+<h1 id="b">B<a class="headerlink" href="#b" title="Permanent link">&para;</a></h1>
+<h1 id="c">C<a class="headerlink" href="#c" title="Permanent link">&para;</a></h1>
+<h1 id="d">D<a class="headerlink" href="#d" title="Permanent link">&para;</a></h1>
+<h1 id="e">E<a class="headerlink" href="#e" title="Permanent link">&para;</a></h1>
 <p>Now imagine the cut-off point for selection is currently at the third
 position (C).</p>
 <p>The admins need to look a these projects and ensure they are ordered in the
 webapp to make the most appropriate appear at the top of the list. This
 ensures that they are most likely to be awarded a slot. So we may end up
 with:</p>
-<h1 id="b_1">B</h1>
-<h1 id="c_1">C</h1>
-<h1 id="a_1">A</h1>
-<h1 id="e_1">E</h1>
-<h1 id="d_1">D</h1>
+<h1 id="b_1">B<a class="headerlink" href="#b_1" title="Permanent link">&para;</a></h1>
+<h1 id="c_1">C<a class="headerlink" href="#c_1" title="Permanent link">&para;</a></h1>
+<h1 id="a_1">A<a class="headerlink" href="#a_1" title="Permanent link">&para;</a></h1>
+<h1 id="e_1">E<a class="headerlink" href="#e_1" title="Permanent link">&para;</a></h1>
+<h1 id="d_1">D<a class="headerlink" href="#d_1" title="Permanent link">&para;</a></h1>
 <p>Unfortunately this process needs to happen very quickly and there is no
 time for community discussion around these points. Therefore it is
 important that mentors and mentees provide as much information in the
@@ -318,7 +329,7 @@ cut-off point may move as well, so Googl
 need to ensure that all rank 7 projects are correctly ordered, not just the
 best.</p>
 <p><a name="MenteeRankingProcess-Theprocessofbreakingclusters"></a></p>
-<h2 id="the-process-of-breaking-clusters">The process of breaking clusters</h2>
+<h2 id="the-process-of-breaking-clusters">The process of breaking clusters<a class="headerlink" href="#the-process-of-breaking-clusters" title="Permanent link">&para;</a></h2>
 <p>Admins work through all applications adding a +8 to all those ranked above
 the cut off score. This has the effect of increasing the "space" we have to
 work in re-ranking the clustered projects.</p>
@@ -331,7 +342,7 @@ score for this one (i.e. try and spread
 <p>It's not practical to ask the community to comment at this point as we are
 on a tight deadline. We ask that the community trusts the assigned admins.</p>
 <p><a name="MenteeRankingProcess-Resolveconflicts"></a></p>
-<h1 id="resolve-conflicts">Resolve conflicts</h1>
+<h1 id="resolve-conflicts">Resolve conflicts<a class="headerlink" href="#resolve-conflicts" title="Permanent link">&para;</a></h1>
 <p>Inevitably there will be one or two students who have been accepted in
 multiple organizations. This is resolved during an IRC meeting with Google
 admins during the final hours of ranking. In these cases the admins will

Modified: websites/staging/community/trunk/content/mentor-request-mail.html
==============================================================================
--- websites/staging/community/trunk/content/mentor-request-mail.html (original)
+++ websites/staging/community/trunk/content/mentor-request-mail.html Mon Nov 16 08:24:18 2015
@@ -153,7 +153,18 @@
 <li><a href="/mentor-request-mail.html">Mentor request mail</a></li>
 </ul>
    <hr>
-    <p>Having identified a project and an issue you would like to work on it is a
+    <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>
+<p>Having identified a project and an issue you would like to work on it is a
 good idea to introduce yourself to the project community and outline your
 plans for tackling the issue. This means the community know you are working
 on the issue and gives the community an early opportunity to help course

Modified: websites/staging/community/trunk/content/mentoring/experiences.html
==============================================================================
--- websites/staging/community/trunk/content/mentoring/experiences.html (original)
+++ websites/staging/community/trunk/content/mentoring/experiences.html Mon Nov 16 08:24:18 2015
@@ -154,11 +154,22 @@
 <li><a href="/mentoring/experiences.html">Apache in GSoC</a></li>
 </ul>
    <hr>
-    <p>This page a place for
+    <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>
+<p>This page a place for
 collecting information about GSoC activities each year for historical tracking. It 
 was started in 2012 so is missing plenty of detail in the early years, your help 
 filling it out would be appreciated.</p>
-<h1 id="2012-overview">2012 Overview</h1>
+<h1 id="2012-overview">2012 Overview<a class="headerlink" href="#2012-overview" title="Permanent link">&para;</a></h1>
 <ul>
 <li>Students accepted: 41</li>
 <li>Students who passed midterm: 40</li>
@@ -170,7 +181,7 @@ Wookie, OpenMeetings, Nuvem, Hama, VXQue
 </ul>
 </li>
 </ul>
-<h2 id="2012-blogs">2012 Blogs</h2>
+<h2 id="2012-blogs">2012 Blogs<a class="headerlink" href="#2012-blogs" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="http://scottbw.wordpress.com/2012/08/22/wookie-adds-support-for-signed-widgets-thanks-to-google-summer-of-code/">Scott Wilson: Wookie Mentor</a></li>
 <li><a href="http://pushpalankajaya.blogspot.co.uk/search/label/GSoC">Pushpalanka: Wookie Student</a></li>
@@ -178,13 +189,13 @@ Wookie, OpenMeetings, Nuvem, Hama, VXQue
 <li><a href="http://summerwithairavata.blogspot.com/">Bhathiya Jayasekara: Airavata Student</a></li>
 <li><a href="https://blogs.apache.org/openmeetings/entry/google_summer_of_code_2012">OpenMeetings Mentors: Sebastian Wagner, Alexei Fedotov, Maxim Solodovnik - Students: Ankur Ankan, German Grekhov, Dmitry Zamula, Josh Dolitsky </a></li>
 </ul>
-<h1 id="2011-overview">2011 Overview</h1>
+<h1 id="2011-overview">2011 Overview<a class="headerlink" href="#2011-overview" title="Permanent link">&para;</a></h1>
 <ul>
 <li>Students accepted: 40</li>
 <li>Students who passed midterm: 38</li>
 <li>Students who passed final: 36</li>
 </ul>
-<h1 id="2010-overview">2010 Overview</h1>
+<h1 id="2010-overview">2010 Overview<a class="headerlink" href="#2010-overview" title="Permanent link">&para;</a></h1>
 <ul>
 <li>Students accepted: 44</li>
 </ul>

Modified: websites/staging/community/trunk/content/mentoringprogramme-icfoss-pilot.html
==============================================================================
--- websites/staging/community/trunk/content/mentoringprogramme-icfoss-pilot.html (original)
+++ websites/staging/community/trunk/content/mentoringprogramme-icfoss-pilot.html Mon Nov 16 08:24:18 2015
@@ -153,7 +153,18 @@
 <li><a href="/mentoringprogramme-icfoss-pilot.html">Pilot Mentoring Programme with India ICFOSS</a></li>
 </ul>
    <hr>
-    <p>The ASF has been participating in many mentoring initiatives, and it's now
+    <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>
+<p>The ASF has been participating in many mentoring initiatives, and it's now
 partening in a pilot project with India ICFOSS to provide mentoring for 
 undergraduated and graduated students that have interest in learning how
 to participate in open source communitites at ASF.</p>
@@ -167,7 +178,7 @@ need to bring the confidence to take the
 for yourself.</p>
 <p>More information on the <a href="mentoringprogramme.html">Mentoring Programme</a> page.</p>
 <p><a name="Schedule"></a></p>
-<h2 id="proposed-schedule">Proposed Schedule</h2>
+<h2 id="proposed-schedule">Proposed Schedule<a class="headerlink" href="#proposed-schedule" title="Permanent link">&para;</a></h2>
 <table>
 <th align="left">Date</th><th align="left">Description</th>
 <tr><td>June 20</td><td>Local Workshop at ICFOSS headequarters in Kerala - India</td></tr>
@@ -185,17 +196,17 @@ for yourself.</p>
 </table>
 
 <p><a name="MentoringProgramme-WorkshopMaterials"></a></p>
-<h2 id="workshop-materials">Workshop Materials</h2>
+<h2 id="workshop-materials">Workshop Materials<a class="headerlink" href="#workshop-materials" title="Permanent link">&para;</a></h2>
 <p>The slides used for the local workshop at ICFOSS headquarters in Kerala are available for <a href="http://people.apache.org/~lresende/presentations/asf-icfoss-mentoring.pdf">download</a>.</p>
 <p><a name="MentoringProgramme-ProjectIdeas"></a></p>
-<h2 id="project-ideas">Project Ideas</h2>
+<h2 id="project-ideas">Project Ideas<a class="headerlink" href="#project-ideas" title="Permanent link">&para;</a></h2>
 <p>Project ideas are jira created by possible mentors and can be viewed at:</p>
 <ul>
 <li><a href="http://s.apache.org/icfoss2013ideas">2013 ICFOSS Programme Project Ideas</a></li>
 <li><a href="http://s.apache.org/gsoc2013ideas">2013 GSoC Project Ideas</a></li>
 </ul>
 <p><a name="MentoringProgramme-ApplyingfortheMentorProgramme"></a></p>
-<h2 id="applying-for-the-mentor-programme">Applying for the Mentor Programme</h2>
+<h2 id="applying-for-the-mentor-programme">Applying for the Mentor Programme<a class="headerlink" href="#applying-for-the-mentor-programme" title="Permanent link">&para;</a></h2>
 <p>Students can propose their own project ideas, or select one from the asf provided list. After selecting the project ideas. students should create a project prosoal following guidance from the <b>mentor</b> and the <b>project community</b>.</p>
 <p>The project proposal should have, at minimum :</p>
 <ul>



Mime
View raw message