You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by gi...@apache.org on 2023/04/01 23:55:10 UTC
[comdev-site] branch asf-site updated: Updated asf-site from master at 48f4128d1491265d289878ff9ea28b205d437ad2
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 4f18c4e Updated asf-site from master at 48f4128d1491265d289878ff9ea28b205d437ad2
4f18c4e is described below
commit 4f18c4e988eecb04dbc2a89fa08553bb6922513e
Author: jenkins <bu...@apache.org>
AuthorDate: Sat Apr 1 23:55:04 2023 +0000
Updated asf-site from master at 48f4128d1491265d289878ff9ea28b205d437ad2
Built from https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/238/
---
content/_pagefind/fragment/en_63d56d2.pf_fragment | Bin 2410 -> 0 bytes
content/_pagefind/fragment/en_6b6484d.pf_fragment | Bin 4141 -> 0 bytes
content/_pagefind/fragment/en_71a0859.pf_fragment | Bin 10045 -> 0 bytes
content/_pagefind/fragment/en_96525da.pf_fragment | Bin 0 -> 10046 bytes
content/_pagefind/fragment/en_b54b92f.pf_fragment | Bin 0 -> 2411 bytes
content/_pagefind/fragment/en_c593f46.pf_fragment | Bin 0 -> 4141 bytes
content/_pagefind/index/en_7aef4be.pf_index | Bin 40273 -> 0 bytes
content/_pagefind/index/en_806a4f2.pf_index | Bin 14207 -> 0 bytes
content/_pagefind/index/en_87d89d2.pf_index | Bin 41873 -> 0 bytes
content/_pagefind/index/en_a020c84.pf_index | Bin 0 -> 14249 bytes
content/_pagefind/index/en_a252897.pf_index | Bin 0 -> 41929 bytes
content/_pagefind/index/en_f7eb2df.pf_index | Bin 0 -> 40476 bytes
content/_pagefind/pagefind-entry.json | 2 +-
content/_pagefind/pagefind.en_6be99aafa1.pf_meta | Bin 503 -> 0 bytes
content/_pagefind/pagefind.en_b7ea028c2b.pf_meta | Bin 0 -> 504 bytes
content/about/index.html | 1 -
content/apache-way.html | 1 -
.../apache-way/apache-project-maturity-model.html | 1 -
content/boardreport.html | 1 -
content/calendars/conferences.html | 3 +-
content/calendars/index.html | 1 -
content/calendars/index.xml | 2 +-
content/comdevboardreports.html | 1 -
content/committers/consensusBuilding.html | 1 -
content/committers/decisionMaking.html | 1 -
content/committers/funding-disclaimer.html | 17 ++---
content/committers/index.html | 1 -
content/committers/lazyConsensus.html | 1 -
content/committers/voting.html | 1 -
content/contactpoints.html | 1 -
content/contributors/becomingacommitter.html | 3 +-
content/contributors/etiquette.html | 1 -
content/contributors/index.html | 1 -
content/contributors/index.xml | 2 +-
content/events.html | 1 -
content/events/small-events.html | 1 -
content/gettingStarted/101.html | 1 -
content/gettingstarted.html | 1 -
content/gsoc/experiences.html | 3 +-
content/gsoc/gsoc-admin-tasks.html | 3 +-
content/gsoc/guide-to-being-a-mentor.html | 4 +-
content/gsoc/index.html | 1 -
content/gsoc/index.xml | 9 +--
content/gsoc/mentee-ranking-process.html | 3 +-
...e-comdev-gsoc-issue-tracker-for-gsoc-tasks.html | 3 +-
content/history.html | 1 -
content/history/boardresolution.html | 3 +-
content/history/index.xml | 4 +-
.../history/mentoringprogramme-icfoss-pilot.html | 3 +-
content/index.html | 7 +-
content/index.xml | 31 ++++----
content/links.html | 3 +-
content/lists.html | 1 -
content/mentor-request-mail.html | 81 ++++++++++-----------
content/mentoring/committer.html | 3 +-
content/mentoring/firstpatch.html | 3 +-
content/mentoring/index.html | 1 -
content/mentoring/index.xml | 6 +-
content/mentoring/mentor.html | 3 +-
content/mentoring/pmc.html | 1 -
content/newbiefaq.html | 3 +-
content/newcomers/index.html | 1 -
content/newcommitter.html | 3 +-
content/newsletter/2017-04.html | 1 -
content/newsletter/2017-05.html | 1 -
content/newsletter/index.html | 1 -
content/projectIndependence.html | 1 -
content/proposals.html | 1 -
content/proposals/ZestProposal.html | 7 +-
content/proposals/index.xml | 2 +-
content/speakers/index.html | 1 -
content/speakers/slides.html | 1 -
content/speakers/speakers.html | 7 +-
73 files changed, 100 insertions(+), 154 deletions(-)
diff --git a/content/_pagefind/fragment/en_63d56d2.pf_fragment b/content/_pagefind/fragment/en_63d56d2.pf_fragment
deleted file mode 100644
index c505ed9..0000000
Binary files a/content/_pagefind/fragment/en_63d56d2.pf_fragment and /dev/null differ
diff --git a/content/_pagefind/fragment/en_6b6484d.pf_fragment b/content/_pagefind/fragment/en_6b6484d.pf_fragment
deleted file mode 100644
index 34de1a4..0000000
Binary files a/content/_pagefind/fragment/en_6b6484d.pf_fragment and /dev/null differ
diff --git a/content/_pagefind/fragment/en_71a0859.pf_fragment b/content/_pagefind/fragment/en_71a0859.pf_fragment
deleted file mode 100644
index 0065b73..0000000
Binary files a/content/_pagefind/fragment/en_71a0859.pf_fragment and /dev/null differ
diff --git a/content/_pagefind/fragment/en_96525da.pf_fragment b/content/_pagefind/fragment/en_96525da.pf_fragment
new file mode 100644
index 0000000..ed129be
Binary files /dev/null and b/content/_pagefind/fragment/en_96525da.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_b54b92f.pf_fragment b/content/_pagefind/fragment/en_b54b92f.pf_fragment
new file mode 100644
index 0000000..3d8e95c
Binary files /dev/null and b/content/_pagefind/fragment/en_b54b92f.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_c593f46.pf_fragment b/content/_pagefind/fragment/en_c593f46.pf_fragment
new file mode 100644
index 0000000..4410a51
Binary files /dev/null and b/content/_pagefind/fragment/en_c593f46.pf_fragment differ
diff --git a/content/_pagefind/index/en_7aef4be.pf_index b/content/_pagefind/index/en_7aef4be.pf_index
deleted file mode 100644
index dceeb06..0000000
Binary files a/content/_pagefind/index/en_7aef4be.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_806a4f2.pf_index b/content/_pagefind/index/en_806a4f2.pf_index
deleted file mode 100644
index d946f5e..0000000
Binary files a/content/_pagefind/index/en_806a4f2.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_87d89d2.pf_index b/content/_pagefind/index/en_87d89d2.pf_index
deleted file mode 100644
index c217126..0000000
Binary files a/content/_pagefind/index/en_87d89d2.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_a020c84.pf_index b/content/_pagefind/index/en_a020c84.pf_index
new file mode 100644
index 0000000..99e0206
Binary files /dev/null and b/content/_pagefind/index/en_a020c84.pf_index differ
diff --git a/content/_pagefind/index/en_a252897.pf_index b/content/_pagefind/index/en_a252897.pf_index
new file mode 100644
index 0000000..bec3978
Binary files /dev/null and b/content/_pagefind/index/en_a252897.pf_index differ
diff --git a/content/_pagefind/index/en_f7eb2df.pf_index b/content/_pagefind/index/en_f7eb2df.pf_index
new file mode 100644
index 0000000..f60b509
Binary files /dev/null and b/content/_pagefind/index/en_f7eb2df.pf_index differ
diff --git a/content/_pagefind/pagefind-entry.json b/content/_pagefind/pagefind-entry.json
index 9d4cc75..d54eb48 100644
--- a/content/_pagefind/pagefind-entry.json
+++ b/content/_pagefind/pagefind-entry.json
@@ -1 +1 @@
-{"version":"0.12.0","languages":{"en":{"hash":"en_6be99aafa1","wasm":"en","page_count":51}}}
\ No newline at end of file
+{"version":"0.12.0","languages":{"en":{"hash":"en_b7ea028c2b","wasm":"en","page_count":51}}}
\ No newline at end of file
diff --git a/content/_pagefind/pagefind.en_6be99aafa1.pf_meta b/content/_pagefind/pagefind.en_6be99aafa1.pf_meta
deleted file mode 100644
index 0bd4936..0000000
Binary files a/content/_pagefind/pagefind.en_6be99aafa1.pf_meta and /dev/null differ
diff --git a/content/_pagefind/pagefind.en_b7ea028c2b.pf_meta b/content/_pagefind/pagefind.en_b7ea028c2b.pf_meta
new file mode 100644
index 0000000..0c87647
Binary files /dev/null and b/content/_pagefind/pagefind.en_b7ea028c2b.pf_meta differ
diff --git a/content/about/index.html b/content/about/index.html
index 14f87c8..866c378 100644
--- a/content/about/index.html
+++ b/content/about/index.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/about/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Community Development: What we do</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/apache-way.html b/content/apache-way.html
index 0ca0b90..a14f376 100644
--- a/content/apache-way.html
+++ b/content/apache-way.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/apache-way.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Apache-ways</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/apache-way/apache-project-maturity-model.html b/content/apache-way/apache-project-maturity-model.html
index e02bd3a..9715f90 100644
--- a/content/apache-way/apache-project-maturity-model.html
+++ b/content/apache-way/apache-project-maturity-model.html
@@ -15,7 +15,6 @@ Overview ¶ The goals of this maturity model are to describe how Apache proj
<meta property="article:modified_time" content="2021-06-21T10:25:49+02:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - A Maturity Model for Apache Projects</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/boardreport.html b/content/boardreport.html
index c1d3016..d9d8851 100644
--- a/content/boardreport.html
+++ b/content/boardreport.html
@@ -15,7 +15,6 @@ https://apache.org/foundation/board/reporting" />
<meta property="article:modified_time" content="2023-03-21T14:07:43-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - BoardReport</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/calendars/conferences.html b/content/calendars/conferences.html
index a428514..49bf55f 100644
--- a/content/calendars/conferences.html
+++ b/content/calendars/conferences.html
@@ -9,14 +9,13 @@
<meta property="og:title" content="Apache Conferences Calendar" />
<meta property="og:description" content="Deprecated - See New Calendar instead ¶ This calendar is no longer maintained; please see this page instead.
This Calendar is maintained by the Apache Community Development Committee (ComDev), to have your event listed considered for addition please mail dev@community.apache.org. Note that to be listed in this calendar events must conform to the Third Party Event Branding Policy.
-Upcoming events ¶ List loading This Calendar is also available as an iCal feed" />
+Upcoming events ¶ List loading This Calendar is also available as an iCal feed" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/calendars/conferences.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="calendars" />
<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Apache Conferences Calendar</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/calendars/index.html b/content/calendars/index.html
index 36e3746..890e60e 100644
--- a/content/calendars/index.html
+++ b/content/calendars/index.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/calendars/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Apache Related Event Calendars</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/calendars/index.xml b/content/calendars/index.xml
index 1d89c1f..bf92e62 100644
--- a/content/calendars/index.xml
+++ b/content/calendars/index.xml
@@ -14,7 +14,7 @@
<guid>https://community.apache.org/calendars/conferences.html</guid>
<description>Deprecated - See New Calendar instead &para; This calendar is no longer maintained; please see this page instead.
This Calendar is maintained by the Apache Community Development Committee (ComDev), to have your event listed considered for addition please mail dev@community.apache.org. Note that to be listed in this calendar events must conform to the Third Party Event Branding Policy.
-Upcoming events &para; List loading This Calendar is also available as an iCal feed</description>
+Upcoming events &para; List loading This Calendar is also available as an iCal feed</description>
</item>
</channel>
diff --git a/content/comdevboardreports.html b/content/comdevboardreports.html
index 8c2200e..88eb765 100644
--- a/content/comdevboardreports.html
+++ b/content/comdevboardreports.html
@@ -15,7 +15,6 @@ You can read the complete list of Apache Community Development board reports. A
<meta property="article:modified_time" content="2023-03-21T13:34:10-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - ComDevBoardReports</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/committers/consensusBuilding.html b/content/committers/consensusBuilding.html
index 0ba73c3..0e8dc3d 100644
--- a/content/committers/consensusBuilding.html
+++ b/content/committers/consensusBuilding.html
@@ -15,7 +15,6 @@ Constructive discussion is the lifeblood of a successful project. However, we wa
<meta property="article:modified_time" content="2020-12-02T09:52:19-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Consensus Building</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/committers/decisionMaking.html b/content/committers/decisionMaking.html
index 507ee2e..64ec9cd 100644
--- a/content/committers/decisionMaking.html
+++ b/content/committers/decisionMaking.html
@@ -15,7 +15,6 @@ To some, the idea of having to establish consensus in a large and distributed te
<meta property="article:modified_time" content="2021-01-15T09:22:16-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Decision-Making</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/committers/funding-disclaimer.html b/content/committers/funding-disclaimer.html
index 293baf5..24767d4 100644
--- a/content/committers/funding-disclaimer.html
+++ b/content/committers/funding-disclaimer.html
@@ -17,7 +17,6 @@ If you have any question about this, feel free to ask on our dev@community." />
<meta property="article:modified_time" content="2021-07-06T11:05:05-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Funding campaign disclaimer</title>
<link rel="shortcut icon" href="images/favicon.ico">
@@ -199,14 +198,14 @@ ASF and how its projects work.</p>
<a href="https://lists.apache.org/list.html?dev@community.apache.org">dev@community.apache.org</a> mailing list.</p>
<h2 id="example-disclaimer-for-a-personal-crowdfunding-campaign">Example disclaimer for a personal crowdfunding campaign <a class="headerlink" title="Permalink" href="#example-disclaimer-for-a-personal-crowdfunding-campaign">¶</a></h2>
<p>Here’s a nice example, based on a disclaimer one committer has used:</p>
-<div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-text" data-lang="text"> Disclaimers: This campaign is done by me, FOO, as an independent individual, not
- by the Apache Software Foundation nor the Apache BAR project. I'm not representing
- the Foundation in any way in this campaign, nor does Apache endorse it. The
- Foundation has a policy of not paying for development work. All its members are
- voluntary, me included. Any code I'll write or change will have to pass the usual BAR
- team approval process. If this campaign isn't funded, I'll continue participating
- in the BAR project in the same way as before.
-</code></pre></div><p>See also the <a href="https://mail-archives.apache.org/mod_mbox/community-dev/201310.mbox/%3Cop.w4fwv6ewovlrp5%40arsmachina%3E">discussion thread</a> about this
+<div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span> Disclaimers: This campaign is done by me, FOO, as an independent individual, not
+</span></span><span style="display:flex;"><span> by the Apache Software Foundation nor the Apache BAR project. I'm not representing
+</span></span><span style="display:flex;"><span> the Foundation in any way in this campaign, nor does Apache endorse it. The
+</span></span><span style="display:flex;"><span> Foundation has a policy of not paying for development work. All its members are
+</span></span><span style="display:flex;"><span> voluntary, me included. Any code I'll write or change will have to pass the usual BAR
+</span></span><span style="display:flex;"><span> team approval process. If this campaign isn't funded, I'll continue participating
+</span></span><span style="display:flex;"><span> in the BAR project in the same way as before.
+</span></span></code></pre></div><p>See also the <a href="https://mail-archives.apache.org/mod_mbox/community-dev/201310.mbox/%3Cop.w4fwv6ewovlrp5%40arsmachina%3E">discussion thread</a> about this
campaign.</p>
<h2 id="friends-of-apache-groovy">Friends of Apache Groovy <a class="headerlink" title="Permalink" href="#friends-of-apache-groovy">¶</a></h2>
<p><a href="https://opencollective.com/friends-of-groovy">Friends of Apache Groovy</a> has another good example which supports activities
diff --git a/content/committers/index.html b/content/committers/index.html
index dcb86e3..4bb5336 100644
--- a/content/committers/index.html
+++ b/content/committers/index.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/committers/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Committer resources</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/committers/lazyConsensus.html b/content/committers/lazyConsensus.html
index 5ef11fd..ee5b4a8 100644
--- a/content/committers/lazyConsensus.html
+++ b/content/committers/lazyConsensus.html
@@ -14,7 +14,6 @@
<meta property="article:modified_time" content="2022-02-20T11:10:20-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Lazy Consensus</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/committers/voting.html b/content/committers/voting.html
index 4b6d90a..a490021 100644
--- a/content/committers/voting.html
+++ b/content/committers/voting.html
@@ -15,7 +15,6 @@ Preparing for a Vote ¶ It is important to ensure that the community has tim
<meta property="article:modified_time" content="2022-02-20T11:05:53-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Voting</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/contactpoints.html b/content/contactpoints.html
index 894b110..c1671cc 100644
--- a/content/contactpoints.html
+++ b/content/contactpoints.html
@@ -17,7 +17,6 @@ Technical Questions ¶ If you have a technical question about this website,
<meta property="article:modified_time" content="2020-12-10T09:12:00-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - ContactPoints</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/contributors/becomingacommitter.html b/content/contributors/becomingacommitter.html
index 0cfb7f6..a79b39a 100644
--- a/content/contributors/becomingacommitter.html
+++ b/content/contributors/becomingacommitter.html
@@ -7,14 +7,13 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Becoming a committer" />
-<meta property="og:description" content="Read the mailing list Contribute code (and other things) End user support Documentation Review PRs and tickets Be visible Test, and vote on releases (non-binding) Give talks Disclaimer ¶ Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons." />
+<meta property="og:description" content="Read the mailing list Contribute code (and other things) End user support Documentation Review PRs and tickets Be visible Test, and vote on releases (non-binding) Give talks Disclaimer ¶ Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/contributors/becomingacommitter.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="contributors" />
<meta property="article:modified_time" content="2023-03-30T13:02:33-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Becoming a committer</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/contributors/etiquette.html b/content/contributors/etiquette.html
index 2dad8cb..d6229f0 100644
--- a/content/contributors/etiquette.html
+++ b/content/contributors/etiquette.html
@@ -15,7 +15,6 @@ Code of Conduct ¶ The ASF has adopted a Code of Conduct which covers intera
<meta property="article:modified_time" content="2023-03-17T12:29:24-05:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - ASF Community Etiquette Guidelines</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/contributors/index.html b/content/contributors/index.html
index cfd2285..7a25a29 100644
--- a/content/contributors/index.html
+++ b/content/contributors/index.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Contributing to the Apache Software Foundation</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/contributors/index.xml b/content/contributors/index.xml
index e4a0001..4449e91 100644
--- a/content/contributors/index.xml
+++ b/content/contributors/index.xml
@@ -22,7 +22,7 @@ Code of Conduct &para; The ASF has adopted a Code of Conduct which covers in
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/contributors/becomingacommitter.html</guid>
- <description>Read the mailing list Contribute code (and other things) End user support Documentation Review PRs and tickets Be visible Test, and vote on releases (non-binding) Give talks Disclaimer &para; Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.</description>
+ <description>Read the mailing list Contribute code (and other things) End user support Documentation Review PRs and tickets Be visible Test, and vote on releases (non-binding) Give talks Disclaimer &para; Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.</description>
</item>
</channel>
diff --git a/content/events.html b/content/events.html
index f3b425a..8b2c8de 100644
--- a/content/events.html
+++ b/content/events.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/events.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Events</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/events/small-events.html b/content/events/small-events.html
index 83bdf9c..b4c4c38 100644
--- a/content/events/small-events.html
+++ b/content/events/small-events.html
@@ -19,7 +19,6 @@ c) Once brand use is approved by the respective PMCs, inform the community devel
<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Requirements for organizers of small Apache-related events</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/gettingStarted/101.html b/content/gettingStarted/101.html
index 65490d3..2cba70c 100644
--- a/content/gettingStarted/101.html
+++ b/content/gettingStarted/101.html
@@ -15,7 +15,6 @@ Finding the right project ¶ The key to working on projects at Apache (and o
<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Getting started</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/gettingstarted.html b/content/gettingstarted.html
index 7165715..360751e 100644
--- a/content/gettingstarted.html
+++ b/content/gettingstarted.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/gettingstarted.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - GettingStarteds</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/gsoc/experiences.html b/content/gsoc/experiences.html
index b988552..da32aa5 100644
--- a/content/gsoc/experiences.html
+++ b/content/gsoc/experiences.html
@@ -9,14 +9,13 @@
<meta property="og:title" content="Apache in GSoC" />
<meta property="og:description" content="This should be in the GSoC directory
This is 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.
-2018 Overview ¶ Students accepted: ? Students who passed final: 29 2017 Overview ¶ Students accepted: ? Students who passed final: 27 2016 Overview ¶ Students accepted: 49 Students who passed final: 35 2015 Overview ¶ Students accepted: 56 Students who passed final: 47 2014 Overview ¶ Students accepted: 42 Students who passed final: 35 2013 Overview ¶ Students accepted: 51 Students who passed final: 44 2012 Overview ¶ Students accepted: 41 [...]
+2018 Overview ¶ Students accepted: ? Students who passed final: 29 2017 Overview ¶ Students accepted: ? Students who passed final: 27 2016 Overview ¶ Students accepted: 49 Students who passed final: 35 2015 Overview ¶ Students accepted: 56 Students who passed final: 47 2014 Overview ¶ Students accepted: 42 Students who passed final: 35 2013 Overview ¶ Students accepted: 51 Students who passed final: 44 2012 Overview ¶ Students accepted: 41 Students who [...]
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/gsoc/experiences.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gsoc" />
<meta property="article:modified_time" content="2023-03-21T10:25:42+07:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Apache in GSoC</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/gsoc/gsoc-admin-tasks.html b/content/gsoc/gsoc-admin-tasks.html
index 617a026..a683552 100644
--- a/content/gsoc/gsoc-admin-tasks.html
+++ b/content/gsoc/gsoc-admin-tasks.html
@@ -9,14 +9,13 @@
<meta property="og:title" content="GSoC admins" />
<meta property="og:description" content="A comprehensive guide to being a GSoC admin for the ASF
List of duties:
- Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc<year>; and mentor. If a project doesn’t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next)." />
+Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc<year>; and mentor. If a project doesn’t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next)." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/gsoc/gsoc-admin-tasks.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gsoc" />
<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - GSoC admins</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/gsoc/guide-to-being-a-mentor.html b/content/gsoc/guide-to-being-a-mentor.html
index 94823a5..0534c93 100644
--- a/content/gsoc/guide-to-being-a-mentor.html
+++ b/content/gsoc/guide-to-being-a-mentor.html
@@ -8,15 +8,13 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="guide to being a mentor" />
<meta property="og:description" content="Submitting ideas to the mentoring programme ¶ We invite all ASF projects 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 use the Comdev Issue Tracker For GSoC Tasks. We are looking for as many interesting projects as we can come up with.
-
-Important Steps ¶ Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with “mentor” (these will show up at the ASF-wide list of issues) Label the main issue with “gsoc2023” if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available." />
+Important Steps ¶ Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with “mentor” (these will show up at the ASF-wide list of issues) Label the main issue with “gsoc2023” if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/gsoc/guide-to-being-a-mentor.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gsoc" />
<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - guide to being a mentor</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/gsoc/index.html b/content/gsoc/index.html
index 0cc2f1a..6b4a064 100644
--- a/content/gsoc/index.html
+++ b/content/gsoc/index.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/gsoc/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - GSoC</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/gsoc/index.xml b/content/gsoc/index.xml
index a952b30..0bede6c 100644
--- a/content/gsoc/index.xml
+++ b/content/gsoc/index.xml
@@ -14,7 +14,7 @@
<guid>https://community.apache.org/gsoc/experiences.html</guid>
<description>This should be in the GSoC directory
This is 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.
-2018 Overview &para; Students accepted: ? Students who passed final: 29 2017 Overview &para; Students accepted: ? Students who passed final: 27 2016 Overview &para; Students accepted: 49 Students who passed final: 35 2015 Overview &para; Students accepted: 56 Students who passed final: 47 2014 Overview &para; Students accepted: 42 Students who passed final: 35 2013 Overview &para; Students accepted: 51 Students who passed final: 44 2012 Overview &p [...]
+2018 Overview &para; Students accepted: ? Students who passed final: 29 2017 Overview &para; Students accepted: ? Students who passed final: 27 2016 Overview &para; Students accepted: 49 Students who passed final: 35 2015 Overview &para; Students accepted: 56 Students who passed final: 47 2014 Overview &para; Students accepted: 42 Students who passed final: 35 2013 Overview &para; Students accepted: 51 Students who passed final: 44 2012 Overview &para; Student [...]
</item>
<item>
@@ -25,7 +25,7 @@ This is a place for collecting information about GSoC activities each year for h
<guid>https://community.apache.org/gsoc/gsoc-admin-tasks.html</guid>
<description>A comprehensive guide to being a GSoC admin for the ASF
List of duties:
- Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc&lt;year&gt;; and mentor. If a project doesn&rsquo;t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next).</description>
+Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc&lt;year&gt;; and mentor. If a project doesn&rsquo;t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next).</description>
</item>
<item>
@@ -35,8 +35,7 @@ List of duties:
<guid>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</guid>
<description>Submitting ideas to the mentoring programme &para; We invite all ASF projects 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 use the Comdev Issue Tracker For GSoC Tasks. We are looking for as many interesting projects as we can come up with.
-
-Important Steps &para; Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with &ldquo;mentor&rdquo; (these will show up at the ASF-wide list of issues) Label the main issue with &ldquo;gsoc2023&rdquo; if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available.</description>
+Important Steps &para; Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with &ldquo;mentor&rdquo; (these will show up at the ASF-wide list of issues) Label the main issue with &ldquo;gsoc2023&rdquo; if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available.</description>
</item>
<item>
@@ -57,7 +56,7 @@ Remember, mentoring is all about the mentee and open source as a whole. It is no
<guid>https://community.apache.org/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html</guid>
<description>If your project does not use the ASF Jira for issue tracking, you can use the ComDev GSoC Jira project to record your GSoC tasks.
- Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community.</description>
+Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community.</description>
</item>
</channel>
diff --git a/content/gsoc/mentee-ranking-process.html b/content/gsoc/mentee-ranking-process.html
index 506094b..eff2be1 100644
--- a/content/gsoc/mentee-ranking-process.html
+++ b/content/gsoc/mentee-ranking-process.html
@@ -16,7 +16,6 @@ Remember, mentoring is all about the mentee and open source as a whole. It is no
<meta property="article:modified_time" content="2023-03-21T10:25:42+07:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Mentee Ranking Process</title>
<link rel="shortcut icon" href="images/favicon.ico">
@@ -293,7 +292,7 @@ community members to mark a proposal up or down (-4 to +4).</li>
</ul>
<p>The admins transfer the scores to Melange.</p>
<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>
+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? <a class="headerlink" title="Permalink" href="#what-are-we-looking-for-in-a-good-proposal">¶</a></h1>
<p>In general we much prefer new mentees to repeat mentees. The goal is to
diff --git a/content/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html b/content/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html
index 0d9a924..a8e10f0 100644
--- a/content/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html
+++ b/content/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html
@@ -8,14 +8,13 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Use the Comdev Issue Tracker For GSoC Tasks" />
<meta property="og:description" content="If your project does not use the ASF Jira for issue tracking, you can use the ComDev GSoC Jira project to record your GSoC tasks.
- Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community." />
+Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gsoc" />
<meta property="article:modified_time" content="2023-03-21T13:35:34+05:30" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Use the Comdev Issue Tracker For GSoC Tasks</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/history.html b/content/history.html
index 4e4d714..896146c 100644
--- a/content/history.html
+++ b/content/history.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/history.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Histories</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/history/boardresolution.html b/content/history/boardresolution.html
index ae1db33..42c9fdc 100644
--- a/content/history/boardresolution.html
+++ b/content/history/boardresolution.html
@@ -8,14 +8,13 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="ComDevBoardResolution" />
<meta property="og:description" content="The Apache Community Development Project was created in November 2009.
-Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Community Development Projec [...]
+Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Community Development Project& [...]
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/history/boardresolution.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="history" />
<meta property="article:modified_time" content="2023-03-27T22:49:45+01:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - ComDevBoardResolution</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/history/index.xml b/content/history/index.xml
index 8be86e2..69f34e9 100644
--- a/content/history/index.xml
+++ b/content/history/index.xml
@@ -13,7 +13,7 @@
<guid>https://community.apache.org/history/boardresolution.html</guid>
<description>The Apache Community Development Project was created in November 2009.
-Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the &quot;Apache Community Development Pr [...]
+Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the &quot;Apache Community Development Proj [...]
</item>
<item>
@@ -23,7 +23,7 @@ Board Resolution Creating the Apache Community Development Project Establish t
<guid>https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html</guid>
<description>Note that this information is about a pilot program that happened back in 2013.
- The ASF has been participating in many mentoring initiatives, and it&rsquo;s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
+The ASF has been participating in many mentoring initiatives, and it&rsquo;s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
The mentoring programme is not here to teach you to write documentation or code.</description>
</item>
diff --git a/content/history/mentoringprogramme-icfoss-pilot.html b/content/history/mentoringprogramme-icfoss-pilot.html
index 741280c..c58c0d5 100644
--- a/content/history/mentoringprogramme-icfoss-pilot.html
+++ b/content/history/mentoringprogramme-icfoss-pilot.html
@@ -8,7 +8,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Pilot Mentoring Programme with India ICFOSS" />
<meta property="og:description" content="Note that this information is about a pilot program that happened back in 2013.
- The ASF has been participating in many mentoring initiatives, and it’s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
+The ASF has been participating in many mentoring initiatives, and it’s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
The mentoring programme is not here to teach you to write documentation or code." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="history" />
@@ -16,7 +16,6 @@ The mentoring programme is not here to teach you to write documentation or code.
<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Pilot Mentoring Programme with India ICFOSS</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/index.html b/content/index.html
index 43a1db8..3ffc132 100644
--- a/content/index.html
+++ b/content/index.html
@@ -3,7 +3,7 @@
<html lang="en">
<head>
- <meta name="generator" content="Hugo 0.92.2" />
+ <meta name="generator" content="Hugo 0.111.3">
<meta name="description" content="Apache Community Development"/>
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
@@ -13,7 +13,6 @@
<meta property="og:url" content="https://community.apache.org/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Apache Community Development - Welcome</title>
<link rel="shortcut icon" href="images/favicon.ico">
@@ -224,9 +223,9 @@ in the specific Apache projects that interest you.</p>
<div class="row">
<div class="col-md-4">
<h4 id="open-source-contributors">Open Source Contributors <a class="headerlink" title="Permalink" href="#open-source-contributors">¶</a></h4>
-<p>If you know a little about open source, and want to understand how the ASF works, our <a href="contributors/index.html">contributors' section</a> is for you.</p>
+<p>If you know a little about open source, and want to understand how the ASF works, our <a href="contributors/index.html">contributors’ section</a> is for you.</p>
<p>We also have a collection of <a href="links.html">links</a> to relevant information.</p>
-<p>Apache Committers should read our <a href="committers/index.html">committers' section</a> and see the <a href="https://www.apache.org/dev/">Developer Information site</a>.</p>
+<p>Apache Committers should read our <a href="committers/index.html">committers’ section</a> and see the <a href="https://www.apache.org/dev/">Developer Information site</a>.</p>
</div>
<div class="col-md-4">
<h4 id="how-apache-works">How Apache works <a class="headerlink" title="Permalink" href="#how-apache-works">¶</a></h4>
diff --git a/content/index.xml b/content/index.xml
index c0f8970..ec9f6ae 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -13,7 +13,7 @@
<guid>https://community.apache.org/proposals/ZestProposal.html</guid>
<description>title: Zest Proposal
-Abstract &para; qi4j = new Energy4Java(); 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.
+Abstract &para; qi4j = new Energy4Java(); 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.
Governance of Provisional Top Level Project &para; 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.</description>
</item>
@@ -35,7 +35,7 @@ Overview &para; The goals of this maturity model are to describe how Apache
<guid>https://community.apache.org/calendars/conferences.html</guid>
<description>Deprecated - See New Calendar instead &para; This calendar is no longer maintained; please see this page instead.
This Calendar is maintained by the Apache Community Development Committee (ComDev), to have your event listed considered for addition please mail dev@community.apache.org. Note that to be listed in this calendar events must conform to the Third Party Event Branding Policy.
-Upcoming events &para; List loading This Calendar is also available as an iCal feed</description>
+Upcoming events &para; List loading This Calendar is also available as an iCal feed</description>
</item>
<item>
@@ -46,7 +46,7 @@ Upcoming events &para; List loading This Calendar is also available as an
<guid>https://community.apache.org/gsoc/experiences.html</guid>
<description>This should be in the GSoC directory
This is 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.
-2018 Overview &para; Students accepted: ? Students who passed final: 29 2017 Overview &para; Students accepted: ? Students who passed final: 27 2016 Overview &para; Students accepted: 49 Students who passed final: 35 2015 Overview &para; Students accepted: 56 Students who passed final: 47 2014 Overview &para; Students accepted: 42 Students who passed final: 35 2013 Overview &para; Students accepted: 51 Students who passed final: 44 2012 Overview &p [...]
+2018 Overview &para; Students accepted: ? Students who passed final: 29 2017 Overview &para; Students accepted: ? Students who passed final: 27 2016 Overview &para; Students accepted: 49 Students who passed final: 35 2015 Overview &para; Students accepted: 56 Students who passed final: 47 2014 Overview &para; Students accepted: 42 Students who passed final: 35 2013 Overview &para; Students accepted: 51 Students who passed final: 44 2012 Overview &para; Student [...]
</item>
<item>
@@ -57,7 +57,7 @@ This is a place for collecting information about GSoC activities each year for h
<guid>https://community.apache.org/newbiefaq.html</guid>
<description>These answers to frequently asked questions may help newcomers to The Apache Software Foundation (ASF) and our many Apache projects understand how we work.
Index of Questions
- About The Apache Software Foundation How do I find projects or technologies at the ASF? How are projects managed at the ASF? How do I ask a question about the ASF in general? How do I get user support for an Apache project?</description>
+About The Apache Software Foundation How do I find projects or technologies at the ASF? How are projects managed at the ASF? How do I ask a question about the ASF in general? How do I get user support for an Apache project? Getting involved with Apache projects How do I choose an Apache project to work on?</description>
</item>
<item>
@@ -99,7 +99,7 @@ Code of Conduct &para; The ASF has adopted a Code of Conduct which covers in
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/contributors/becomingacommitter.html</guid>
- <description>Read the mailing list Contribute code (and other things) End user support Documentation Review PRs and tickets Be visible Test, and vote on releases (non-binding) Give talks Disclaimer &para; Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.</description>
+ <description>Read the mailing list Contribute code (and other things) End user support Documentation Review PRs and tickets Be visible Test, and vote on releases (non-binding) Give talks Disclaimer &para; Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.</description>
</item>
<item>
@@ -129,7 +129,7 @@ You can read the complete list of Apache Community Development board reports. A
<guid>https://community.apache.org/history/boardresolution.html</guid>
<description>The Apache Community Development Project was created in November 2009.
-Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the &quot;Apache Community Development Pr [...]
+Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the &quot;Apache Community Development Proj [...]
</item>
<item>
@@ -203,7 +203,7 @@ Finding the right project &para; The key to working on projects at Apache (a
<guid>https://community.apache.org/gsoc/gsoc-admin-tasks.html</guid>
<description>A comprehensive guide to being a GSoC admin for the ASF
List of duties:
- Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc&lt;year&gt;; and mentor. If a project doesn&rsquo;t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next).</description>
+Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc&lt;year&gt;; and mentor. If a project doesn&rsquo;t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next).</description>
</item>
<item>
@@ -213,8 +213,7 @@ List of duties:
<guid>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</guid>
<description>Submitting ideas to the mentoring programme &para; We invite all ASF projects 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 use the Comdev Issue Tracker For GSoC Tasks. We are looking for as many interesting projects as we can come up with.
-
-Important Steps &para; Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with &ldquo;mentor&rdquo; (these will show up at the ASF-wide list of issues) Label the main issue with &ldquo;gsoc2023&rdquo; if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available.</description>
+Important Steps &para; Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with &ldquo;mentor&rdquo; (these will show up at the ASF-wide list of issues) Label the main issue with &ldquo;gsoc2023&rdquo; if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available.</description>
</item>
<item>
@@ -244,7 +243,7 @@ Here&rsquo;s an example of what your first email might look like:</descripti
<guid>https://community.apache.org/links.html</guid>
<description>This is a collection of links to information that&rsquo;s relevant to the Apache Way and Open Source in general.
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.
-Books &para; Producing Open Source Software - by Karl Fogel Blog posts &para; Apache - the Switzerland of Open Source?</description>
+Books &para; Producing Open Source Software - by Karl Fogel Blog posts &para; Apache - the Switzerland of Open Source?</description>
</item>
<item>
@@ -291,7 +290,7 @@ These things vary from one project to another, so clearly documenting them for y
Here&rsquo;s the basics that are true across (almost) all Apache projects.
TODO
Outline:
- Encouraging other contributors Good commit messages Becoming a PMC member </description>
+Encouraging other contributors Good commit messages Becoming a PMC member </description>
</item>
<item>
@@ -311,7 +310,7 @@ These things vary a little from one project to another, so clearly documenting t
<guid>https://community.apache.org/mentoring/mentor.html</guid>
<description>Mentoring Mentors &para; The job of a mentor is to reproduce - spread the work load. Once you&rsquo;ve mentored someone, you need to encourage them to become a mentor themselves. Here&rsquo;s some ways you can do that.
- Point out people that need a little help Encourage them to answer a question rather than answering it yourself &hellip; TODO</description>
+Point out people that need a little help Encourage them to answer a question rather than answering it yourself &hellip; TODO</description>
</item>
<item>
@@ -323,7 +322,7 @@ These things vary a little from one project to another, so clearly documenting t
<description>Mentoring: First Patch &para; A beginner&rsquo;s first patch on a project can be an intimidating and frustrating experience. Clearly documenting the entire process from checkout to accepted patch greatly lowers the barrier for a new contributor, and makes it more likely that they&rsquo;ll come back for their second patch.
Here&rsquo;s some tips on how to do that.
Outline:
- Talk to the project first Make sure it&rsquo;s wanted/welcome See if there&rsquo;s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation </description>
+Talk to the project first Make sure it&rsquo;s wanted/welcome See if there&rsquo;s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation </description>
</item>
<item>
@@ -334,7 +333,7 @@ Outline:
<guid>https://community.apache.org/newcommitter.html</guid>
<description>Identifying potential new committers, calling a vote for their recognition as a committer and processing the relevant documents are tasks to which the whole community can contribute.
Each project has a different approach to managing new committers. This page describes a common process found in many Apache projects. It also provides drafts for the various communications that are necessary.
- Guidelines for assessing new candidates for committership Ability to work cooperatively with peers.</description>
+Guidelines for assessing new candidates for committership Ability to work cooperatively with peers.</description>
</item>
<item>
@@ -344,7 +343,7 @@ Each project has a different approach to managing new committers. This page desc
<guid>https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html</guid>
<description>Note that this information is about a pilot program that happened back in 2013.
- The ASF has been participating in many mentoring initiatives, and it&rsquo;s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
+The ASF has been participating in many mentoring initiatives, and it&rsquo;s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
The mentoring programme is not here to teach you to write documentation or code.</description>
</item>
@@ -379,7 +378,7 @@ c) Once brand use is approved by the respective PMCs, inform the community devel
<guid>https://community.apache.org/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html</guid>
<description>If your project does not use the ASF Jira for issue tracking, you can use the ComDev GSoC Jira project to record your GSoC tasks.
- Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community.</description>
+Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community.</description>
</item>
<item>
diff --git a/content/links.html b/content/links.html
index 5fbeaf4..56f0671 100644
--- a/content/links.html
+++ b/content/links.html
@@ -9,14 +9,13 @@
<meta property="og:title" content="Links" />
<meta property="og:description" content="This is a collection of links to information that’s relevant to the Apache Way and Open Source in general.
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.
-Books ¶ Producing Open Source Software - by Karl Fogel Blog posts ¶ Apache - the Switzerland of Open Source?" />
+Books ¶ Producing Open Source Software - by Karl Fogel Blog posts ¶ Apache - the Switzerland of Open Source?" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/links.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
<meta property="article:modified_time" content="2023-03-16T12:35:40-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Links</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/lists.html b/content/lists.html
index 6b3284a..2ba8ba2 100644
--- a/content/lists.html
+++ b/content/lists.html
@@ -14,7 +14,6 @@
<meta property="article:modified_time" content="2020-12-15T09:34:12-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Community Development Mailing Lists</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/mentor-request-mail.html b/content/mentor-request-mail.html
index 233267f..2505238 100644
--- a/content/mentor-request-mail.html
+++ b/content/mentor-request-mail.html
@@ -15,7 +15,6 @@ Here’s an example of what your first email might look like:" />
<meta property="article:modified_time" content="2020-12-13T09:34:53-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - How To: Write A Mentor Request Email</title>
<link rel="shortcut icon" href="images/favicon.ico">
@@ -189,46 +188,46 @@ plans for tackling the issue. This lets the community know you are working
on the issue and gives the community an early opportunity to help course
correct your proposal, if necessary (which can save you lots of time).</p>
<p>Here’s an example of what your first email might look like:</p>
-<div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-text" data-lang="text">SUBJECT: A proposal for Skinnable widgets (WOOKIE-131)
-
-Hi, I'm new to the Wookie project but I'd like to tackle the "Skinnablewidgets"
-issue (WOOKIE-131, see [1]). Before I start implementing this I'd like to
-run my ideas past you to make sure I'm not missing something important.
-
-If I understand the issue correctly, we need to define the structure of a minimal
-widget. For example:
-
-<div id="wookie-widget">
- <div id="wookie-toolbar">This is where the toolbar will be</div>
- <div id="wookie-content">This is where the content will be</div>
- <div id="wookie-footer">This is where the footer will be</div>
-</div>
-
-We also need to provide a default CSS for rendering this as, for example:
-
-+-----------------------+
-|TOOLBAR |
-+-----------------------+
-| |
-|CONTENT |
-| |
-+-----------------------+
-|FOOTER |
-+-----------------------+
-
-We need to document all this (how to use it and how to extend it) on the Wookie website, and change all widgets to conform to
-this format.
-
-Once all this is in place I would like to start extending it to provide documented
-CSS identifiers to use in common cases. For example, we may want to define a
-"wookie-navigation" style for a common navigation menu. We can then provide
-various CSS alternatives for rending this as a vertical navigation menu, drop down
-menu, or whatever.
-
-Am I on the right track? Are there any important points I'm missing?
-
-[1] https://issues.apache.org/jira/browse/WOOKIE-131
-</code></pre></div><p>There are two main advantages to sending a mail like this. First, you
+<div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span>SUBJECT: A proposal for Skinnable widgets (WOOKIE-131)
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>Hi, I'm new to the Wookie project but I'd like to tackle the "Skinnablewidgets"
+</span></span><span style="display:flex;"><span>issue (WOOKIE-131, see [1]). Before I start implementing this I'd like to
+</span></span><span style="display:flex;"><span>run my ideas past you to make sure I'm not missing something important.
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>If I understand the issue correctly, we need to define the structure of a minimal
+</span></span><span style="display:flex;"><span>widget. For example:
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><div id="wookie-widget">
+</span></span><span style="display:flex;"><span> <div id="wookie-toolbar">This is where the toolbar will be</div>
+</span></span><span style="display:flex;"><span> <div id="wookie-content">This is where the content will be</div>
+</span></span><span style="display:flex;"><span> <div id="wookie-footer">This is where the footer will be</div>
+</span></span><span style="display:flex;"><span></div>
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>We also need to provide a default CSS for rendering this as, for example:
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>+-----------------------+
+</span></span><span style="display:flex;"><span>|TOOLBAR |
+</span></span><span style="display:flex;"><span>+-----------------------+
+</span></span><span style="display:flex;"><span>| |
+</span></span><span style="display:flex;"><span>|CONTENT |
+</span></span><span style="display:flex;"><span>| |
+</span></span><span style="display:flex;"><span>+-----------------------+
+</span></span><span style="display:flex;"><span>|FOOTER |
+</span></span><span style="display:flex;"><span>+-----------------------+
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>We need to document all this (how to use it and how to extend it) on the Wookie website, and change all widgets to conform to
+</span></span><span style="display:flex;"><span>this format.
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>Once all this is in place I would like to start extending it to provide documented
+</span></span><span style="display:flex;"><span>CSS identifiers to use in common cases. For example, we may want to define a
+</span></span><span style="display:flex;"><span>"wookie-navigation" style for a common navigation menu. We can then provide
+</span></span><span style="display:flex;"><span>various CSS alternatives for rending this as a vertical navigation menu, drop down
+</span></span><span style="display:flex;"><span>menu, or whatever.
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>Am I on the right track? Are there any important points I'm missing?
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>[1] https://issues.apache.org/jira/browse/WOOKIE-131
+</span></span></code></pre></div><p>There are two main advantages to sending a mail like this. First, you
force yourself to think carefully about what the project requires and whether you
have the skills to do it (and thus where you will need help). Second, it lets
people in the community provide input. For example, in the above case
diff --git a/content/mentoring/committer.html b/content/mentoring/committer.html
index aa48e95..df1db0c 100644
--- a/content/mentoring/committer.html
+++ b/content/mentoring/committer.html
@@ -12,14 +12,13 @@ These things vary from one project to another, so clearly documenting them for y
Here’s the basics that are true across (almost) all Apache projects.
TODO
Outline:
- Encouraging other contributors Good commit messages Becoming a PMC member " />
+Encouraging other contributors Good commit messages Becoming a PMC member " />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/mentoring/committer.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="mentoring" />
<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Mentoring a new committer</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/mentoring/firstpatch.html b/content/mentoring/firstpatch.html
index 922ddd9..7640181 100644
--- a/content/mentoring/firstpatch.html
+++ b/content/mentoring/firstpatch.html
@@ -10,14 +10,13 @@
<meta property="og:description" content="Mentoring: First Patch ¶ A beginner’s first patch on a project can be an intimidating and frustrating experience. Clearly documenting the entire process from checkout to accepted patch greatly lowers the barrier for a new contributor, and makes it more likely that they’ll come back for their second patch.
Here’s some tips on how to do that.
Outline:
- Talk to the project first Make sure it’s wanted/welcome See if there’s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation " />
+Talk to the project first Make sure it’s wanted/welcome See if there’s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation " />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/mentoring/firstpatch.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="mentoring" />
<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Mentoring: First Patch</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/mentoring/index.html b/content/mentoring/index.html
index 4628b09..efd7e49 100644
--- a/content/mentoring/index.html
+++ b/content/mentoring/index.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/mentoring/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Mentoring</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/mentoring/index.xml b/content/mentoring/index.xml
index 40433de..8460a5b 100644
--- a/content/mentoring/index.xml
+++ b/content/mentoring/index.xml
@@ -17,7 +17,7 @@ These things vary from one project to another, so clearly documenting them for y
Here&rsquo;s the basics that are true across (almost) all Apache projects.
TODO
Outline:
- Encouraging other contributors Good commit messages Becoming a PMC member </description>
+Encouraging other contributors Good commit messages Becoming a PMC member </description>
</item>
<item>
@@ -37,7 +37,7 @@ These things vary a little from one project to another, so clearly documenting t
<guid>https://community.apache.org/mentoring/mentor.html</guid>
<description>Mentoring Mentors &para; The job of a mentor is to reproduce - spread the work load. Once you&rsquo;ve mentored someone, you need to encourage them to become a mentor themselves. Here&rsquo;s some ways you can do that.
- Point out people that need a little help Encourage them to answer a question rather than answering it yourself &hellip; TODO</description>
+Point out people that need a little help Encourage them to answer a question rather than answering it yourself &hellip; TODO</description>
</item>
<item>
@@ -49,7 +49,7 @@ These things vary a little from one project to another, so clearly documenting t
<description>Mentoring: First Patch &para; A beginner&rsquo;s first patch on a project can be an intimidating and frustrating experience. Clearly documenting the entire process from checkout to accepted patch greatly lowers the barrier for a new contributor, and makes it more likely that they&rsquo;ll come back for their second patch.
Here&rsquo;s some tips on how to do that.
Outline:
- Talk to the project first Make sure it&rsquo;s wanted/welcome See if there&rsquo;s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation </description>
+Talk to the project first Make sure it&rsquo;s wanted/welcome See if there&rsquo;s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation </description>
</item>
</channel>
diff --git a/content/mentoring/mentor.html b/content/mentoring/mentor.html
index 78bb12a..c4d829a 100644
--- a/content/mentoring/mentor.html
+++ b/content/mentoring/mentor.html
@@ -8,14 +8,13 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Mentoring Mentors" />
<meta property="og:description" content="Mentoring Mentors ¶ The job of a mentor is to reproduce - spread the work load. Once you’ve mentored someone, you need to encourage them to become a mentor themselves. Here’s some ways you can do that.
- Point out people that need a little help Encourage them to answer a question rather than answering it yourself … TODO" />
+Point out people that need a little help Encourage them to answer a question rather than answering it yourself … TODO" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/mentoring/mentor.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="mentoring" />
<meta property="article:modified_time" content="2020-03-24T15:03:46+01:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Mentoring Mentors</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/mentoring/pmc.html b/content/mentoring/pmc.html
index cc00fb4..fd64871 100644
--- a/content/mentoring/pmc.html
+++ b/content/mentoring/pmc.html
@@ -15,7 +15,6 @@ These things vary a little from one project to another, so clearly documenting t
<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Mentoring a new PMC member</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/newbiefaq.html b/content/newbiefaq.html
index 33b9129..06700bd 100644
--- a/content/newbiefaq.html
+++ b/content/newbiefaq.html
@@ -9,14 +9,13 @@
<meta property="og:title" content="Apache Newcomer FAQs" />
<meta property="og:description" content="These answers to frequently asked questions may help newcomers to The Apache Software Foundation (ASF) and our many Apache projects understand how we work.
Index of Questions
- About The Apache Software Foundation How do I find projects or technologies at the ASF? How are projects managed at the ASF? How do I ask a question about the ASF in general? How do I get user support for an Apache project?" />
+About The Apache Software Foundation How do I find projects or technologies at the ASF? How are projects managed at the ASF? How do I ask a question about the ASF in general? How do I get user support for an Apache project? Getting involved with Apache projects How do I choose an Apache project to work on?" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/newbiefaq.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Apache Newcomer FAQs</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/newcomers/index.html b/content/newcomers/index.html
index 930ff0c..7959a6a 100644
--- a/content/newcomers/index.html
+++ b/content/newcomers/index.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/newcomers/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Welcome, Apache newcomers!</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/newcommitter.html b/content/newcommitter.html
index f62938a..410eb36 100644
--- a/content/newcommitter.html
+++ b/content/newcommitter.html
@@ -9,14 +9,13 @@
<meta property="og:title" content="New Committer" />
<meta property="og:description" content="Identifying potential new committers, calling a vote for their recognition as a committer and processing the relevant documents are tasks to which the whole community can contribute.
Each project has a different approach to managing new committers. This page describes a common process found in many Apache projects. It also provides drafts for the various communications that are necessary.
- Guidelines for assessing new candidates for committership Ability to work cooperatively with peers." />
+Guidelines for assessing new candidates for committership Ability to work cooperatively with peers." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/newcommitter.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - New Committer</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/newsletter/2017-04.html b/content/newsletter/2017-04.html
index e9b30f5..de1a921 100644
--- a/content/newsletter/2017-04.html
+++ b/content/newsletter/2017-04.html
@@ -17,7 +17,6 @@ In our recent community survey, we heard from a lot of you that you want more in
<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - April 2017 Community Newsletter</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/newsletter/2017-05.html b/content/newsletter/2017-05.html
index 12e7521..ca2e3f2 100644
--- a/content/newsletter/2017-05.html
+++ b/content/newsletter/2017-05.html
@@ -16,7 +16,6 @@ If you blog about anything Apache related, you might want to know about http://p
<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - May 2017 Community Newsletter</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/newsletter/index.html b/content/newsletter/index.html
index af5b8f0..50118c0 100644
--- a/content/newsletter/index.html
+++ b/content/newsletter/index.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/newsletter/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Newsletter</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/projectIndependence.html b/content/projectIndependence.html
index 8605b08..b6b6f3c 100644
--- a/content/projectIndependence.html
+++ b/content/projectIndependence.html
@@ -15,7 +15,6 @@ A community is not merely a set of rules; it is also a set of behaviors that the
<meta property="article:modified_time" content="2022-01-07T11:22:24-08:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Project Independence</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/proposals.html b/content/proposals.html
index 44cdb95..ba9668d 100644
--- a/content/proposals.html
+++ b/content/proposals.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/proposals.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Proposals</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/proposals/ZestProposal.html b/content/proposals/ZestProposal.html
index fbef05a..04a45a3 100644
--- a/content/proposals/ZestProposal.html
+++ b/content/proposals/ZestProposal.html
@@ -8,7 +8,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="" />
<meta property="og:description" content="title: Zest Proposal
-Abstract ¶ qi4j = new Energy4Java(); 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.
+Abstract ¶ qi4j = new Energy4Java(); 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.
Governance of Provisional Top Level Project ¶ 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." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/proposals/ZestProposal.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="proposals" />
@@ -16,7 +16,6 @@ Governance of Provisional Top Level Project ¶ Provisional Top Level Project
<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - </title>
<link rel="shortcut icon" href="images/favicon.ico">
@@ -232,7 +231,7 @@ It comprises of the ability to write smaller parts of code than regular classes,
<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 [...]
<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/ [...]
-<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 [...]
+<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 [...]
<h1 id="history">History <a class="headerlink" title="Permalink" href="#history">¶</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>
@@ -316,7 +315,7 @@ But for Qi4j, we think that our choice to challenge every notion, not based on 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 <a class="headerlink" title="Permalink" href="#homogenous-developers">¶</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 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 <a class="headerlink" title="Permalink" href="#reliance-on-salaried-developers">¶</a></h2>
diff --git a/content/proposals/index.xml b/content/proposals/index.xml
index 1999b47..592c387 100644
--- a/content/proposals/index.xml
+++ b/content/proposals/index.xml
@@ -13,7 +13,7 @@
<guid>https://community.apache.org/proposals/ZestProposal.html</guid>
<description>title: Zest Proposal
-Abstract &para; qi4j = new Energy4Java(); 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.
+Abstract &para; qi4j = new Energy4Java(); 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.
Governance of Provisional Top Level Project &para; 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.</description>
</item>
diff --git a/content/speakers/index.html b/content/speakers/index.html
index 662c9e2..cadff4d 100644
--- a/content/speakers/index.html
+++ b/content/speakers/index.html
@@ -12,7 +12,6 @@
<meta property="og:url" content="https://community.apache.org/speakers/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Speaking about Apache, our Projects and our Community</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/speakers/slides.html b/content/speakers/slides.html
index 0a813b7..16c5ae0 100644
--- a/content/speakers/slides.html
+++ b/content/speakers/slides.html
@@ -16,7 +16,6 @@ Many Apache speakers post their slides to the SlideShare website, and the Feathe
<meta property="article:modified_time" content="2023-03-17T10:04:48-04:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Apache-related slides, videos and presentations</title>
<link rel="shortcut icon" href="images/favicon.ico">
diff --git a/content/speakers/speakers.html b/content/speakers/speakers.html
index 4eff1d7..c713484 100644
--- a/content/speakers/speakers.html
+++ b/content/speakers/speakers.html
@@ -16,7 +16,6 @@ Listing yourself as a potential speaker ¶ To list yourself as someone inter
<meta property="article:modified_time" content="2021-07-05T14:07:56-03:00" /><meta property="og:site_name" content="Apache Community Development" />
-
<title>Apache Community Development - Listing yourself as a Potential Speaker</title>
<link rel="shortcut icon" href="images/favicon.ico">
@@ -223,16 +222,16 @@ svn:</p>
helper. If your FOAF file is in svn and showing up on people.apache.org,
add in:</p>
<pre tabindex="0"><code><helper>
- <foaf:Person rdf:resource="urn:org:apache:[your username].rdf" />
+ <foaf:Person rdf:resource="urn:org:apache:[your username].rdf" />
</helper>
</code></pre><p>If you have your FOAF file externally hosted, the <strong>rdf:resource</strong>
should point to the URL of the file.</p>
<p>For an apache committer with username “foo”, your entry would be one of:</p>
<pre tabindex="0"><code><helper>
- <foaf:Person rdf:resource="urn:org:apache:foo.rdf" />
+ <foaf:Person rdf:resource="urn:org:apache:foo.rdf" />
</helper>
<helper>
- <foaf:Person rdf:resource="https://www.example.com/foaf/foo.rdf" />
+ <foaf:Person rdf:resource="https://www.example.com/foaf/foo.rdf" />
</helper>
</code></pre><p>Within 24 hours of committing your addition to
<em>local-outreach/ApacheSpeakers.rdf</em>, you should appear in the web