Modified: websites/staging/community/trunk/content/speakers/speakers.html
==============================================================================
--- websites/staging/community/trunk/content/speakers/speakers.html (original)
+++ websites/staging/community/trunk/content/speakers/speakers.html Mon Nov 16
08:24:18 2015
@@ -154,19 +154,30 @@
<li><a href="/speakers/speakers.html">Listing yourself as a Potential
Speaker</a></li>
</ul>
<hr>
- <p>If you're an Apache committer, and you're interested in speaking about
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>If you're an Apache committer, and you're interested in speaking about
Apache
Technologies, Apache Projects or the Apache Software Foundation as a whole,
we'd encourage you to get involved and list yourself in our speaker
application!</p>
-<h2 id="finding-speakers">Finding Speakers</h2>
+<h2 id="finding-speakers">Finding Speakers<a class="headerlink"
href="#finding-speakers" title="Permanent link">¶</a></h2>
<p>If you are organising an event and looking for speakers, please see
<a href="/speakers/">the Apache Speakers homepage</a> for details.</p>
-<h2 id="listing-yourself-as-a-potential-speaker">Listing yourself as a
Potential Speaker</h2>
+<h2 id="listing-yourself-as-a-potential-speaker">Listing yourself as a
Potential Speaker<a class="headerlink"
href="#listing-yourself-as-a-potential-speaker" title="Permanent
link">¶</a></h2>
<p>To list yourself as someone interested in being an Apache Speaker, there are
two steps involved. The first is to create a FOAF file for yourself, including
a couple of key pieces of information. The second is to list yourself in the
speaking DOAP file.</p>
-<h3 id="creating-your-foaf-file">Creating your FOAF file</h3>
+<h3 id="creating-your-foaf-file">Creating your FOAF file<a class="headerlink"
href="#creating-your-foaf-file" title="Permanent link">¶</a></h3>
<p>Creating a FOAF file for yourself is very easy, assuming you don't already
have one available. Details on how to create a FOAF file, along with a
handy wizard to guide you through the process, are available at
@@ -180,7 +191,7 @@ to include a few key bits of information
<li>Your twitter ID (so we can point people at your speaking history on
<a href="http://lanyrd.com/";>Lanyrd</a>)</li>
</ul>
-<h3 id="listing-yourself-in-the-speakers-doap-file">Listing yourself in the
Speakers DOAP file</h3>
+<h3 id="listing-yourself-in-the-speakers-doap-file">Listing yourself in the
Speakers DOAP file<a class="headerlink"
href="#listing-yourself-in-the-speakers-doap-file" title="Permanent
link">¶</a></h3>
<p>Now, if you haven't already done so, checkout the committers directory from
svn:</p>
<div class="codehilite"><pre><span class="n">svn</span> <span
class="n">co</span> <span class="n">https</span><span class="p">:</span><span
class="o">//</span><span class="n">svn</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">repos</span><span class="o">/</span><span
class="n">private</span><span class="o">/</span><span
class="n">committers</span><span class="o">/</span>
Modified:
websites/staging/community/trunk/content/use-the-comdev-issue-tracker-for-gsoc-tasks.html
==============================================================================
---
websites/staging/community/trunk/content/use-the-comdev-issue-tracker-for-gsoc-tasks.html
(original)
+++
websites/staging/community/trunk/content/use-the-comdev-issue-tracker-for-gsoc-tasks.html
Mon Nov 16 08:24:18 2015
@@ -153,7 +153,18 @@
<li><a href="/use-the-comdev-issue-tracker-for-gsoc-tasks.html">Use the Comdev
Issue Tracker For GSoC Tasks</a></li>
</ul>
<hr>
- <p>If your project does not use the ASFs JIRA for issue tracking you can
use
+ <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 your project does not use the ASFs JIRA for issue tracking you can use
the Community Development project to record your GSoC tasks. </p>
<ul>
<li>Add tasks to the <a
href="https://issues.apache.org/jira/browse/COMDEV";>Comdev project</a></li>
