Modified: websites/staging/community/trunk/content/mentoringprogramme.html
==============================================================================
--- websites/staging/community/trunk/content/mentoringprogramme.html (original)
+++ websites/staging/community/trunk/content/mentoringprogramme.html Mon Nov 16
08:24:18 2015
@@ -153,7 +153,18 @@
<li><a href="/mentoringprogramme.html">MentoringProgramme</a></li>
</ul>
<hr>
- <p>Many projects in the ASF are able to provide mentors for newcomers. In
+ <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>Many projects in the ASF are able to provide mentors for newcomers. In
fact, most projects are happy to assist newcomers to their projects as part
of their normal operations. However, some people are looking for more
structure. The Mentor Programme of the The Apache Software Foundation
@@ -172,7 +183,7 @@ for business, but, like many other thing
constant improvement and revision. Therefore, the description below is
marked 'draft.'</p>
<p><a name="MentoringProgramme-QuickDefinitions"></a></p>
-<h1 id="quick-definitions">Quick Definitions</h1>
+<h1 id="quick-definitions">Quick Definitions<a class="headerlink"
href="#quick-definitions" title="Permanent link">¶</a></h1>
<p>The ASF believes that the best way for people (and, indeed, entire
projects) to join the community is with the help of committed members of
the community. A community member who makes a commitment to help a new
@@ -184,7 +195,7 @@ The document uses 'TLP' when it is refer
word 'project' to refer to a the work a mentee does under the Mentoring
Programme.</p>
<p><a name="MentoringProgramme-Whocanbeamentee?"></a></p>
-<h1 id="who-can-be-a-mentee">Who can be a mentee?</h1>
+<h1 id="who-can-be-a-mentee">Who can be a mentee?<a class="headerlink"
href="#who-can-be-a-mentee" title="Permanent link">¶</a></h1>
<p>The Mentor Programme is intended to assist people in becoming contributors
to ASF projects. Thus, anyone interested in contributing effort to an ASF
project is a potential mentee. You need to be a self starter, your mentor
@@ -200,7 +211,7 @@ a plan for a significant effort and show
volunteer basis. The Foundation does not pay anyone to mentor or
contribute.</p>
<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">¶</a></h2>
<p>There are two simple steps to apply:</p>
<ol>
<li>Review the content below to learn about the details of the
requirements.</li>
@@ -210,7 +221,7 @@ contribute.</p>
of your formal education there are some <a
href="mentorprogrammeformaleducation.html">additional requirements</a>
that you must fulfill, along with your tutor.</p>
<p><a name="MentoringProgramme-Draft:TheASFMentoringProgramme"></a></p>
-<h1 id="draft-the-asf-mentoring-programme">Draft: The ASF Mentoring
Programme</h1>
+<h1 id="draft-the-asf-mentoring-programme">Draft: The ASF Mentoring
Programme<a class="headerlink" href="#draft-the-asf-mentoring-programme"
title="Permanent link">¶</a></h1>
<p>The Mentoring Programme is structured around mentee projects. Each mentee
project is a coherent task contributing to one of the ASF's ongoing TLPs.</p>
<p>The Mentoring Programme does not work on a fixed calendar. Project start as
@@ -222,7 +233,7 @@ contributes to an existing Foundation pr
prototyping projects are not acceptable -- working with an ASF project
community is an essential part of the process.</p>
<p><a name="MentoringProgramme-SettingupaMentoringProject"></a></p>
-<h2 id="setting-up-a-mentoring-project">Setting up a Mentoring Project</h2>
+<h2 id="setting-up-a-mentoring-project">Setting up a Mentoring Project<a
class="headerlink" href="#setting-up-a-mentoring-project" title="Permanent
link">¶</a></h2>
<p>The first step is for a potential mentee to make contact with the Mentoring
Programme. Several of the following steps call for interactions with
potential mentors and target projects, and the Mentoring Programme mailing
@@ -246,7 +257,7 @@ and adds the project to the Mentoring Wi
linked from the Mentoring page.</p>
<p>The mentee joins the development community of the TLP and sets to work.</p>
<p><a name="MentoringProgramme-WorkingontheProject"></a></p>
-<h2 id="working-on-the-project">Working on the Project</h2>
+<h2 id="working-on-the-project">Working on the Project<a class="headerlink"
href="#working-on-the-project" title="Permanent link">¶</a></h2>
<p>During the course of the project, the mentee is a member of the TLP
community. This has implications for both the mentee and the
TLP.</p>
@@ -278,7 +289,7 @@ a JIRA project, and open a JIRA for each
mentee can then ask committers to include their JIRA in commit comments and
thus set up automatic tracking.</p>
<p><a name="MentoringProgramme-TheMid-ProjectReview"></a></p>
-<h2 id="the-mid-project-review">The Mid-Project Review</h2>
+<h2 id="the-mid-project-review">The Mid-Project Review<a class="headerlink"
href="#the-mid-project-review" title="Permanent link">¶</a></h2>
<p>The Mentoring Programme reviews all projects at the half-way point. The
input to the programme review is a pair of reports: one from the mentor
and from the mentee. These are public documents.</p>
@@ -287,7 +298,7 @@ the
disposition of the project: continue to completion, or stop. The report
must also describe any changes to the project's scope.</p>
<p><a name="MentoringProgramme-ScopeandScheduleChanges"></a></p>
-<h2 id="scope-and-schedule-changes">Scope and Schedule Changes</h2>
+<h2 id="scope-and-schedule-changes">Scope and Schedule Changes<a
class="headerlink" href="#scope-and-schedule-changes" title="Permanent
link">¶</a></h2>
<p>Inevitably, ugly facts will conflict with plans and intentions. Mentors and
mentees can agree to change the scope of a project and document the change
on the wiki and, as appropriate, on reports. The programme does not
@@ -303,7 +314,7 @@ it is very likely that they are ready to
mentor. Their Mentor Programme project can end in good
order even though coding continues.</p>
<p><a name="MentoringProgramme-FinishuptheProject"></a></p>
-<h2 id="finish-up-the-project">Finish up the Project</h2>
+<h2 id="finish-up-the-project">Finish up the Project<a class="headerlink"
href="#finish-up-the-project" title="Permanent link">¶</a></h2>
<p>Every project ends, either when the work is done. or when the agree time
period is over. At the end, the mentee updates the Wiki page with a final
summary of their work.</p>
@@ -314,9 +325,9 @@ as appropriate on the Mentoring Wiki.</p
<p>Relevant certification is issued to both the mentor and mentee by the admin
team.</p>
<p><a name="MentoringProgramme-RolesandExpectations"></a></p>
-<h2 id="roles-and-expectations">Roles and Expectations</h2>
+<h2 id="roles-and-expectations">Roles and Expectations<a class="headerlink"
href="#roles-and-expectations" title="Permanent link">¶</a></h2>
<p><a name="MentoringProgramme-Mentee"></a></p>
-<h3 id="mentee">Mentee</h3>
+<h3 id="mentee">Mentee<a class="headerlink" href="#mentee" title="Permanent
link">¶</a></h3>
<ul>
<li>The mentee is any individual interested in getting involved in open
source.</li>
@@ -332,7 +343,7 @@ to code changes.</li>
and completion points of the programme.</li>
</ul>
<p><a name="MentoringProgramme-Mentor"></a></p>
-<h3 id="mentor">Mentor</h3>
+<h3 id="mentor">Mentor<a class="headerlink" href="#mentor" title="Permanent
link">¶</a></h3>
<ul>
<li>The mentor must be a committer on the project accepting the mentees
contributions.</li>
@@ -346,7 +357,7 @@ the project community.</li>
and completion points of the programme.</li>
</ul>
<p><a name="MentoringProgramme-Admin"></a></p>
-<h3 id="admin">Admin</h3>
+<h3 id="admin">Admin<a class="headerlink" href="#admin" title="Permanent
link">¶</a></h3>
<ul>
<li>The Apache Mentoring Program admin(s) will liaise with ASF projects to
maintain a JIRA list of projects that are available and in progress.</li>
Modified:
websites/staging/community/trunk/content/mentorprogrammeapplication.html
==============================================================================
--- websites/staging/community/trunk/content/mentorprogrammeapplication.html
(original)
+++ websites/staging/community/trunk/content/mentorprogrammeapplication.html
Mon Nov 16 08:24:18 2015
@@ -153,12 +153,23 @@
<li><a
href="/mentorprogrammeapplication.html">MentorProgrammeApplication</a></li>
</ul>
<hr>
- <p><a
name="MentorProgrammeApplication-MentoringProgrammeApplicationProcedure"></a></p>
-<h1 id="mentoring-programme-application-procedure">Mentoring Programme
Application Procedure</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="MentorProgrammeApplication-MentoringProgrammeApplicationProcedure"></a></p>
+<h1 id="mentoring-programme-application-procedure">Mentoring Programme
Application Procedure<a class="headerlink"
href="#mentoring-programme-application-procedure" title="Permanent
link">¶</a></h1>
<p>Applying for the Apache Mentoring Programme is simple. This page will take
you through the steps:</p>
<p><a
name="MentorProgrammeApplication-Creatingaproposalandfindingamentor"></a></p>
-<h2 id="creating-a-proposal-and-finding-a-mentor">Creating a proposal and
finding a mentor</h2>
+<h2 id="creating-a-proposal-and-finding-a-mentor">Creating a proposal and
finding a mentor<a class="headerlink"
href="#creating-a-proposal-and-finding-a-mentor" title="Permanent
link">¶</a></h2>
<ol>
<li>Find the project you are interested in (see our <a
href="newbiefaq.html">FAQ</a>
for some guidance on how to do this)</li>
@@ -172,7 +183,7 @@ like this <a href="mentor-request-mail.h
project mailing list asking for someone to be your mentor.</li>
</ol>
<p><a name="MentorProgrammeApplication-Projectproposal"></a></p>
-<h3 id="project-proposal">Project proposal</h3>
+<h3 id="project-proposal">Project proposal<a class="headerlink"
href="#project-proposal" title="Permanent link">¶</a></h3>
<p>Your project proposal should include:</p>
<ul>
<li>Your full name</li>
@@ -199,7 +210,7 @@ to understand the guidance that the ment
provide. We are not here to teach basic programming skills, rather we are
here to teach the application of those skills to an Apache Project.</p>
<p><a
name="MentorProgrammeApplication-Applyingtothementoringprogramme"></a></p>
-<h2 id="applying-to-the-mentoring-programme">Applying to the mentoring
programme</h2>
+<h2 id="applying-to-the-mentoring-programme">Applying to the mentoring
programme<a class="headerlink" href="#applying-to-the-mentoring-programme"
title="Permanent link">¶</a></h2>
<p>At this point you will probably want to apply to the Community Development
mentoring programme, however, you are not required to do so. If you so
desire you can just get on with your work within the project community,
Modified:
websites/staging/community/trunk/content/mentorprogrammeformaleducation.html
==============================================================================
---
websites/staging/community/trunk/content/mentorprogrammeformaleducation.html
(original)
+++
websites/staging/community/trunk/content/mentorprogrammeformaleducation.html
Mon Nov 16 08:24:18 2015
@@ -153,15 +153,26 @@
<li><a
href="/mentorprogrammeformaleducation.html">MentorProgrammeFormalEducation</a></li>
</ul>
<hr>
- <p><a
name="MentorProgrammeFormalEducation-MentoringinFormalEducation"></a></p>
-<h1 id="mentoring-in-formal-education">Mentoring in Formal Education</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="MentorProgrammeFormalEducation-MentoringinFormalEducation"></a></p>
+<h1 id="mentoring-in-formal-education">Mentoring in Formal Education<a
class="headerlink" href="#mentoring-in-formal-education" title="Permanent
link">¶</a></h1>
<p>It is expected that some mentees will wish to participate in the <a
href="mentoringprogramme.html">Mentoring Programme</a>
as part of a formal education course. In these cases there will be
additional requirements on the process to ensure that the mentees can be
evaluated by their tutor. This section describes these additional
requirements and process.</p>
<p><a name="MentorProgrammeFormalEducation-Overview"></a></p>
-<h2 id="overview">Overview</h2>
+<h2 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h2>
<p>Projects are defined by the students tutor in consultation with the project
community/mentors and the student. They will need to be isolated enough
from other ongoing work to ensure that success/failure to deliver is not
@@ -173,11 +184,11 @@ mentor. The mentor must be available for
and must be willing to mentor the tutor with respect to how they encourage
the students to participate</p>
<p><a name="MentorProgrammeFormalEducation-RolesandExpectations"></a></p>
-<h2 id="roles-and-expectations">Roles and Expectations</h2>
+<h2 id="roles-and-expectations">Roles and Expectations<a class="headerlink"
href="#roles-and-expectations" title="Permanent link">¶</a></h2>
<p>In addition to the notes found in the <a
href="mentoringprogramme.html">Mentoring Programme</a>
documentation the following should be considered.</p>
<p><a name="MentorProgrammeFormalEducation-Tutors"></a></p>
-<h3 id="tutors">Tutors</h3>
+<h3 id="tutors">Tutors<a class="headerlink" href="#tutors" title="Permanent
link">¶</a></h3>
<ul>
<li>Ensure the mentee is participating in the program</li>
<li>Tutor grades the student within their formal education (the mentor
@@ -188,7 +199,7 @@ feedback should assist here)</li>
</li>
</ul>
<p><a name="MentorProgrammeFormalEducation-Mentees"></a></p>
-<h3 id="mentees">Mentees</h3>
+<h3 id="mentees">Mentees<a class="headerlink" href="#mentees" title="Permanent
link">¶</a></h3>
<ul>
<li>mentees are typically students in their final year (exceptional students
may be considered)</li>
@@ -196,7 +207,7 @@ may be considered)</li>
part of their examined work.</li>
</ul>
<p><a name="MentorProgrammeFormalEducation-Admins"></a></p>
-<h3 id="admins">Admins</h3>
+<h3 id="admins">Admins<a class="headerlink" href="#admins" title="Permanent
link">¶</a></h3>
<ul>
<li>Provide assistance interpreting reports to allow tutors to grade student
participation</li>
Modified: websites/staging/community/trunk/content/newbiefaq.html
==============================================================================
--- websites/staging/community/trunk/content/newbiefaq.html (original)
+++ websites/staging/community/trunk/content/newbiefaq.html Mon Nov 16 08:24:18
2015
@@ -153,7 +153,18 @@
<li><a href="/newbiefaq.html">NewbieFAQ</a></li>
</ul>
<hr>
- <p>This set of Frequently Asked Questions are intended to help newcomers 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>This set of Frequently Asked Questions are intended to help newcomers to
The Apache Software Foundation (ASF) understand how we work.</p>
<p><em>Index of Questions</em></p>
<ul>
@@ -183,9 +194,9 @@ the information they're looking for. Pl
<a href="mailto:[email protected]";>[email protected]</a>
(subscribe with
<a
href="mailto:[email protected]";>[email protected]</a>
first).</p>
<p><a name="NewbieFAQ-AboutTheApacheSoftwareFoundation"></a></p>
-<h1 id="about-the-apache-software-foundation">About The Apache Software
Foundation</h1>
+<h1 id="about-the-apache-software-foundation">About The Apache Software
Foundation<a class="headerlink" href="#about-the-apache-software-foundation"
title="Permanent link">¶</a></h1>
<p><a
name="NewbieFAQ-WhatprojectscanIfindinTheApacheSoftwareFoundation?"></a></p>
-<h2 id="what-projects-can-i-find-in-the-apache-software-foundation">What
projects can I find in The Apache Software Foundation?</h2>
+<h2 id="what-projects-can-i-find-in-the-apache-software-foundation">What
projects can I find in The Apache Software Foundation?<a class="headerlink"
href="#what-projects-can-i-find-in-the-apache-software-foundation"
title="Permanent link">¶</a></h2>
<p>There are over 200 separate projects and communities hosted at The Apache
Software Foundation. We have
four classes, or types, of project (in terms of their community; not in terms
of technology):</p>
<ul>
@@ -197,7 +208,7 @@ have active development and are moving t
development, but may still be useful</li>
</ul>
<p><a
name="NewbieFAQ-HowareprojectsmanagedinTheApacheSoftwareFoundation"></a></p>
-<h2 id="how-are-projects-managed-in-the-apache-software-foundation">How are
projects managed in The Apache Software Foundation</h2>
+<h2 id="how-are-projects-managed-in-the-apache-software-foundation">How are
projects managed in The Apache Software Foundation<a class="headerlink"
href="#how-are-projects-managed-in-the-apache-software-foundation"
title="Permanent link">¶</a></h2>
<p>Apache projects all believe that if we look after the community then good
code will emerge from that community. That is, when people with similar
needs come together they will work out a way of solving their common
@@ -219,20 +230,20 @@ constructively within them!</p>
<p>To learn more about "The Apache Way" in general see the <a
href="http://apache.org/foundation/how-it-works.html";>How It Works</a>
pages. We also have <a
href="https://www.apache.org/foundation/governance/";>detailed overviews of how
the ASF and projects are governed</a>.</p>
<p><a name="NewbieFAQ-HowdoIlearnaboutthewayApacheProjectsWork?"></a></p>
-<h2 id="how-do-i-learn-about-the-way-apache-projects-work">How do I learn
about the way Apache Projects Work?</h2>
+<h2 id="how-do-i-learn-about-the-way-apache-projects-work">How do I learn
about the way Apache Projects Work?<a class="headerlink"
href="#how-do-i-learn-about-the-way-apache-projects-work" title="Permanent
link">¶</a></h2>
<p>You should consider applying to the <a
href="mentoringprogramme.html">Apache Mentor Programme</a>
. We will help you find a mentor within the project of your choice. They
will take you through a semi-formal mentoring programme that will ensure
you quickly find your feet. There is no cost other than a promise to commit
some of your time to the goals you agree with your mentor.</p>
<p><a name="NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?"></a></p>
-<h2 id="how-do-i-ask-a-question-about-the-asf-in-general">How do I ask a
question about the ASF in general?</h2>
+<h2 id="how-do-i-ask-a-question-about-the-asf-in-general">How do I ask a
question about the ASF in general?<a class="headerlink"
href="#how-do-i-ask-a-question-about-the-asf-in-general" title="Permanent
link">¶</a></h2>
<p>The Community Development Project is here for this very purpose. Check out
the resources on this site first, if you don't find the answer send a mail
to mailto:[email protected] (subscribe first by sending a mail to
mailto:[email protected])</p>
<p><a name="NewbieFAQ-HowdoIgetusersupportforanASFproject?"></a></p>
-<h2 id="how-do-i-get-user-support-for-an-asf-project">How do I get user
support for an ASF project?</h2>
+<h2 id="how-do-i-get-user-support-for-an-asf-project">How do I get user
support for an ASF project?<a class="headerlink"
href="#how-do-i-get-user-support-for-an-asf-project" title="Permanent
link">¶</a></h2>
<p>Everyone active in ASF projects is here as a volunteer, nobody is paid to
provide support here. So the first thing to realize is that you need to be
careful not to waste people's time, so do your homework. Generally, if
@@ -269,9 +280,9 @@ the future.</p>
expertise grows. Again, earning merit in this way will help you to get
the support you need in the future.</p>
<p><a name="NewbieFAQ-GettingInvolvedwithApacheprojects"></a></p>
-<h1 id="getting-involved-with-apache-projects">Getting Involved with Apache
projects</h1>
+<h1 id="getting-involved-with-apache-projects">Getting Involved with Apache
projects<a class="headerlink" href="#getting-involved-with-apache-projects"
title="Permanent link">¶</a></h1>
<p><a name="NewbieFAQ-HowdoIchooseanApacheprojecttoworkon?"></a></p>
-<h2 id="how-do-i-choose-an-apache-project-to-work-on">How do I choose an
Apache project to work on?</h2>
+<h2 id="how-do-i-choose-an-apache-project-to-work-on">How do I choose an
Apache project to work on?<a class="headerlink"
href="#how-do-i-choose-an-apache-project-to-work-on" title="Permanent
link">¶</a></h2>
<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
@@ -289,7 +300,7 @@ inspiration about how you might be able
you see an issue you would like to tackle, it's time to join the projects
mailing list and get started.</p>
<p><a name="NewbieFAQ-HowdoIgetinvolvedwithanApacheproject?"></a></p>
-<h2 id="how-do-i-get-involved-with-an-apache-project">How do I get involved
with an Apache project?</h2>
+<h2 id="how-do-i-get-involved-with-an-apache-project">How do I get involved
with an Apache project?<a class="headerlink"
href="#how-do-i-get-involved-with-an-apache-project" title="Permanent
link">¶</a></h2>
<p>You can certainly improve your programming skills by watching the commit
lists, receiving code reviews and participating in discussion. However
this learning opportunity is a healthy side effect of open source
@@ -301,7 +312,7 @@ and be willing to research the rest.</p>
started guide</a>. You will also find our <a
href="http://apache.org/foundation/getinvolved.html";>get involved</a>
page a useful starting point.</p>
<p><a name="NewbieFAQ-IsthereaCodeofConductforApacheprojects?"></a></p>
-<h2 id="is-there-a-code-of-conduct-for-apache-projects">Is there a Code of
Conduct for Apache projects?</h2>
+<h2 id="is-there-a-code-of-conduct-for-apache-projects">Is there a Code of
Conduct for Apache projects?<a class="headerlink"
href="#is-there-a-code-of-conduct-for-apache-projects" title="Permanent
link">¶</a></h2>
<p>Yes there is a code of conduct which may be found at
<a
href="http://www.apache.org/foundation/policies/conduct.html";>http://www.apache.org/foundation/policies/conduct.html</a></p>
<p>PMCs are allowed to define their own additional code of conduct for their
individual communities
@@ -318,9 +329,9 @@ projects. This section includes such gem
<li>Don't feed the trolls. </li>
</ul>
<p><a name="NewbieFAQ-AbouttheApacheMentoringProgramme"></a></p>
-<h2 id="about-the-apache-mentoring-programme">About the Apache Mentoring
Programme</h2>
+<h2 id="about-the-apache-mentoring-programme">About the Apache Mentoring
Programme<a class="headerlink" href="#about-the-apache-mentoring-programme"
title="Permanent link">¶</a></h2>
<p><a name="NewbieFAQ-WhatistheApacheMentoringProgramme"></a></p>
-<h3 id="what-is-the-apache-mentoring-programme">What is the Apache Mentoring
Programme</h3>
+<h3 id="what-is-the-apache-mentoring-programme">What is the Apache Mentoring
Programme<a class="headerlink" href="#what-is-the-apache-mentoring-programme"
title="Permanent link">¶</a></h3>
<p>Many projects in the ASF are able to provide mentors for newcomers. In
fact, most projects are happy to assist newcomers to their projects as part
of their normal operations. However, some people are looking for more
@@ -329,7 +340,7 @@ provides additional support and structur
initial contribution to an ASF project.</p>
<p>For more information see our <a href="mentoringprogramme.html">mentoring
page</a>.</p>
<p><a name="NewbieFAQ-HowdoIApplytotheMentorProgramme?"></a></p>
-<h3 id="how-do-i-apply-to-the-mentor-programme">How do I Apply to the Mentor
Programme?</h3>
+<h3 id="how-do-i-apply-to-the-mentor-programme">How do I Apply to the Mentor
Programme?<a class="headerlink" href="#how-do-i-apply-to-the-mentor-programme"
title="Permanent link">¶</a></h3>
<p>Take a look at our <a href="mentoringprogramme.html">mentoring page</a>. If
you are
planning on working on an Apache project as part of your formal education you
should also read <a href="mentorprogrammeformaleducation.html">mentoring in
formal education</a>.</p>
@@ -339,7 +350,7 @@ gives us enough background information t
chosen project community and for you to work with prospective mentors in
defining your mentored activity.</p>
<p><a name="NewbieFAQ-AboutSpeakers"></a></p>
-<h2 id="how-can-i-find-speakers-willing-to-help-us-understand-apache">How can
I find speakers willing to help us understand Apache?</h2>
+<h2 id="how-can-i-find-speakers-willing-to-help-us-understand-apache">How can
I find speakers willing to help us understand Apache?<a class="headerlink"
href="#how-can-i-find-speakers-willing-to-help-us-understand-apache"
title="Permanent link">¶</a></h2>
<p>The best way to start getting involved is joining the
<a
href="##NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?">[email protected]</a>
mailing list. We also have a <a
href="https://community.apache.org/speakers/";>listing of volunteer speakers</a>
Modified: websites/staging/community/trunk/content/newcomers/index.html
==============================================================================
--- websites/staging/community/trunk/content/newcomers/index.html (original)
+++ websites/staging/community/trunk/content/newcomers/index.html Mon Nov 16
08:24:18 2015
@@ -153,7 +153,18 @@
<li><a href="/newcomers">Newcomers</a></li>
</ul>
<hr>
- <p>In this section we hope to help you take your first steps as an open
source
+ <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 this section we hope to help you take your first steps as an open source
developer in one of our many Apache project communities.</p>
<ul>
<li><a href="/gettingStarted/101.html">Where do I start?</a> - a guide to your
first engagement with an Apache project</li>
@@ -165,7 +176,7 @@ developer in one of our many Apache proj
<li><a href="/newbiefaq.html">Newbie FAQ</a> - some commonly asked questions
(and their answers)</li>
</ul>
<p><a name="Index-FirstContributions"></a></p>
-<h1 id="first-contributions">First Contributions</h1>
+<h1 id="first-contributions">First Contributions<a class="headerlink"
href="#first-contributions" title="Permanent link">¶</a></h1>
<p><em>The more you give the more you get out</em>. </p>
<p>It's natural to assume that, as a newcomer,
you have little to offer the ASF. However, you will be surprised at
Modified: websites/staging/community/trunk/content/newcommitter.html
==============================================================================
--- websites/staging/community/trunk/content/newcommitter.html (original)
+++ websites/staging/community/trunk/content/newcommitter.html Mon Nov 16
08:24:18 2015
@@ -153,7 +153,18 @@
<li><a href="/newcommitter.html">NewCommitter</a></li>
</ul>
<hr>
- <p>Identifying potential new committers, calling a vote for their
recognition
+ <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>Identifying potential new committers, calling a vote for their recognition
as a committer and processing the relevant documents is something that the
whole community can contribute to.</p>
<p>Each project has different approaches to managing new committers, this page
@@ -189,41 +200,41 @@ drafts for the various communications th
</ul>
</div>
<p><a
name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a></p>
-<h1 id="guidelines-for-assessing-new-candidates-for-committership">Guidelines
for assessing new candidates for committership</h1>
+<h1 id="guidelines-for-assessing-new-candidates-for-committership">Guidelines
for assessing new candidates for committership<a class="headerlink"
href="#guidelines-for-assessing-new-candidates-for-committership"
title="Permanent link">¶</a></h1>
<p>When voting, all PMC members need to make up your own mind, perhaps search
mailing lists and Jira, etc. The following are some tips that we developed.
Also consider the Apache Forrest <a
href="http://forrest.apache.org/committed.html";>committer guidelines</a>.</p>
<p><a name="NewCommitter-Abilitytoworkco-operativelywithpeers."></a></p>
-<h2 id="ability-to-work-cooperatively-with-peers">Ability to work
cooperatively with peers.</h2>
+<h2 id="ability-to-work-cooperatively-with-peers">Ability to work
cooperatively with peers.<a class="headerlink"
href="#ability-to-work-cooperatively-with-peers" title="Permanent
link">¶</a></h2>
<p>How do we evaluate? By the interactions they have through mail. By how
they respond to criticism. By how they participate in decision-making
process.</p>
<p><a name="NewCommitter-Abilitytobeamentor."></a></p>
-<h2 id="ability-to-be-a-mentor">Ability to be a mentor.</h2>
+<h2 id="ability-to-be-a-mentor">Ability to be a mentor.<a class="headerlink"
href="#ability-to-be-a-mentor" title="Permanent link">¶</a></h2>
<p>How do we evaluate? By the interactions they have through mail. By how
clear they are and how willing they are to point at appropriate background
materials (or even create them).</p>
<p><a name="NewCommitter-Community"></a></p>
-<h2 id="community">Community</h2>
+<h2 id="community">Community<a class="headerlink" href="#community"
title="Permanent link">¶</a></h2>
<p>How do we evaluate? By the interactions they have through mail. Do they
help to answer questions raised on the mailing list; do they show a helpful
attitude and respect for other's ideas.</p>
<p><a name="NewCommitter-Committment"></a></p>
-<h2 id="committment">Committment</h2>
+<h2 id="committment">Committment<a class="headerlink" href="#committment"
title="Permanent link">¶</a></h2>
<p>How do we evaluate? By time, by sticking through tough issues, by helping
on not-so-fun tasks as well.</p>
<p><a name="NewCommitter-Personalskill/ability"></a></p>
-<h2 id="personal-skillability">Personal skill/ability</h2>
+<h2 id="personal-skillability">Personal skill/ability<a class="headerlink"
href="#personal-skillability" title="Permanent link">¶</a></h2>
<p>How do we evaluate? A solid general understanding of the project.
Quality of discussion in mail. Patches (where applicable) easy to apply with
only
a cursory review.</p>
<p><a name="NewCommitter-NewCommitterProcess"></a></p>
-<h1 id="new-committer-process">New Committer Process</h1>
+<h1 id="new-committer-process">New Committer Process<a class="headerlink"
href="#new-committer-process" title="Permanent link">¶</a></h1>
<p>This section describes a typical Apache projects process for handling the
voting of a new committer. Templates mentioned in the process appear at
later in this document.</p>
<p><a name="NewCommitter-Summary"></a></p>
-<h2 id="summary">Summary</h2>
+<h2 id="summary">Summary<a class="headerlink" href="#summary" title="Permanent
link">¶</a></h2>
<ol>
<li>Call a vote: templates/committerVote.txt</li>
<li>Invite the new committer: templates/committerInvite.txt</li>
@@ -243,7 +254,7 @@ PMC member (templates/committerAccept.tx
<li>Announce the new committer (template/committerAnnounce.txt)</li>
</ol>
<p><a name="NewCommitter-Discussion"></a></p>
-<h2 id="discussion">Discussion</h2>
+<h2 id="discussion">Discussion<a class="headerlink" href="#discussion"
title="Permanent link">¶</a></h2>
<p>We do the vote on the private mailing list to enable a frank discussion.</p>
<p>Start a separate Vote thread for each new person. This makes it much easier
to review the mail archives.</p>
@@ -277,8 +288,8 @@ will announce it on the dev list. We can
our praise in public.</p>
<p>Other notes about the process are available on the main <a
href="http://www.apache.org/dev/pmc.html#newcommitter";>Apache site</a></p>
<p><a name="NewCommitter-EmailTemplates"></a></p>
-<h1 id="email-templates">Email Templates</h1>
-<h2 id="committer-vote-template">Committer Vote Template</h2>
+<h1 id="email-templates">Email Templates<a class="headerlink"
href="#email-templates" title="Permanent link">¶</a></h1>
+<h2 id="committer-vote-template">Committer Vote Template<a class="headerlink"
href="#committer-vote-template" title="Permanent link">¶</a></h2>
<p>This is the email to commence a vote for a new committer member.
Some projects make committers PMC members automatically, if this is the case
then
merge this with the following template (PMC Vote Template)</p>
@@ -299,7 +310,7 @@ merge this with the following template (
</pre></div>
-<h2 id="pmc-vote-template">PMC Vote Template</h2>
+<h2 id="pmc-vote-template">PMC Vote Template<a class="headerlink"
href="#pmc-vote-template" title="Permanent link">¶</a></h2>
<p>This is the email to commence a vote for a new PMC candidate. New PMC
members need
to be voted for by the existing PMC members and subsequently approved by the
Board
(or Incubator PMC for Incubating projects).</p>
@@ -318,7 +329,7 @@ to be voted for by the existing PMC memb
</pre></div>
-<h2 id="close-vote">Close Vote</h2>
+<h2 id="close-vote">Close Vote<a class="headerlink" href="#close-vote"
title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">This</span> <span
class="n">is</span> <span class="n">the</span> <span class="n">email</span>
<span class="n">ends</span> <span class="n">the</span> <span
class="n">vote</span> <span class="n">and</span> <span class="n">reports</span>
<span class="n">the</span> <span class="n">result</span> <span
class="n">to</span> <span class="n">the</span> <span
class="n">project</span><span class="p">.</span>
<span
class="o">------------------------------------------------------------</span>
@@ -337,9 +348,9 @@ to be voted for by the existing PMC memb
</pre></div>
-<h2 id="board-approval-of-new-pmc-member">Board Approval of new PMC member</h2>
+<h2 id="board-approval-of-new-pmc-member">Board Approval of new PMC member<a
class="headerlink" href="#board-approval-of-new-pmc-member" title="Permanent
link">¶</a></h2>
<p>See <a
href="http://www.apache.org/dev/pmc.html#newpmc";>http://www.apache.org/dev/pmc.html#newpmc</a></p>
-<h2 id="committer-invite-template">Committer Invite Template</h2>
+<h2 id="committer-invite-template">Committer Invite Template<a
class="headerlink" href="#committer-invite-template" title="Permanent
link">¶</a></h2>
<p>This is the suggested invitation email to send to the newly elected
committer,
sent after a positive result from the vote for a new committer.</p>
<div class="codehilite"><pre><span
class="o">------------------------------------------------------------</span>
@@ -397,7 +408,7 @@ sent after a positive result from the vo
</pre></div>
-<h2 id="committer-accept-template">Committer Accept Template</h2>
+<h2 id="committer-accept-template">Committer Accept Template<a
class="headerlink" href="#committer-accept-template" title="Permanent
link">¶</a></h2>
<p>This is the followup email after the new committer has accepted the
invitation</p>
<div class="codehilite"><pre><span
class="o">------------------------------------------------------------------------</span>
<span class="n">To</span><span class="p">:</span> <span
class="n">JoeBloggs</span><span class="p">@</span><span
class="n">foo</span><span class="p">.</span><span class="n">net</span>
@@ -446,7 +457,7 @@ sent after a positive result from the vo
</pre></div>
-<h2 id="committer-account-creation">Committer Account Creation</h2>
+<h2 id="committer-account-creation">Committer Account Creation<a
class="headerlink" href="#committer-account-creation" title="Permanent
link">¶</a></h2>
<p>Follow the instructions at:
http://www.apache.org/dev/pmc.html#newcommitter</p>
<p>In summary the account creation request is made by the
@@ -457,7 +468,7 @@ Request</a> page for ASF members to use.
<p>For elections held on public lists, please supply the
<a href="http://mail-archives.apache.org/";>mail-archives.apache.org</a> url.
For private lists, you can
use the <a href="https://mail-search.apache.org/";>Mail Search tool</a> to
locate the apprpropriate url. </p>
-<h2 id="committer-announce-template">Committer Announce Template</h2>
+<h2 id="committer-announce-template">Committer Announce Template<a
class="headerlink" href="#committer-announce-template" title="Permanent
link">¶</a></h2>
<p>This is the email to announce to [PROJECT]-dev once the account has been
created.</p>
<div class="codehilite"><pre><span
class="o">------------------------------------------------------------</span>
<span class="n">To</span><span class="p">:</span> <span
class="n">dev</span><span class="p">@[</span><span
class="n">PROJECT</span><span class="p">].</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span>
@@ -477,7 +488,7 @@ use the <a href="https://mail-search.apa
</pre></div>
-<h2 id="committer-done-template">Committer Done Template</h2>
+<h2 id="committer-done-template">Committer Done Template<a class="headerlink"
href="#committer-done-template" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">After</span> <span
class="n">the</span> <span class="n">committer</span> <span
class="n">account</span> <span class="n">is</span> <span
class="n">established</span><span class="p">.</span>
<span
class="o">------------------------------------------------------------</span>
Modified: websites/staging/community/trunk/content/projectIndependence.html
==============================================================================
--- websites/staging/community/trunk/content/projectIndependence.html (original)
+++ websites/staging/community/trunk/content/projectIndependence.html Mon Nov
16 08:24:18 2015
@@ -153,7 +153,18 @@
<li><a href="/projectIndependence.html">Project Independence</a></li>
</ul>
<hr>
- <p>While not all aspects of the Apache Way are practiced the same way by
+ <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>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 and policies that Apache
projects are required to follow â things like complying with PMC
<a href="http://www.apache.org/dev/release.html";>release voting</a>, <a
href="http://www.apache.org/legal/";>legal policy</a>, <a
href="http://www.apache.org/foundation/marks/";>brand policy</a>,
@@ -181,7 +192,7 @@ Apache products for virtually any purpos
our permissive <a
href="http://www.apache.org/licenses/LICENSE-2.0.html";>Apache License</a> and
by our <a href="http://www.apache.org/foundation/marks/";>formal trademark
policy</a>.<br />
While many third parties create Apache licensed
software, only software released from the ASF itself is properly called
"Apache software".</p>
-<h2 id="apache-projects-are-independent">Apache projects are independent</h2>
+<h2 id="apache-projects-are-independent">Apache projects are independent<a
class="headerlink" href="#apache-projects-are-independent" title="Permanent
link">¶</a></h2>
<p>Apache projects are controlled by their Project Management Committee
(PMC). A PMC represents the consensus view of the individual PMC
members by discussion and [VOTE]ing on project releases and new committers.
@@ -194,12 +205,12 @@ with low diversity (i.e. PMCs that are d
Similarly, the ASF does not allow corporations to participate directly in
Apache project management or other governance activities at the ASF; only
individuals.</p>
<p>There are several important aspects to this independence: project
management, project use by end users, and project code availability.</p>
-<h2 id="apache-projects-are-managed-independently">Apache projects are managed
independently</h2>
+<h2 id="apache-projects-are-managed-independently">Apache projects are managed
independently<a class="headerlink"
href="#apache-projects-are-managed-independently" title="Permanent
link">¶</a></h2>
<p>Apache projects must be managed independently, and PMCs must ensure that
they are acting in the best interests of the project as a whole. Note that it
is similarly important that the PMC clearly show this independence within their
project community. The perception of existing and new participants within the
community that the PMC is run independently and without favoring any specific
third parties over others is important, to allow new contributors to feel
comfortable both joining the community and contributing their work. A community
that obviously favors one specific vendor in some exclusive way will often
discourage new contributors from competing vendors, which is an issue for the
long term health of the project.</p>
-<h2 id="apache-products-may-be-used-independently">Apache products may be used
independently</h2>
+<h2 id="apache-products-may-be-used-independently">Apache products may be used
independently<a class="headerlink"
href="#apache-products-may-be-used-independently" title="Permanent
link">¶</a></h2>
<p>All Apache projects must release their code under the <a
href="http://www.apache.org/licenses/LICENSE-2.0.html";>Apache License</a>,
which clearly specifies the minimum restrictions that users of Apache software
must agree to. Apache software is all about being able to use it for virtually
whatever our users want: open source, proprietary, secret: weâre happy to
have users take our software (although not our name) for virtually any purpose.
While our legal guidelines allow certain other software licenses to be used for
specific dependencies, the software we release always uses our license.</p>
<p>Extending this idea, users of Apache software should be able to find our
software, learn how to use it, and actually apply it to all its common use
cases solely by going to the Apache projectâs own website. Apache projects
should provide sufficient documentation, install features, basic user help
(through mailing lists) and services for the common use cases to the user,
without them having to rely on third parties. It is important that our users
can both make use of our software freely â both in terms of not having to pay
for the software, as well as not having to worry about IP claims or other more
restrictive licenses on either the software or the configurations or other
common materials required to actually use the software.</p>
-<h2 id="apache-projects-are-branded-as-apache-projects">Apache projects are
branded as Apache projects</h2>
+<h2 id="apache-projects-are-branded-as-apache-projects">Apache projects are
branded as Apache projects<a class="headerlink"
href="#apache-projects-are-branded-as-apache-projects" title="Permanent
link">¶</a></h2>
<p>Similar to the requirement that users can use Apache projects
independently; so should
users understand that when they download and use an Apache product that it is
from
Apache and not from nor related to any third party. That is, the user
experience when
@@ -216,7 +227,7 @@ plugs into, or works with our many Apach
product must be clearly branded as such, and must follow our <a
href="http://www.apache.org/foundation/marks/";>formal trademark policy</a>.
In this way, users clearly understand the different sources for software
products such as
Apache Foo (from the ASF) versus BigCo SuperThing, Powered By Apache Foo (from
BigCo).</p>
-<h2 id="apache-projects-are-non-commercial">Apache projects are
non-commercial</h2>
+<h2 id="apache-projects-are-non-commercial">Apache projects are
non-commercial<a class="headerlink" href="#apache-projects-are-non-commercial"
title="Permanent link">¶</a></h2>
<p>The ASFâs mission is to produce software for the public good. All <a
href="http://www.apache.org/free/";>Apache software is always available for
free</a>, and solely under the Apache License. While our projects manage the
technical implementation of their individual software products independently,
Apache software is released from the ASF, and is always meant to serve the
public good.</p>
<p>Weâre happy to have third parties, including for-profit corporations,
take our software and use it for their own purposes â even when in some cases
it may technically compete with Apache software. However it is important in
these cases to ensure that the brand and reputation of the Apache project is
not misused by third parties for their own purposes. It is important for the
longevity and community health of our projects that they get the appropriate
credit for producing our freely available software.</p>
</div>
Modified: websites/staging/community/trunk/content/proposals/ZestProposal.html
==============================================================================
--- websites/staging/community/trunk/content/proposals/ZestProposal.html
(original)
+++ websites/staging/community/trunk/content/proposals/ZestProposal.html Mon
Nov 16 08:24:18 2015
@@ -154,14 +154,25 @@
<li><a href="/proposals/ZestProposal.html">ZestProposal.html</a></li>
</ul>
<hr>
- <h1 id="abstract">Abstract</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="abstract">Abstract<a class="headerlink" href="#abstract"
title="Permanent link">¶</a></h1>
<div class="codehilite"><pre> <span class="n">qi4j</span> <span
class="p">=</span> <span class="n">new</span> <span
class="n">Energy4Java</span><span class="p">();</span>
</pre></div>
<p>That is how to create the Qi4j runtime, and it captures the essence of its
spirit.
Qi4j is a platform to develop Composite Oriented Programming applications in
Java in a new, exciting and productive manner.</p>
-<h1 id="governance-of-provisional-top-level-project">Governance of Provisional
Top Level Project</h1>
+<h1 id="governance-of-provisional-top-level-project">Governance of Provisional
Top Level Project<a class="headerlink"
href="#governance-of-provisional-top-level-project" title="Permanent
link">¶</a></h1>
<p>Provisional Top Level Project is a new idea at the ASF, and the Qi4j
community is willing to try the idea, instead of simply debating it. If it
doesn't work, Qi4j will re-enter via the Incubator.</p>
<p>In addition of regular Top Level Projects, we are making the following
self-imposed suggestions to the Governance of this Provisional TLP;</p>
<ol>
@@ -181,45 +192,45 @@ Qi4j is a platform to develop Composite
<p>Maturity of project into a regular Top Level Project is decided separately
by the Board, with input from PMC and ComDev.</p>
</li>
</ol>
-<h1 id="project-naming">Project Naming</h1>
+<h1 id="project-naming">Project Naming<a class="headerlink"
href="#project-naming" title="Permanent link">¶</a></h1>
<p>Apache Zest is the proposed project name, as we have learned that "4j" in
names might ultimately limit the future direction of the project.
Additionally, Qi4j will remain as the Java implementation of the composite
oriented programming platform. There is also a literal port to .NET, which may
be migrated to ASF as well.</p>
-<h1 id="project-description">Project Description</h1>
+<h1 id="project-description">Project Description<a class="headerlink"
href="#project-description" title="Permanent link">¶</a></h1>
<p>Qi4j is a platform that combines Aspects, Composition, Dependency
Injection, Validation, Storage/UnitOfWork handling, Indexing/Search
abstraction, Architectural enforcement and much more, in a holistic top-down
approach, primarily for Domain-rich applications, even explicitly supportive of
Domain Driven Design.</p>
<p>Composite oriented programming is a term coined in the early days of Qi4j,
to capture the notion of using another paradigm for creating applications, than
the prevalent object oriented programming one.
It comprises of the ability to write smaller parts of code than regular
classes, and compose these so called fragments into a larger "Composite". It is
similar to aspect-oriented programming, but we take it one step further, there
is no base class. The Composite consists of fragments, but no fragment has
higher significance than any other fragment. However, there are explicit types
of fragments, namely Composite Types, Constraints, Mixins, Concerns and
Side-effects, to clearly communicate "Intent". The macro level composition
takes the form of Applications has Layers which contains Modules in which the
Composite Types are declared.</p>
<p>Qi4j also evangelizes strong typing, so the equivalent of Around-Advice in
AOP, which is called Concerns, can be made type-safe or like AOP be generic
(using java.lang.reflect.InvocationHandler interface). Composites can either be
hard coded using annotations, or assembled dynamically during the bootstrap
phase.</p>
<p>Qi4j is a whole new way to write Java applications, where focus lies on
structures and interfaces, where classes are 'mere' implementation details.</p>
<p>Qi4j boldly challenges bad practices head-on, such as "What is a
Property?", "Why are null arguments allowed by default?" and "Is the structural
assembly of the application actually the same as configuration values?"</p>
-<h1 id="background">Background</h1>
+<h1 id="background">Background<a class="headerlink" href="#background"
title="Permanent link">¶</a></h1>
<p>Java is NOT an object-oriented language. Neither is C# or C++. IF they
were, how come an Object is DERIVED FROM a Class? A true object-oriented
language should for sure have Class(es) assigned to Objects (or a similar
construct), which are created 'clean', like stem cells can take on practically
any cell's role of the body.</p>
<p>Additionally, in real life, most objects have different properties and
behaviors depending on the context. In front of the computer, I am primarily a
'programmer', but in the jungle I am primarily 'scared prey'. Modeling this in
Java (and many other languages) requires the introduction of additional Object
abstractions, often resulting in many similar classes representing the same
underlying entity, again reinforcing our view that Java is a Class Oriented
language.</p>
<p>Many problems in software engineering can be attributed to (lack of)
cohesion and (too tight) coupling. The original promise was that we write a
Class once and we can re-use it in many different applications, subsystems and
modules. In reality, the Class often contains "too much" for the next use-case.
The granularity is too coarse, causing too much coupling to other parts. This
have resulted in libraries being the smallest granularity that is practical,
and solutions like OSGi, Spring and others have emerged to tackle the many
issues that may arise from this, from dependency injection to configuration to
assembly to runtime resolution of versioning.</p>
<p>But we often wish that we could have smaller fragments and COMPOSE objects
from these fragments. This also makes it easier to replace parts of
implementations, instead of fragile overloading, library extension (assuming
the library author provides that) and the famous monkey patching approach.</p>
<p>Aspect Oriented Programming is a concept to capture cross-cutting concerns
in one place. Classic cases are Logging and Authentication. This is an
excellent concept, but we claim that AspectJ/AspectWerkz and others fail in the
implementations, as most rely on naming conventions and declarations separated
from the code itself. It is therefor often difficult to know what aspects are
in effect at a given point in the code. The code weaving involved sometimes
interferes with debugging and/or classloading in environments like OSGi. AOP is
often only used by frameworks to "enhance" code supplied by a third-party
developer, and less often being part of the downstream developer's daily
life.</p>
<p>Many people have architecture/design drawings, often with layers in the
application, with modules within those layers. We call this Worditecture, as
those layers and modules only exist in Word documents and if the code is
inspected, more often than not, it is impossible to relate the code to such
drawings. In Qi4j, we set out to enforce the Application Structure. Entities,
Values and Services must be declared inside one or more Modules, and Modules
belong inside Layers, and Layers are stacked on top of each other. The
Entities, Values and Services have Visibility of either 'within Module',
'within Layer' or 'to Layer directly above'. This leads to less configuration
and inability to mess up the codebase completely.</p>
-<h1 id="history">History</h1>
+<h1 id="history">History<a class="headerlink" href="#history" title="Permanent
link">¶</a></h1>
<p>The principles of composite oriented programming are the brain child of
Rickard Ãberg going back to ~2003. In early 2007, Niclas Hedhman convinced
Rickard to start a new open source project around this, and Qi4j was born.
First announced at Oredev conference in November 2007.</p>
<p>Over the years, 28 people have contributed source to the project and many
others have chimed in on mailing lists around direction, concepts and design.
When Qi4j had the attention of media and others, we were not able to build
long-term community around the project, and we have seen activity declined, as
fewer itches to scratch and fewer people willing to make larger changes.</p>
-<h1 id="rationale-for-migrating-to-asf">Rationale for migrating to ASF</h1>
+<h1 id="rationale-for-migrating-to-asf">Rationale for migrating to ASF<a
class="headerlink" href="#rationale-for-migrating-to-asf" title="Permanent
link">¶</a></h1>
<p>Qi4j community sees direct productivity gains from using the platform,
although the initial learning curve is quite overwhelming, like learning a new
language. The Qi4j community recognizes that it has not been able to
communicate the benefits well enough, to achieve a large user and developer
community. We are confident of Qi4j's technical merit, and would like to draw
on ASF's community merit to build a larger, sustainable and successful
community around this exciting technology.</p>
<p>The technical merit stems from that Qi4j has a strong model for programming
in a more strict, yet more productive environment. A platform where fragments
can be leveraged, where aspects are declared on the interfaces, where null
values are not allowed by default, and where persistence is integrated yet
pluggable at boot time. Qi4j enforces the use of modules and layers, the
infrastructure layer can not access layers above it, and presentation layers at
the top can't bypass service layers to directly access data stores.
All these restrictions are there to provide more guidance to the programmer,
reducing the length of the rope and the number of trees to hang oneself in.</p>
<p>"Common things should be quick and easy, while anything should be
possible", has been the mantra since the inception. And thanks to this
foresight, Qi4j can be deeply integrated with many (but not all) existing Java
technologies, to provide for migration paths.</p>
<p>Qi4j internally contains a lot of functional structures, and the community
is currently migrating Qi4j to Java 8, reducing a chunk of the codebase in the
process, and will likely discover new ways of simplicity. Many argue that Qi4j
should become its own programming language, but our position has always been
that the refactoring tools available in Java are so powerful and should not be
under-estimated. It would take endless amount of effort to even get close to
that, something that many other language platforms are still struggling
with.</p>
-<h1 id="initial-goals">Initial Goals</h1>
+<h1 id="initial-goals">Initial Goals<a class="headerlink"
href="#initial-goals" title="Permanent link">¶</a></h1>
<p>Qi4j is already on version 2.0, and striving towards both a 2.1 release as
well as a Java 8 specific 3.0 release. This will be one of the first "Java
8"-only projects at the ASF, and hopefully a lot of people find this in itself
attractive and exciting.</p>
<p>Qi4j's user base is relatively small, but we are convinced of its
remarkable properties as a productivity enhancing platform, and there is still
much to do to reach its full potential. There are a lot of low hanging fruit
(more extensions and libraries) as well as serious design challenges, such as
reloadable Modules via OSGi and Jigsaw integration in Java 9.</p>
<p>As mentioned above, the small agreeable user base also means that Qi4j can
be much more aggressive in adopting newer Java versions, and currently an
effort is on the way to leverage Java 8. The Stream API and closures are
implemented separately in Qi4j, and we are now converting all the internal code
to those features supplied in Java 8, to reduce the total code size of Qi4j
Core.</p>
-<h1 id="meritocracy">Meritocracy</h1>
+<h1 id="meritocracy">Meritocracy<a class="headerlink" href="#meritocracy"
title="Permanent link">¶</a></h1>
<p>Qi4j has been developed under heavy influence of ASF principles and
guidelines. The barrier to entry has been at the lowest possible level. A
rather aggressive Commit-then-Review process has been in place, but people have
in general been encouraged to do larger changes in publicly visible feature
branches. The low barrier hasn't created any major problems yet, as reverting
mistakes are relatively cheap, and it has been much more important to capture
the long-tail of contributions than to avoid occasional bad commits.</p>
<p>Qi4j is not operated by any organization, and all licensing is directly
from developer to the user. We will engage the legal committee to ensure the IP
rights are in full order.</p>
<p>Qi4j's release process has not been nearly as stringent as the one at ASF,
and will be the biggest change to the community. We will work closely with
willing "Overseers" (see below), change our Gradle-based build system and use
available tools, such as Rat, to ensure the highest quality releases
possible.</p>
-<h1 id="community">Community</h1>
+<h1 id="community">Community<a class="headerlink" href="#community"
title="Permanent link">¶</a></h1>
<p>The current Qi4j developer community is rather small, but passionate
individuals who are all convinced of Qi4j's merit and potential. We also think
that some of the past developers will re-join the effort, once we are at ASF
and some traction is attained.</p>
<p>Over the years there has been 28 code contributors in total, of which 8
have been considered Core Developers, i.e. allowed to make changes on the Core
runtime on trunk without hand-holding. No access control was in place to
enforce that, and a social contract worked very well.</p>
<p>We are probably not the best of community builders, and would welcome
members from ASF projects, who think Qi4j is promising, to assist in the
community building effort needed.</p>
-<h1 id="active-developers">Active Developers</h1>
+<h1 id="active-developers">Active Developers<a class="headerlink"
href="#active-developers" title="Permanent link">¶</a></h1>
<p>All the active developers are independent of each other. No two developers
work for the same employer, and no employer pays anyone for working full-time
on Qi4j. We consider the following developers 'active' at the moment, one way
or the other. It is a very diverse group;</p>
<ul>
<li>
@@ -267,31 +278,31 @@ All these restrictions are there to pro
<li>Michael Hunger - Neo Technology Inc</li>
<li>Tonny Kohar - independent Apache Batik and SVG consultant</li>
</ul>
-<h1 id="alignment">Alignment</h1>
+<h1 id="alignment">Alignment<a class="headerlink" href="#alignment"
title="Permanent link">¶</a></h1>
<p>Apache is a natural option for any Java project, as ASF has an overwhelming
percentage of Java projects.
But for Qi4j, we think that our choice to challenge every notion, not based on
popularity but on technical merit, should be inspiring to existing ASF projects
at large. And by doing so, we hope symbiotic relationships can be established
with a variety of other projects at ASF.</p>
<p>Qi4j is not "finished" and a lot of work in the Big Data space is still
needed. We would like to see HBase and Cassandra use-cases to be "Tackled Qi4j
Style" and practical conventions to emerge. There are several other ASF
projects which Qi4j could support 'better', if we get a little help from those
communities, incl Struts, Camel, ActiveMQ, Cayenne, Karaf and others.</p>
-<h1 id="known-risks">Known Risks</h1>
-<h2 id="orphaned-products">Orphaned products</h2>
+<h1 id="known-risks">Known Risks<a class="headerlink" href="#known-risks"
title="Permanent link">¶</a></h1>
+<h2 id="orphaned-products">Orphaned products<a class="headerlink"
href="#orphaned-products" title="Permanent link">¶</a></h2>
<p>Qi4j is not a company product and never was. It was started by two
individuals who have a long and strong community involvement dating back to
1998, also the time when they first learned to know each other.</p>
<p>If the community can't be built at ASF, then we think that there must be
something about Qi4j that is inherently alien to developers, and Qi4j has no
broader appeal, beyond those who have both seen the advantages as well as
gotten the opportunity to work with it and see for themselves the benefits. We
will work hard to ensure the long-term sustainability of the project, because
we think that Qi4j represents an important step towards a paradigm shift in
software development.</p>
-<h2 id="inexperience-with-open-source">Inexperience with Open Source</h2>
+<h2 id="inexperience-with-open-source">Inexperience with Open Source<a
class="headerlink" href="#inexperience-with-open-source" title="Permanent
link">¶</a></h2>
<p>Not only does Qi4j have a rather long running history of an independent
open source project, 6 major releases, and a track record of operating well as
such, but Niclas Hedhman was a long time member of the Incubator PMC, serving
on the Legal Committee and have plenty of experience of what is required of
Apache projects, as does Marcel Offermans. We wouldn't have proposed to move
Qi4j to Apache, unless we thought that the larger Qi4j community will work well
at the ASF, with a little bit of initial legal and community assistance from
friends at ASF.</p>
<p>All of Qi4j's history, except the initial 2-3 months, were done on open
mailing lists and public repositories. The practice of full discourse and
discussion on asynchronous mailing lists has been respected to the fullest
extent possible, and at no time has other means of communication been
regular.</p>
<p>Full source code history may not exist, as we went from Subversion at OPS4J
to GIT at OPS4J to finally GitHub, initially with sub-repositories (which
didn't work well) to finally the qi4j-sdk repository at GitHub. History has
probably broken at some point.</p>
<p>Just like early Apache project's mailing list history, Qi4j's might be
incomplete in public archives, but we should be able to restore that, from
GMail archives and other mailboxes. We intend to restore the mail archive, as
there are many worth-while nuggets in there.</p>
-<h2 id="homogenous-developers">Homogenous Developers</h2>
+<h2 id="homogenous-developers">Homogenous Developers<a class="headerlink"
href="#homogenous-developers" title="Permanent link">¶</a></h2>
<p>The only homogeneity of Qi4j is the individuals' desire to go beyond the
current status quo, to challenge things we do from habit, to criticize 'good
practices' and offer radically different solutions to so called mainstream
developers and accepted practices.</p>
<p>The contributors have a vast diversity in their backgrounds and interests,
even a non-developer making large contributions.</p>
<p>The group came together at Qi4j, drawn by its uniqueness and different way
to address common concerns. We consider this to be a non-issue.</p>
-<h2 id="reliance-on-salaried-developers">Reliance on Salaried Developers</h2>
+<h2 id="reliance-on-salaried-developers">Reliance on Salaried Developers<a
class="headerlink" href="#reliance-on-salaried-developers" title="Permanent
link">¶</a></h2>
<p>As far as we know, no one is currently paid to work on Qi4j itself. This
has been a factor in the slow down of activity in the last two years, but we
think that the bottom has been reached and that we will see an uptick during
2015, as some of the core members are coming back to write applications using
Qi4j.</p>
-<h2 id="relationships-with-other-apache-products">Relationships with Other
Apache Products</h2>
+<h2 id="relationships-with-other-apache-products">Relationships with Other
Apache Products<a class="headerlink"
href="#relationships-with-other-apache-products" title="Permanent
link">¶</a></h2>
<p>Qi4j is such a unique and radically different platform that there is no
direct alignment in Qi4j Core with other Apache (or any other for that matter)
projects. We have also kept the dependencies to a minimum by choice.
But Qi4j also defines Extension mechanisms, such as storage, indexing,
serialization and metrics, and we have implemented extensions for Apache
Cassandra and Apache Solr. We also have libraries that integrate other
technology into the Qi4j world, such as Apache Shiro, Apache Struts and Apache
CXF. We expect that additional Apache projects will be used in future
Extensions as well as Libraries, especially in the Big Data space, where we see
great opportunities for a Qi4j approach.</p>
-<h2 id="excessive-fascination-with-the-apache-brand">Excessive Fascination
with the Apache Brand</h2>
+<h2 id="excessive-fascination-with-the-apache-brand">Excessive Fascination
with the Apache Brand<a class="headerlink"
href="#excessive-fascination-with-the-apache-brand" title="Permanent
link">¶</a></h2>
<p>There is no doubt that the Apache brand is strong, no one can deny that.
But our primary 'fascination' is around the possibility to build a stronger
community at the ASF, than we otherwise seem to be able to do. Apache is a
natural water cooler, where open development people can share ideas and work
together. We hope to inspire other Apache projects to do greater things after
being exposed to Qi4j's unique approach to many technical challenges.</p>
-<h1 id="documentation">Documentation</h1>
+<h1 id="documentation">Documentation<a class="headerlink"
href="#documentation" title="Permanent link">¶</a></h1>
<div class="codehilite"><pre> <span class="n">Website</span><span
class="p">;</span> <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">qi4j</span><span class="p">.</span><span
class="n">org</span>
<span class="n">Source</span> <span class="n">Repository</span><span
class="p">;</span> <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">github</span><span class="p">.</span><span
class="n">com</span><span class="o">/</span><span class="n">Qi4j</span><span
class="o">/</span><span class="n">qi4j</span><span class="o">-</span><span
class="n">sdk</span>
@@ -300,31 +311,31 @@ But Qi4j also defines Extension mechanis
</pre></div>
-<h1 id="initial-source">Initial Source</h1>
+<h1 id="initial-source">Initial Source<a class="headerlink"
href="#initial-source" title="Permanent link">¶</a></h1>
<p>As mentioned earlier, Qi4j started out at OPS4J community, and the codebase
was initially on Subversion, then moved to OPS4J operated GIT repositories and
finally we moved to GitHub. We tried to preserve history the best we could,
with reasonable effort.
So, https://github.com/Qi4j contains the repositories that are relevant for
the Incubator. In practice, only the qi4j-sdk is current. We suggest that the
qi4j-core, qi4j-libraries and qi4j-extensions are imported but made read-only.
qi4j-sandbox is imported. qi4j.github.com contains the current website, but the
sources for that resides primarily inside the qi4j-sdk repository.</p>
-<h1 id="source-and-intellectual-property-submission-plan">Source and
Intellectual Property Submission Plan</h1>
+<h1 id="source-and-intellectual-property-submission-plan">Source and
Intellectual Property Submission Plan<a class="headerlink"
href="#source-and-intellectual-property-submission-plan" title="Permanent
link">¶</a></h1>
<p>There are no issues that we know of. Source code is available openly and
online. All code has originated directly from Qi4j contributors, marked as
Apache Licensed contributions and to the best of our knowledge there is no
encumbered IP issues.
As Qi4j was never a legal entity, all contributions were directly licensed
(Apache License 2.0) by the developer to the public. There is no problem
reaching out to all of the authors of an overwhelming part (if not all) of the
codebase and ask for paperwork, if this is necessary.</p>
-<h1 id="external-dependencies">External Dependencies</h1>
+<h1 id="external-dependencies">External Dependencies<a class="headerlink"
href="#external-dependencies" title="Permanent link">¶</a></h1>
<p>Qi4j has few dependencies, and all dependencies in all non-optional code is
ASLv2 compatible. The required dependencies are;
* ASM
* SLF4J (To be revised)
* org.json (included in source form in the repository. To be revised)</p>
<p>There are optional libraries and extensions that have dependencies on
projects with other licenses.
One very notable case, the Neo4j entity store extension, is worth mentioning
here. At the time this extension was created, Neo4j was under the AGPL license.
It is now under GPL, yet the Qi4j Neo4j extension is licensed under Apache
License v2. Are we not violating the license requirements of Neo4j? No, we
think not, as the contribution itself was made by Neo Technology under the
Apache license. Neo Technology argued that they had the right to provide the
extension under ALv2, yet whoever ran a Qi4j application with the Neo4j storage
extension, would be subjected to the AGPL (now GPL) requirements. Further
discussion with Legal committee is expected to follow.</p>
-<h1 id="cryptography">Cryptography</h1>
+<h1 id="cryptography">Cryptography<a class="headerlink" href="#cryptography"
title="Permanent link">¶</a></h1>
<p>Qi4j optionally depends on projects that use cryptography. As Qi4j isn't an
organization, and most developers live in Europe, we have not followed the US
trade restrictions on Cryptography.
Without an extensive check of all 100+ optional dependencies, Apache Shiro
stands out. We need to get feedback from legal@ on what the exact requirements
are, and conduct a full review.</p>
-<h1 id="required-resources">Required Resources</h1>
-<h2 id="mailing-lists">Mailing lists</h2>
+<h1 id="required-resources">Required Resources<a class="headerlink"
href="#required-resources" title="Permanent link">¶</a></h1>
+<h2 id="mailing-lists">Mailing lists<a class="headerlink"
href="#mailing-lists" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre> <span class="n">private</span><span
class="p">@</span><span class="n">zest</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span>
<span class="n">dev</span><span class="p">@</span><span
class="n">zest</span><span class="p">.</span><span class="n">apache</span><span
class="p">.</span><span class="n">org</span>
<span class="n">commits</span><span class="p">@</span><span
class="n">zest</span><span class="p">.</span><span class="n">apache</span><span
class="p">.</span><span class="n">org</span>
</pre></div>
-<h2 id="git-repositories">Git Repositories</h2>
+<h2 id="git-repositories">Git Repositories<a class="headerlink"
href="#git-repositories" title="Permanent link">¶</a></h2>
<p>We understand that Apache operates its own Git repositories, as well as
having a large number of read-only mirrors at GitHub under Apache
organization.</p>
<div class="codehilite"><pre> <span class="n">https</span><span
class="p">:</span><span class="o">//</span><span class="n">git</span><span
class="o">-</span><span class="n">wip</span><span class="o">-</span><span
class="n">us</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">asf</span><span
class="o">/</span><span class="n">qi4j</span><span class="p">.</span><span
class="n">git</span>
<span class="n">https</span><span class="p">:</span><span
class="o">//</span><span class="n">git</span><span class="o">-</span><span
class="n">wip</span><span class="o">-</span><span class="n">us</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">asf</span><span class="o">/</span><span
class="n">qi4j</span><span class="o">-</span><span class="n">legacy</span><span
class="o">-</span><span class="n">core</span><span class="p">.</span><span
class="n">git</span>
@@ -334,13 +345,13 @@ Without an extensive check of all 100+ o
</pre></div>
-<h2 id="issue-tracking">Issue Tracking</h2>
+<h2 id="issue-tracking">Issue Tracking<a class="headerlink"
href="#issue-tracking" title="Permanent link">¶</a></h2>
<p>We also have Jira issues we wish to import from Atlassian operated
https://ops4j1.jira.com/browse/QI, if possible, to </p>
<div class="codehilite"><pre> <span class="n">https</span><span
class="p">:</span><span class="o">//</span><span class="n">issues</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">jira</span><span
class="o">/</span><span class="n">browse</span><span class="o">/</span><span
class="n">ZEST</span>
</pre></div>
-<h1 id="initial-pmc">Initial PMC</h1>
+<h1 id="initial-pmc">Initial PMC<a class="headerlink" href="#initial-pmc"
title="Permanent link">¶</a></h1>
<ul>
<li>Alex Karasulu - [email protected]</li>
<li>James Carman - [email protected]</li>
@@ -350,7 +361,7 @@ Without an extensive check of all 100+ o
<li>Niclas Hedhman - [email protected]</li>
<li>Roman Shaposhnik - [email protected]</li>
</ul>
-<h1 id="committers">Committers</h1>
+<h1 id="committers">Committers<a class="headerlink" href="#committers"
title="Permanent link">¶</a></h1>
<ul>
<li>Edward Yakop - [email protected]</li>
<li>Jaydatt Desai - [email protected]</li>
@@ -363,7 +374,7 @@ Without an extensive check of all 100+ o
<li>Stanislav Muhametsin - [email protected]</li>
<li>Tibor Mlynarik - [email protected]</li>
</ul>
-<h1 id="affiliations">Affiliations</h1>
+<h1 id="affiliations">Affiliations<a class="headerlink" href="#affiliations"
title="Permanent link">¶</a></h1>
<ul>
<li>Edward Yakop - ABB Malaysia</li>
<li>Jaydatt Desai - Logicom Solutions</li>
Modified: websites/staging/community/trunk/content/speakers/index.html
==============================================================================
--- websites/staging/community/trunk/content/speakers/index.html (original)
+++ websites/staging/community/trunk/content/speakers/index.html Mon Nov 16
08:24:18 2015
@@ -153,23 +153,34 @@
<li><a href="/speakers">Speakers</a></li>
</ul>
<hr>
- <p>If you are organizing an event and looking for speakers or you are a
speaker looking 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>If you are organizing an event and looking for speakers or you are a
speaker looking for
materials this is the place for you.</p>
<p>If you are seeking to organise an Apache branded event then you must ensure
your activities
conform to the <a href="http://community.zones.apache.org/";>Third Party Event
Branding Policy</a>. Once you have verified you are in
conformance please consider adding your event to the <a
href="http://community.apache.org/calendars/conferences.html";>events
calendar</a>.</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>You can use our "<a href="http://community.zones.apache.org/";>Find
People</a>" application to find people willing and able to
talk about The Apache Software Foundation and its projects. A few people have
shared <a href="slides.html">Apache related presentations</a> for you.</p>
<p><em>NOTE</em> This service is alpha quality right now, and is populated by
only
some of the many volunteer speakers from Apache projects. If you have a
problem with
it or it doesn't turn up a suitable candiate please feel free to contact us
for help (see below).</p>
-<h3 id="listing-yourself-as-a-potential-speaker">Listing yourself as a
Potential Speaker</h3>
+<h3 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></h3>
<p>If you're an Apache committer, and you're interested in speaking about
Apache Projects, our Communities, or the Apache
Software Foundation as a whole, we'd encourage you to get involved and list
yourself in our speaker application!</p>
<p>For more details on how to list yourself as a potential speaker, see the <a
href="speakers.html">Apache Speakers WebApp</a> page.</p>
-<h2 id="speaker-support-materials">Speaker Support Materials</h2>
+<h2 id="speaker-support-materials">Speaker Support Materials<a
class="headerlink" href="#speaker-support-materials" title="Permanent
link">¶</a></h2>
<p>If you are creating your own slides you will find the <a
href="http://www.apache.org/foundation/press/kit/";>ASF Press Kit</a> useful. It
contains logos in various formats.</p>
<p>We aim to collect a set of slide decks about the Apache
Software Foundation for reuse in presentations. So far
Modified: websites/staging/community/trunk/content/speakers/slides.html
==============================================================================
--- websites/staging/community/trunk/content/speakers/slides.html (original)
+++ websites/staging/community/trunk/content/speakers/slides.html Mon Nov 16
08:24:18 2015
@@ -154,7 +154,18 @@
<li><a href="/speakers/slides.html">Slides.html</a></li>
</ul>
<hr>
- <p>This page contains links to presentations about the ASF and how
+ <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 links to presentations about the ASF and how
Apache projects work that you may find useful. Many of these have
been presented at <a href="http://events.apache.org";>ApacheCon conferences</a>
or
other open source conferences in the past.</p>
@@ -163,11 +174,11 @@ each individual presentation for license
<a href="http://community.apache.org/speakers/index.html";>speakers are
available</a>.</p>
<p>Similarly, many Apache speakers post their slides to the <a
href="http://www.slideshare.net/search/slideshow?searchfrom=header&q=apache+software";>SlideShare
website</a>.</p>
<p>New! Our many volunteers have posted <a
href="http://www.youtube.com/user/TheApacheFoundation";>full videos of all
ApacheCon 2013 presentations</a> for you!</p>
-<h1 id="isabel-drost">Isabel Drost</h1>
+<h1 id="isabel-drost">Isabel Drost<a class="headerlink" href="#isabel-drost"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="http://isabel-drost.de/hadoop/slides/christoph.pdf";>Open Source
development for students</a></li>
</ul>
-<h1 id="justin-erenkrantz">Justin Erenkrantz</h1>
+<h1 id="justin-erenkrantz">Justin Erenkrantz<a class="headerlink"
href="#justin-erenkrantz" title="Permanent link">¶</a></h1>
<ul>
<li><a
href="http://www.erenkrantz.com/apachecon/TransferSummit%20-%20Open%20Innovation.pdf";>Open
Innovation in The Apache Software Foundation</a></li>
<li><a
href="http://www.erenkrantz.com/apachecon/OSBC%20-%20No%20Jerks%20Allowed.pdf";>Writing
and Distributing Software "The Apache Way"</a></li>
@@ -175,18 +186,18 @@ each individual presentation for license
<li><a
href="http://www.erenkrantz.com/apachecon/Apache%20Roadshow%20Asia%202009.pdf";>Putting
It Together</a></li>
<li><a href="http://www.erenkrantz.com/apachecon/SAP%20Apache%20Intro.pdf";>An
Overview of The Apache Software Foundation</a></li>
</ul>
-<h1 id="ross-gardler">Ross Gardler</h1>
+<h1 id="ross-gardler">Ross Gardler<a class="headerlink" href="#ross-gardler"
title="Permanent link">¶</a></h1>
<ul>
<li><a
href="http://www.slideshare.net/bosc2010/gardler-bosc2010-communitydevelopmentattheasf";>Community
Development at the ASF</a></li>
<li><a
href="http://www.slideshare.net/rgardler/the-apache-way-and-openofficeorg";>The
Apache Way and OpenOffice.org</a></li>
</ul>
-<h1 id="jim-jagielski">Jim Jagielski</h1>
+<h1 id="jim-jagielski">Jim Jagielski<a class="headerlink"
href="#jim-jagielski" title="Permanent link">¶</a></h1>
<ul>
<li><a
href="http://people.apache.org/~jim/presos/IOOS2011/Creating_Community.pdf";>Communities
and Collaboration</a></li>
<li><a
href="http://people.apache.org/~jim/presos/OR2011/Open_Source_NotJust.pdf";>Open
Source: It's just not for IT anymore</a></li>
<li>More of Jims presentations <a
href="http://people.apache.org/~jim/presos/";>here</a> and <a
href="http://www.slideshare.net/jimjag/";>here</a></li>
</ul>
-<h1 id="bertrand-delacretaz">Bertrand Delacretaz</h1>
+<h1 id="bertrand-delacretaz">Bertrand Delacretaz<a class="headerlink"
href="#bertrand-delacretaz" title="Permanent link">¶</a></h1>
<p>From 2014:</p>
<ul>
<li><a
href="http://www.slideshare.net/bdelacretaz/open-source-at-scale-the-apache-software-foundation";>Open
Source at Scale - the Apache Software Foundation</a></li>
@@ -200,13 +211,13 @@ each individual presentation for license
<li><a
href="http://www.slideshare.net/bdelacretaz/open-source-enables-open-innovation";>Open
Source enables Open Innovation</a> </li>
<li><a
href="http://www.slideshare.net/bdelacretaz/open-source-in-education";>Open
Source in Education</a></li>
</ul>
-<h1 id="shane-curcuru">Shane Curcuru</h1>
+<h1 id="shane-curcuru">Shane Curcuru<a class="headerlink"
href="#shane-curcuru" title="Permanent link">¶</a></h1>
<ul>
<li><a
href="http://communityovercode.com/2012/05/camelone-2012-presentation/";>About:
Apache - The Foundation, The Way, The Projects</a></li>
<li><a
href="http://communityovercode.com/2012/07/oscon-presentation/";>Managing
Community Open Source Brands</a></li>
<li><a
href="http://communityovercode.com/2013/02/apachecon-presentation/";>Managing
Apache Project Brands</a> </li>
</ul>
-<h1 id="andrea-pescetti">Andrea Pescetti</h1>
+<h1 id="andrea-pescetti">Andrea Pescetti<a class="headerlink"
href="#andrea-pescetti" title="Permanent link">¶</a></h1>
<ul>
<li><a
href="http://www.slideshare.net/pescetti/bending-the-rules-community-over-code-over-policy-apachecon-2014";>Bending
the rules: Community over Code over Policy</a></li>
</ul>
