You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by bd...@apache.org on 2023/04/20 16:58:41 UTC
[comdev-site] 01/01: HACK - prepare staging branch
This is an automated email from the ASF dual-hosted git repository.
bdelacretaz pushed a commit to branch preview/bestpractices-staging
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
commit 68ba92d8ca19cdcd8a83b59a00611002b10819ad
Author: Bertrand Delacretaz <bd...@apache.org>
AuthorDate: Thu Apr 20 18:58:07 2023 +0200
HACK - prepare staging branch
---
Jenkinsfile | 125 -------
LICENSE | 202 -----------
NOTICE | 5 -
README.md | 51 ---
archetypes/default.md | 6 -
archives/comdev-blog-html-export-2023-04-20.zip | Bin 155589 -> 0 bytes
.../community.apache.org-content-before-hugo.zip | Bin 875718 -> 0 bytes
hugo.toml | 47 ---
index.html | 1 +
layouts/_default/_markup/render-heading.html | 5 -
layouts/_default/baseof.html | 196 ----------
layouts/_default/list.html | 9 -
layouts/_default/single.html | 7 -
layouts/partials/breadcrumbs.html | 15 -
layouts/partials/matomo.html | 17 -
layouts/partials/page-summary.html | 9 -
layouts/partials/pagination.html | 15 -
layouts/partials/published-date.html | 1 -
layouts/robots.txt | 6 -
layouts/shortcodes/toc.html | 1 -
source/_index.md | 149 --------
source/about/_index.md | 63 ----
source/apache-way/apache-project-maturity-model.md | 395 --------------------
source/blog/2023-preparing-the-move.md | 10 -
source/blog/_index.md | 14 -
source/boardreport.md | 7 -
source/calendars/_index.md | 49 ---
source/calendars/conferences.md | 89 -----
source/comdevboardreports.md | 7 -
source/committers/_index.md | 124 -------
source/committers/consensusBuilding.md | 54 ---
source/committers/decisionMaking.md | 42 ---
source/committers/funding-disclaimer.md | 40 ---
source/committers/lazyConsensus.md | 51 ---
source/committers/voting.md | 36 --
source/contactpoints.md | 61 ----
source/contributors/_index.md | 101 ------
source/contributors/becomingacommitter.md | 110 ------
source/contributors/etiquette.md | 73 ----
source/events/small-events.md | 27 --
source/gettingStarted/101.md | 73 ----
source/gsoc/_index.md | 181 ----------
source/gsoc/experiences.md | 80 -----
source/gsoc/gsoc-admin-tasks.md | 152 --------
source/gsoc/guide-to-being-a-mentor.md | 133 -------
source/gsoc/mentee-ranking-process.md | 214 -----------
...the-comdev-gsoc-issue-tracker-for-gsoc-tasks.md | 15 -
source/history/boardresolution.md | 70 ----
source/history/mentoringprogramme-icfoss-pilot.md | 73 ----
source/links.md | 28 --
source/lists.md | 67 ----
source/mentor-request-mail.md | 60 ----
source/mentoring/_index.md | 26 --
source/mentoring/committer.md | 23 --
source/mentoring/firstpatch.md | 25 --
source/mentoring/mentor.md | 15 -
source/mentoring/pmc.md | 29 --
source/newbiefaq.md | 221 ------------
source/newcomers/_index.md | 37 --
source/newcommitter.md | 400 ---------------------
source/newsletter/2017-04.md | 78 ----
source/newsletter/2017-05.md | 14 -
source/newsletter/_index.md | 15 -
source/projectIndependence.md | 96 -----
source/proposals/ZestProposal.md | 281 ---------------
source/speakers/_index.md | 51 ---
source/speakers/slides.md | 110 ------
source/speakers/speakers.md | 75 ----
static/.htaccess | 7 -
static/css/bootstrap.min.css | 7 -
static/css/main.css | 46 ---
static/doap_ComDev.rdf | 67 ----
static/favicon.ico | Bin 1086 -> 0 bytes
static/images/aceu19_1.jpg | Bin 159826 -> 0 bytes
static/images/aceu19_2.jpg | Bin 150738 -> 0 bytes
static/images/favicon.ico | Bin 1595 -> 0 bytes
static/js/bootstrap.min.js | 7 -
static/js/jquery.min.js | 2 -
static/speakers/talks/Apache_Way_2017.yaml | 24 --
.../talks/Committed_To_The_Apache_Way.yaml | 20 --
static/speakers/talks/From_Dev_To_User.yaml | 20 --
static/speakers/talks/README.yaml | 24 --
static/speakers/talks/Tale_Of_Two_Developers.yaml | 32 --
static/speakers/talks/curcuru.yaml | 10 -
static/speakers/talks/sblackmon.yaml | 8 -
static/speakers/talks/sharan.yaml | 8 -
static/speakers/talks/wang.yaml | 7 -
static/speakers/themes/ASFTheme.kth | Bin 585110 -> 0 bytes
88 files changed, 1 insertion(+), 5150 deletions(-)
diff --git a/Jenkinsfile b/Jenkinsfile
deleted file mode 100644
index 8ca3404..0000000
--- a/Jenkinsfile
+++ /dev/null
@@ -1,125 +0,0 @@
-#!groovy
-/*
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License. You may obtain a copy of the License at
- *
- * https://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-pipeline {
- agent {
- // https://cwiki.apache.org/confluence/display/INFRA/ci-builds.apache.org
- label 'git-websites'
- }
-
- environment {
- DEPLOY_BRANCH = 'preview/bestpractices-staging'
- HUGO_VERSION = '0.111.3'
- HUGO_HASH = 'b382aacb522a470455ab771d0e8296e42488d3ea4e61fe49c11c32ec7fb6ee8b'
- PAGEFIND_VERSION = '0.12.0'
- PAGEFIND_HASH = '3e450176562b65359f855c04894ec2c07ffd30a8d08ef4d5812f8d3469d7a58f'
- }
-
- stages {
- stage('Prepare') {
- steps {
- script {
- // Capture last commit hash for final commit message
- env.LAST_SHA = sh(script:'git log -n 1 --pretty=format:\'%H\'', returnStdout: true).trim()
-
- // Download Hugo
- env.HUGO_DIR = sh(script:'mktemp -d', returnStdout: true).trim()
- sh "mkdir -p ${env.HUGO_DIR}/bin"
- sh "wget --no-verbose -O ${env.HUGO_DIR}/hugo.tar.gz https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_Linux-64bit.tar.gz"
- // Verify the checksum
- def hugo_hash = sha256 file: "${env.HUGO_DIR}/hugo.tar.gz"
- assert hugo_hash == "${HUGO_HASH}"
- // Unpack Hugo
- sh "tar -C ${env.HUGO_DIR}/bin -xkf ${env.HUGO_DIR}/hugo.tar.gz"
-
- // Download Pagefind
- env.PAGEFIND_DIR = sh(script:'mktemp -d', returnStdout: true).trim()
- sh "mkdir -p ${env.PAGEFIND_DIR}/bin"
- sh "wget --no-verbose -O ${env.PAGEFIND_DIR}/pagefind.tar.gz https://github.com/CloudCannon/pagefind/releases/download/v${PAGEFIND_VERSION}/pagefind-v${PAGEFIND_VERSION}-x86_64-unknown-linux-musl.tar.gz"
- // Verify the checksum
- def pagefind_hash = sha256 file: "${env.PAGEFIND_DIR}/pagefind.tar.gz"
- assert pagefind_hash == "${PAGEFIND_HASH}"
- // Unpack Pagefind
- sh "tar -C ${env.PAGEFIND_DIR}/bin -xkf ${env.PAGEFIND_DIR}/pagefind.tar.gz"
-
- // Setup directory structure for generated content
- env.TMP_DIR = sh(script:'mktemp -d', returnStdout: true).trim()
- env.OUT_DIR = "${env.TMP_DIR}/content"
- sh "mkdir -p ${env.OUT_DIR}"
-
- }
- }
- }
- stage('Build') {
- steps {
- script {
- sh "${HUGO_DIR}/bin/hugo --destination ${env.OUT_DIR}"
- sh "${PAGEFIND_DIR}/bin/pagefind --source ${env.OUT_DIR}"
- }
- }
- }
- stage('Deploy') {
- when {
- anyOf {
- branch 'preview/bestpractices'
- }
- }
- steps {
- script {
- // Checkout branch with generated content
- sh """
- git checkout ${DEPLOY_BRANCH}
- git pull origin ${DEPLOY_BRANCH}
- """
-
- // Remove the content of the target branch and replace it with the content of the temp folder
- sh """
- rm -rf ${WORKSPACE}/content
- git rm -r --cached content/*
- mkdir -p ${WORKSPACE}/content
- cp -rT ${env.TMP_DIR}/* ${WORKSPACE}/content
- """
-
- // Commit the changes to the target branch
- env.COMMIT_MESSAGE1 = "Updated ${DEPLOY_BRANCH} from ${BRANCH_NAME} at ${env.LAST_SHA}"
- env.COMMIT_MESSAGE2 = "Built from ${BUILD_URL}"
- sh """
- git add -A
- git commit -m "${env.COMMIT_MESSAGE1}" -m "${env.COMMIT_MESSAGE2}" | true
- """
-
- // Push the generated content for deployment
- sh "git push -u origin ${DEPLOY_BRANCH}"
- }
- }
- }
- }
-
- post {
- always {
- script {
- sh """
- rm -rf ${env.HUGO_DIR}
- rm -rf ${env.PAGEFIND_DIR}
- rm -rf ${env.TMP_DIR}
- """
- }
- deleteDir() /* clean up our workspace */
- }
- }
-}
diff --git a/LICENSE b/LICENSE
deleted file mode 100644
index 62589ed..0000000
--- a/LICENSE
+++ /dev/null
@@ -1,202 +0,0 @@
-
- Apache License
- Version 2.0, January 2004
- https://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- https://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
diff --git a/NOTICE b/NOTICE
deleted file mode 100644
index 60cac2e..0000000
--- a/NOTICE
+++ /dev/null
@@ -1,5 +0,0 @@
-Apache Comdev
-Copyright 2020 The Apache Software Foundation
-
-This product includes software developed at
-The Apache Software Foundation (https://www.apache.org/).
diff --git a/README.md b/README.md
deleted file mode 100644
index cb4874c..0000000
--- a/README.md
+++ /dev/null
@@ -1,51 +0,0 @@
-<!--
-Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements. See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to You under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-# Apache Community Development website
-
-This is the source code for the website of the [Apache Community Development PMC website](https://community.apache.org/), hosted at:
-
- https://community.apache.org/
-
-To get in touch with that PMC please use the [dev@community.apache.org](https://lists.apache.org/list.html?dev@community.apache.org) mailing list.
-
-The repository for the [events.apache.org](https://events.apache.org/) website, which is also managed by the Community Development PMC, is at https://github.com/apache/comdev-events-site
-
-## How to publish the website
-
-Changes to the `main` branch of this repository trigger the [comdev-site Jenkins Job](https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/), which generates the website content and commits it to the `asf-site` branch of this repository. There's currently (April 2020) a lag of about ten minutes for the Jenkins job to start, if you commit directly to the GitHub repository.
-
-The [ASF's gitpubsub mechanism](https://blogs.apache.org/infra/entry/git_based_websites_available) then synchronizes that content to [https://community.apache.org/](https://community.apache.org/), usually within a few seconds. More details about the publication process can be found in the [ASF Documentation about Project sites](https://infra.apache.org/project-site.html). If for some reason this process fails, you can use [the self-service page from ASF Infra](https://selfserve.apache.or [...]
-
-## Powered by Hugo!
-
-The website uses Hugo as static website generator, see the [Hugo website](https://gohugo.io/) for more information
-and for how to install and run it if needed.
-
-Other Apache websites that are built with Hugo should be listed by [this GitHub query for the 'hugo' tag](https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories).
-
-## How to test the website and changes on your own computer
-
-You need a recent version of `hugo`, to find out which one is used to deploy this site
-look at the Jenkins build output, linked above.
-
-To generate the static website, execute `hugo` to generate the website under `target/content` and execute
-`npx -y pagefind --source target/content` to index the content for Pagefind (the search bar on the website).
-
-During development, it may be useful to run an incremental build. For this to work, execute
-`hugo server -D -d /tmp/comdev-generated-site` to continuously (re)generate and serve the website on `localhost:1313`
-(-D means include draft pages). In another terminal, execute `npx -y pagefind --source /tmp/comdev-generated-site` to
-index the site content for Pagefind (the search bar on the website).
diff --git a/archetypes/default.md b/archetypes/default.md
deleted file mode 100644
index 00e77bd..0000000
--- a/archetypes/default.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "{{ replace .Name "-" " " | title }}"
-date: {{ .Date }}
-draft: true
----
-
diff --git a/archives/comdev-blog-html-export-2023-04-20.zip b/archives/comdev-blog-html-export-2023-04-20.zip
deleted file mode 100644
index fdcb0ba..0000000
Binary files a/archives/comdev-blog-html-export-2023-04-20.zip and /dev/null differ
diff --git a/archives/community.apache.org-content-before-hugo.zip b/archives/community.apache.org-content-before-hugo.zip
deleted file mode 100644
index 2d33bbd..0000000
Binary files a/archives/community.apache.org-content-before-hugo.zip and /dev/null differ
diff --git a/hugo.toml b/hugo.toml
deleted file mode 100644
index 0fe5949..0000000
--- a/hugo.toml
+++ /dev/null
@@ -1,47 +0,0 @@
-baseURL = "https://community.apache.org"
-title = "Apache Comdev"
-languageCode = "en"
-
-contentDir = "source"
-publishDir = "target/content"
-
-disablePathToLower = true
-uglyURLs = true
-enableRobotsTXT = true
-disableBrowserError = true
-timeout = 3000
-
-disableKinds = ["taxonomy", "taxonomyTerm"]
-ignoreFiles = [ ] # No files to ignore
-
-# Highlighting config. See https://help.farbox.com/pygments.html
-pygmentsCodeFences = true
-pygmentsUseClasses = false
-pygmentsStyle = "emacs"
-
-# Enable Git variables like commit, lastmod
-enableGitInfo = true
-
-[markup.goldmark.renderer]
-unsafe = true
-
-[blackfriday]
-# hrefTargetBlank = true # We don't want everything opened in a new window
-fractions = false
-
-[frontmatter]
-date = ["date", ":filename", "publishDate", "lastmod"]
-
-[params]
-# Source Code repository section
-repositoryUrl = "https://github.com/apache/comdev-site"
-repositorySourceBranch = "main"
-
-# Open Graph section
-title = "Apache Community Development"
-description = "The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health."
-images = ["images/aceu19_1.jpg", "images/aceu19_2.jpg"] # Open graph images are placed in `static/images`
-tags = ["OpenSource", "Community", "Apache Software Foundation"]
-
-[social]
-twitter = "ApacheCommunity"
diff --git a/index.html b/index.html
new file mode 100644
index 0000000..d248144
--- /dev/null
+++ b/index.html
@@ -0,0 +1 @@
+Temporary index.html to prepare this branch
\ No newline at end of file
diff --git a/layouts/_default/_markup/render-heading.html b/layouts/_default/_markup/render-heading.html
deleted file mode 100644
index 485bb88..0000000
--- a/layouts/_default/_markup/render-heading.html
+++ /dev/null
@@ -1,5 +0,0 @@
-<h{{ .Level }}{{- range $k, $v := .Attributes -}}{{- printf " %s=%q" $k $v | safeHTMLAttr -}}{{- end }}>{{- .Text | safeHTML -}}
-{{- if and (ge .Level 1) (le .Level 4) }}{{" " -}}
-<a class="headerlink" title="Permalink" href="#{{ .Anchor | safeURL }}">¶</a>
-{{- end -}}
-</h{{ .Level }}>
diff --git a/layouts/_default/baseof.html b/layouts/_default/baseof.html
deleted file mode 100644
index 7d5f5ea..0000000
--- a/layouts/_default/baseof.html
+++ /dev/null
@@ -1,196 +0,0 @@
-<!DOCTYPE html>
-<!--
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
-
- https://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-
-<html lang="en">
-<head>
- <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" />
- {{ template "_internal/opengraph.html" . }}
-
- <title>Apache Community Development - {{ .Title }}</title>
- <link rel="shortcut icon" href="images/favicon.ico">
-
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
- <link href="/css/main.css" rel="stylesheet" media="screen">
- <link href="/css/bootstrap.min.css" rel="stylesheet" media="screen">
- <style type="text/css">
- .footer {
- text-align:center;
- color:grey;
- font-size:80%;
- border-top: solid #ddd 1px;
- margin-top:1em;
- }
- .navbar-brand img {
- height: 50px;
- }
- </style>
-
- {{ partial "matomo.html" . }}
-</head>
-
-<body>
- <header class="navbar navbar-expand-lg navbar-dark bg-dark fixed-top">
- <div class="container">
- <a class="navbar-brand" href="/">
- <img src="https://svn.apache.org/repos/asf/comdev/project-logos/originals/foundation.svg" alt="Apache Software Foundation">
- </a>
- <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#mainNavbar" aria-controls="mainNavbar" aria-expanded="false" aria-label="Toggle navigation">
- <span class="navbar-toggler-icon"></span>
- </button>
-
- <div class="collapse navbar-collapse" id="mainNavbar">
- <div class="container"> <!-- this one is required to center Nav -->
- <ul class="navbar-nav mr-auto">
- <li class="nav-item"><a class="nav-link" href="/">Home</a></li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="aboutDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- About
- </a>
- <div class="dropdown-menu" aria-labelledby="aboutDropdown">
- <a class="dropdown-item" href="/about/">What We Do</a>
- <a class="dropdown-item" href="/newbiefaq.html">Frequently Asked Questions</a>
- <a class="dropdown-item" href="/projectIndependence.html">Apache Project Independence</a>
- <a class="dropdown-item" href="/apache-way/apache-project-maturity-model.html">Apache Project Maturity Model</a>
- <a class="dropdown-item" href="/contactpoints.html">Contact Points Within the ASF</a>
- <a class="dropdown-item" href="https://whimsy.apache.org/board/minutes/Community_Development.html#2009-11-01">ComDev Original Board Resolution</a>
- <a class="dropdown-item" href="https://whimsy.apache.org/board/minutes/Community_Development.html">ComDev Board Reports</a>
- <a class="dropdown-item" href="https://issues.apache.org/jira/projects/COMDEV">Community Development Jira</a>
- <a class="dropdown-item" href="https://issues.apache.org/jira/projects/GSOC">GSoC Jira</a>
- <div class="dropdown-divider"></div>
- <a class="dropdown-item text-uppercase disabled" href="#">About Apache</a>
- <a class="dropdown-item" href="https://www.apache.org/">The Apache Software Foundation</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship">Sponsor Apache</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/thanks">Thanks to our Sponsors</a>
- <a class="dropdown-item" href="https://www.apache.org/licenses">License</a>
- <a class="dropdown-item" href="https://www.apache.org/security">Security</a>
- </div>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="contribDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- For Contributors
- </a>
- <div class="dropdown-menu" aria-labelledby="contribDropdown">
- <a class="dropdown-item" href="/newcomers/">Newcomers</a>
- <a class="dropdown-item" href="/gettingStarted/101.html">Getting Started</a>
- <a class="dropdown-item" href="/contributors/">Finding Your Way Around The Apache Software Foundation</a>
- <a class="dropdown-item" href="https://www.apache.org/dev/">Technical Developer FAQs</a>
- <div class="dropdown-divider"></div>
- <a class="dropdown-item text-uppercase disabled" href="#">Google Summer of Code</a>
- <a class="dropdown-item" href="/gsoc/">Google Summer Of Code Information</a>
- <a class="dropdown-item" href="/gsoc/mentee-ranking-process.html">Mentee Ranking Process</a>
- <a class="dropdown-item" href="/gsoc/experiences.html">Past GSoC Experiences</a>
- <a class="dropdown-item" href="/gsoc/guide-to-being-a-mentor.html">Guide to being a Mentor</a>
- <a class="dropdown-item" href="/gsoc/use-the-comdev-issue-tracker-for-gsoc-tasks.html">Using ComDev's Jira for GSoC Ideas</a>
- <a class="dropdown-item" href="/gsoc/gsoc-admin-tasks.html">Tasks of a GSoC Admin at the ASF</a>
- </div>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="commitDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- For Committers/PMCs
- </a>
- <div class="dropdown-menu" aria-labelledby="commitDropdown">
- <a class="dropdown-item" href="/newcommitter.html">Recruiting New Committers</a>
- <a class="dropdown-item" href="/committers/">Useful Information for Committers</a>
- <a class="dropdown-item" href="/committers/consensusBuilding.html">Consensus Building</a>
- <a class="dropdown-item" href="/committers/lazyConsensus.html">Lazy Consensus</a>
- <a class="dropdown-item" href="/committers/decisionMaking.html">Decision Making</a>
- <a class="dropdown-item" href="/committers/voting.html">Voting</a>
- <a class="dropdown-item" href="/committers/funding-disclaimer.html">Funding Campaign Disclaimer</a>
- </div>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="eventDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Events
- </a>
- <div class="dropdown-menu" aria-labelledby="eventDropdown">
- <a class="dropdown-item" href="https://apachecon.com/">Community Over Code - (formerly ApacheCon)</a>
- <a class="dropdown-item" href="https://events.apache.org/">Other Apache-related Events</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/marks/events">Apache event branding policies</a>
- <div class="dropdown-divider"></div>
- <a class="dropdown-item text-uppercase disabled" href="#">Conference Speakers</a>
- <a class="dropdown-item" href="/speakers/slides.html">Sample presentations</a>
- </div>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="conversDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Join the Conversation
- </a>
- <div class="dropdown-menu" aria-labelledby="conversDropdown">
- <a class="dropdown-item" href="/blog/">Blog</a>
- <a class="dropdown-item" href="https://www.facebook.com/ApacheSoftwareFoundation">Facebook</a>
- <a class="dropdown-item" href="https://twitter.com/ApacheCommunity">Twitter</a>
- <a class="dropdown-item" href="/lists.html">Mailing List</a>
- </div>
- </li>
- </ul>
- </div>
- </div><!--/.navbar-collapse -->
- </div><!--container div-->
- </header>
-
- <main class="cd-main" id="content" role="main">
- <div class="container">
- <section id="content" class="row">
- <div class="col-md-9">
- <h3 class="mt-3 text-muted">The Apache Software Foundation</h3>
- </div>
- <div class="col-md-12"><h4 class="text-muted">Community > Code</h4></div>
- </section>
- {{ partial "breadcrumbs.html" . }}
- <hr>
- {{ block "main" . }}{{ end }}
- </div>
- </main>
-
- <footer class="page-footer bg-secondary mt-4 pt-3">
- <div class="container text-center text-md-left mb-3">
- <div class="row">
- <div class="col-md-6 mt-md-0 mt-3">
- <h5 class="text-uppercase">Trademarks</h5>
- <p>
- Apache®, the names of Apache projects, and the multicolor feather logo are
- <a href="https://www.apache.org/foundation/marks/list/">registered trademarks or trademarks</a> of the Apache
- Software Foundation in the United States and/or other countries.
- </p>
- </div>
-
- <hr class="clearfix w-100 d-md-none pb-3">
-
- <div class="col-md-6 mb-md-0 mb-3">
- <h5 class="text-uppercase">Website sources</h5>
-
- <p>
- This website is generated from the <a href="https://github.com/apache/comdev-site">comdev-site repository</a>.<br>
- Patches are welcome!
- </p>
- </div>
- </div>
- </div>
-
- <div class="footer-copyright text-center py-3">
- <em>Copyright © {{ now.Year }}, <a href="https://www.apache.org/">the Apache Software Foundation</a>. Licensed under the
- <a rel="license" href="https://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a></em>
- </div>
- </footer>
-
- <script src="/js/jquery.min.js"></script>
- <script src="/js/bootstrap.min.js"></script>
-</body>
-</html>
diff --git a/layouts/_default/list.html b/layouts/_default/list.html
deleted file mode 100644
index 5e47456..0000000
--- a/layouts/_default/list.html
+++ /dev/null
@@ -1,9 +0,0 @@
-{{ define "main" }}
- {{ .Content }}
- {{ if .Params.list_pages }}
- <ul class="child-pages">
- {{ range .Paginator.Pages.ByWeight }} {{ partial "page-summary" . }} {{ end }}
- <section>{{ partial "pagination" .}}</section>
- </ul>
- {{ end }}
-{{ end }}
diff --git a/layouts/_default/single.html b/layouts/_default/single.html
deleted file mode 100644
index 78f64cf..0000000
--- a/layouts/_default/single.html
+++ /dev/null
@@ -1,7 +0,0 @@
-{{ define "main" }}
- {{ if .Params.blog_post }}
- <h2>{{ .Title }}</h2>
- {{ partial "published-date" .}}
- {{ end }}
- {{ .Content }}
-{{ end }}
diff --git a/layouts/partials/breadcrumbs.html b/layouts/partials/breadcrumbs.html
deleted file mode 100644
index f94b6e6..0000000
--- a/layouts/partials/breadcrumbs.html
+++ /dev/null
@@ -1,15 +0,0 @@
-{{ $url := replace .Permalink ( printf "%s" .Site.BaseURL) "" }}
-{{ $.Scratch.Set "path" "/" }}
-<nav aria-label="breadcrumb">
- <ol class="breadcrumb">
- <li class="breadcrumb-item"><a href="/">Home</a></li>
- {{ range $index, $element := split $url "/" }}
- {{ $.Scratch.Add "path" $element }}
- {{ if ne $element "" }}
- <li class="breadcrumb-item"><a href='{{ $.Scratch.Get "path" }}'>{{ humanize . | replaceRE "\\.[hH]tml$" "" }}</a></li>
- {{ $.Scratch.Add "path" "/" }}
- {{ end }}
- {{ end }}
- </ol>
-</nav>
-
diff --git a/layouts/partials/matomo.html b/layouts/partials/matomo.html
deleted file mode 100644
index c2479be..0000000
--- a/layouts/partials/matomo.html
+++ /dev/null
@@ -1,17 +0,0 @@
-<!-- Matomo -->
-<script>
- var _paq = window._paq = window._paq || [];
- /* We explicitly disable cookie tracking to avoid privacy issues */
- _paq.push(['disableCookies']);
- /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
- _paq.push(['trackPageView']);
- _paq.push(['enableLinkTracking']);
- (function() {
- var u="https://analytics.apache.org/";
- _paq.push(['setTrackerUrl', u+'matomo.php']);
- _paq.push(['setSiteId', '36']);
- var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
- g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
- })();
-</script>
-<!-- End Matomo Code -->
diff --git a/layouts/partials/page-summary.html b/layouts/partials/page-summary.html
deleted file mode 100644
index a49ed07..0000000
--- a/layouts/partials/page-summary.html
+++ /dev/null
@@ -1,9 +0,0 @@
-<li class="page-summary" itemscope itemtype="http://schema.org/CreativeWork">
- <h2 class="title">
- <a href="{{ .Permalink }}" itemprop="headline">{{ .Title }}</a>
- <p>{{ partial "published-date" .}}</p>
- </h2>
- {{ if .Description }}
- <p class="summary" itemprop="about">{{ .Description }}</p>
- {{ end }}
-</li>
diff --git a/layouts/partials/pagination.html b/layouts/partials/pagination.html
deleted file mode 100644
index 95353e5..0000000
--- a/layouts/partials/pagination.html
+++ /dev/null
@@ -1,15 +0,0 @@
-<nav class="pagination pager align-center">
- <hr>
- <ul>
- {{if .Paginator.HasPrev }}
- <li class="prev"><a href="{{ .Paginator.Prev.URL }}">Previous</a></li>
- {{ end }}
- <li>
-
- <a href="" class="button round small outline">Page {{ .Paginator.PageNumber }} of {{ .Paginator.TotalPages }}</a>
- </li>
- {{ if .Paginator.HasNext }}</a>
- <li class="next"><a href="{{ .Paginator.Next.URL }}">Next</a></li>
- {{ end }}
- </ul>
-</nav>
\ No newline at end of file
diff --git a/layouts/partials/published-date.html b/layouts/partials/published-date.html
deleted file mode 100644
index 084dd32..0000000
--- a/layouts/partials/published-date.html
+++ /dev/null
@@ -1 +0,0 @@
-<span class="published-date">{{ time.Format "Monday, Jan 2, 2006" .Date }}</span>
\ No newline at end of file
diff --git a/layouts/robots.txt b/layouts/robots.txt
deleted file mode 100644
index 1ce9645..0000000
--- a/layouts/robots.txt
+++ /dev/null
@@ -1,6 +0,0 @@
-User-agent: *
-
-Disallow: /404/
-Disallow: 404.html
-
-SITEMAP: {{ "sitemap.xml" | absLangURL }}
diff --git a/layouts/shortcodes/toc.html b/layouts/shortcodes/toc.html
deleted file mode 100644
index aca3785..0000000
--- a/layouts/shortcodes/toc.html
+++ /dev/null
@@ -1 +0,0 @@
-{{ .Page.TableOfContents }}
\ No newline at end of file
diff --git a/source/_index.md b/source/_index.md
deleted file mode 100644
index 4c8924d..0000000
--- a/source/_index.md
+++ /dev/null
@@ -1,149 +0,0 @@
----
-title: Apache Community Development - Welcome
----
-
-<link href="/_pagefind/pagefind-ui.css" rel="stylesheet">
-<script src="/_pagefind/pagefind-ui.js" type="text/javascript"></script>
-<div id="search"></div>
-<script>
- window.addEventListener('DOMContentLoaded', (event) => {
- new PagefindUI({ element: "#search" });
- });
-</script>
-
-<div class="jumbotron">
-<a href="https://www.apache.org/events/current-event.html"><img src="https://www.apache.org/events/current-event-125x125.png" style="float: right;"/></a>
-
-## Apache Community Development!
-
-Mission: The Community Development project creates and provides tools,
-processes, and advice to help open-source projects improve their own
-community health. We are primarily focused on Apache Software Foundation (ASF)
-projects; however, because we believe that the Apache Way is the
-best way to manage a software project, we strive also to make these
-artifacts releasable to the open-source community as a whole.
-
-Here, we focus on the common processes and policies
-(called The Apache Way) found in most ASF projects. Our goal is to help you
-<em>understand how the ASF works</em> and give you the confidence to participate
-in the specific Apache projects that interest you.
-
-</div>
-
-<h1>BEST PRACTICES DOCS STAGING</h1>
-
-<a name="Index-Startingpoints"></a>
-
-
-<!-- Row 1 -->
-<div class="row">
- <div class="col-md-4">
-
-#### Newcomers to the ASF
-
-If you are new to open source, our <a href="newcomers/index.html"><b>newcomers section</b></a> explains basic concepts, first steps to get started, and where to ask for help.
-
-To get our software, see our <a href="https://projects.apache.org/projects.html?category" target="_blank">categorized listing of all Apache projects</a>, which are <a href="https://www.apache.org/free/"><b>always free</b> to download and use</a>.
-
-The ASF is a large organization made up of many separate projects. Each project community may have its own ways of working, while still following the basic Apache Way process.
-
- </div>
- <div class="col-md-4">
-
-#### Events
-
-Producers should read our <a href="https://www.apache.org/foundation/marks/events">Event Branding Policy</a> for ticketed events, and we have some <a href="events/small-events.html">tips for organizing small community events</a> about Apache projects.
-
-The <a href="https://events.apache.org/event/calendar.html">event calendar</a> lists approved Apache-related events, including Community Over Code (formerly ApacheCon) and project summits.
-
- </div>
- <div class="col-md-4">
-
-#### The Foundation
-
-The Apache Software Foundation (ASF) is a <a href="https://www.apache.org/foundation/">US 501(c)3 non-profit public charity</a>. The Foundation is <a href="https://www.apache.org/foundation/governance/">governed by a Board of Directors</a>, elected by our Membership, and we publish our <a href="https://www.apache.org/foundation/board/calendar.html">monthly board meeting minutes</a>.
-
-Our mission is to create software for the public good that we <a href="https://www.apache.org/free/">give away for free</a>. You can read how <a href="https://www.apache.org/foundation/governance/" target="_blank">ASF and Apache projects are governed</a>. We <a href="https://www.apache.org/foundation/contributing.html" target="_blank">welcome your support of Apache</a>.
-
- </div>
-</div>
-
-<!-- Row 2 -->
-<div class="row">
- <div class="col-md-4">
-
-#### Open Source Contributors
-
-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.
-
-We also have a collection of <a href="links.html">links</a> to relevant information.
-
-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>.
-
- </div>
- <div class="col-md-4">
-
-#### How Apache works
-
-Our <a href="apache-way/apache-project-maturity-model.html">Apache Project Maturity Model</a> defines a structure for evaluating our projects (communities & technology) that can serve as an example for other communities.
-
-Our <a href="https://www.apache.org/foundation/how-it-works.html" target="_blank">how Apache works</a> guide describes key ASF
-concepts, such as the difference between ASF Members and project committers, how decisions are made (voting), how elections take place,
-and the ASF's structure and organization.
-
- </div>
- <div class="col-md-4">
-
-#### FAQ & Code of Conduct
-
-Please be nice! The ASF has a <a href="https://www.apache.org/foundation/policies/conduct">Code of Conduct</a> that we expect participants to abide by.
-
-If you still haven't found what you are looking for, try our <a href="newbiefaq.html">FAQ</a>, send us an e-mail at <code>dev@community.apache.org</code>, or read the <a href="https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:" target="_blank">Community mail archives</a>.
-
-</div>
-
-<!-- Row 3 -->
-<div class="row">
- <div class="col-md-4">
-
-#### Diversity and Inclusion
-
-The <a href="http://diversity.apache.org/">Apache Diversity</a> website has more information
-on that project, dedicated to understanding and promoting diversity and inclusion in ASF communities.
-
- </div>
- <div class="col-md-4">
-
-#### Google Summer of Code program (GSoC)
-
-The Community Development project also manages the <a href="/gsoc/">ASF's participation in the Google Summer of Code program</a>. Each year since 2005, we've taken on between 30 and 45 students. Many have gone on to become long-term committers to projects, and even Members of the Foundation.
-
-Read about a few of our <a href="/gsoc/experiences.html">GSoC successes</a>.
-
- </div>
- <div class="col-md-4">
-
-#### Apache Local Community (ALC)
-
-The <a href="https://s.apache.org/alc">Apache Local Community</a> comprises local groups of Apache (Open Source) enthusiasts, called an 'ALC Chapter'. There will be a single ALC chapter per town/city.
-
-The ALC Chapters spread awareness of the ASF in local communities, hosting local events to share information about the ASF, The Apache Way, and various Apache projects by bringing together project users and developers.
-
- </div>
-</div>
-
-<div>
-
-#### How to ask questions
-
-All Apache projects use <a href="https://lists.apache.org/">publicly-archived mailing lists</a> that anyone may subscribe
-to. There you can ask questions related to that specific project and gain a sense of its current activities and focus. Most projects have a
-<code>dev@project.apache.org</code> mailing list for technical discussions about the code, and a
-<code>user@</code> or <code>users@</code> mailing list for questions about the product or features.
-
-We have a <a href="/contributors/etiquette">Code of Conduct and Etiquette guidelines</a> to help you write good emails.
-
-The ComDev project has our own mailing list where you can ask general questions
-about Apache at <a href="https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:">dev@community.apache.org</a>.
-
-</div>
diff --git a/source/about/_index.md b/source/about/_index.md
deleted file mode 100755
index 42fc175..0000000
--- a/source/about/_index.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: "Community Development: What we do"
-url: /about/
----
-
-## Community Development: What We Do
-
-The Community Development (ComDev) project
-provides a wide array of information, [FAQs](/newbiefaq.html), and help to newcomers and existing committers, and maintains a number of [helpful tools](#getcode).
-
-{{% toc %}}
-
-### Mentoring for Individuals and Help Getting Around
-- [GSoC](/gsoc/)
-- [Contributors Guide](/newcomers/)
-- [Committers Guide](/committers)
-- Project Management Committees
-
-### Mentoring for Projects
-- [Incubator Mentors](https://incubator.apache.org/guides/mentor.html) - Many folks here are IPMC members or mentors, too
-- Get community advice on dev@community
-
-### Education + Outreach
-- [ApacheCon](https://apachecon.com/)
-- Partnered Industry Events (FOSDEM etc.)
-- MeetUps, Apache BarCamps, etc.
-- Event Representatives (booth coverage, etc.)
-- [Sample Presentations](/speakers/slides.html)
-
-### Diversity
-- [Code of Conduct](https://www.apache.org/foundation/policies/conduct.html)
-- Surveys
-
-### Conference Travel Assistance
-- [TAC - Travel Assistance Committee](https://www.apache.org/travel)
-
-### Tools and Code we Maintain ### {#getcode}
-
-ComDev manages a number of helpful tools for finding your way around.
-
- - The [Apache Projects Directory](https://projects.apache.org/) lists all our software projects. [See the Project Directory **code**](https://projects.apache.org/about.html) and the JSON data feeds available.
- - [Apache Committers Phone Book](https://home.apache.org/) lists all individual Apache committers. [See the Phonebook **code**](https://home.apache.org/phonebook-about.html).
- - The [Project Reporting Tool](https://reporter.apache.org/) (requires login) helps Apache PMCs create quarterly board reports. [See the Reporter **code**](https://svn.apache.org/repos/asf/comdev/projects.apache.org/).
- - The [ComDev Wiki](https://cwiki.apache.org/confluence/display/COMDEV/ComDev+Wiki) is also available for scratch or experimental work, although most permanent content should be here in the website.
-
-The ComDev PMC maintains these tools, so bring questions to our [dev@](https://lists.apache.org/list.html?dev@community.apache.org) list.
-
-### Physical artifacts
-
-* Stickers: Request project stickers for your event, depending on geography
-* Assistance with producing [swag for your project](https://www.redbubble.com/people/comdev/shop)
-
-## About This Website
-
-The [Apache Community Development PMC](/) maintains this `community.apache.org` website and works through the
-dev@community.apache.org [archived mailing list](/lists.html).
-
-See our [Newcomer FAQ](/newbiefaq.html#websitecms) for how to suggest changes to this website.
-
-The content is written in Markdown and published automatically via a Jenkins job.
-Source code is hosted in a [Git repository](https://github.com/apache/comdev-site).
-
-See the [README.md](https://github.com/apache/comdev-site/blob/main/README.md) for more info.
diff --git a/source/apache-way/apache-project-maturity-model.md b/source/apache-way/apache-project-maturity-model.md
deleted file mode 100755
index c8e76e6..0000000
--- a/source/apache-way/apache-project-maturity-model.md
+++ /dev/null
@@ -1,395 +0,0 @@
----
-title: A Maturity Model for Apache Projects
----
-
-The **Apache Project Maturity Model** provides a suggested framework for evaluating the overall maturity of an Apache project community and the codebase that it maintains. While this model is specific to projects of the Apache Software Foundation (ASF), many of these factors apply to any open source project.
-
-# Overview
-
-The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.
-
-It is usable outside of the ASF as well, for projects that might want to adopt some or all of these principles. Projects that envision moving to the ASF at some point might start working towards this to prepare for their move.
-
-It does not describe all the details of how our projects operate, but aims to capture the invariants of Apache projects and point to additional information where needed. To be as concise as possible we use footnotes for anything that's not part of the core model.
-
-Contrary to other maturity models, we do not define staged partial compliance levels. A mature Apache project complies with all the elements of this model, and other projects are welcome to adopt the elements that suit their goals.
-
-Note that we try to avoid using the word "must" below. The model describes the state of a mature project, as opposed to a set of rules.
-
-Projects which incubate at the ASF might not fit into all the parts of this model; however a major goal of incubation is to bring the project's community closer to it.
-
-We welcome questions and feedback about this model on the <a href="https://lists.apache.org/list.html?dev@community.apache.org" target="_blank">comdev mailing list</a>.
-
-# The Apache Project Maturity Model
-
-Each item in the model has a unique ID to allow it to be easily referenced elsewhere.
-
-## Code
-
-<dl>
-<dt id="CD10">CD10</dt>
-<dd>
-The project produces Open Source software for distribution to the public, at no charge.
-<sup><a href="#fnref-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872" id="fndef-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872-0">1</a></sup>
-</dd>
-
-<dt id="CD20">CD20</dt>
-<dd>
-Anyone can easily discover and access the project's code.
-</dd>
-
-<dt id="CD30">CD30</dt>
-<dd>
-Anyone using standard, widely-available tools, can build the code in a reproducible way.
-</dd>
-
-<dt id="CD40">CD40</dt>
-<dd>
-The full history of the project's code is available via a source code
-control system, in a way that allows anyone to recreate any released version.
-</dd>
-
-<dt id="CD50">CD50</dt>
-<dd>
-The source code control system establishes the provenance of each line of code in a reliable way, based on strong authentication of the
-committer. When third parties contribute code, commit messages provide reliable information about the code provenance.
-<sup><a href="#fnref-1a581282a720702d3a9e11f81f8c9eeddbee55a9" id="fndef-1a581282a720702d3a9e11f81f8c9eeddbee55a9-1">2</a></sup>
-</dd>
-
-</dl>
-
-## Licenses and Copyright
-
-<dl>
-<dt id="LC10">LC10</dt>
-<dd>The Apache License, version 2.0, covers the released code.
-</dd>
-
-<dt id="LC20">LC20</dt>
-<dd>
-Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does.
-<sup><a href="#fnref-76d333d056757395d9b6eb1d62e91a57dad757fa" id="fndef-76d333d056757395d9b6eb1d62e91a57dad757fa-2">3</a></sup>
-<sup><a href="#fnref-3e4d977daeeb59a808fb0c40477b2cd50e913f2e" id="fndef-3e4d977daeeb59a808fb0c40477b2cd50e913f2e-3">4</a></sup>
-</dd>
-
-<dt id="LC30">LC30</dt>
-<dd>
-The libraries mentioned in LC20 are available as Open Source software.
-</dd>
-
-<dt id="LC40">LC40</dt>
-<dd>Committers are bound by an Individual Contributor Agreement (the <a href="https://www.apache.org/licenses/icla.txt">"Apache iCLA"</a>) that
-defines which code they may commit and how they need to
-identify code that is not their own.
-</dd>
-
-<dt id="LC50">LC50</dt>
-<dd>
-The project clearly defines and documents the copyright ownership of everything that the project produces.
-<sup><a href="#fnref-258df7a61c975c67bbef17d3cf7851bafd40b8fb" id="fndef-258df7a61c975c67bbef17d3cf7851bafd40b8fb-4">5</a></sup>
-</dd>
-
-</dl>
-
-## Releases
-<dl>
-
-<dt id="RE10">RE10</dt>
-<dd>Releases consist of source code, distributed using standard and open archive
-formats that are expected to stay readable in the long term.
-<sup><a href="#fnref-d2389850862fcc9bddabb3c2e23b13922d68e3fc" id="fndef-d2389850862fcc9bddabb3c2e23b13922d68e3fc-5">6</a></sup>
-</dd>
-
-<dt id="RE20">RE20</dt>
-<dd>
-The project's PMC (Project Management Committee, see CS10) approves each software release in order to make the release an act of the Foundation.
-</dd>
-
-<dt id="RE30">RE30</dt>
-<dd>
-Releases are signed and/or distributed along with digests that anyone can reliably use to validate the downloaded archives.
-</dd>
-
-<dt id="RE40">RE40</dt>
-<dd>The project can distribute convenience binaries alongside source code, but they are not Apache Releases, they are provided with no guarantee.
-</dd>
-
-<dt id="RE50">RE50</dt>
-<dd>The project documents a repeatable release process so that
-someone new to the project can independently generate the complete
-set of artifacts required for a release.
-</dd>
-
-</dl>
-
-
-## Quality
-<dl>
-
-<dt id="QU10">QU10</dt>
-<dd>The
-project is open and honest about the quality of its code. Various levels
- of quality and maturity for various modules are natural and acceptable
-as long as they are clearly communicated.
-</dd>
-
-<dt id="QU20">QU20</dt>
-<dd>
-The project puts a very high priority on producing secure software.
-<sup><a href="#fnref-89a5257606b929cc5ced2bee207c80b43541d488" id="fndef-89a5257606b929cc5ced2bee207c80b43541d488-6">7</a></sup>
-</dd>
-
-<dt id="QU30">QU30</dt>
-<dd>
-The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them.
-<sup><a href="#fnref-7c23a24b04dcf9b4b10423685fbd37f69b2b3783" id="fndef-7c23a24b04dcf9b4b10423685fbd37f69b2b3783-7">8</a></sup>
-</dd>
-
-<dt id="QU40">QU40</dt>
-<dd>The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features.
- </dd>
-
- <dt id="QU50">QU50</dt>
- <dd>
- The project strives to respond to documented bug reports in a timely manner.
- </dd>
- </dl>
-
-## Community
-
-<dl>
-
-<dt id="CO10">CO10</dt>
-<dd>
-The project has a well-known homepage that points to all the information required to operate according to this maturity model.
-</dd>
-
-<dt id="CO20">CO20</dt>
-<dd>
-The community welcomes contributions from anyone who acts in good faith and
- in a respectful manner, and who adds value to the project.
-</dd>
-
-<dt id="CO30">CO30</dt>
-<dd>
-Contributions include source code, documentation, constructive bug
-reports, constructive discussions, marketing and generally anything that adds value to the project.
-</dd>
-
-<dt id="CO40">CO40</dt>
-<dd>
-The community strives to be meritocratic and gives more rights and
-responsibilities to contributors who, over time, add value to the project.
-</dd>
-
-<dt id="CO50">CO50</dt>
-<dd>
-The project documents how contributors can earn more rights such as commit
-access or decision power, and applies these principles consistently.
-</dd>
-
-<dt id="CO60">CO60</dt>
-<dd>
-The community operates based on consensus of its members (see CS10) who
-have decision power. Dictators, benevolent or not, are not welcome in
-Apache projects.
-</dd>
-
-<dt id="CO70">CO70</dt>
-<dd>
-The project strives to answer user questions in a timely manner.
-</dd>
-
-</dl>
-
-## Consensus Building
-<dt id="CS10">CS10</dt>
-<dd>The
-project maintains a public list of its contributors who have decision
-power. The project's PMC (Project Management Committee) consists of
-those contributors.
-</dd>
-
-<dt id="CS20">CS20</dt>
-<dd>
-Decisions require a consensus among PMC members
-<sup><a href="#fnref-08fda1a3461c11086b8542178f35e0c27a4a46c3" id="fndef-08fda1a3461c11086b8542178f35e0c27a4a46c3-8">9</a></sup>
- and are documented on the project's main communications channel.
-The PMC takes community opinions into account, but the PMC has the final word.
- </dd>
-
- <dt id="CS30">CS30</dt>
- <dd>
- The project uses documented voting rules to build consensus when discussion is not sufficient.
- <sup><a href="#fnref-9b0cf71f04bcd81dddbf6199f1c771e27566611e" id="fndef-9b0cf71f04bcd81dddbf6199f1c771e27566611e-9">10</a></sup>
- </dd>
-
- <dt id="CS40">CS40</dt>
- <dd>In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules
-defined in CS30.
-</dd>
-
-<dt id="CS50">CS50</dt>
-<dd>
-All "important" discussions happen asynchronously in written form on the
-project's main communications channel. Offline, face-to-face or private discussions
-<sup><a href="#fnref-d9e7a517f046358463f038f3830fef171e69f78b" id="fndef-d9e7a517f046358463f038f3830fef171e69f78b-10">11</a></sup>
-that affect the project are also documented on that channel.
-</dd>
-
-</dl>
-
-## Independence
-
-<dl>
-
-<dt id="IN10">IN10</dt>
-<dd>
-The project is independent from any corporate or organizational influence.
-<sup><a href="#fnref-764b2c2fd32deb4ff73ea01efa67c8556303c359" id="fndef-764b2c2fd32deb4ff73ea01efa67c8556303c359-11">12</a></sup>
-</dd>
-
-<dt id="IN20">IN20</dt>
-<dd>Contributors act as themselves, not as representatives of a corporation or organization.
-</dd>
-
-</dl>
-
-# How To Use The Apache Project Maturity Model
-
-**Remember:** This model is a guide; it is not a requirements document. The model shows what generally good behaviors in an Apache project look like.
-
-So far, inside the ASF, podlings preparing their graduation
-from the [Apache Incubator](https://incubator.apache.org) have used this model, mostly for self-assessment.
-
-It might be useful for top-level ASF projects to regularly assess their maturity based on this model, but this is not a requirement at this time.
-
-Here are a few self-assessment examples:
-
-* [Apache Groovy podling self-assessment, 2015](https://github.com/apache/groovy/blob/576b3c5d6a7022ac4a8df1ef118666456ce627fb/MATURITY.adoc)
-* [Apache Taverna Graduation Maturity Assessment, 2016](https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+Taverna+Graduation+Maturity+Assessment)
-* [Apache CarbonData Podling Maturity Assessment, 2017](https://cwiki.apache.org/confluence/display/CARBONDATA/Apache+Maturity+Model+Assessment+for+CarbonData)
-* [Apache ServiceComb Maturity Model Assessment, 2018](https://cwiki.apache.org/confluence/display/SERVICECOMB/Apache+Maturity+Model+Assessment+for+ServiceComb)
-
-## Other Open Source Project Models
-
-See [https://s.apache.org/apache_maturity_model](https://s.apache.org/apache_maturity_model) for the discussions that led to this document. Thanks to the many people who provided input! The links below are both inspirations for our model, and are some of the other ways that FOSS project participants have tried to quantify ways to measure open source projects.
-
-* [http://oss-watch.ac.uk/resources/ssmm](http://oss-watch.ac.uk/resources/ssmm)
-* [https://osswatch.jiscinvolve.org/wp/2014/12/11/open-or-fauxpen-use-the-oss-watch-openness-rating-tool-to-find-out/](https://osswatch.jiscinvolve.org/wp/2014/12/11/open-or-fauxpen-use-the-oss-watch-openness-rating-tool-to-find-out/)
-* [https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different](https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different)
-* [https://rfc.zeromq.org/spec:16](https://rfc.zeromq.org/spec:16)
-* [http://oss-watch.ac.uk/resources/reusereadinessrating](http://oss-watch.ac.uk/resources/reusereadinessrating)
-* [https://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration](https://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration)
-* [https://www.apache.org/dev/project-requirements](https://www.apache.org/dev/project-requirements)
-
-## Status / Document Version
-
-v 1.0, February 2015, defined by consensus by Apache Community Development project.
-
-v 1.1, October 2016 added RE50.
-
-v 1.2, February 2018, reworked the "how to use" section with more links to self-assessments.
-
-v 1.3, June 2021, improve readability and simplify the language where possible.
-
-See the <a href="https://svn.apache.org/viewvc/comdev/site/trunk/content/apache-way/apache-project-maturity-model.mdtext?view=log" target="_blank">svn revision history</a> (for older
-versions) and <a href="https://github.com/apache/comdev-site/commits/main/source/apache-way/apache-project-maturity-model.md">GitHub history</a> (since March 2020) of this document for more details and other minor changes.
-
-### Footnotes
-
-<ol>
-
-<li>
-<a id="fnref-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872"></a>
-"For distribution to the public at no charge" is straight from the from the ASF Bylaws at <a class="http" href="https://apache.org/foundation/bylaws.html" target="_blank">https://apache.org/foundation/bylaws.html</a>.
-
-(<a href="#fndef-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872-0">1</a>)
-</li>
-
-<li>
-<a id="fndef-1a581282a720702d3a9e11f81f8c9eeddbee55a9-1"></a>
-See also LC40.
-
-(<a href="#fndef-1a581282a720702d3a9e11f81f8c9eeddbee55a9-1">2</a>)
-</li>
-
-<li>
-<a id="fnref-76d333d056757395d9b6eb1d62e91a57dad757fa"></a>
-It's ok for platforms (like a runtime used to execute our code) to have different licenses as long as they don't impose reciprocal licensing on
-what we are distributing.
-
-(<a href="#fndef-76d333d056757395d9b6eb1d62e91a57dad757fa-2">3</a>)
-</li>
-
-<li>
-<a id="fnref-3e4d977daeeb59a808fb0c40477b2cd50e913f2e"></a>
-<a class="http" href="https://apache.org/legal/resolved.html">https://apache.org/legal/resolved.html</a> has information about acceptable licenses for third-party dependencies.
-
-(<a href="#fndef-3e4d977daeeb59a808fb0c40477b2cd50e913f2e-3">4</a>)
-</li>
-
-<li>
-<a id="fnref-258df7a61c975c67bbef17d3cf7851bafd40b8fb"></a>
-In Apache projects, the ASF owns the copyright for the collective work,
-i.e. the project's releases. Contributors retain copyright on their
-contributions but grant the ASF a perpetual copyright license for them.
-
-(<a href="#fndef-258df7a61c975c67bbef17d3cf7851bafd40b8fb-4">5</a>)
-</li>
-
- <li>
- <a id="fnref-d2389850862fcc9bddabb3c2e23b13922d68e3fc"></a>
- See <a class="http" href="https://www.apache.org/legal/release-policy.html">https://www.apache.org/legal/release-policy.html</a> for more info on Apache releases.
-
- (<a href="#fndef-d2389850862fcc9bddabb3c2e23b13922d68e3fc-5">6</a>)
- </li>
-
- <li>
- <a id="fnref-89a5257606b929cc5ced2bee207c80b43541d488"></a>
- The required level of security depends on the software's intended uses, of course. Projects should clearly document security expectations.
-
- (<a href="#fndef-89a5257606b929cc5ced2bee207c80b43541d488-6">7</a>)
- </li>
-
- <li>
- <a id="fnref-7c23a24b04dcf9b4b10423685fbd37f69b2b3783"></a>
- Apache projects can just point to <a class="http" href="https://www.apache.org/security/">https://www.apache.org/security/</a> or use their own security contacts page, which should also point to that.
-
- (<a href="#fndef-7c23a24b04dcf9b4b10423685fbd37f69b2b3783-7">8</a>)
- </li>
-
- <li>
- <a id="fnref-08fda1a3461c11086b8542178f35e0c27a4a46c3"></a>
- In Apache projects, "consensus" means <em>widespread agreement among people who have decision power</em>. It does not necessarily mean "unanimity".
-
- (<a href="#fndef-08fda1a3461c11086b8542178f35e0c27a4a46c3-8">9</a>)
- </li>
-
- <li>
- <a id="fnref-9b0cf71f04bcd81dddbf6199f1c771e27566611e"></a>
- For Apache projects, <a class="http" href="https://www.apache.org/foundation/voting.html" target="_blank">https://www.apache.org/foundation/voting.html</a> defines the voting rules.
-
- (<a href="#fndef-9b0cf71f04bcd81dddbf6199f1c771e27566611e-9">10</a>)
- </li>
-
- <li>
- <a id="fnref-d9e7a517f046358463f038f3830fef171e69f78b"></a>
-Each Apache project has a private mailing list that its PMC is expected to use
-only when really needed. The private list is typically used for
-discussions about people, for example to discuss and to vote on PMC
-and committer candidates.
-
-(<a href="#fndef-d9e7a517f046358463f038f3830fef171e69f78b-10">11</a>)
-</li>
-
-<li>
-<a id="fnref-764b2c2fd32deb4ff73ea01efa67c8556303c359"></a>
-Independence can be understood as basing the project's decisions on the open
-discussions that happen on the project's main communications channel,
-with no hidden agendas.
-
-(<a href="#fndef-764b2c2fd32deb4ff73ea01efa67c8556303c359-11">12</a>)
-</li>
-
-</ol>
diff --git a/source/blog/2023-preparing-the-move.md b/source/blog/2023-preparing-the-move.md
deleted file mode 100644
index f4de61e..0000000
--- a/source/blog/2023-preparing-the-move.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Preparing the Community Development blog move
-url: /blog/preparing-the-move/
-description: We're about to move our blog here
-date: 2023-04-20
-blog_post: true
----
-
-We're in the process of moving our content here from the
-existing [blogs.apache.org](https://blogs.apache.org/) location.
diff --git a/source/blog/_index.md b/source/blog/_index.md
deleted file mode 100644
index 9c3666f..0000000
--- a/source/blog/_index.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Community Development Blog
-url: /blog/
-list_pages: true
----
-
-## Community Development Blog
-
-Contributions to this blog are welcome!
-
-We are looking for posts related community building, community-related success or failure stories
-and related topics.
-
-### Posts
\ No newline at end of file
diff --git a/source/boardreport.md b/source/boardreport.md
deleted file mode 100644
index bbdccda..0000000
--- a/source/boardreport.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: BoardReport
----
-
-For complete details about what should be in ASF project board reports, including instructions on using the handy Reporter tool, please see:
-
-[https://apache.org/foundation/board/reporting](https://apache.org/foundation/board/reporting)
\ No newline at end of file
diff --git a/source/calendars/_index.md b/source/calendars/_index.md
deleted file mode 100644
index 34424c4..0000000
--- a/source/calendars/_index.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Apache Related Event Calendars
-url: /calendars/
----
-
-This calendar lists major events relating to The Apache Software Foundation
-and our many Apache projects. We also have an automated
-[listing of upcoming Apache-related Meetups][5] (smaller events) available.
-
-This Calendar is maintained by Apache Community Development volunteers (ComDev);
-to have your event listed considered for addition please mail [dev@community.apache.org][1].
-Note that to be listed in this calendar events must <b>already</b> conform
-to the [Third Party Event Branding Policy][2] and have been approved by
-either the relevant Apache PMC or the Branding Committee.
-
-## Upcoming Events
-<ul id="events">
- <li><i>List loading</i></li>
-</ul>
-
-<em>Disclaimer: Events called 'ApacheCon' or 'Apache Roadshow' are
-official Apache Software Foundation events. Other listed events are put
-on by projects, or third-party producers, and are listed here to support
-our community, but are not official Foundation events.</em>
-
-<iframe src="https://www.google.com/calendar/embed?src=nerseigospses068jd57bk5ar8%40group.calendar.google.com&ctz=America/New_York"
-style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe>
-
-This Calendar is also available as an [iCal feed][3]
-
-<script src="/js/jquery.min.js"></script>
-<script src="https://events.apache.org/js/events-calendar.js"></script>
-<script src="https://apis.google.com/js/client.js"></script>
-
-## Other Related Events
-
-In addition to major conferences that have applied for approval with us, there are a wide range of other
-events which feature Apache projects and technologies. A list of upcoming
-[Apache related Meetups is available][5], powered in part by [this script][6]
-(patches welcome!). Secondly, a crowd-sourced list of related events is maintained
-as a [Lanyrd Guide][4], and we encourage people to help list
-Apache project related events there.
-
- [1]: mailto:dev@community.apache.org
- [2]: https://www.apache.org/foundation/marks/events.html
- [3]: https://www.google.com/calendar/ical/nerseigospses068jd57bk5ar8%40group.calendar.google.com/public/basic.ics
- [4]: http://lanyrd.com/guides/apache-software-and-technologies/
- [5]: https://www.apache.org/events/meetups.html
- [6]: https://svn.apache.org/repos/asf/comdev/tools/get_meetups
diff --git a/source/calendars/conferences.md b/source/calendars/conferences.md
deleted file mode 100644
index 7a455c7..0000000
--- a/source/calendars/conferences.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: Apache Conferences Calendar
----
-
-## Deprecated - See New Calendar instead
-
-This calendar is no longer maintained; please see [this page](/calendars/) 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][1].
-Note that to be listed in this calendar events must conform to the [Third Party Event Branding Policy][2].
-
-## Upcoming events
-
-* _List loading_
-
-<iframe src="https://www.google.com/calendar/embed?src=nerseigospses068jd57bk5ar8%40group.calendar.google.com&ctz=America/New_York"
-style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe>
-
-This Calendar is also available as an [iCal feed][3]
-
-<script type="text/javascript">
-function handleContents(li, text) {
- if(text == undefined || text.length == 0) {
- return;
- }
- parts = text.split("\n");
- for(var i=0; i<parts.length; i++) {
- li.appendChild(document.createElement("br"));
- li.appendChild(document.createTextNode(parts[i]));
- }
-}
-
-var dateRegExp = new RegExp("^(\\d{4})-(\\d{2})-(\\d{2})$");
-function handleDates(li, when) {
- var from = when['startTime'];
- var to = when['endTime'];
- if(from.match(dateRegExp) && to.match(dateRegExp)) {
- var fp = from.split(dateRegExp);
- var tp = to.split(dateRegExp);
- var fromDate = new Date(fp[1],fp[2]-1,fp[3]);
- var toDate = new Date(tp[1],tp[2]-1,tp[3]);
- var realToDate = new Date(toDate.getTime() - 24*60*60*1000);
-
- var text;
- if(fromDate.getTime() == realToDate.getTime()) {
- // Single day
- text = from;
- } else {
- // Really multi day
- text = from + " to " + realToDate.getFullYear() + "-" +
- (realToDate.getMonth()+1) + "-" + realToDate.getDate();
- }
- li.appendChild(document.createTextNode(" - " + text))
- } else {
- li.appendChild(document.createTextNode(" - " + from))
- }
-}
-
-function render(data) {
- var ev = document.getElementById("events");
- if(ev.hasChildNodes()) {
- while(ev.childNodes.length >= 1) {
- ev.removeChild(ev.firstChild);
- }
- }
-
- var feed = data.feed;
- for(var i=0; i<feed.entry.length; i++) {
- var entry = feed.entry[i];
- var title = entry.title.$t;
- var text = entry.content.$t;
- var when = entry['gd$when'][0];
-
- var li = document.createElement("li");
- var li_b = document.createElement("b");
- li_b.appendChild(document.createTextNode(title));
- li.appendChild(li_b);
- handleDates(li, when);
- handleContents(li, text);
- ev.appendChild(li);
- }
-}
-</script>
-<script src="https://www.google.com/calendar/feeds/nerseigospses068jd57bk5ar8@group.calendar.google.com/public/full?alt=json-in-script&callback=render&orderby=starttime&max-results=30&singleevents=true&sortorder=ascending&futureevents=true"></script>
-
- [1]: mailto:dev@community.apache.org
- [2]: https://www.apache.org/foundation/marks/events.html
- [3]: https://www.google.com/calendar/ical/nerseigospses068jd57bk5ar8%40group.calendar.google.com/public/basic.ics
diff --git a/source/comdevboardreports.md b/source/comdevboardreports.md
deleted file mode 100644
index 66c7a3f..0000000
--- a/source/comdevboardreports.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: ComDevBoardReports
----
-
-Like every other ASF project, the ComDev PMC sends a [quarterly report to the board](https://www.apache.org/foundation/board/reporting). These reports are read by the board, and sometimes directors will ask the PMC for clarification or to make suggestions for the project.
-
-You can read the complete list of [Apache Community Development board reports](https://whimsy.apache.org/board/minutes/Community_Development.html). A [chronological view of all minutes from ASF Board meetings](https://www.apache.org/foundation/board/calendar.html#board-meeting-minutes) is also public.
diff --git a/source/committers/_index.md b/source/committers/_index.md
deleted file mode 100755
index 3505a2b..0000000
--- a/source/committers/_index.md
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: Committer resources
-url: /committers/
----
-
-There are a number of useful Apache tools and services available for Apache projects
- and committers. This is a brief set of pointers or signposts to that information.
-
-## Apache Infrastructure Information
-
-The primary portals for Apache Infra questions - how Subversion/Git/Websites, etc. work at the ASF - are pages at <a href="https://www.apache.org/dev/" target="_blank">apache.org/dev</a> and <a href="https://www.infra.apache.org" target="_blank">infra.apache.org</a>.
-
-If you're a committer, you can [patch this very website yourself][2]!
-
-## Decision making
-
-Decisions in Apache projects result from:
-
- - action
- - consensus in the community
- - (if needed) votes within the community
-
-We have, over the years, developed a very simple and effective approach to
-consensus building and decision making. Projects, and the ASF generally, make the vast majority of decisions
-using [lazy consensus][3]. If the "lazy" approach to consensus building seems
-unsuitable for a particular decision, we seek to [build consensus][4] within
-the community. Very occasionally, usually for formal reasons relating to legal
-responsibilities, it is necessary to call a [vote][5].
-
-Full descriptions of each of these approaches are available on various foundation
-and project sites. However, we've provided an initial introduction to [decision
-making][6] here on the community development site.
-
-## Project independence
-
-While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-[release voting][7], [legal policy][8], [brand policy][9],
-using [mailing lists][10], etc., which [various sites document][11].
-
-One of these invariant rules is that PMCs manage projects
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. There is more discussion of this principle
-in our document [Project Independence][12].
-
-<a name="Index-Assistingwithprojectmanagement"></a>
-
-## Development processes
-
-Each project in Apache is free to define its own development processes as
-long as it respects our decision-making, legal and independence requirements.
-However, over the many years that the ASF has existed, our projects have evolved and documented many best practices. In this section we
-bring together some of the most popular of these practices. Most Apache projects
-operate in ways that are largely similar to these processes.
-
- * [Crediting contributors][13] is a critical part of community building
- * [ASF Licensing Policy][14]
- * Releases
- * [Releases FAQ][15]
- * Release audit is a process each release candidate must go through to ensure it is managing intellectual property (IP) correctly
- * [RAT/Creadur][16] is a tool to assist this process
- * [Release management][17] is how the project prepares and publishes its releases
- * [Handling cryptography][18] in an Apache Release
- * [Source Headers and NOTICE][19] Files
- * [Distribution best practices][20]
- * [ASF Developer section sitemap][21]
-
-## Assisting with project management and marketing
-
-There are many visible contributions of value in an Apache projects
-(documentation, testing, coding user support, design etc.), but there are
-also plenty of "back office" tasks that are necessary to maintain a healthy
-project. This section describes some of the activities that you can help
-with. In most cases you will need to be a committer to carry out these
-activities, although non-committers can often act in supporting roles.
-
- * Write informational [blogs][22]
- * [Assessing and approving new committers](/newcommitter.html)
- * [Board Reports](/boardreport.html)
- * [Apache Project Branding/Trademark Resources](https://www.apache.org/foundation/marks/resources)
-
-## Speaking about Apache projects at events
-
-We encourage all of our committers to speak about Apache projects and
-technologies, and generally to help to grow and enhance our community.
-
-## Other Resources
-
-There is no shortage of useful resources for committers at Apache. Here are a few you might want to take a look at:
-
- - [How the ASF works][23]
- - [Guide for New Committers][24]
- - [Developer resources][25]
- - [Apache service list][26]
-
-
- [1]: https://www.apache.org/dev/
- [2]: /newbiefaq.html#websitecms
- [3]: /committers/lazyConsensus.html
- [4]: /committers/consensusBuilding.html
- [5]: /committes/voting.html
- [6]: /committers/decisionMaking.html
- [7]: https://www.apache.org/legal/release-policy.html
- [8]: https://www.apache.org/legal/
- [9]: https://www.apache.org/foundation/marks/
- [10]: https://www.apache.org/dev/#mail
- [11]: https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different
- [12]: /projectIndependence.html
- [13]: https://subversion.apache.org/docs/community-guide/conventions.html#crediting
- [14]: https://www.apache.org/legal/resolved.html
- [15]: https://www.apache.org/legal/release-policy.html
- [16]: https://incubator.apache.org/rat/
- [17]: https://sling.apache.org/site/release-management.html
- [18]: https://infra.apache.org/crypto.html
- [19]: https://www.apache.org/legal/src-headers.html
- [20]: https://incubator.apache.org/guides/releasemanagement.html#distribution-best-practice
- [21]: https://www.apache.org/dev/
- [22]: https://infra.apache.org/project-blogs
- [23]: https://www.apache.org/foundation/how-it-works.html
- [24]: https://infra.apache.org/new-committers-guide.html
- [25]: https://www.apache.org/dev
- [26]: https://infra.apache.org/services.html
diff --git a/source/committers/consensusBuilding.md b/source/committers/consensusBuilding.md
deleted file mode 100644
index e8cdfc1..0000000
--- a/source/committers/consensusBuilding.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Consensus Building
----
-
-In some cases there is no obvious path to take, or you might be a new community,
-or a new member of an existing community. In these cases people often
-need to build consensus by making proposals and eliciting responses.
-
-Constructive discussion is the lifeblood of a successful project. However, we want to avoid unnecessary discussion and significant
-amounts of unnecessary mail that everyone in the community needs to read. so many ASF projects adopt a
-shorthand notation for showing support, or otherwise, for a proposal.
-
-## Expressing support (or otherwise)
-
-It is important to understand that everyone is invited to express
-their opinion of any given action or proposal. Apache projects are community
-projects in which no single individual has more power than any other single
-individual (except in a very few procedural situations).
-
-The notation used is "+1", "-1" and "0". It's also common to see "+0" and "-0".
-
-So, what do these notations mean?
-
- - +1 means "I agree with this and will help make it happen"
- - +0 means "I agree with this but probably won't make it happen, so my
-opinion is not that important"
- - -0 means "I don't agree with this, but I'm offering no alternative so
-my opinion is not that important"
- - -1 means "I don't agree and I am offering an alternative that I am able
-to help implement"
-
-Many people use fractions to indicate the strength of their feelings,
- e.g. "+0.5". Some will even indicate their opinion that the proposal is a "no brainer" with something
-like "+1000".
-
-This notation is not an exact science. It's just a shorthand
-way of communicating strength of feeling.
-
-## Consensus building is not voting
-
-A confusing thing about this notation is that it is the same notation
-used in a formal vote. Knowing when something is a vote and when it is a
-preference is important. It's easy to tell, though: if the subject line of the email thread does not have
-"[Vote]" at the start then it's just an opinion. We try not to call votes;
-consensus building is much more inclusive.
-
-The reasons for this notation being common is that when someone wants to
-summarise a discussion thread they can mentally
-add up the strength of feeling of the community and decide whether there is consensus.
-
-If there is clear consensus in favor of a proposal, members of the community can proceed with
-the work under the [lazy consensus][1] model.
-
- [1]: /committers/lazyConsensus.html
diff --git a/source/committers/decisionMaking.md b/source/committers/decisionMaking.md
deleted file mode 100644
index 00863d3..0000000
--- a/source/committers/decisionMaking.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Decision-Making
----
-
-The most important thing about engaging with any Apache project is that everyone
-is equal. All project participants with an opinion can express that opinion and, where
-appropriate, have the community consider it.
-
-To some, the idea of having to establish consensus in a large and distributed team
-sounds inefficient and frustrating. Don't despair, though: The Apache Way has a
-set of simple processes to ensure things proceed at a good pace.
-
-In ASF projects we don't like to vote. We reserve that for the few things that need
-official approval for legal or process reasons (e.g. approving a release or adding a new committer).
-Most of the time we work with the consensus-building techniques documented below.
-
-## Lazy Consensus
-
-[Lazy consensus][10] is the first, and possibly the most important, consensus-building
-tool we have. Essentially lazy consensus means that you don't need to get explicit
-approval to proceed, but you need to be prepared to listen if someone objects.
-
-## Consensus Building
-
-Sometimes lazy consensus is not appropriate. In such cases it is necessary to
-make a proposal to the email list and discuss options. There are mechanisms
-for quickly showing your support or otherwise for a proposal and
-[building consensus][11] within the community.
-
-Once there is consensus to approve a proposal, people can proceed with the work under the [lazy
-consensus][12] model.
-
-## Voting
-
-Occasionally a "feel" for consensus is not enough. Sometimes we need to
-have a measurable consensus, for example, when [voting][13] to add committers or
-to approve a release.
-
- [10]: /committers/lazyConsensus.html
- [11]: /committers/consensusBuilding.html
- [12]: /committers/lazyConsensus.html
- [13]: /committers/voting.html
diff --git a/source/committers/funding-disclaimer.md b/source/committers/funding-disclaimer.md
deleted file mode 100644
index 9dd9684..0000000
--- a/source/committers/funding-disclaimer.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Funding campaign disclaimer
----
-
-Some Apache committers have successfully run funding campaigns to support their work on their favorite Apache projects.
-
-This is ok in principle, but you have to make it clear that the campaign is your own thing, and avoid any confusion about the role of the
-ASF and how its projects work.
-
-This page gives a few examples of how to do that.
-
-If you have any question about this, feel free to ask on our
-[dev@community.apache.org](https://lists.apache.org/list.html?dev@community.apache.org) mailing list.
-
-## Example disclaimer for a personal crowdfunding campaign
-
-Here's a nice example, based on a disclaimer one committer has used:
-
-
-```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.
-```
-
-See also the [discussion thread](https://mail-archives.apache.org/mod_mbox/community-dev/201310.mbox/%3Cop.w4fwv6ewovlrp5%40arsmachina%3E) about this
-campaign.
-
-## Friends of Apache Groovy
-
-[Friends of Apache Groovy](https://opencollective.com/friends-of-groovy) has another good example which supports activities
-in the Apache Groovy community.
-
-The [explanation in their 'about' section](https://opencollective.com/friends-of-groovy#section-about) makes it clear that the
-initiative is _not_ affiliated with or driven by the ASF, and also that any contributions, funded or not, have to go
-through the usual Apache Groovy acceptance process.
diff --git a/source/committers/lazyConsensus.md b/source/committers/lazyConsensus.md
deleted file mode 100644
index a6ac85e..0000000
--- a/source/committers/lazyConsensus.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Lazy Consensus
----
-
-The concept of "lazy consensus" is very important in your project. Lazy
-consensus means that when you are convinced that you know what the community
-would like to see happen, you can assume that you have consensus in favor of the proposed work and
-can get on with it. You don't have to insist people discuss and/or
-approve your plan, and you certainly don't need to call a vote to get approval.
-You just assume you have the community's support unless someone says otherwise.
-
-We have a time machine (Subversion or Git). As long as you commit
-(or submit patches) early and often, the community has plenty of opportunity
-to indicate disapproval or point out issues. If you believe the community will support your action
-you can operate on lazy consensus as long as you are prepared to roll back
-any work should someone raise a valid objection.
-
-## Avoiding unnecessary discussion
-
-The key thing about lazy consensus is that it's easier for people to agree
-by doing nothing, than it is to object, which requires them to propose an alternative. This has two effects: first, people are less
-likely to object for the sake of objecting and, second, it cuts down on the amount
-of unnecessary email traffic and discussion.
-
-Lazy consensus lets us avoid having to wait for a community-based decision
-before proceeding. However, it does require everyone who cares about the health
-of the project to watch what is happening, as it is happening. Objecting too
-far down the road will cause upset, while objecting (or asking for clarification
-of intent) early is likely to be greeted with relief that someone is watching
-and cares.
-
-## Stating lazy consensus
-
-Sometimes a member of the community will believe a specific action is the correct
-one for the project but is not sure that there will be consensus. They may not wish to proceed with the work without giving the
-community an opportunity to provide feedback. In these circumstances they can make the
-proposal and state that lazy consensus is in operation, like this:
-
- - In an email to `dev@PROJECT`, they state their proposal, with sufficient supporting material for someone familiar with the project to understand it.
- - In the email they indicate that they will start
-implementing the proposal in 72 hours unless someone objects. The time period takes into account that project members are a) busy and b) in time zones around the world.
-
-In this approach the the proposer does not insist that the developer community discuss or explicitly support the proposal. However, it allows space and time to [express support or objections][1] or propose corrections to the proposal before work begins.
-
-## Silence is consent
-
-People may choose to indicate their support for the proposal with a +1
-mail - quick and easy to read and reassuring for the implementer. However,
-remember, in a lazy consensus world silence is equivalent to support.
-
- [1]: /committers/consensusBuilding.html
diff --git a/source/committers/voting.md b/source/committers/voting.md
deleted file mode 100644
index 5d7e25f..0000000
--- a/source/committers/voting.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Voting
----
-
-Occasionally a "feel" for consensus is not enough. Sometimes we need to
-have a measurable consensus, for example, when voting to invite new committers or
-to approve a release.
-
-## Preparing for a Vote
-
-It is important to ensure that the community has time to
-discuss the issue before voting. To do this, post an email to the list
-indicating the intention to call a vote and the options available. By the time
-a vote takes place there usually is [consensus in the community][1] on what path to take. The vote
-itself is, normally, a formality; however, it is important as part of the record of the decisions of the PMC and the development of the project.
-
-## Calling a Vote
-
-Once it is time to call the vote, the proposer or a member of the PMC posts an email with the subject line starting
-with **[VOTE]**. This helps community members not miss
-an important vote thread. It also indicates that this is not a consensus-building conversation
-but a formal vote.
-
-### Casting Your Vote
-
-The notation used in voting is:
-
- - +1 Yes, I agree
- - 0 I have no strong opinion
- - -1 I object on the following grounds
-
-If you object you **must** support your objection and provide an alternative course
-of action that you are willing and able to implement (where appropriate).
-
-
- [1]: /committers/consensusBuilding.html
diff --git a/source/contactpoints.md b/source/contactpoints.md
deleted file mode 100644
index 0745058..0000000
--- a/source/contactpoints.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: ContactPoints
----
-
-If you have a question about anything Apache, the ComDev project is here to help.
-To help us help you, try to direct your question to the right mailing list - our
-volunteer committers do all their work on mailing lists.
-
-# Community Questions
-
-Email questions about community or issues across multiple Apache projects to [dev@community.apache.org](mailto:dev@community.apache.org?subject=New-Contact-Question) - or see our detailed [Mailing List How To](//community.apache.org/lists.html) page.
-
-# Technical Questions
-
-If you have a *technical* question about *this* website, or one of the tools that
-the ComDev project builds, email us at `dev@community`.
-
-If you *technical* question about *any other* Apache project, email
-the [appropriate user@*projectname*.apache.org](/lists.html) list, or the `dev@` list for
-the project.
-
-# Non-Technical Questions
-
-Each of Apache's email lists is privately archived: you can mail to them, and
-we'll answer, but you won't be able to read the archives.
-
-<a name="ContactPoints-Trademarks"></a>
-## Trademarks
-
-Issues regarding trademarks, specific project names, or branding of the
-ASF and any projects: see our [Trademark Site Map](//www.apache.org/foundation/marks/resources),
-or send email to [trademarks@apache.org](mailto:trademarks@apache.org).
-
-
-<a name="ContactPoints-PublicityandMarketing"></a>
-## Publicity and Marketing
-
-Issues dealing with publicity, marketing, or any inquires from the
-press or analysts: see our [Press Team Page](https://www.apache.org/press/),
- or email to [press@apache.org](mailto:press@apache.org).
-
-<a name="ContactPoints-FundraisingandSponsorship"></a>
-## Fundraising and Sponsorship
-
-Questions about fundraising, sponsorships, donations, or related
-finances: see our [Donations Information](//www.apache.org/foundation/contributing.html),
-or email to [fundraising@apache.org](mailto:fundraising@apache.org).
-
-<a name="ContactPoints-Legal"></a>
-### Legal
-
-Send specific legal questions that may need to be private, and require a
-response from the ASF's legal counsel to
-[legal-internal@apache.org](mailto:legal-internal@apache.org).
-
-Please read our [Legal FAQs](https://www.apache.org/legal/#user-links) first.
-
-<a name="ContactPoints-Other"></a>
-### Other
-
-For more information on these and other foundation lists, see the [Mailing Lists](https://www.apache.org/foundation/mailinglists.html) page.
diff --git a/source/contributors/_index.md b/source/contributors/_index.md
deleted file mode 100755
index cbc6a86..0000000
--- a/source/contributors/_index.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: Contributing to the Apache Software Foundation
-url: /contributors/
----
-
-This page is for people who are reasonably
-comfortable with open source development models but need a helping hand finding
-their way around the Apache Software Foundation and our way of developing software
-(commonly called "The Apache Way"). For those wishing to start from
-the very beginning, we have a [newcomers page][1].
-
-# Project Independence And Policies
-
-While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
-projects must follow – things like complying with PMC
-[release voting][2], [legal policy][3], [brand policy][4],
-using [mailing lists][5], etc., which are [documented in various places][6].
-
-One of these invariant rules is that projects are managed
-independently of any commercial interests. The goal is to create an
-environment in which all participants are equal and thus have an equal
-opportunity to contribute to and benefit from our software, regardless
-of motivation or financial objectives. This is discussed in more detail
-in our document [Project Independence][7].
-
-# Moving From Contributor to Committer
-
-Anyone can be a contributor to an Apache project. Being a contributor simply means
-that you take an interest in the project and contribute in some way, ranging from asking
-sensible questions (which document the project and provide feedback to developers)
-through to providing new features as code patches.
-
-If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
-a _committer_. At the ASF, a committer is someone who is
-committed to a particular project. It brings with it the privilege of write access to
-the project repository and resources. In many projects, committers may also be invited
-to be part of the core group within the project that ensures the project's vitality, the PMC.
-In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.
-
-One thing that is sometimes hard to understand, when you are new to the open
-development process used at the ASF, is that we value the community more than
-the code. A strong and healthy community will be respectful and be a fun and
-rewarding place. More importantly, a diverse and healthy community can
-continue to support the code over the longer term, even as individual
-contributors come and go from the field.
-
-In particular, we have some [etiquette and behavior expectations][8] when
-you work with Apache communities.
-
-See also this [detailed advice for how to become a committer](/contributors/becomingacommitter.html)
-
-## Contributing A Project - CoPDoC
-
-The foundations of an Apache project and how the community contributes to it are
-sometimes referred to by the acronym CoPDoC:
-
- - (Co)mmunity - one must interact with others, and share vision and knowledge
- - (P)roject - a clear vision and consensus are needed
- - (Do)cumentation - without it, the stuff remains only in the minds of the authors
- - (C)ode - discussion goes nowhere without code
-
-## Anyone Can Become A Committer
-
-There is nothing at the Apache Software Foundation that says you must write code
-in order to be a committer. Anyone who is supportive of the community and works
-in any of the CoPDoC areas is a likely candidate for committership.
-
-Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
-any area of CoPDoC they can be voted in as a committer. Being a committer does
-not necessarily mean you commit code; it means you are committed to the project
-and are productively contributing to its success.
-
-One of the key contributions people can make to the community is through the
-support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
-A main idea behind being a committer is the ability to be a mentor and to work
-cooperatively with your peers.
-
-Some users of a project's software become committers in their own right. Some will test code,
-some will write documentation, some will do bug triage and some will write code.
-
-For more details see "[How it works][9]". You can also make
-[suggestions for how to update this website][10] you're reading right now!
-
-## Questions and Feedback
-
-You can provide feedback and ask questions by subscribing to our mailing
-list: send an email to
-[dev-subscribe@community.apache.org](mailto:dev-subscribe@community.apache.org). Once subscribed, you can send your mail to
-[dev@community.apache.org](mailto:dev@community.apache.org).
-
-
- [1]: /newcomers/index.html
- [2]: https://www.apache.org/legal/release-policy.html
- [3]: https://www.apache.org/legal/
- [4]: https://www.apache.org/foundation/marks/
- [5]: https://www.apache.org/dev/#mail
- [6]: https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different
- [7]: /projectIndependence.html
- [8]: /contributors/etiquette
- [9]: https://www.apache.org/foundation/how-it-works.html
- [10]: /newbiefaq.html#websitecms
diff --git a/source/contributors/becomingacommitter.md b/source/contributors/becomingacommitter.md
deleted file mode 100644
index fa276a8..0000000
--- a/source/contributors/becomingacommitter.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Becoming a committer
-slug: becomingacommitter
----
-
-{{% toc %}}
-
-# 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.
-
-On the contrary, this document discusses how things should work, and sometimes do work, in some Apache Software Foundation (ASF) projects, but might not on the one you’re interested in.
-
-Beneath each of these recommendations is the assumption that you are acting in good faith, for the benefit of the project. Simply attempting to check these boxes to game the system will reflect badly on you, and probably on your employer, too.
-
-# Becoming a Committer
-It’s important to remember that becoming a committer is not a reward, or a recognition, so much as that it is the project expressing self-interest. That is, people are added as a committer to a project because it benefits the project, not because it’s some kind of pat on the back for the individual in question. As such, every behavior suggested here is about advancing the interests of the project. It is critical that you think, first and foremost, about being a project owner, and working [...]
-
-These, therefore, are the behaviors that you should exhibit if you want to become a committer, and then a PMC member, on an ASF project. (These are not unique to ASF projects, of course, but process will differ greatly from one project to another, and are largely similar among ASF projects.)
-
-## Read the mailing list
-ASF projects communicate on the mailing list. If you want to be involved in the community, you must set aside time every week (preferably every day) to keep current on the community discussion.
-
-When first participating in an ASF project, you can (and should) look back several months (or as far as you have time for) to see what has been discussed recently. You can do this at [lists.apache.org](http://lists.apache.org/).
-
-A growing number of projects also have a presence on Slack, Discord, or somewhere else. Find where that is, and become a regular. A shrinking number of projects have a presence on Libera IRC – mostly the much older projects. This is where you’ll connect with the older members of the projects and learn more of the ancient project lore.
-
-## Contribute code (and other things)
-If you want to become a committer, you should make significant contributions to the project. The most obvious thing to contribute to a software project is code. Code contributions should be diverse in terms of size and significance. That is, you should work on small issues and large. You should collaborate with others on features and fixes, and you should propose significant changes yourself. You should dig up old tickets, and work towards resolving them.
-
-In particular, you should work on code that is of benefit to all users, rather than focusing solely on features that benefit only yourself, or your employer. As a project owner, you should care about the entire health and sustainability of the project.
-
-Code contributions are not the only type of contribution that counts towards becoming a committer, it’s just the most common. Design, documentation, marketing, event management, and many other ways of contributing to the success of a project are also often considered in making someone a committer. While the term “committer” implies committing code, it can also be interpreted as someone who is committed to the project.
-
-## End user support
-Answering end user questions has many benefits. It’s the best way to establish expertise in aspects of the software that effect actual users, and, thus, the best way to stay in touch with user concerns. It’s also the way to establish and maintain visibility in the project community, because your name is always visible on the mailing list.
-
-Caution: Do not just jump in and answer every question with visibility as a primary goal. Ensure that your answers are actually useful, and contribute something to the conversation. Simply posting to every conversation, particularly when someone else has already offered a good answer, can be perceived as attempting to game the metrics.
-
-## Documentation
-Improving the documentation is one of the most effective things that one can do to improve the user experience. If you notice many people asking similar questions, this is usually an indication that the documentation is weak on that point. Fix it. When the question is asked again, point to the improved documentation, and ask for feedback as to how it could be further improved.
-
-Take criticism of the documentation as a challenge, rather than a personal criticism.
-
-As you learn about the project, consider yourself a tester of the documentation. If anything is unclear, propose a patch.
-
-## Review PRs and tickets
-Dig into unmerged PRs and outstanding tickets. Figure out how to navigate the process to get an old ticket resolved, or a PR merged.
-
-This is an investment in the project in two ways.
-
-The obvious improvement is getting an issue fixed or a PR merged, thus enhancing the project. The less obvious way is that ancient tickets, and unmerged PRs, communicate that the project is not actively maintained, and that user issues are being ignored. This undermines project trust. Thus, addressing these things builds community trust, and increases your personal value to the project.
-
-## Be visible
-Participate meaningfully in discussions on the developer mailing list. Drive discussions through to action. Advocate for changes that help yourself and your employer, but also for those that improve the project as a whole.
-
-Get to know the important characters on the project, and what their priorities are. Help them achieve those priorities in whatever way you can. Figure out who you can best collaborate with to advance your own personal interests in the project, but also the overall health of the project and community.
-
-Start conversations around topics you’re passionate about, and volunteer to be the one to address them.
-
-Do not, however, just talk to be seen. Nobody is fooled by that.
-
-## Test, and vote on releases (non-binding)
-
-Testing releases, and then reporting problems or suggesting
-improvements, is one of the most important functions of users, and is an
-important way to contribute to a project. It also familiarizes you with
-the function of the software, which will lead you to be a better
-contributor.
-
-Many projects use CI to continuously test proposed patches and PRs. Each
-platform needs to be individually set up for testing, and often the
-projects do not have enough people familiar with the specific
-environments that might benefit from testing. You can propose additional
-platforms to test on.
-
-Vote on release candidates and releases (non-binding).
-
-Note that a vote should always mean that you’ve actually tested, so testing releases is implied here, too. Indicate what platform(s) you’ve tested on, and what was the nature of the tests that you performed. Testing releases on a variety of platforms and configurations is a very valuable piece of information for projects with limited testing infrastructure.
-
-While these votes don’t "count" towards making a release official, it’s both hugely beneficial for the project, and increases your visibility.
-
-## Give talks
-Propose talks to conferences about the project, and about how your employer’s customers are using it.
-
-Proposing "Introduction to Apache Woobly" talks has many benefits. It is a great way to get the word out about the project. It’s good for establishing yourself as an expert in the field. It educates users (and potential customers) about operating the software. And it will help you identify what’s actually important about the software, how people use it, and what kinds of questions real users are asking about the software.
-
-Community Over Code (formerly called ApacheCon) is the obvious place to give these talks, but also look for conferences about the general technology space around the project you’re contributing to.
-
-# Once you’re a committer …
-If and when you achieve your goal of becoming a committer, don’t consider your journey done.
-
-Becoming a PMC member is a continuation of the same path. Continue to do all of the above things, focusing more on the health of the project as a whole, rather than just your personal interests, or those of your employer or manager.
-
-Also, take an active interest in other contributors – both those on your team, and those with other employers. Mentor them in following the same path that you followed. Encourage them. Celebrate them, and mention them to other contributors. This is an investment in the future of the project, so that, some day, when you move on to something else, the project will live on.
-
-Interest across multiple projects, and at the Foundation-wide level, is the start of the path to becoming a Foundation Member, if that is something that interests you.
-
-# Summary
-Finally, a reminder – there’s no way to guarantee promotion to committer or the PMC. However, if you make your goal the improvement of the project, rather than just about personal promotion, and approach these recommendations as a path to project ownership, in good faith, these are your best path towards that goal.
-
-# Resources
-Find your project’s [committer and PMC membership lists](https://projects.apache.org/)
-
-Read [mailing list archives](https://lists.apache.org/)
-
-Find your contribution count to date on Github, for example: [Apache Hadoop contributors](https://github.com/apache/hadoop/graphs/contributors) (You can drag a date range to narrow it down to recent contributions.)
-
-View [past board reports from your project](https://www.apache.org/foundation/board/calendar.html). This is a good way to judge the rate at which a given project adds committers and PMC members. It’s also a way to compare how long other individuals took to attain committer status.
-
-
diff --git a/source/contributors/etiquette.md b/source/contributors/etiquette.md
deleted file mode 100644
index a5f766c..0000000
--- a/source/contributors/etiquette.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: ASF Community Etiquette Guidelines
----
-
-The ASF and our many projects welcome all
-participants. Before you begin, it is important to review and respect our community guidelines. We have a few
-ASF-specific tips below.
-
-# Code of Conduct # {#coc}
-
-The ASF has adopted a [Code of Conduct][1] which covers interactions in
-all the online spaces that ASF projects use - email, issue trackers, wikis,
-websites, IRC, and the like. ASF projects are made up of volunteers, and
-we work to ensure that all productive contributions are welcomed. Every PMC is expected to ensure their project's lists show
-proper behavior.
-
-
-# Guidelines for Conduct and Etiquette # {#member}
-
-The ASF as a corporation is run by several hundred members, who have deep and lasting experience
-in helping to build and run long-term, successful open source projects. Below are some guidelines to help you communicate with other volunteers, and get the most out of your communication experience.
-
-
-**General Communication Guidelines**
-
- * Use a thoughtful, respectful tone to communicate your thoughts. Remember, text is difficult to interpret. There are no body language or voice tones to help interpret the messenger's intent. Remember that the person on the other side of your communication is also a human deserving of understanding and
-respect.
-
- * If you agree with someone, let them know. If you disagree, let them know as well. Positive and negative feedback are both necessary. Positive
-feedback will help others feel more confident in their ideas, as well as ensure they know they're on the right track. Negative feedback, given in a
-respectable tone, will help to guide the messenger toward a more productive solution.
-
- * Avoid idiomatic and metaphoric language. At the ASF, we have thousands of volunteers that speak different languages. To avoid miscommunication, it
-is best to avoid this type of language in favor of clear, direct statements.
-
- * Be patient when waiting for responses. Because the ASF is an international community, there may be some delays in response time. We call these
-"asynchronous responders." We understand that it can be difficult and frustrating to wait, but please give these asynchronous responders time to read
-and address your message. The ASF strives to respond to all messages (email, slack, etc.) in a timely manner.
-
- * Dealing with conflict and miscommunication: Here at the ASF, we strive to make everyone feel welcome and wanted in their roles. With that said, we
-also understand that miscommunications happen, especially in text. If you are sent a message that you don't understand, or feel uncomfortable with, a
-good first step would be to ask for clarification. Don't be afraid to ask specific questions. Chances are, the person you're communicating with has been
-in your position before, and will understand.
-
- * Be forgiving and accept different priorities: Everyone that works on ASF projects is passsionate about their work, and we love and welcome that
-passion and hope you will bring your own passion to your projects. Please remember, the ASF currently has over 300 projects, each with their own project
-priorities. If your priorities seem at odds with others, remember that compromise is essential to progress. Work with the other person to come up with a
-compromise that takes all project priorities into account.
-
- * Note: Foul, derogatory, or divisive language in any form, up to and including threats, harassment, and discriminatory language, is strongly
-prohibited.
-
-
-**Face-to-Face** is excellent way to eliminate disagreements, but that is often
-not practical. Consider a conversation via Skype, Google Hangouts or a Slack channel, just for the social aspect
-of being part of this community. It does not need to be a formal meeting. Once we have a face to add to the words, and a general
-idea how that person is socially, we are much more capable to interact via text.
-
-**Project decisions must always be made on mailing lists**.
-It's great to have a synchronous online chat to work through some questions, but
-be sure to bring the results of the chat (and any proposals for the
-project community to consider) back to the mailing list. People who
-weren't able to attend the chat or call might also have ideas on the topic.
-Be sure to allow at least 72 hours for others to read the proposals and
-comment before closing out the issue.
-
-# Other Etiquette Guidelines # {#other}
-
- - [Official Apache-wide Code of Conduct][1]
- - [Email Etiquette Guidelines - writing good emails](https://www.apache.org/dev/contrib-email-tips)
- - [Building Consensus in a community](/committers/consensusBuilding.html)
-
- [1]: https://www.apache.org/foundation/policies/conduct.html
diff --git a/source/events/small-events.md b/source/events/small-events.md
deleted file mode 100644
index 737e731..0000000
--- a/source/events/small-events.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Requirements for organizers of small Apache-related events
----
-
-# Approval of small Apache-related events
-
-The Community Development PMC is responsible for assisting with the
-organisation and promotion of all Apache events.
-
-Organizers of Apache-related events need approval for using the
-Apache trademarks in their event brandings.
-
-The main steps are:
-
-a) Get approval from the PMCs of the projects that your event is about.
-
-b) Abide by the [Apache branding rules](https://www.apache.org/foundation/marks/events.html).
-
-c) Once brand use is approved by the respective PMCs, inform the community
-development PMC of your event, including references to PMCs approval.
-Ideally on our public (dev@community.apache.org) mailing list,
-but at least in private (private@community.apache.org).
-
-d) Wait at least 72 hours for comments from the community development PMC
-and then send an announcement of your event to
-dev@community.apache.org so that it can be included in our
-[events calendar](../calendars/).
diff --git a/source/gettingStarted/101.md b/source/gettingStarted/101.md
deleted file mode 100644
index 22997a6..0000000
--- a/source/gettingStarted/101.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: Getting started
----
-
-# Where do I start?
-
-If you have no idea where to start your engagement with an Apache project,
-this is the page for you.
-
-### Finding the right project
-
-The key to working on projects at Apache (and on any open source project, for that matter)
-is to have a personal reason for being involved. You might be trying to solve
-a day job issue or learn a new technology, or
-simply want to do something fun in your free time. We don't care what your
-motivation is; we just care about you wanting to get involved.
-
-If you don't have a specific technical issue to solve you might be willing to
-work on any project. Our [projects page][1] provides a useful index which
-allows you to view projects alphabetically, by category or by coding language. When you view a project's detail page in this list you will find information about their
-mailing lists, issue tracker and other resources.
-
-You might also like to view our
-[Incubating projects][2]. These projects work in exactly the same way as our "top
-level projects" but are still developing their initial community.
-
-Once you've found some interesting-looking projects, join their mailing lists and
-start "lurking". Read the mails that come through the list. Initially you will not
-understand what people are talking about, but over time you will start to
-pick up the language, objectives, strategies, concerns and working patterns of the community.
-
-#### Finding an issue to work on
-
-If you are trying to satisfy a specific technical problem, you already know
-what you want to work on; but if you are looking for something useful to do in
-order to participate in an ASF project, the project's issue/bug tracker is your
-friend. You can find a link to it from the project's home page or from its entry on the
-projects page linked above.
-
-In the project's issue tracker you will find details of bugs that have been reported and feature
-requests the project is considering. This should give you some
-inspiration about how you might be able to help the project community. If
-you are looking for a beginner-level issue, try searching Jira for issues
-with the label "GSoC" or "mentor"; these are issues the community feels are
-manageable for someone new to the ASF and their project.
-
-## Joining the community
-
-Once you have identified an issue you would like to tackle, it's time to join the
-project's mailing list (if you haven't already) and get started.
-
-Remember, community members are usually happy to help you, but they have to get something
-in return. The community needs to believe that you intend to contribute positively
-to their work. There is a limit to how much "hand-holding" you will get, so be ready
-to do some work if you expect to continue to be helped in your first foray into
-open source.
-
-Alternatively you can dive straight in and work with the community. Since you've
-been lurking on the lists for a while, you
-should have a feel for how to get involved, so go for it.
-
-A very good first step would be to introduce yourself in an email to the list. Explain your interest in the project and anything relevant in your background or skills, and identify the bug or feature request you would like to work on.
-
-# Further Reading
- * Answers to some common questions are in our [FAQ][5]
- * To learn more about "The Apache Way" of developing software, see the
-Foundation's [How It Works][6] pages.
-
-
- [1]: https://projects.apache.org/
- [2]: https://incubator.apache.org/
- [5]: /newbiefaq.html
- [6]: https://apache.org/foundation/how-it-works.html
diff --git a/source/gsoc/_index.md b/source/gsoc/_index.md
deleted file mode 100644
index 1d7813f..0000000
--- a/source/gsoc/_index.md
+++ /dev/null
@@ -1,181 +0,0 @@
----
-title: GSoC
-url: /gsoc/
----
-
-<div class="card mb-3">
- <div class="card-header">
- Currently happening
- </div>
- <div class="card-body">
- <h5 class="card-title text-info">Proposal ranking phase 1</h5>
- </div>
-</div>
-
-Google is sponsoring the [2023 Summer of Code](https://summerofcode.withgoogle.com/) and
-[The Apache Software Foundation](https://www.apache.org/) (ASF) registered as a mentoring organization.
-This page is your entry point to the ASF GSoC program.
-Please watch this page for updates concerning our participating in 2023.
-
-<a name="GSoC-Students:readthis"></a>
-# Students: read this
-
-* Learn [about GSoC](https://summerofcode.withgoogle.com/about/)
-* Decide if you are [eligible](https://summerofcode.withgoogle.com/get-started/) for GSoC?
-* Review [Advice for Students](https://opensource.googleblog.com/2011/03/dos-and-donts-of-google-summer-of-code.html)
- to make sure you really want to apply to GSoC.
-* Watch [GSoC video presentation](https://www.youtube.com/watch?v=S6IP_6HG2QE)
- for students.
-* Examine the list of [available ASF GSoC 2023 projects](https://s.apache.org/gsoc2023ideas)
- * <span class="text-primary">**NOTE**</span> that you can search the issue tracker for GSoC projects by
-filtering using the "*gsoc2023*" label, this allows you to narrow down the list
-to the projects you are interested in.<br/>
-Or simply use this link https://issues.apache.org/jira/issues/?jql=labels+%3D+gsoc2023
-* If you do not see any interesting projects from the proposed ideas, we encourage you to contact one of the Apache Project's mailing list and propose a new idea. But these ideas have to be vetted on the project dev list. The ASF does not encourage and will not respond to your personal new open source project ideas which are unrelated to any Apache projects.
-
-<a name="GSoC-ApplyingforGSoC"></a>
-### Applying for GSoC
-
-Details are announced now and we are in the project discussion phase. We encourage you to discuss you application with the project community.
-
-In order to apply we ask that you create
-
-* a list of deliverables, quantifiable results for the Apache community,
-* a detailed description / design document,
-* an approach,
-* an approximate schedule and
-* something of a background text.
-
-We also need you to let us know what other commitments you
-have for the period of GSoC, for example, do you have any exams or a part
-time job? In other words - sell yourselves, as if this was an actual job.
-
-In drawing up your proposal you should work with your chosen projects
-community.
-
-One of our evaluation criteria is that you have already engaged
-with the community to ensure that you understand the needs of the project
-and the commitment you need to make to your mentors.
-
-Once open applications are made through the [GSoC site](https://summerofcode.withgoogle.com/)
-
-### Application template
-
-_This is just a suggested template, feel free to add and remove sections as appropriate. Be brief, don't write a large essay!_
-
-#### About me
-
-_What relevant experience have you got, including university, work and hobby activities?_
-
-#### Background
-
-_What exists already? What is the identified need? What can you reuse, what needs to he replaced?_
-
-_Example: Apache Foo has already got support for HTTP client requests, but this does not work well with OAuth-based services. The main interface for requests can be reused, but this project proposes to replace the backend code with a modular approach based on Apache Bar._
-
-#### Design / description of work
-
-_Brief list of things you will do / create, in some rough chronological order._
-
-_Show which bits are essential, and which are optional. Highlight what is new, what are modifications, and how your work fits into the existing architecture._
-
-_Example:_
-
-* _Investigate REST client libraries_
-* _Develop JavaScript functions for browsing files (optional)_
-* _Integrate with Apache Foo's request system (essential)_
-
-
-#### Results for the Apache community
-
-_Benefit of your work to Apache $Project users and developers. What will be the legacy of your work after you finish?_
-
-#### Deliverables
-
-_Including milestones, components, documentation, tests._
-
-#### Scheduling
-
-_Not too detailed, but some milestones and checkpoints. Rough estimates per work item (weeks/days). Remember to leave time for slack and bugfixing!_
-
-#### Other commitments
-
-_Exams, part time work, holidays, lectures._
-
-#### Community engagement
-
-_In particular with Apache $Project, including project mailing lists, wikis, issue trackers, test systems._
-
-_This should show a rough understanding of working with open source communities. You should be engaged with the rest of the community both before coding start (e.g. to develop this proposal) and during the project._
-
-_Include any planned user testing, prototypes, code review._
-
-
-
-<a name="GSoC-ContactingtheASF"></a>
-## Contacting the ASF
-
-The ASF is not just one project, it is a federation of projects, see the
-lists at [https://www.apache.org/](https://www.apache.org) and [https://incubator.apache.org/](https://incubator.apache.org/). Each of our
-projects has its own community of users, contributors and committers. GSoC
-students will usually be interacting with just one of these communities.
-
-Each of the proposed subjects (link to be provided if we are confirmed as a
-mentoring organisation) applies to a single ASF project. You will need to
-engage with that project community.
-
-Please contact dev@community.apache.org if you have questions/difficulties.
-
-<a name="GSoC-ASFGSoCTimeline"></a>
-# ASF GSoC 2023 Timeline
-
-Below is a timeline of events for The Apache Software Foundation's
-involvement in GSoC. Unless otherwise stated deadlines are 24:00 UTC on the
-date indicated.
-
-<a name="GSoC-StudentApplicationandSelection"></a>
-## Student Application and Selection
-
- - 2023-02-22: Potential GSoC contributors discuss application ideas with mentoring organizations
- - 2023-03-20: GSoC contributor application period begins
- - 2023-04-04: GSoC contributor application deadline
- - 2023-04-22: Proposals to ASF projects must be reviewed roughly and have a potential mentor so that we know how many slots to request. Proposals that don't have a mentor at this point will be down-rated.
- - 2023-04-26: Proposal scoring must be completed. Proposals without a score will be rejected, no exceptions.
- - 2023-05-04: Accepted student proposals announced on the Google Summer of Code site.
-
-<a name="GSoC-GSocisunderway"></a>
-## GSoC is underway
-
- - 2023-05-04: Community bonding start
- - 2023-05-28: Community bonding end
- - 2023-05-29: Coding start
- - 2023-07-10: Mentors and GSoC contributors can begin submitting Phase 1 evaluations
- - 2023-07-13: Phase 1 Evaluation deadline (standard coding period)
-
-<a name="GSoC-Winddown"></a>
-## Wind down
-
- - 2023-08-21: GSoC contributors submit their final work product and their final mentor evaluation (standard coding period)
- - 2023-08-28: ASF Mentors evaluations can be submitted
- - 2023-09-03: ASF Mentors final evaluations deadline
- - 2023-09-05: Initial results of Google Summer of Code 2023 announced
-
-<a name="GSoC-Extended"></a>
-## Extended coding period
- - 2023-09-04: GSoC contributors with extended timelines continue coding
- - 2023-11-05: Final date for all GSoC contributors to submit their final work product and final evaluation
- - 2023-11-12: Final date for mentors to submit evaluations for GSoC contributor projects with extended deadlines
-
-<a name="GSoC-Vouching"></a>
-# Organization Vouching
-
-The ASF currently has no policy establishing the criteria on what basis to vouch for another organization. Until one is established the ASF therefore doesn't vouch for any organization.
-
-<a name="GSoC-UsefulLinks"></a>
-# Useful Links
-
- * [Summer of Code home](https://summerofcode.withgoogle.com)
- * [Official Google Summer of Code 2023 Timeline, FAQs](https://developers.google.com/open-source/gsoc/timeline)
- * [GSoC discussion list](https://groups.google.com/group/google-summer-of-code-discuss)
- * [Python notes on expectations](https://wiki.python.org/moin/SummerOfCode/Expectations)
- * \#gsoc on Freenode
diff --git a/source/gsoc/experiences.md b/source/gsoc/experiences.md
deleted file mode 100644
index 6f69886..0000000
--- a/source/gsoc/experiences.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Apache in GSoC
----
-
-*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
- * Students who passed midterm: 40
- * 26 projects mentoring (17 TLPs and 9 Podlings)
- * Participating TLPS are: Xerces, Pig, OODT, Hive, James, Tapestry, Ofbiz,
-Gora, Synapse, Derby, Axis, POI, Whirr, Lucene, Velocity, Libcloud, Xalan
- * Participating Podlings are: ODF Toolkit, Airavata, Stanbol, Photark,
-Wookie, OpenMeetings, Nuvem, Hama, VXQuery
-
-## 2012 Blogs
-
- * [Scott Wilson: Wookie Mentor][1]
- * [Pushpalanka: Wookie Student][2]
- * [Mike McCandless: Lucene Mentor][3]
- * [Bhathiya Jayasekara: Airavata Student][4]
- * [OpenMeetings Mentors: Sebastian Wagner, Alexei Fedotov, Maxim Solodovnik - Students: Ankur Ankan, German Grekhov, Dmitry Zamula, Josh Dolitsky ][5]
-
-
-# 2011 Overview
-
- * Students accepted: 40
- * Students who passed midterm: 38
- * Students who passed final: 36
-
-# 2010 Overview
-
- * Students accepted: 44
- * Students who passed final: 39
-
-# 2005
-
-First year Apache participated
-
- [1]: https://scottbw.wordpress.com/2012/08/22/wookie-adds-support-for-signed-widgets-thanks-to-google-summer-of-code/
- [2]: https://pushpalankajaya.blogspot.com/search/label/GSoC
- [3]: http://blog.mikemccandless.com/2012/08/lucenes-new-blockpostingsformat-thanks.html
- [4]: https://summerwithairavata.blogspot.com/
- [5]: https://blogs.apache.org/openmeetings/entry/google_summer_of_code_2012
diff --git a/source/gsoc/gsoc-admin-tasks.md b/source/gsoc/gsoc-admin-tasks.md
deleted file mode 100644
index 729c61e..0000000
--- a/source/gsoc/gsoc-admin-tasks.md
+++ /dev/null
@@ -1,152 +0,0 @@
----
-title: GSoC admins
----
-
-A comprehensive guide to being a GSoC admin for the ASF
-
-List of duties:
-
-1. 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). Have
-prospective mentors subscribe to `mentors@community.apache.org`. The following is an email sent to `pmcs@a.o`
-explaining the procedures to them:
-
-<pre>
-Hello PMCs,
-
-Google Summer of Code is the ideal opportunity for you to attract new
-contributors to your projects.
-
-If you want to participate with your project you now need to
-
- - understand what it means to be a mentor [1]
- - propose your project ideas. Just label your issues with gsoc2023 in Jira and
- they will show up at [2]. See also [1].
- - subscribe to mentors@community.apache.org (restricted to potential mentors, meant to be used
- as a private list - general discussions on the public
- dev@community.apache.org list as much as possible, please)
-
-The ASF has applied as a participating organization with GSoC, so your project
-doesn't need to do that. See [3] for more information. Note that the ASF isn't
-accepted yet; nevertheless you *really* should start recording your ideas now.
-
-Last year we had XX students complete GSoC successfully, some of whom are
-now active contributors to the projects they worked on. Let's make this a
-success again this year!
-
-On behalf of the GSoC 20XX admins,
-
-Uli
-
-[1] https://community.apache.org/gsoc/guide-to-being-a-mentor.html
-[2] https://s.apache.org/gsoc2011tasks
-[3] https://community.apache.org/gsoc/
-</pre>
-
-1. Update our GSoC pages at [https://community.apache.org/gsoc/](/gsoc/) with the
-current year's timeline and at [https://community.apache.org/gsoc/guide-to-being-a-mentor.html](guide-to-being-a-mentor.html).
-
-1. Apply for the ASF to be a mentoring organization for Google Summer of Code.
-I faintly remember that they wanted to know some stats like how often we have
-already participated and what the number of students was last year. I believe
-the ASF has participated since GSoC's inception in 2005. Consult [participation statistics](http://community.apache.org/gsoc/experiences.html), although the page may not be up to date.
-
-1. Once our application is accepted, write a press release and
-request press@ to send it out. We don't have a template yet, so work
-with th `dev@community.apache.org` and `press@apache.org` lists to get one
-written and add it here.
-
-1. Check with Google whether they changed the ranking process -- again. Find out
-what we need to be change to our internal ranking process in order to be compatible
-with melange (the system Google uses to administer GSOC) and update the [mentee ranking process](mentee-ranking-process.html) page
-accordingly. In 2011 we used a Google Docs spreadsheet and did our ranking there. The
-org admin (and only the org admin) then transferred the rankings to Melange.
-
-1. Once the application phase starts, make sure that mentors rank the proposals. They
-should complete this at least one week before Google's official deadline in order to have
-some time for changes that might become necessary. Send reminders.
-
-1. Once Google has assigned our slots and we know who is accepted,
-mail each mentee with details of the `dev@community.apache.org` list, which they can
-use for general assistance with the ASF. They should seek project-specific
-assistance on the project's `dev` list. We don't have a
-template for this yet. Please add it here when one is written.
-
-1. Once GSoC is under way, make sure we meet deadlines for midterm and final evaluations. Make it clear to the mentors that we'd like to see their evaluation way before
-the end of the deadline. If a mentor still hasn't submitted their evaluation three days
-before the end of the deadline period, mail their PMC and ask them whether they know of
-any reason why the mentor might not be able to do the evaluation.
-
-1. Once GSoC is done, get a PO# from Google to invoice against. Supplier name is The
-Apache Software Foundation, 1901 Munsey Drive, Forest Hill, MD 21050-2747. Our vendor ID
-with Google is 13039.
-
-1. Issue a press release congratulating those who have passed and
-thanking our wonderful mentors. We should invite everyone to come and
-contribute to ASF projects. We should include some stats such as the
-number of full committers resulting from GSoC, the number of issues
-closed etc. We don't have a template yet but work with the
-`dev@community.apache.org` and `press@apache.org` lists to get one written
-and add it here.
-
-1. Decide who is going to the mentor summit. If you are going, book your flight (or arrange the details for attending virtually) and
-nag the comdev PMC chair to submit your travel expenses to financials/Bills/received (if
-you don't have access yourself) and move them to `financials/Bills/approved`.
-
-1. Ask treasurer to invoice Google. The amount is number of students * USD 500 (at time
-of writing) + actual travel expenses up to USD 2,000. Attach PO document (you'll get that
-from Google at some point). Example:
-
-<pre>
-Geir,
-
-please invoice Google the following, according to attached purchase order:
-
-40x Google Summer of Code 2011 mentor stipends for 40 student á USD 500.00 = USD 20,000.00
-1x travel expenses for mentor summit participant Noirin Plunkett = USD 743.70 (see [1], [2], [3])
-1x travel expenses for mentor summit participant Ulrich Stärk = EUR 834.03 = USD 1190,91 @1.4279
-USD/EUR as of 2011/08/09 (see [4] and [5])
-
-PO# is 132387, vendor ID is 13039
-
-The payment process to follow is:
-
-Payment Process - Step Two
-
-Once you receive your Purchase Order via email, you can then bill Google for your mentoring
-organization's payment. In order to receive payment, please send a PDF invoice to p2phelp@google.com
-and cc carols@google.com on the message.
-
-Your invoice *must* include the following information:
-
- 1. Name and address of your organization - official letterhead is preferred if available, must
-match supplier enrollment
- 2. Line(s) stating what the money is for e.g. "For mentoring 3 Google Summer of Code students for
-the Foo project"
- 3. It is likely most useful to simply mirror the wording on the Purchase Order you receive
- 4. If you have purchased flights for the mentor summit, invoice only for the amount paid for
-airfare or driving mileage (55 cents/mile, locals only)
- 1. Amount of payment in USD
- 2. Your invoice MUST include the PO#.
- 3. Your invoice MUST be dated after the issue date of your PO number
-
-
-
-Google has to receive the PDF invoice by November 4th, 2011 and it has to include PDF copies of our
-actual travel expenses, i.e. [2],[3],[4] and [5].
-
-Thanks,
-
-Uli
-
-
-[1] https://svn.apache.org/repos/private/financials/Bills/approved/Noirin-GSoC/README
-[2] https://svn.apache.org/repos/private/financials/Bills/approved/Noirin-GSoC/Noirin-GSoC-Amtrak.pdf
-[3] https://svn.apache.org/repos/private/financials/Bills/approved/Noirin-GSoC/Noirin-GSoC-Delta.pdf
-[4] https://svn.apache.org/repos/private/financials/Bills/received/Uli-GSOC-flights.txt
-[5]
-https://www.oanda.com/currency/historical-rates-classic?date_fmt=us&date=08/09/11&date1=08/09/11&exch=EUR&exch2=EUR&expr=USD&margin_fixed=0&format=HTML&redirected=1
-
-</pre>
diff --git a/source/gsoc/guide-to-being-a-mentor.md b/source/gsoc/guide-to-being-a-mentor.md
deleted file mode 100644
index 1abe6db..0000000
--- a/source/gsoc/guide-to-being-a-mentor.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: guide to being a mentor
----
-
-<!--
-Note: This document is bout GSoC, not about a generic Mentoring Program.
--->
-
-<a name="guidetobeingamentor-Submittingideastothementoringprogramme"></a>
-# 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](use-the-comdev-issue-tracker-for-gsoc-tasks.html). We are looking for as many interesting projects as we can come up with.
-
-<a name="guidetobeingamentor-Summary"></a>
-## 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](use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html)
- * Add sub-tasks if necessary
-* Label the main issue with "*mentor*" (these will show up at the [ASF-wide list of issues](https://issues.apache.org/jira/issues?jql=labels%20in%20(gsoc2023)%20AND%20labels%20in%20(mentor,%20Mentor)))
-* Label the main issue with "*gsoc2023*" if appropriate (these will show up at [GSoC 2023 Ideas](https://s.apache.org/gsoc2023ideas))
-
-<div class="card border-success mb-3">
- <div class="card-header">Size of project</div>
- <div class="card-body text-success">
- <p class="card-text">Starting this year there are 2 types of projects available.<br> Please put "<em>full-time</em>" label for ~350 hours project and<br> "<em>part-time</em>" label for ~175 hours project</p>
- </div>
-</div>
-
-Please NOTE Ideas list is manually updated by GSoC admins, please ping mentors (at) community.apache.org if the page is not being updated .. :))
-
-<a name="guidetobeingamentor-Detail"></a>
-## Details
-
-To ensure we include your Jira issues in our list of mentored projects,
-please add the label "mentor" to the issue. If you want it to be included
-in the Google Summer of Code lists also add the "gsoc" label. If you want
-to include a number of issues in a single mentored project, please create a
-parent issue, label that one appropriately and add the other issues as
-sub-tasks. Do not label each individual sub-task as that would make them appear as
-separate tasks.
-
-If you have identifed a mentor, assign the issue to that
-mentor.
-
-ASF Members and committers can volunteer to mentor or co-mentor proposals.
-When in doubt about all this, contact `mentors@community.apache.org`.
-
-For more information about what it means to be a mentor and on how to write
-a proposal, see:
-
- - [GSoC Mentoring Guide](https://developers.google.com/open-source/gsoc/resources/guide#mentor_guide)
- - [Gnome HowTo on mentoring](https://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/)
- - [How to be a lazy but successful Google SoC mentor](https://ploum.net/221-how-to-be-a-lazy-but-successful-googlesoc-mentor/)
-
-Note that interest, even by a qualified student, does not mean that any of
-those project will automatically go ahead. Depending on the number of
-projects; the number of people able to mentor, and the timing we will
-probably have to make a smaller selection.
-
-<a name="guidetobeingamentor-Publicisingyourmentoredissues"></a>
-### Publicising your mentored issues
-
-You can link to the [ASF wide list of issues](https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12315361)
- or you can create your own lists and feeds within your own website.
-
-Since your mentored issues appear alongside your normal Jira issues, you
-can create and use filters to help people find them. You can provide RSS
-feeds, JSON exports and many more goodies for helping to get the message
-out.
-
-If you have any cool ideas for using this data, let us know so we can
-share them with other projects (mail `dev@community.apache.org`).
-
-<a name="guidetobeingamentor-Examples"></a>
-## Examples
-
- - [Wookie GSoC Issues](https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12315360)
- - [Wookie RSS GSoC feed](https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-rss/12315360/SearchRequest-12315360.xml?tempMax=1000)
- - [Wookie XML GSoC feed](https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12315360/SearchRequest-12315360.xml?tempMax=1000)
-
-<a name="guidetobeingamentor-Stayingintouch"></a>
-# Staying in touch
-
-All mentors/prospective mentors **must** subscribe to `mentors@community.apache.org`, our list for
-coordinating mentor activities.
-This is where mentor specific issues are dealt with, and where announcements will be made.
-
-We only accept subscriptions to mentors@ from addresses known to
-belong to ASF committers, so please use your @apache.org address to
-subscribe if possible, or at least an address that we can match to your
-`@apache.org` address via the ASF's private/committers/info or
-private/committers/MailAlias.txt data.
-
-Once the ASF is confirmed as a mentoring organisation mentors must register
-with the GSoC webapp, and request to become a mentor for the ASF organization.
-Make sure that the email address you use for that (it’s often your @gmail.com address by default)
-is ‘‘‘registered as a mail alias for your Apache account at (https://id.apache.org)’’’
-so that we can match it to your ASF account.
-
-If you are interested in mentor programme administration please also
-subscribe to `dev@community.apache.org`.
-
-If you are planning on mentoring as part of the GSoC programme you also
-need to register with Google. See our [GSoC](/gsoc/) page for more information.
-
-<a name="guidetobeingamentor-Howmucheffortisinvolvedwithbeingamentor"></a>
-## How much effort is involved with being a mentor?
-
-Most mentors spend between three and five hours per week with their students. Most
-of this time is spent encouraging them.
-
-Within the ASF we like to think that the whole project community will help
-the student, just as they would any other community member. If your
-project is supportive in this way, you may be able to get away with spending
-less time yourself. However, as mentor _you_ are responsible for evaluating the
-student and helping them deliver on their commitments.
-
-The [GSoC Mentoring Guide](https://developers.google.com/open-source/gsoc/resources/guide#mentor_guide) has plenty of useful materials for mentors.
-
-<a name="guidetobeingamentor-Anoteabouteligibility"></a>
-## A note about eligibility
-
-If your project has any restrictions on who can participate (as is the case
-with Harmony, for example) be sure to clarify these with potential
-students as early as possible. It causes unnecessary confusion and
-disappointment if a student is awarded a slot but is later found to be
-ineligible. Don't rely on the fact that the student should have read
-details on the project web site. You must discuss their eligibility before
-offering to mentor them. Also make a note in the webapp stating that
-you have, as far as possible, confirmed the student is eligible to
-contribute.
diff --git a/source/gsoc/mentee-ranking-process.md b/source/gsoc/mentee-ranking-process.md
deleted file mode 100644
index a531b17..0000000
--- a/source/gsoc/mentee-ranking-process.md
+++ /dev/null
@@ -1,214 +0,0 @@
----
-title: Mentee Ranking Process
----
-
-This page describes the ranking process The Apache Software
-Foundation uses to evaluate mentee proposals.
-
-The ranking process makes sure the most promising
-applicants get a mentor with an ASF project. The goal is *not* to
-identify the "best" projects for the ASF, but the best mentees who have
-applied to the ASF.
-
-Remember, mentoring is all about the mentee and open source as a whole. It
-is not about the mentors or their projects.
-
-Any ASF committer can help with the ranking: all you need to do is register
-as a potential mentor (you don't actually have to _become_ a mentor).
-
-The instructions below described ranking proposals using the Google Summer
-of Code application.
-
-<a name="MenteeRankingProcess-ScoringSystem"></a>
-# Scoring System
-
-We rank projects using this scoring system:
-
-## *Pre-Selection Phase* : a mentor does this when accepting to be mentor of a given proposal
-
-* if the proposal is for a project you will be mentoring and you feel the
-proposal looks good enough for you to commit your time to it, click the
-"I am willing to Mentor" button in Melange (the software that administers the Google Summer of Code).
-
-Please only offer to mentor a single project unless you have discussed why you should mentor more than one on
-mentors@community.apache.org first. We encourage multiple mentors per project, though.
-
-Other community members are free to comment on proposals as they see fit.
-In the re-evaluation phase (see below) admins use
-comments provided by mentors and community members.
-
-##*Selection Phase* : a mentor does this during ranking time
-
-In this phase mentors evaluate each proposal. We do all scoring in the Google Docs spreadsheet shared on
-mentors@community.apache.org. Add an explanation to every score, using the criteria below, to help admins in the later stages of evaluation.
-DO NOT ADD SCORES IN MELANGE! Use integer numbers only!
-
-_Please do not add scores outside these criteria._
-
-Address any questions to the admins on mentors@community.apache.org
-
-* Did the student demonstrate that they have the required skills to start
-the project and learn what's needed along the way? And how happy are we
-with the results? (0-4 points)
-
-* How do we rate the quality of the student's proposal, in terms of
-technical relevance, completeness, awareness of issues, and realistic planning
-(less copy and paste)? (0-4 points)
-
-* How does the mentor rate the student's chances of success, based on an
-in-person (face-to-face, video, audio, IRC, email) interview? (0-3 points, or
-0-1 if email interview only)
-
-* How do we rate the originality of the student's contributions to the
-proposal? (0-2 points: 0 if mentor provides proposal, 1 if student builds
-proposal from suggested ideas, 2 if proposal is original idea from student)
-
-* Did the student work with the project community, on our public mailing lists,
-to create the proposal? (0-2 points)
-
-* Did the student explicitly indicate how much time they are going to dedicate
-to GSoC for the project's duration, and mention any other committments that
-could conflict with the project (holidays, course work, etc.)? Are we happy with
-this commitment (it should be their major occupation during the summer)? (0-2 points)
-
-* Did the student respond quickly to mentor inquiries? (0-2 points)
-
-* Are you or your student affiliated in any way (e.g. share(d) the same employer or will do so in the foreseeable future, are
-you their adviser at university, personal relationships, etc.)? (yes/no)
-
-
-Other community members are free to comment on proposals inside Melange as they see fit.
-However, DO NOT ADD A SCORE TO THE PROPOSAL. In the re-evaluation phase (see below) admins use
-comments provided by mentors and community members.
-
-At the end of the selection phase proposals to be considered for support
-will have a score of between 0 and +19, and should only have scores from
-the assigned mentor and admins (at this stage admin scores are only
-corrections). The admins check in periodically during the selection phase
-to look for problems by scanning the scores (i.e. anything
-over +19 has an error).
-
-At the end of this selection phase we know the minimum score a proposal
-must have in order to be selected (i.e. if we have 30 slots, projects with
-a score at or above the project ranked 30th will go forward to the next
-phase). Before progressing to the next phase, admins read all proposals
-above or near the minimum score and ensure that there are no errors
-in this phase of ranking.
-
-## *Re-Evaluation* : admins do this during or after selection phase
-
-In this phase admins evaluate all proposals above the required score and
-those that are just below it. We check those just below the required score
-to ensure that the scores have been equally assigned across all proposals
-(some mentors are more generous than others).
-
-* Has the mentor fully engaged with the student during the writing of the
-proposal? (0-4 points)
-* Does the mentor show an understanding of how to mentor a student? (0-4
-points)
-* Discretionary score: admins may use their experience and the comments of
-community members to mark a proposal up or down (-4 to +4).
-* Admin discretionary points (-10 to +10 points, only used to break
-"deadlocks" across the cut-off point, see below).
-
-The admins transfer the scores to Melange.
-
-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.
-
-<a name="MenteeRankingProcess-Whatarewelookingforinagoodproposal?"></a>
-# What are we looking for in a good proposal?
-
-In general we much prefer new mentees to repeat mentees. The goal is to
-enable new people to learn about open source software development.
-
-In past years we have seen some consistent patterns in high-quality proposals:
-
-* Detailed proposal with realistic and measurable milestones
-* Engagement with the project communication during proposal writing
-* Willingness to engage with the ranking process (i.e. responding to
-requests for more info)
-* Acknowledgment of weaknesses in existing skill set and a plan for
-addressing those weaknesses
-
-<a name="MenteeRankingProcess-Warningsignsinabadproposal"></a>
-# Warning signs in a bad proposal
-
-* No engagement with project community
-* Lack of understanding of what open source is and how it is developed
-* Indication of external commitments (exams, job etc.)
-* Previous failures within the mentor programme
-
-<a name="MenteeRankingProcess-Whathappensnext?"></a>
-# What happens next?
-
-Towards the end of the ranking period Google announces how many slots
-the ASF has. Shortly after that we ask ASF committers to
-stop ranking, and the ASF GSoC admins adjust the rankings to
-ensure that the right number of projects are ranked above the cut-off line.
-
-In this last stage we avoid adjusting community rankings; however, in past
-years there has been a cluster of students with equal rankings around the
-cut-off point. In this case the admins cast a final vote on those
-projects to ensure that Google can assign awards as appropriate.
-
-For example, imagine that 7 is the number of points that causes the
-clustering, and we have the following projects ranked at 7:
-
-# A
-# B
-# C
-# D
-# E
-
-Now imagine the cut-off point for selection is currently at the third
-position (C).
-
-The admins need to look at these projects and ensure they are ordered in the
-webapp to make the most appropriate appear at the top of the list. This
-ensures that they are most likely to receive a slot. So we may end up
-with:
-
-# B
-# C
-# A
-# E
-# D
-
-Unfortunately this process needs to happen very quickly and there is no
-time for community discussion around these points. Therefore it is
-important that mentors and mentees provide as much information in the
-previous ranking stages as possible.
-
-The problem becomes a little more complicated when we remember that the
-cut-off point may move as well, so Google may give us one extra slot. So we
-need to ensure that all rank-7 projects are correctly ordered, not just the
-best.
-
-<a name="MenteeRankingProcess-Theprocessofbreakingclusters"></a>
-## The process of breaking clusters
-
-Admins work through all applications, adding a +8 to all those ranked above
-the cut off score. This has the effect of increasing the "space" we have to
-work with in re-ranking the clustered projects.
-
-Admins then work through all the clustered applications, adding scores as
-defined above (with a comment justifying the ranking).
-
-If there is still a cluster of projects around the cut-off point, the
-lead admin looks at the mentors and projects involved. If a project/mentor
-already has a higher scored application, the lead admin reduces the
-score for this one (i.e. to try to spread the love).
-
-It's not practical to ask the community to comment at this point as we are
-on a tight deadline. We ask that the community trust the assigned admins.
-
-<a name="MenteeRankingProcess-Resolveconflicts"></a>
-# Resolve conflicts
-
-Inevitably there will be one or two students who have been accepted in
-multiple organizations. We resolve these conflicts during an IRC meeting with Google
-admins during the final hours of ranking. In these cases the admins
-attempt to contact mentors and students; but we sometimes have to make a
-judgment call on how to best resolve such conflicts, as things happen quite
-fast during this meeting.
diff --git a/source/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.md b/source/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.md
deleted file mode 100644
index b8f86df..0000000
--- a/source/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Use the Comdev Issue Tracker For GSoC Tasks
----
-
-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](https://issues.apache.org/jira/browse/GSOC)
-* Ensure you add the labels `gsoc2023`, `mentor` and `_YOUR_PROJECT_NAME_`
-* Your issues will appear in the [list of projects](https://s.apache.org/gsoc2023ideas)
-* 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.apache.org if you have questions/difficulties.
-
-You can then link to the task tickets from your own site and access XML, RSS feeds.
diff --git a/source/history/boardresolution.md b/source/history/boardresolution.md
deleted file mode 100644
index 1bafe0c..0000000
--- a/source/history/boardresolution.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: ComDevBoardResolution
----
-The Apache Community Development Project was created in November 2009.
-
-
-<div class="code panel" style="border-style: solid;border-width: 1px;">
- <div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;">
- <b>Board Resolution Creating the Apache Community Development Project</b>
- </div>
-
- <div class="codeContent panelContent">
-
- Establish the Apache Community Development Project
-
- 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", be and hereby is established
- pursuant to Bylaws of the Foundation; and be it further
-
- RESOLVED, that the Apache Community Development Project
- be and hereby is responsible for helping people become
- involved with Apache projects; and be it further
-
- RESOLVED, that the office of Vice President, Apache Community
- Development Project, be and hereby is created, the person
- holding such office to serve at the direction of the Board
- of Directors as the chair of the Community Development PMC,
- and to have primary responsibility for management of the
- projects within the scope of the Apache Community Development
- project; and be it further
-
- RESOLVED, that the persons listed immediately below be and
- hereby are appointed to serve as the initial members of the
- Apache Community Development Project PMC:
-
- * Ross Gardler <rg...@apache.org>
- * Luciano Resende <lr...@apache.org>
- * Santiago Gala <sg...@apache.org>
- * Bertrand Delacretaz <bd...@apache.org>
- * Ted Dunning <td...@apache.org>
- * Noirin Shirley <no...@apache.org>
-
- NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ross Gardler
- be appointed to the office of Vice President, Apache Community
- Development Project, to serve in accordance with and
- subject to the direction of the Board of Directors and
- the Bylaws of the Foundation until death, resignation,
- retirement, removal or disqualification, or until a successor
- is appointed; and be it further
-
- RESOLVED, that the initial Apache Community Development PMC
- be and hereby is tasked with the creation of a set of bylaws
- intended to encourage open participation in the Apache
- Community Development Project.
-
- Special order 3A, establish the Apache Community Development Project,
- was approved by Unanimous Vote of the directors present.
-
- Furthermore, the board requested that this PMC take over the
- stewardship of the community@ and women@ mailing lists.
-
- </div>
-</div>
\ No newline at end of file
diff --git a/source/history/mentoringprogramme-icfoss-pilot.md b/source/history/mentoringprogramme-icfoss-pilot.md
deleted file mode 100644
index 6554645..0000000
--- a/source/history/mentoringprogramme-icfoss-pilot.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: Pilot Mentoring Programme with India ICFOSS
----
-
-> 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 mentoring programme is not here to teach you to write documentation or
-code. It is here to help you understand how to make a valuable contribution
-to an Apache project. You can expect to be guided through our contribution
-processes. You can also expect to get technical support with respect to
-your chosen project. You cannot expect your mentor to be a "teacher", they
-will provide enough information for you to progress within the project. You
-need to bring the confidence to take their guidance and discover the detail
-for yourself.
-
-<a name="Schedule"></a>
-## Proposed Schedule
-
-| Date | Description |
-| :--- | :--- |
-| June 20 | Local Workshop at ICFOSS headquarters in Kerala - India |
-| June 24 - July 12 | Would-be student participants discuss application ideas with ASF projects |
-| July 15 | Students project proposal submission opens |
-| July 19 | Students project proposal submission deadline |
-| July 22 - August 02 | Mentors review and rank students project proposals |
-| August 05 | Accepted student proposals announced |
-| August 05 | Students start coding their project proposal with Mentor guidance |
-| September 09 | Mentors and students can begin submitting mid-term evaluations |
-| September 13 | Mid-term evaluation deadline |
-| October 21 | Suggested 'DCUT' date, where students should then scrub code, enhance documentation, etc |
-| October 28 | Mentors and students can begin submitting final evaluations |
-| November 1 | Final evaluation deadline |
-
-<a name="MentoringProgramme-WorkshopMaterials"></a>
-## Workshop Materials
-
-The slides used for the local workshop at ICFOSS headquarters in Kerala are available for [download](https://people.apache.org/~lresende/presentations/asf-icfoss-mentoring.pdf).
-
-
-<a name="MentoringProgramme-ProjectIdeas"></a>
-## Project Ideas
-
-Project ideas are jira created by possible mentors and can be viewed at:
-
-
-+ [2013 ICFOSS Programme Project Ideas](https://s.apache.org/icfoss2013ideas)
-+ [2013 GSoC Project Ideas](https://s.apache.org/gsoc2013ideas)
-
-
-<a name="MentoringProgramme-ApplyingfortheMentorProgramme"></a>
-## Applying for the Mentor Programme
-
-Students can propose their own project ideas, or select one from the ASF provided list. After selecting the project ideas. students should create a project proposal following guidance from the **mentor** and the **project community**.
-
-The project proposal should have, at minimum :
-
-+ **WHAT** Detailed description of the what is being implemented as part of the project.
-+ **HOW** How the project is going to be implemented. Here you would describe your approach towards solving the problem, as well as technical details (which shows to the mentor that you have a clear idea of what needs to be implemented). High level system design diagrams is a plus.
-+ **WHEN** A detailed schedule of what tasks you are going to implement by when.
-
-See the proposals examples below as guidance:
-
-+ [Searching artifact across SCA Domains](https://cwiki.apache.org/confluence/display/TUSCANYWIKI/Searching+artifacts+across+SCA+domain)
-+ [GIMPLE to GRAPHITE transformation](http://students.fim.uni-passau.de/~grosser/gcc_soc/)
-+ [Nmap Scripting Engine – Infrastructure Manager](http://opendz.org/users/tixxdz/gsoc/gsoc_2010_proposal_nmap_scripting_engine_short_version.pdf)
-
-Note that the proposals below are just examples from previous GSoC programs, and each one have different strengths. But you should always follow your mentors advice, as he is the one that is going to be judging your proposals.
diff --git a/source/links.md b/source/links.md
deleted file mode 100644
index 553fc88..0000000
--- a/source/links.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Links
----
-
-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][1] - by Karl Fogel
-
-# Blog posts
-* [Apache - the Switzerland of Open Source?][2] - by Bertrand Delacretaz
-* [Thinking Together][3] - by Phil Steitz
-
-# Slides
-* [Behind the Scenes of the Apache Software Foundation][4] - by Lars Eilebrecht (PDF)
-
-# Apache community members websites and links
-* [Shane's "the Apache Way"][5] - An Apache Way Primer by Shane Curcuru
-
- [1]: https://producingoss.com/
- [2]: https://grep.codeconsult.ch/2009/03/30/the-asf-is-the-switzerland-of-open-source/
- [3]: https://psteitz.blogspot.ch/2011/11/thinking-together.html
- [4]: http://archive.apachecon.com/eu2007/materials/asf-intro-slides-eilebrecht.pdf
- [5]: http://theapacheway.com/
-
diff --git a/source/lists.md b/source/lists.md
deleted file mode 100644
index 3425840..0000000
--- a/source/lists.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Community Development Mailing Lists
----
-
-Almost everything and everyone at Apache use email lists to get work done, including this Community Development project right here! When people
-send email to a list, many other community members get the message, and
-someone usually provides a useful reply. Every email list at Apache is archived: most lists are
-[archived publicly][1]. That means that newcomers to a community can learn how
-decisions on a project have been made in the past, because all the email discussions
-a project has had are archived.
-
-If you have questions about anything at Apache, the first thing to do is
-find the right mailing list - and then send your question!
-
-# Read This First
-
-[Detailed instructions][2] on how to use Apache email lists (subscribing, sending
-email, reading the archives, and other technical steps) are available on our main developer site. You can email most
-lists without subscribing, but some lists require that you subscribe first. Most emails
-are moderated, so they won't show up on the list immediately. You may need to wait
-a day, especially if you are new.
-
-Please be sure your [question is on topic for the list][3], and that you have at
-least checked the relevant documentation first. Everyone at Apache is a volunteer,
-and if you don't do your homework, we probably can't help you.
-It's also best to follow our [email etiquette guidelines][4].
-
-# Find The Right Email List
-
-Finding the right list helps get your question in front of people who will know
-the answer. Each project at Apache uses their own dev@, user@, and
-other email lists - so asking about Apache Tomcat on the Apache Cassandra
-lists is likely going to be ignored.
-
-Most projects have a `Mailing Lists`, `Community`, or `Contact Us` link on their homepage,
-so start there if you know which project you're asking about. If you don't know which
-kind of list to ask on, consult our full list of all [Apache-wide mailing lists][5].
-
-If you have **any non-technical questions** - or a question for us here in community
-development - ask here by sending email to **`dev@community.apache.org`**!
-You can also [read the archives of our dev@community][6] email list to see what other people have asked and learned.
-
-# Read The List Archives
-
-Almost every list at Apache is archived publicly. Browsing the archives is a great way to learn about
-how a community has done things in the past, or to learn about *why* a project
-operates the way they do. The ASF maintains an official archive and allows both
-browsing and searching through all public email archives:
-
- * [https://lists.apache.org/](https://lists.apache.org/)
-
-Several other organizations also archive many/most Apache email lists, and some
-offer useful search or sending functionality:
-
- * MarkMail [https://apache.markmail.org/](https://apache.markmail.org/) - natural language search
- * MARC [https://marc.info/](https://marc.info/)
- * The (old) Mail Archive [https://mail-archive.com/][7]
- * GMANE [http://gmane.org/](http://dir.gmane.org/search.php?match=apache)
-
-
- [1]: https://www.apache.org/foundation/public-archives.html
- [2]: https://www.apache.org/dev/#mail
- [3]: https://infra.apache.org/contrib-email-tips
- [4]: /contributors/etiquette
- [5]: https://www.apache.org/foundation/mailinglists.html
- [6]: https://lists.apache.org/list.html?dev@community.apache.org:lte=12M:
- [7]: https://mail-archive.com/search?l=all&q=apache&e=listname
diff --git a/source/mentor-request-mail.md b/source/mentor-request-mail.md
deleted file mode 100644
index 0eec8a9..0000000
--- a/source/mentor-request-mail.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: "How To: Write A Mentor Request Email"
----
-
-Having identified a Top Level Project (TLP) and an issue you would like to work on, it is a
-good idea to introduce yourself to the project community and outline your
-plans for tackling the issue. This 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).
-
-Here's an example of what your first email might look like:
-
-```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
-```
-
-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
-the community might point out that there is a widget template
-system that would need modification to use this format consistently.
diff --git a/source/mentoring/_index.md b/source/mentoring/_index.md
deleted file mode 100644
index 121fa93..0000000
--- a/source/mentoring/_index.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Mentoring
-url: /mentoring/
----
-
-# Mentoring
-
-A major job of Community Development is mentoring. Mentoring is the
-process of actively bringing someone along in a discipline - investing
-your time into influencing the future. Time spent mentoring today will
-pay off for years to come.
-
-Anyone can be a mentor. You just have to take a moment to encourage
-someone else to participate.
-
-Here's some concrete ways you can provide mentoring to other members of
-your community.
-
-- [GSoC](/gsoc/)
-- [Participate in the incubator](https://incubator.apache.org/)
-- [Walk a beginner through their first patch](/mentoring/firstpatch.html)
-- [Coach a new committer](/mentoring/committer.html)
-- [Take a new PMC member under your wing](/mentoring/pmc.html)
-- [Encourage someone to mentor someone else](/mentoring/mentor.html)
-
-
diff --git a/source/mentoring/committer.md b/source/mentoring/committer.md
deleted file mode 100644
index 48fc2e8..0000000
--- a/source/mentoring/committer.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: Mentoring a new committer
----
-
-# Mentoring a new committer
-
-So I'm a committer now. What's next? What rights do I have now that I
-didn't have before? What are the social conventions around making a
-commit?
-
-These things vary from one project to another, so clearly documenting
-them for your particular project is critical.
-
-Here's the basics that are true across (almost) all Apache projects.
-
-TODO
-
-Outline:
-
-* Encouraging other contributors
-* Good commit messages
-* Becoming a PMC member
-
diff --git a/source/mentoring/firstpatch.md b/source/mentoring/firstpatch.md
deleted file mode 100644
index 2218a68..0000000
--- a/source/mentoring/firstpatch.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: "Mentoring: First Patch"
----
-
-# 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
-
diff --git a/source/mentoring/mentor.md b/source/mentoring/mentor.md
deleted file mode 100644
index 9b02b63..0000000
--- a/source/mentoring/mentor.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Mentoring Mentors
----
-
-# 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
diff --git a/source/mentoring/pmc.md b/source/mentoring/pmc.md
deleted file mode 100644
index 3db9233..0000000
--- a/source/mentoring/pmc.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Mentoring a new PMC member
----
-
-# Mentoring a new PMC member
-
-So I'm a PMC member now. What does this mean? What rights do I have now
-that I didn't have before? What conversations belong on the private
-list, as opposed to the public list.
-
-These things vary a little from one project to another, so clearly
-documenting them for your particular project is critical. And
-specifically assigning a PMC mentor to new PMC members can greatly help
-that new member get up to speed, and prevent problems in the future.
-
-Here's the basic things that a new PMC member needs to know, and how you
-can help them in their new job.
-
-TODO
-
-Outline:
-
-* The PMC chair is not the project lead
-* Any PMC member can nominate committers, PMC members
-* Reporting
-* Responding to the Board
-* A word about vendor neutrality
-
-
diff --git a/source/newbiefaq.md b/source/newbiefaq.md
deleted file mode 100644
index e9533fa..0000000
--- a/source/newbiefaq.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-title: Apache Newcomer FAQs
----
-
-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](#NewbieFAQ-AboutTheApacheSoftwareFoundation)
- - [How do I find projects or technologies at the ASF?](#NewbieFAQ-WhatprojectscanIfindinTheApacheSoftwareFoundation?)
- - [How are projects managed at the ASF?](#NewbieFAQ-HowareprojectsmanagedinTheApacheSoftwareFoundation)
- - [How do I ask a question about the ASF in general?](#NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?)
- - [How do I get user support for an Apache project?](#NewbieFAQ-HowdoIgetusersupportforanASFproject?)
- - [Getting involved with Apache projects](#NewbieFAQ-GettingInvolvedwithApacheprojects)
- - [How do I choose an Apache project to work on?](#NewbieFAQ-HowdoIchooseanApacheprojecttoworkon?)
- - [How do I get involved with an Apache project?](#NewbieFAQ-HowdoIgetinvolvedwithanApacheproject?)
- - [Is there a Code of Conduct for Apache projects?](#NewbieFAQ-IsthereaCodeofConductforApacheprojects?)
- - [How do I suggest or make changes to this website?](#websitecms)
- - [What other useful websites about Apache are there?](#comdevweb)
- - [How do I report a bug for Comdev websites or tools?](#comdevbug)
-
-We are always looking for better ways to help newcomers to the ASF find
-the information they're looking for. Please ask questions or give us suggestions on
-[dev@community.apache.org](mailto:dev@community.apache.org) (subscribe by sending an email to
-[dev-subscribe@community.apache.org](mailto:dev-subscribe@community.apache.org) first).
-
-
-<a name="NewbieFAQ-AboutTheApacheSoftwareFoundation"></a>
-# About The Apache Software Foundation
-
-<a name="NewbieFAQ-WhatprojectscanIfindinTheApacheSoftwareFoundation?"></a>
-## What projects can I find in The Apache Software Foundation?
-
-There are over 350 separate projects and communities hosted at the Apache Software Foundation. We have
-three classes, or types, of project (in terms of their community, not in terms of technology):
-
- * [Top Level Projects](https://projects.apache.org) (TLPs): these are projects with healthy communities and active development; and supported software products you can find here: [listing by technologies](https://projects.apache.org/).
- * [Incubating Projects](https://incubator.apache.org): these are projects that have yet to build a sustainable community, but
-have active development and are moving towards graduating to become TLPs.
- * [Attic](https://attic.apache.org): these are end-of-life projects that are no longer receiving active
-development, but may still be useful.
-
-<a name="NewbieFAQ-HowareprojectsmanagedinTheApacheSoftwareFoundation"></a>
-## How are projects managed in the Apache Software Foundation?
-
-Apache project participants all believe that if we look after the community, good
-code will emerge from that community. That is, when people with similar
-needs come together, they will work out a way to solve their common
-problems. For this reason we created the Community
-Development project (where you are right now). The ASF has grown to be very
-large and, from the outside, can look too mature for newcomers and novices.
-However, these communities seek to be flat in structure. No single person
-in any community has more influence than the next; a newcomer with a good
-idea has just as much input and influence as the original creator of the
-project.
-
-We do have a system, _meritocracy_, that allows those who have
-demonstrated commitment and understanding to the community to earn certain
-privileges, such as being able to make changes directly to documentation
-and program code. However, these privileges simply streamline the
-process; they do not (in most cases) give additional powers over the
-project.
-
-In summary, Apache projects work because people like you participate
-constructively within them!
-
-To learn more about "The Apache Way" in general, see the [How it Works](https://apache.org/foundation/how-it-works.html)
- pages. We also have [detailed overviews of how the ASF and projects are governed](https://www.apache.org/foundation/governance/).
-
-<a name="NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?"></a>
-## How do I ask a question about the ASF in general? ## {#generalquestion}
-
-The Community Development Project is here for this very purpose. Check out
-the resources on this site first. If you don't find the answer to your question, send an email
-to `dev@community.apache.org` (subscribe first by sending an email to
-`dev-subscribe@community.apache.org`).
-
-<a name="NewbieFAQ-HowdoIgetusersupportforanASFproject?"></a>
-## How do I get user support for an ASF project?
-
-Everyone active in ASF projects is here as a volunteer. You need to be
-careful not to waste people's time, so do your homework. Generally, if
-people can see that you have tried to solve your problem before asking for help, they are more
-likely to respond. So, before asking a question, do the following:
-
-* Search that project's documentation
-* Search that [project's user@ mailing list archives](https://mail-archives.apache.org/mod_mbox/)
-* Search the project issue tracker for any related known issues
-* Search the web in general
-
-If you don't find a solution, send a concise, but detailed, request for
-support to the appropriate `users@` mailing list (you will usually need to
-subscribe first, by sending an email to `users-subscribe@`). Indicate that you have read the appropriate documentation
-and explain what you have tried, what you expect to happen and what
-actually happens. All Apache projects should have a "Mailing List",
-"How to Contribute" or similar link on their home page that tells you how to subscribe
-to that project's specific lists. Mailing lists at Apache are also
-[publicly archived][1] at the ASF and [elsewhere][2].
-
-Be patient waiting for a response: give it at least three working days
-before you send a second message. People are busy, and they will deal with your
-request when they can. If you need urgent help it is best not to rely on
-the community support channels, but to find an outside organization willing to support you for
-a fee. Remember that committers on Apache mailing lists are generally working as volunteers.
-
-It is worth noting that people are more willing to help those who
-contribute back to the project in some way. If you hit a problem that was
-not documented, it is likely others will, too. A good idea is to propose a
-patch to the project to improve its documentation. Then those
-who follow in your footsteps get an answer in the first step above and you
-start to build merit in the community that will result in further help in
-the future.
-
-A second way of contributing is to provide user support to others as your
-expertise grows. Again, earning merit in this way will help you to get
-the support you need in the future.
-
-
-<a name="NewbieFAQ-GettingInvolvedwithApacheprojects"></a>
-# Getting Involved with Apache projects
-
-<a name="NewbieFAQ-HowdoIchooseanApacheprojecttoworkon?"></a>
-## How do I choose an Apache project to work on?
-
-The key to working on projects at Apache (and any open source project, for that
-matter) is to have a personal reason for being involved. You might be
-trying to solve a day job issue, you might be looking to learn a new
-technology or you might simply want to do something fun in your free time.
-The key is that you must *want* to get involved. It is also important that
-you have appropriate skills to be able to help the project.
-
-Our [projects page](https://projects.apache.org/) provides a list of projects that you can sort alphabetically, by category or by language. When you view a project's details
-page you can find out about its mailing lists, issue tracker and other resources.
-
-In the project's issue tracker you will find details of bugs and feature
-requests the project would like help with. This should give you some
-inspiration about how you might be able to help the project community. If
-you see an issue you would like to tackle, it's time to join the project's
-mailing list and get started.
-
-<a name="NewbieFAQ-HowdoIgetinvolvedwithanApacheproject?"></a>
-## How do I get involved with an Apache project?
-
-You can improve your programming skills by watching the `commit`
-lists, receiving code reviews and participating in discussions. However,
-this learning opportunity is a healthy side effect of open source
-activities rather than a goal in itself. Nobody in an Apache project is
-going to spend time teaching you Programming 101, technical writing or
-testing (to mention just a few of the skills we need). You need to know the basics
-and be willing to research the rest.
-
-To learn more about getting involved with an Apache Project, see our [getting
-started guide][3]. You will also find our [get involved](https://apache.org/foundation/getinvolved.html) page a useful starting point.
-
-<a name="NewbieFAQ-IsthereaCodeofConductforApacheprojects?"></a>
-## Is there a Code of Conduct for Apache projects?
-
-Our code of conduct is posted at
-[https://www.apache.org/foundation/policies/conduct.html](https://www.apache.org/foundation/policies/conduct.html).
-The ASF expects that everyone participating on an Apache project, whether it be improving websites; contributing to email lists, bugtrackers, or forums hosted at `apache.org`; or contributing code will abide by our code of conduct.
-
-PMCs are allowed to define their own additional codes of conduct for their individual communities, but all PMCs are expected to abide by the Foundation-wide policy.
-
-The [Incubator document](https://incubator.apache.org/guides/committer.html) also
-has some really useful information for both the newbie and the
-old hands. The section on **ASF Mottos** is especially useful as a reminder of the way things are in most ASF
-projects. This section includes such gems as:
-
-* Put community before code.
-* Let them who do the work make the decisions.
-* If it didn't happen on a mailing list, it didn't happen.
-* Don't feed the trolls.
-
-# How do I suggest changes to this website? # {#websitecms}
-
-The content for the `community.apache.org` website is written in Markdown
-and published automatically using a [Jenkins job](https://builds.apache.org/job/comdev-site/).
-Any contributor is able to submit changes via pull requests. Comdev committers are able to merge
-proposed changes.
-
-Website sources are available via:
-- GitHub: https://github.com/apache/comdev-site
-- Gitbox: https://gitbox.apache.org/repos/asf/comdev-site.git
-
-For general questions you can [ask us on dev@community](#generalquestion)
-or read our [mailing list archives][7] for past questions and answers.
-
-For technical website details, see [About this Website][8].
-To submit a formal bug, see our [COMDEV JIRA](#comdevbug).
-
-# What else does Community Development publish or manage? # {#comdevweb}
-
-The Community Development project maintains several other tools
-that help you navigate the ASF.
-
- - The [Apache Projects Directory][9] lists all our software technologies, and you can learn [how it works][10] and what JSON data feeds are available.
- - [Home.apache.org][11] serves as a telephone directory of all Apache committers.
- - Apache committers can log in to the [Project Reporting Tool][14] that helps PMCs create quarterly board reports; you can [see the code that does this][15].
- - A [ComDev Wiki][wiki] is also available for scratch or experimental work, although most permanent content should be here in the website.
-
-# How do I report a bug for Comdev websites or tools? # {#comdevbug}
-
-The Community Development project has a Jira issue tracker queue where you
-can submit bug reports related to any of our services or websites.
-
- - [https://issues.apache.org/jira/browse/COMDEV](https://issues.apache.org/jira/browse/COMDEV)
-
-
- [1]: https://mail-archives.apache.org/mod_mbox/
- [2]: https://apache.markmail.org/
- [3]: /gettingStarted/101.html
- [7]: https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:
- [8]: /about/#about-this-website
- [9]: https://projects.apache.org/
- [10]: https://projects.apache.org/about.html
- [11]: https://home.apache.org/
- [14]: https://reporter.apache.org/
- [15]: https://svn.apache.org/repos/asf/comdev/reporter.apache.org/
-
-[wiki]: https://cwiki.apache.org/confluence/display/COMDEV/ComDev+Wiki
diff --git a/source/newcomers/_index.md b/source/newcomers/_index.md
deleted file mode 100644
index 6dde185..0000000
--- a/source/newcomers/_index.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Welcome, Apache newcomers!
-url: /newcomers/
----
-
-In this section we'll help you take your first steps as an open source
-developer in one of our many Apache project communities. As an all-volunteer
-run organization, Apache and the many Apache projects rely on people like
-you stepping up to help out.
-
- * [Where do I start?](/gettingStarted/101.html) - a guide to your first engagement with an Apache project
- * [How should I behave?](/contributors/etiquette) - etiquette and codes of conduct at Apache
- * [Newbie FAQ](/newbiefaq.html) - some commonly asked questions (and their answers)
- * [How many projects are at Apache?](https://projects.apache.org/) - we have a **LOT** of different project communities!
- * [Just show me the code!](https://www.apache.org/dev/) - site index of technical questions (where's SVN, how to log in, etc.)
-
-<a name="Index-FirstContributions"></a>
-# First Contributions
-
-*The more you give the more you get out*.
-
-It's natural to assume that, as a newcomer,
-you have little to offer the ASF. However, you will be surprised at
-how much you can help, even now.
-
-Since we aim to be a place for newcomers to learn
-about the ASF as a whole and you are (probably) a newcomer, *any feedback
-you can give or unanswered questions you can ask us here* will help us improve what
-we offer to those who come after you. Our [etiquette tips](/contributors/etiquette) can help you
-write emails that will get some answers.
-
-You can provide feedback on this website and ask questions about anything Apache by subscribing to our mailing
-list. Send an email to
-[dev-subscribe@community.apache.org](mailto:dev-subscribe@community.apache.org). Once subscribed you can send your questions or feedback to
-[dev@community.apache.org](mailto:dev@community.apache.org).
-
-
diff --git a/source/newcommitter.md b/source/newcommitter.md
deleted file mode 100644
index d87c076..0000000
--- a/source/newcommitter.md
+++ /dev/null
@@ -1,400 +0,0 @@
----
-title: New Committer
----
-
-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.
-
-{{% toc %}}
-
-<a name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a>
-## Guidelines for assessing new candidates for committership
-
-When voting, all PMC members need to make up their own minds as to whether a candidate
-should be approved to become a committer. They might search mailing lists and Jira to see
-how the candidate interacts with others, and the contributions (code or doc patches, suggestions, engagement in conversation) they have made.
-
-All new committers **must** adhere to the [Apache Code of Conduct](https://www.apache.org/foundation/policies/conduct.html).
-
-Each PMC may want to create their own supplemental committer guidelines; here are the [Apache Forrest committer guidelines](https://forrest.apache.org/committed.html).
-
-The following are some points to consider when assessing a candidate's qualifications for committership.
-
-<a name="NewCommitter-Abilitytoworkco-operativelywithpeers."></a>
-### Ability to work cooperatively with peers.
-How do we evaluate?
-
- - By the interactions they have through email.
- - By how they respond to criticism.
- - By how they participate in the group decision-making process.
-
-<a name="NewCommitter-Abilitytobeamentor."></a>
-### Ability to be a mentor.
-How do we evaluate?
-
- - By the interactions they have through email.
- - By how clear they are and how willing they are to identify or even create appropriate background
-materials.
-
-<a name="NewCommitter-Community"></a>
-### Community
-How do we evaluate?
-
- - By the interactions they have through email.
- - Do they help to answer questions raised on the mailing list; do they show a helpful
-attitude and respect for other people's ideas?
-
-<a name="NewCommitter-Committment"></a>
-### Commitment
-How do we evaluate?
-
- - By time already given to the project.
- - By how well they stick with the process through tough issues.
- - By how they help on not-so-fun tasks.
-
-<a name="NewCommitter-Personalskill/ability"></a>
-### Personal skill/ability
-How do we evaluate?
-
- - A solid general understanding of the project.
- - Quality of discussion in email.
- - Whether their patches (where applicable) are easy to apply with only a cursory review.
-
-<a name="NewCommitter-NewCommitterProcess"></a>
-## New Committer Process
-
-This section describes a typical Apache project's process for handling the
-vote to add a new committer. Templates mentioned in the process appear
-later in this document.
-
-<a name="NewCommitter-Summary"></a>
-### Summary
-
-1. Discuss the proposed committer or PMC member. If the discussion seems to be going positively, call a vote (templates/committerVote.txt)
-1. Close the vote (templates/closeVote.txt)
-1. If the result is positive, invite the new committer (templates/committerInvite.txt)
-
-If they accept, then:
-
-1. If they already have an Apache id, grant appropriate commit privileges.
-Use the Whimsy tool to update the roster via https://whimsy.apache.org/roster/committee/ or https://whimsy.apache.org/roster/ppmc/
-1. If they have already filed an ICLA, request creation of the committer account.
- If they need to change anything in a previously filed ICLA, wait until the new ICLA is filed,
- then request the account.
- 1. Wait until root says it is done
- 1. PMC Chair updates LDAP group membership which enables svn, gitbox and other access.
-If the committer uses GitHub, they are responsible for linking it to their ASF account.
- 1. Add committer to the appropriate groups in Jira and CWiki
-1. Notify the committer of completion (template/committerDone.txt)
-1. If committer is also to be a PMC member, PMC Chair sends email to board@ asking for acknowledgement of new PMC member
-(templates/email-member-ack.txt)
-1. Announce the new committer (template/committerAnnounce.txt)
-
-<a name="NewCommitter-Discussion"></a>
-### Discussion
-
-We do the discussion and vote on the `private@` mailing list to enable a frank
-discussion. Any PMC member may propose a potential committer or PMC
-member. This is **not** the sole responsibility or right of the PMC
-chair.
-
-We invite people to join as committers/PMC members, not github ids. It is
-fine to refer to the candidate's github id for context, but the person should
-be referred to by their name. It is not necessary to have their full legal
-name (that will be kept private) but it is important to use their name, as
-they refer to themselves in email. If a person is known only by their github
-id, it is ok to ask them for their real name prior to holding a VOTE.
-
-Start a separate [VOTE] thread for each new person. This makes it much easier
-to review the email archives.
-
-We need to be sure that they are committed people with whom we can work.
-They will be our peers. We will have already observed that they are
-committed to the project and graceful toward users and other developers.
-
-Don't wait too long before proposing and don't be too hasty. There is a
-trade-off and something about timeliness. A point is reached where it
-becomes obvious that we should invite them. This encourages them and keeps
-them enthusiastic. If we leave it too long, then we risk them becoming
-disillusioned.
-
-On the `private@` list we can each say exactly what we feel about each person,
-with no holds barred. Keep the discussion concise. The praise part can
-be done later in public. Keep in mind, however, that if the member becomes
-a PMC member later, they will have access to this discussion.
-
-Let the Vote thread run for one week.
-
-A positive result is achieved by **Consensus Approval**: at least 3 +1
-votes and no vetoes.
-
-Any veto must be accompanied by reasoning and the vetoer must be prepared to defend it.
-Other members can attempt to encourage them to change their mind.
-
-New committers can be either quiet or active as they choose. If we find
-that certain people lapse and don't ever contribute, then the project can take steps
-to retire them.
-
-After a positive result, record the result on the PMC list with a [RESULT][VOTE] subject
-and then invite the candidate. We give candidates a chance to decline committership in private. They
-can post a reply to the PMC mailing list.
-
-After we reach a decision on the `private@` list, and after the steps above, we
-announce the new committer on the `dev` list. We can then each follow up with
-our praise in public.
-
-Other notes about the process are available on the main [Apache site](https://www.apache.org/dev/pmc.html#newcommitter).
-
-<a name="NewCommitter-EmailTemplates"></a>
-## Email Templates
-
-### Committer Vote Template
-This is the email to commence a vote for a new committer.
-Some projects make committers PMC members automatically. If this is the case,
-merge this template with the following one (PMC Vote Template).
-
- ------------------------------------------------------------
- To: private@[PROJECT].apache.org
- Subject: [VOTE] New committer: Jo Bloggs
-
- [ add the reasons behind your nomination here ]
-
- Voting ends one week from today, i.e. midnight UTC on YYYY-MM-DD
- https://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
-
- See voting guidelines at
- https://community.apache.org/newcommitter.html
-
- ------------------------------------------------------------
-
-### PMC Vote Template
-This is the email to commence a vote for a new **PMC candidate**. New PMC members need
-to be voted for by the existing PMC members and subsequently approved by the Board
-(or Incubator PMC for incubating projects).
-
- ------------------------------------------------------------
- To: private@[PROJECT].apache.org
- Subject: [VOTE] New PMC candidate: Jo Bloggs
-
- [ add the reasons behind your nomination here ]
-
- Voting ends one week from today, i.e. midnight UTC on YYYY-MM-DD
- https://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
-
- See voting guidelines at
- https://community.apache.org/newcommitter.html
-
-### Close Vote
-This email ends the vote and reports the result to the project.
-
- ------------------------------------------------------------
- To: private@[PROJECT].a.o
- Subject: [RESULT] [VOTE] New committer (or PMC candidate): Jo Bloggs
-
- The vote has now closed. The results are:
-
- Binding Votes:
-
- +1 [TOTAL BINDING +1 VOTES]
- 0 [TOTAL BINDING +0/-0 VOTES]
- -1 [TOTAL BINDING -1 VOTES]
-
- The vote is ***successful/not successful***
-
-### Notify Board of new PMC member
-See [https://www.apache.org/dev/pmc.html#newpmc][1]
-
-### Committer Invite Template
-This is the suggested invitation email to send to the newly elected committer,
-sent after a positive result from the vote for a new committer.
-
- ------------------------------------------------------------
- To: JoBloggs@foo.net
- Cc: private@[PROJECT].apache.org
- Subject: Invitation to become [PROJECT] committer: Jo Bloggs
-
- Hello [invitee name],
-
- The [Project] Project Management Committee (PMC)
- hereby offers you committer privileges to the project
- [as well as membership in the PMC]. These privileges are
- offered on the understanding that you'll use them
- reasonably and with common sense. We like to work on trust
- rather than unnecessary constraints.
-
- Being a committer enables you to more easily make
- changes without needing to go through the patch
- submission process. [Being a PMC member enables you
- to guide the direction of the project.]
-
- Being a committer does not require you to
- participate any more than you already do. It does
- tend to make one even more committed. You will
- probably find that you spend more time here.
-
- Of course, you can decline and instead remain as a
- contributor, participating as you do now.
-
- This personal invitation is a chance for you to accept or decline in private.
- Please let us know in reply to this message whether you accept or decline.
-
- If you accept, you will need an Apache account (id) with privileges.
- Please follow these instructions.
-
- A. If you already have an ICLA on file:
-
- 1. If you already have an Apache account, let us know your id and we
- will grant you privileges on the project repositories.
-
- 2. If you have previously sent an ICLA, let us know the email address
- and public name used on the ICLA and your preferred Apache id, and
- we will request your account.
-
- 3. If the email address on the previously submitted ICLA is no longer
- valid, let us know the email address and public name used on the new ICLA,
- and your preferred Apache id. Continue to step B below and file your new ICLA.
-
- Look to see if your preferred ID is already taken at
- https://people.apache.org/committer-index.html
-
- B. If there is not already an ICLA on file, you need to submit an ICLA:
-
- 1. Details of the ICLA and the forms are found
- through this link: https://www.apache.org/licenses/#clas
-
- 2. Instructions for its completion and return to
- the Secretary of the ASF are found at
- https://www.apache.org/licenses/contributor-agreements.html#submitting
-
- Do not copy the project or any other individual on your message
- to Secretary, as the form contains Personally Identifiable Information
- that should be kept private.
-
- 3. When you complete the ICLA form, be sure to include in the form
- the Apache [Project] project and choose a
- unique Apache ID. Look to see if your preferred
- ID is already taken at
- https://people.apache.org/committer-index.html
- This will allow the Secretary to notify the PMC
- when your ICLA has been recorded.
-
- When recording of your ICLA is noted, you will
- receive a follow-up message with the next steps for
- establishing you as a committer.
-
-### Committer Account Creation
-Follow the instructions
- [here](https://www.apache.org/dev/pmc.html#newcommitter).
-
-In summary:
-
-If the ICLA identifies the project and a valid Apache ID, and the
-[RESULT][VOTE] message has been posted to the PMC private list,
-the account creation request is made by the
-secretary or assistant who files the ICLA.
-
-Otherwise, the new account request should be made by the
-PMC Chair (or any [ASF Member][6] if the chair is unavailable).
-
-The PMC chair needs to use the [ASF New Account Request][2] form to
-send a new account request. Members may use [ASF New Account
-Request][3] page.
-
-For elections held on public lists, please supply the
-[mail-archives.apache.org][4] url. For private lists, you can
-use the [Mail Search tool][5] to locate the appropriate url.
-
-### Committer Announce Template
-This is the email to announce the new committer to `[PROJECT]-dev` once the account has been created.
-
- ------------------------------------------------------------
- To: dev@[PROJECT].apache.org
- Subject: new committer: ###Jo Bloggs
-
- The Project Management Committee (PMC) for Apache [PROJECT]
- has invited Jo Bloggs to become a committer and we are pleased
- to announce that they have accepted.
-
- ### add specific details here ###
-
- Being a committer enables easier contribution to the
- project since there is no need to go via the patch
- submission process. This should enable better productivity.
- A PMC member helps manage and guide the direction of the project.
-
-### Committer Done Template
- After the committer account is established.
-
- ------------------------------------------------------------
- To: private@[PROJECT].a.o, ###JoBloggs@foo.net
- Subject: account request: ###Jo Bloggs
-
- ####, as you know, the ASF Infrastructure has set up your
- committer account with the username '####'.
-
- Please follow the instructions to set up your SSH,
- svn password, svn configuration, email forwarding, etc.
- https://www.apache.org/dev/#committers
-
- [If your project automatically adds committers to the PMC]
- Please subscribe to the [PROJECT] Project Management
- Committee mailing list private@[PROJECT].apache.org.
- [/If]
-
- You have commit access to specific sections of the
- ASF repository, as follows:
-
- [PROJECT] has various resources at:
- https://svn.apache.org/repos/asf/[PROJECT]
- https://gitbox.apache.org
-
- The general "committers" at:
- https://svn.apache.org/repos/private/committers
-
- If using svn, you will probably need to 'svn switch" previous checkouts to now use https,
- for example:
-
- svn switch --relocate https://svn.apache.org/repos/asf/[PROJECT] https://svn.apache.org/repos/asf/[PROJECT]
-
- The developer section of the website describes roles within the ASF and provides other
- resources:
- https://www.apache.org/foundation/how-it-works.html
- https://www.apache.org/dev/
-
- The incubator also has some useful information for new committers
- in incubating projects:
- https://incubator.apache.org/guides/committer.html
- https://incubator.apache.org/guides/ppmc.html
-
- Just as before you became a committer, participation in any ASF community
- requires adherence to the ASF Code of Conduct:
- https://www.apache.org/foundation/policies/conduct.html
-
- [PROJECT should insert its own guidelines here; if none are available,
- the Apache Forrest guidelines are available as a template.]
- https://forrest.apache.org/guidelines.html
-
- If you have any questions during this phase, then please
- see the following resources:
-
- Apache developer's pages: https://www.apache.org/dev/
- Incubator committer guide: https://incubator.apache.org/guides/committer.html
-
- Naturally, if you don't understand anything be sure to ask us on the [PROJECT] dev mailing list.
- Documentation is maintained by volunteers and hence can be out-of-date and incomplete - of course
- you can now help fix that.
-
- A PMC member will announce your election to the dev list soon.
-
-
- [1]: https://www.apache.org/dev/pmc.html#newpmc
- [2]: https://id.apache.org/acreq/pmc-chairs/
- [3]: https://id.apache.org/acreq/members/
- [4]: https://mail-archives.apache.org/
- [5]: https://mail-search.apache.org/
- [6]: https://www.apache.org/foundation/glossary.html#Member
diff --git a/source/newsletter/2017-04.md b/source/newsletter/2017-04.md
deleted file mode 100644
index 13c4e95..0000000
--- a/source/newsletter/2017-04.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: April 2017 Community Newsletter
----
-
-# Apache Committer Newsletter, April 2017
-
-Dear Apache Committer,
-
-In this newsletter: [committer resources you might not know about](#committer-resources),
-[Foundation news](#board-and-member-elections), and [upcoming community events](#upcoming-events).
-
-Thank you for your hard work on our Apache projects. You are the reason the Foundation exists, and your work is the reason we have the reputation we enjoy.
-
-In our recent community survey, we heard from a lot of you that you want more information about what committer resources are available, how to connect with developers from other projects, and more information about what’s going on in the Foundation at large.
-
-In this inaugural edition of the Apache Committers Newsletter, we’re trying to keep the committers better informed about what happens at Apache, and let you know about ways that you can become more involved with the Foundation as a whole.
-
-## Committer Resources
-
-As we grow larger, it can be harder to stay connected with the larger Apache community. We offer a number of resources that make it easier to stay in touch, and find out what’s going on. We encourage you to take advantage of these opportunities, because the Apache community is what makes Apache work.
-
-The [Apache Community website](/) - is full of
-resources for committers, from [new committer information](/committers/)
- - to [developer and contributor information](https://www.apache.org/dev/)
- - to [general information about the services provided by the Community
-Development PMC](/about/ ).
-
-If you’re going to be traveling somewhere, the best way to find out what
-other Apache people are in the area is the Party mailing list -
-[party@apache.org](https://lists.apache.org/list.html?party@apache.org).
-Tell us where you’re going to be, and if you’re interested in meeting for dinner or drinks. It’s a great way to feel at home in an unfamiliar city, and also connect with other Apache community members. Subscribe by sending a message to party-subscribe@apache.org
-
-## Board and Member Elections
-
-Apache is governed by a Board of Directors - a 9-member board that keeps the administrative side of things running, and ensures that projects operate according to the Apache Way, in sustainable, independent ways. The board doesn’t tinker in technical decisions, so it’s possible that many committers are unaware that it’s even there. The board is elected once a year by the membership.
-
-In the recent members meeting (March 28th) a new board of directors was elected, with two directors leaving the board, and two new directors being added. We thank outgoing directors Isabel Drost-Fromm and and Marvin Humphrey for their service, and welcome Phil Steitz and Ted Dunning for the new term.
-
-## Apache is 18!
-
-The Apache Software Foundation turned 18 years old last week!
-
-The Foundation was established in March of 1999, by a small group of enthusiasts that wanted to ensure a sustainable future for the projects that they were running. Since that time, we’ve had huge growth, growing from 21 members to 620, from a handful of developers to over 6,000, and from two projects to more than 300, including some of the most important software projects in the industry.
-
-Read more in our [official press release](https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces6).
-
-## Upcoming Events
-
-As you all hopefully know by now, [ApacheCon North America 2017](https://apachecon.com/)
-will be held in Miami, Florida, May 15-18. It will consist of several parallel events, which, together, make up ApacheCon.
-
-Apache: Big Data celebrates our presence in the Big Data world, with three days, four tracks of content around our various Big Data projects.
-
-Apache: IoT covers our projects in the Internet of Things space.
-
-TomcatCon will have content around the ever-popular Tomcat application server, one of the oldest projects at the ASF.
-
-CloudStack Collaboration Conference is 2 tracks of content for this popular cloud infrastructure project.
-
-The FlexJS Summit will be a developer-focused event to work on the FlexJS project, as well as user-focused sessions.
-
-And BarCampApache is our traditional unConference format event, where you can propose and lead sessions on any topic which is relevant to our community.
-
-Join us Wednesday night for the Lightning Talks - 5 minute presentations by you, about any topic of interest - sometimes funny, sometimes serious, always fun and informative. This will be followed by an offsite attendee reception where you can meet your colleagues from your project, and other ASF projects.
-
-As a committer, you have a deep discount to attend this event, since it is our event, by us and for us, and we want all of our committers to attend. Use the registration code APCOMM17 to register. (Don’t share this with your non-committer colleagues, since we check that you’re a committer when you use this code.)
-
-Learn more about ApacheCon, see the schedule, and register, at [apachecon.com](https://apachecon.com/)
-
-## Next Time …
-
-If you want your message to appear in this newsletter, come get
-involved in writing it for next time. To get involved in the crafting of
-this message, join the [Community Development mailing list](https://lists.apache.org/list.html?dev@community.apache.org)
-by sending email to dev-subscribe@community.apache.org where we’ll be drafting the next newsletter.
-
-Also, please let us know how we’re doing. Was this newsletter helpful?
-Did you read all of it? Drop us a note at dev@community.apache.org to let us know.
diff --git a/source/newsletter/2017-05.md b/source/newsletter/2017-05.md
deleted file mode 100644
index 174e8d2..0000000
--- a/source/newsletter/2017-05.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: May 2017 Community Newsletter
----
-
-
-Committer Resources
-
-(So that we didn't put them all in the first edition)
-
-If you blog about anything Apache related, you might want to know about http://planet.apache.org/committers/ - the Apache committer blog aggregator. It’s valuable in seeing what the rest of the Apache community is working on. To add yourself to the planet, edit the file https://svn.apache.org/repos/asf/planet/committers.ini in svn. It’s preferable if you use an ‘apache’ tag to separate out the stuff that is relevant to the community. If you have difficulty editing that file, come ask som [...]
-
-Every week Sally Khudairi, our VP Marketing, posts an update of what’s going on across the Foundation. You can always find these at the Apache blog - https://blogs.apache.org/foundation/ - or by following our official Twitter stream, @TheASF ( https://twitter.com/theasf ). Our community Facebook page is at http://facebook.com/ApacheSoftwareFoundation and you’re encouraged to participate there by posting your news, releases, and announcements.
-
-
diff --git a/source/newsletter/_index.md b/source/newsletter/_index.md
deleted file mode 100644
index 4d73097..0000000
--- a/source/newsletter/_index.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Newsletter
-url: /newsletter/
----
-
-# Community Development Newsletter
-
-The Community Development project has started a monthly newsletter, to
-keep the larger Apache Community informed of what's happening across the
-Foundation. If you would like to contribute content to this newsletter,
-please join the [ComDev mailing
-list](https://lists.apache.org/list.html?dev@community.apache.org)
-where this message is drafted.
-
-* [April 2017](2017-04)
diff --git a/source/projectIndependence.md b/source/projectIndependence.md
deleted file mode 100644
index 0d3b732..0000000
--- a/source/projectIndependence.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: Project Independence
----
-
-While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules and policies that Apache
-projects must follow – things like complying with PMC
-[release voting][1], [legal policy][2], [brand policy][3],
-using [mailing lists][4], etc., which are [documented in various places][5].
-
-A community is not merely a set of rules; it is also a set of behaviors
-that the participants express when interacting within that
-community. While the ASF is happy to host
-many different styles of project communities, there are some core behaviors that
-we expect and require of any Apache project.
-
-A primary purpose of the basic requirements the ASF places on its
-projects is to help ensure long-lived and stable projects by having
-a broad-enough community to maintain the project even in the
-absence of any individual volunteer or any sea change at a major vendor
-in that area. The [Apache project governance model][7] is explicitly based
-on a diverse community. This is different from other governance models,
-like the “benevolent dictator” idea or the corporate-backed model that projects like
-Eclipse use.
-
-**Please Note:** These requirements apply to *Apache projects*: that is,
-to individual committer and PMC member behaviors and actions within the context
-of collaboratively building software products *at The Apache
-Software Foundation*. By definition, "Apache project" is the collaborative
-activity of building and releasing software products at the ASF.
-
-The ASF and all Apache projects welcome the public to broadly re-use any released
-Apache products for virtually any purpose. Our permissive [Apache License][6] and our [formal trademark policy][3] govern third-party use.
-While many third parties create Apache licensed
-software, only software released from the ASF itself is properly called "Apache software".
-
-## Apache projects are independent
-
-A Project Management Committee
-(PMC) controls each Apache project. A PMC represents the consensus view of the individual PMC
-members by discussing and [VOTE]ing on project releases and adding new committers.
-A PMC's actions within their Apache project community and management of
-their project must be in the interest of that consensus and consistent with
-the ASF's mission of producing software for the public good.
-
-There are also certain expectations of diversity within a PMC; the board may apply extra scrutiny to PMCs
-with low diversity (i.e. PMCs that are dominated by individuals with a common employer).
-Similarly, the ASF does not allow corporations to participate directly in
-Apache project management or other governance activities at the ASF; only individuals.
-
-There are several important aspects to this independence: project management, project use by end users, and project code availability.
-
-## Apache projects are managed independently
-
-Apache projects must be managed independently, and PMCs must ensure that they are acting in the best interests of the project as a whole. It is similarly important that the PMC clearly show this independence within their project community. The perception that the PMC is run independently and without favoring any specific third parties over others is important to help new contributors feel comfortable both joining the community and contributing their work. A community that obviously favor [...]
-
-## Apache products may be used independently
-
-All Apache projects must release their code under the [Apache License][6], which clearly specifies the minimum restrictions that users of Apache software must agree to. Apache software is all about being able to use it for whatever our users want: open source, proprietary, secret. We’re happy to have users take our software (although not our name) for virtually any purpose. While our legal guidelines allow certain other software licenses to be used for specific dependencies, the software [...]
-
-Extending this idea, users of Apache software should be able to find our software, learn how to use it, and apply it to all its common use cases solely by going to the Apache project’s own website. Apache projects should provide sufficient documentation, install features, basic user help (through mailing lists) and services for the common use cases, without users having to rely on third parties. It is important that our users can both make use of our software freely – both in terms of no [...]
-
-## Apache projects are branded as Apache projects
-
-Similar to the requirement that users can use Apache projects independently, users should understand that, when they download and use an Apache product, it is from
-Apache and not from nor related to any third party. That is, the user experience when
-using an Apache project in its common use cases should clearly show the Apache project
-branding in the UI or in whatever other ways users would normally interact with the product.
-
-Ensuring that Apache projects are branded as Apache projects is critical to the longevity
-of our communities. As users use the software, they may discover bugs, or have ideas for
-improving the software, documentation, or other aspects of the project. When a user chooses
-to share these ideas or improvements, ensuring that the product they are using
-is clearly branded as coming from Apache ensures that they are likely to contribute
-those ideas and improvements back to Apache and our projects.
-
-The ASF welcomes third parties who build software that builds atop, improves,
-plugs into, or works with our many Apache products. However any such third party software
-product must be clearly branded as such, and must follow our [formal trademark policy][3].
-In this way, users clearly understand the different sources for software products such as
-Apache Foo (from the ASF) and BigCo SuperThing, Powered By Apache Foo (from BigCo).
-
-## Apache projects are non-commercial
-
-The ASF’s mission is to produce software for the public good. All [Apache software is always available for free][8], and solely under the Apache License. While our projects manage the technical implementation of their individual software products independently, the ASF releases all Apache software, always intending to serve the public good.
-
-We’re happy to have third parties, including for-profit corporations, take our software and use it for their own purposes – even when in some cases it may technically compete with Apache software. However it is important in these cases to ensure that the third party not misuse the brand and reputation of the Apache project for its own purposes. It is important for the longevity and community health of our projects that they get the appropriate credit for producing our freely available software.
-
-
- [1]: https://www.apache.org/legal/release-policy.html
- [2]: https://www.apache.org/legal/
- [3]: https://www.apache.org/foundation/marks/
- [4]: https://www.apache.org/dev/#mail
- [5]: https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different
- [6]: https://www.apache.org/licenses/LICENSE-2.0.html
- [7]: https://www.apache.org/foundation/governance/
- [8]: https://www.apache.org/free/
diff --git a/source/proposals/ZestProposal.md b/source/proposals/ZestProposal.md
deleted file mode 100644
index b9b3cbb..0000000
--- a/source/proposals/ZestProposal.md
+++ /dev/null
@@ -1,281 +0,0 @@
-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.
-
-# 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. If it doesn't work, Qi4j will re-enter via the Incubator.
-
-In addition of regular Top Level Projects, we are making the following self-imposed suggestions to the Governance of this Provisional TLP;
-
-1. The initial PMC consists only of Apache Members, to ensure a solid foundation of understanding The Apache Way.
-
-1. On top of being an ASF Member, the PMC Chair is an active contributor to the project, and has a vested interest in its success.
-
-1. Raising the consensus of Releases from 3 +1 votes to 5 +1 votes.
-
-1. Disclaimer on website and releases, marked with "Provisional" and links to the pTLP status at the ASF.
-
-1. Maturity of project into a regular Top Level Project is decided separately by the Board, with input from PMC and ComDev.
-
-
-# Project Naming
-
-Apache Zest is the proposed project name, as we have learned that "4j" in names might ultimately limit the future direction of the project.
-Additionally, Qi4j will remain as the Java implementation of the composite oriented programming platform. There is also a literal port to .NET, which may be migrated to ASF as well.
-
-# Project Description
-
-Qi4j is a platform that combines Aspects, Composition, Dependency Injection, Validation, Storage/UnitOfWork handling, Indexing/Search abstraction, Architectural enforcement and much more, in a holistic top-down approach, primarily for Domain-rich applications, even explicitly supportive of Domain Driven Design.
-
-Composite oriented programming is a term coined in the early days of Qi4j, to capture the notion of using another paradigm for creating applications, than the prevalent object oriented programming one.
-It comprises of the ability to write smaller parts of code than regular classes, and compose these so called fragments into a larger "Composite". It is similar to aspect-oriented programming, but we take it one step further, there is no base class. The Composite consists of fragments, but no fragment has higher significance than any other fragment. However, there are explicit types of fragments, namely Composite Types, Constraints, Mixins, Concerns and Side-effects, to clearly communicat [...]
-
-Qi4j also evangelizes strong typing, so the equivalent of Around-Advice in AOP, which is called Concerns, can be made type-safe or like AOP be generic (using java.lang.reflect.InvocationHandler interface). Composites can either be hard coded using annotations, or assembled dynamically during the bootstrap phase.
-
-Qi4j is a whole new way to write Java applications, where focus lies on structures and interfaces, where classes are 'mere' implementation details.
-
-Qi4j boldly challenges bad practices head-on, such as "What is a Property?", "Why are null arguments allowed by default?" and "Is the structural assembly of the application actually the same as configuration values?"
-
-# Background
-
-Java is NOT an object-oriented language. Neither is C# or C++. IF they were, how come an Object is DERIVED FROM a Class? A true object-oriented language should for sure have Class(es) assigned to Objects (or a similar construct), which are created 'clean', like stem cells can take on practically any cell's role of the body.
-
-Additionally, in real life, most objects have different properties and behaviors depending on the context. In front of the computer, I am primarily a 'programmer', but in the jungle I am primarily 'scared prey'. Modeling this in Java (and many other languages) requires the introduction of additional Object abstractions, often resulting in many similar classes representing the same underlying entity, again reinforcing our view that Java is a Class Oriented language.
-
-Many problems in software engineering can be attributed to (lack of) cohesion and (too tight) coupling. The original promise was that we write a Class once and we can re-use it in many different applications, subsystems and modules. In reality, the Class often contains "too much" for the next use-case. The granularity is too coarse, causing too much coupling to other parts. This have resulted in libraries being the smallest granularity that is practical, and solutions like OSGi, Spring a [...]
-
-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.
-
-Aspect Oriented Programming is a concept to capture cross-cutting concerns in one place. Classic cases are Logging and Authentication. This is an excellent concept, but we claim that AspectJ/AspectWerkz and others fail in the implementations, as most rely on naming conventions and declarations separated from the code itself. It is therefor often difficult to know what aspects are in effect at a given point in the code. The code weaving involved sometimes interferes with debugging and/or [...]
-
-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 st [...]
-
-# History
-
-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.
-
-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.
-
-# Rationale for migrating to ASF
-
-Qi4j community sees direct productivity gains from using the platform, although the initial learning curve is quite overwhelming, like learning a new language. The Qi4j community recognizes that it has not been able to communicate the benefits well enough, to achieve a large user and developer community. We are confident of Qi4j's technical merit, and would like to draw on ASF's community merit to build a larger, sustainable and successful community around this exciting technology.
-
-The technical merit stems from that Qi4j has a strong model for programming in a more strict, yet more productive environment. A platform where fragments can be leveraged, where aspects are declared on the interfaces, where null values are not allowed by default, and where persistence is integrated yet pluggable at boot time. Qi4j enforces the use of modules and layers, the infrastructure layer can not access layers above it, and presentation layers at the top can't bypass service layers [...]
-All these restrictions are there to provide more guidance to the programmer, reducing the length of the rope and the number of trees to hang oneself in.
-
-"Common things should be quick and easy, while anything should be possible", has been the mantra since the inception. And thanks to this foresight, Qi4j can be deeply integrated with many (but not all) existing Java technologies, to provide for migration paths.
-
-Qi4j internally contains a lot of functional structures, and the community is currently migrating Qi4j to Java 8, reducing a chunk of the codebase in the process, and will likely discover new ways of simplicity. Many argue that Qi4j should become its own programming language, but our position has always been that the refactoring tools available in Java are so powerful and should not be under-estimated. It would take endless amount of effort to even get close to that, something that many [...]
-
-
-
-# Initial Goals
-
-Qi4j is already on version 2.0, and striving towards both a 2.1 release as well as a Java 8 specific 3.0 release. This will be one of the first "Java 8"-only projects at the ASF, and hopefully a lot of people find this in itself attractive and exciting.
-
-Qi4j's user base is relatively small, but we are convinced of its remarkable properties as a productivity enhancing platform, and there is still much to do to reach its full potential. There are a lot of low hanging fruit (more extensions and libraries) as well as serious design challenges, such as reloadable Modules via OSGi and Jigsaw integration in Java 9.
-
-As mentioned above, the small agreeable user base also means that Qi4j can be much more aggressive in adopting newer Java versions, and currently an effort is on the way to leverage Java 8. The Stream API and closures are implemented separately in Qi4j, and we are now converting all the internal code to those features supplied in Java 8, to reduce the total code size of Qi4j Core.
-
-# Meritocracy
-
-Qi4j has been developed under heavy influence of ASF principles and guidelines. The barrier to entry has been at the lowest possible level. A rather aggressive Commit-then-Review process has been in place, but people have in general been encouraged to do larger changes in publicly visible feature branches. The low barrier hasn't created any major problems yet, as reverting mistakes are relatively cheap, and it has been much more important to capture the long-tail of contributions than to [...]
-
-Qi4j is not operated by any organization, and all licensing is directly from developer to the user. We will engage the legal committee to ensure the IP rights are in full order.
-
-Qi4j's release process has not been nearly as stringent as the one at ASF, and will be the biggest change to the community. We will work closely with willing "Overseers" (see below), change our Gradle-based build system and use available tools, such as Rat, to ensure the highest quality releases possible.
-
-# Community
-
-The current Qi4j developer community is rather small, but passionate individuals who are all convinced of Qi4j's merit and potential. We also think that some of the past developers will re-join the effort, once we are at ASF and some traction is attained.
-
-Over the years there has been 28 code contributors in total, of which 8 have been considered Core Developers, i.e. allowed to make changes on the Core runtime on trunk without hand-holding. No access control was in place to enforce that, and a social contract worked very well.
-
-We are probably not the best of community builders, and would welcome members from ASF projects, who think Qi4j is promising, to assist in the community building effort needed.
-
-# Active Developers
-
-All the active developers are independent of each other. No two developers work for the same employer, and no employer pays anyone for working full-time on Qi4j. We consider the following developers 'active' at the moment, one way or the other. It is a very diverse group;
-
-* Niclas Hedhman is an ASF Member, previous long-term member of the Incubator PMC and mentor of 5-10 projects. Freelancing consultant and founder of Bright Things UN Ltd
-
-* Marcel Offermans is an ASF Member, PMC Chair of Apache ACE and on Celix, Felix and Incubator PMC, mentor of several podlings. Day time he runs Luminis Technologies in Holland.
-
-* Rickard Oberg is one of the founders of JBoss, created Xdoclet and WebWork (now Apache Struts2). He now works at Neo Technology Inc, creators of Neo4j.
-
-* Paul Merlin is working at his own company CodeArtisans and a volunteer stone mason of antique walls and buildings.
-
-* Stanislav Muhametsin is working at Cometa Solutions Oy. Stan has also ported Qi4j verbatim to C# as the Qi4CS project on GitHub.
-
-* Tibor Mlynarik works at ADLER iTech.
-
-* Edward Yakop technical architect at ABB Malaysia.
-
-* Marc Grue is a professional musician, but has strong interest in computer science abstractions.
-
-* Kent Sølvsten is working with energy systems at Arosii A/S in Denmark...
-
-* Philippe van Dyck is in the banking industry and works at BNP Paribas
-
-* Jiri Jetmar - Independent consultant
-
-* Jaydatt Desai - Logicom Solutions
-
-Additional important contributions over the years have come from;
-
-* Alex Schneyderman - Voalté
-* Alin Dreghiciu - Sonatype
-* Arvid Huss - Jayway
-* Michael Hunger - Neo Technology Inc
-* Tonny Kohar - independent Apache Batik and SVG consultant
-
-
-# Alignment
-
-Apache is a natural option for any Java project, as ASF has an overwhelming percentage of Java projects.
-But for Qi4j, we think that our choice to challenge every notion, not based on popularity but on technical merit, should be inspiring to existing ASF projects at large. And by doing so, we hope symbiotic relationships can be established with a variety of other projects at ASF.
-
-Qi4j is not "finished" and a lot of work in the Big Data space is still needed. We would like to see HBase and Cassandra use-cases to be "Tackled Qi4j Style" and practical conventions to emerge. There are several other ASF projects which Qi4j could support 'better', if we get a little help from those communities, incl Struts, Camel, ActiveMQ, Cayenne, Karaf and others.
-
-
-# Known Risks
-
-## Orphaned products
-
-Qi4j is not a company product and never was. It was started by two individuals who have a long and strong community involvement dating back to 1998, also the time when they first learned to know each other.
-
-If the community can't be built at ASF, then we think that there must be something about Qi4j that is inherently alien to developers, and Qi4j has no broader appeal, beyond those who have both seen the advantages as well as gotten the opportunity to work with it and see for themselves the benefits. We will work hard to ensure the long-term sustainability of the project, because we think that Qi4j represents an important step towards a paradigm shift in software development.
-
-## Inexperience with Open Source
-
-Not only does Qi4j have a rather long running history of an independent open source project, 6 major releases, and a track record of operating well as such, but Niclas Hedhman was a long time member of the Incubator PMC, serving on the Legal Committee and have plenty of experience of what is required of Apache projects, as does Marcel Offermans. We wouldn't have proposed to move Qi4j to Apache, unless we thought that the larger Qi4j community will work well at the ASF, with a little bit [...]
-
-All of Qi4j's history, except the initial 2-3 months, were done on open mailing lists and public repositories. The practice of full discourse and discussion on asynchronous mailing lists has been respected to the fullest extent possible, and at no time has other means of communication been regular.
-
-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.
-
-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.
-
-## Homogenous Developers
-
-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.
-
-The contributors have a vast diversity in their backgrounds and interests, even a non-developer making large contributions.
-
-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.
-
-## Reliance on Salaried Developers
-
-As far as we know, no one is currently paid to work on Qi4j itself. This has been a factor in the slow down of activity in the last two years, but we think that the bottom has been reached and that we will see an uptick during 2015, as some of the core members are coming back to write applications using Qi4j.
-
-## Relationships with Other Apache Products
-
-Qi4j is such a unique and radically different platform that there is no direct alignment in Qi4j Core with other Apache (or any other for that matter) projects. We have also kept the dependencies to a minimum by choice.
-But Qi4j also defines Extension mechanisms, such as storage, indexing, serialization and metrics, and we have implemented extensions for Apache Cassandra and Apache Solr. We also have libraries that integrate other technology into the Qi4j world, such as Apache Shiro, Apache Struts and Apache CXF. We expect that additional Apache projects will be used in future Extensions as well as Libraries, especially in the Big Data space, where we see great opportunities for a Qi4j approach.
-
-## Excessive Fascination with the Apache Brand
-
-There is no doubt that the Apache brand is strong, no one can deny that. But our primary 'fascination' is around the possibility to build a stronger community at the ASF, than we otherwise seem to be able to do. Apache is a natural water cooler, where open development people can share ideas and work together. We hope to inspire other Apache projects to do greater things after being exposed to Qi4j's unique approach to many technical challenges.
-
-# Documentation
-
- Website; http://qi4j.org
-
- Source Repository; https://github.com/Qi4j/qi4j-sdk
-
- Current Mailing list; https://groups.google.com/forum/#!forum/qi4j-dev
-
-# Initial Source
-
-As mentioned earlier, Qi4j started out at OPS4J community, and the codebase was initially on Subversion, then moved to OPS4J operated GIT repositories and finally we moved to GitHub. We tried to preserve history the best we could, with reasonable effort.
-So, https://github.com/Qi4j contains the repositories that are relevant for the Incubator. In practice, only the qi4j-sdk is current. We suggest that the qi4j-core, qi4j-libraries and qi4j-extensions are imported but made read-only. qi4j-sandbox is imported. qi4j.github.com contains the current website, but the sources for that resides primarily inside the qi4j-sdk repository.
-
-# Source and Intellectual Property Submission Plan
-
-There are no issues that we know of. Source code is available openly and online. All code has originated directly from Qi4j contributors, marked as Apache Licensed contributions and to the best of our knowledge there is no encumbered IP issues.
-As Qi4j was never a legal entity, all contributions were directly licensed (Apache License 2.0) by the developer to the public. There is no problem reaching out to all of the authors of an overwhelming part (if not all) of the codebase and ask for paperwork, if this is necessary.
-
-# External Dependencies
-
-Qi4j has few dependencies, and all dependencies in all non-optional code is ASLv2 compatible. The required dependencies are;
- * ASM
- * SLF4J (To be revised)
- * org.json (included in source form in the repository. To be revised)
-
-There are optional libraries and extensions that have dependencies on projects with other licenses.
-One very notable case, the Neo4j entity store extension, is worth mentioning here. At the time this extension was created, Neo4j was under the AGPL license. It is now under GPL, yet the Qi4j Neo4j extension is licensed under Apache License v2. Are we not violating the license requirements of Neo4j? No, we think not, as the contribution itself was made by Neo Technology under the Apache license. Neo Technology argued that they had the right to provide the extension under ALv2, yet whoever [...]
-
-# Cryptography
-
-Qi4j optionally depends on projects that use cryptography. As Qi4j isn't an organization, and most developers live in Europe, we have not followed the US trade restrictions on Cryptography.
-Without an extensive check of all 100+ optional dependencies, Apache Shiro stands out. We need to get feedback from legal@ on what the exact requirements are, and conduct a full review.
-
-# Required Resources
-
-## Mailing lists
-
- private@zest.apache.org
- dev@zest.apache.org
- commits@zest.apache.org
-
-## Git Repositories
-
-We understand that Apache operates its own Git repositories, as well as having a large number of read-only mirrors at GitHub under Apache organization.
-
- https://git-wip-us.apache.org/repos/asf/qi4j.git
- https://git-wip-us.apache.org/repos/asf/qi4j-legacy-core.git
- https://git-wip-us.apache.org/repos/asf/qi4j-legacy-libraries.git
- https://git-wip-us.apache.org/repos/asf/qi4j-legacy-extensions.git
- https://git-wip-us.apache.org/repos/asf/qi4j-sandbox.git
-
-## Issue Tracking
-
-We also have Jira issues we wish to import from Atlassian operated https://ops4j1.jira.com/browse/QI, if possible, to
-
- https://issues.apache.org/jira/browse/ZEST
-
-# Initial PMC
-
-* Alex Karasulu - akarasulu@apache.org
-* James Carman - jcarman@apache.org
-* Jeff Genender - jgenender@apache.org
-* Marcel Offermans - marrs@apache.org
-* Chris Mattmann - mattmann@apache.org
-* Niclas Hedhman - niclas@apache.org
-* Roman Shaposhnik - rvs@apache.org
-
-
-# Committers
-
-* Edward Yakop - efy@apache.org
-* Jaydatt Desai - jaydattdesai@gmail.com
-* Jiri Jetmar - juergen.jetmar@gmail.com
-* Kent Sølvsten - kent.soelvsten@gmail.com
-* Marc Grue - marcgrue@gmail.com
-* Paul Merlin - paul@nosphere.org
-* Phillipe van Dyck - pvdyck@gmail.com
-* Rickard Öberg - rickardoberg@gmail.com
-* Stanislav Muhametsin - stanislav.muhametsin@cometasolutions.fi
-* Tibor Mlynarik - tibor.mlynarik@gmail.com
-
-
-# Affiliations
-
-* Edward Yakop - ABB Malaysia
-* Jaydatt Desai - Logicom Solutions
-* Jiri Jetmar - Independent consultant
-* Kent Sølvsten - Arosii A/S
-* Marc Grue - Musician
-* Marcel Offermanns - Luminis Technologies
-* Niclas Hedhman - Bright Things UN Ltd
-* Paul Merlin - CodeArtisans
-* Phillipe van Dyck - BNP Paribas
-* Rickard Öberg - Neo Technology AB
-* Stanislav Muhametsin - Cometa Solutions Oy
-* Tibor Mlynarik - ADLER iTech s.r.o.
diff --git a/source/speakers/_index.md b/source/speakers/_index.md
deleted file mode 100644
index ecfe238..0000000
--- a/source/speakers/_index.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Speaking about Apache, our Projects and our Community
-url: /speakers/
----
-
-If you are looking for speakers for an event, or are a speaker looking for
-materials, this is the place for you.
-
-If you are seeking to organise an Apache-branded event, you must ensure your activities
-conform to the [Third Party Event Branding Policy][1]. Once you have verified you are in
-conformance, please consider adding your event to the [events calendar][2].
-
-## Finding speakers
-
-You can use our "[Find People][3]" application to find speakers willing and able to
-talk about The Apache Software Foundation and its projects. A few people have shared [Apache related presentations][4] for you.
-
-*NOTE* This service is alpha-quality right now, and features only
-some of the many volunteer speakers from Apache projects. If you have a problem with
-it, or it doesn't turn up a suitable candidate, feel free to contact us
-for help (see below).
-
-### Listing yourself as a potential speaker
-
-If you're an Apache committer, and you're interested in speaking about Apache Projects, our Communities, or the Apache
-Software Foundation as a whole, we encourage you to get involved: list yourself in our speaker application!
-
-For more details on how to list yourself as a potential speaker, see the [Apache Speakers WebApp][5] page.
-
-## Speaker support materials
-
-If you are creating your own slides, you will find the [ASF Press Kit][6] useful. It contains logos in various formats.
-We also have [sample themes][8] available.
-
-We aim to collect a set of slide decks about the Apache
-Software Foundation for reuse in presentations. So far
-A few people have shared [Apache related presentations][7]
-for you. If you have a slide deck under a permissive license
-that talks about Apache communities, best practices, or the like
-(i.e. one that is applicable to more than just one project
-at Apache), please email us and suggest we include your slides.
-
-
- [1]: https://community.zones.apache.org/
- [2]: /calendars/conferences.html
- [3]: https://community.zones.apache.org/
- [4]: slides.html
- [5]: speakers.html
- [6]: https://www.apache.org/foundation/press/kit/
- [7]: slides.html
- [8]: themes
diff --git a/source/speakers/slides.md b/source/speakers/slides.md
deleted file mode 100755
index 8399657..0000000
--- a/source/speakers/slides.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Apache-related slides, videos and presentations
----
-
-This page contains links to presentations and other key papers about the ASF and how
-Apache projects work that you may find useful. Many of these have
-been presented at [ApacheCon conferences](https://events.apache.org) or
-other open source conferences.
-
-These presentations are available under permissive licenses; please see
-each individual presentation for license details.
-
-Many Apache speakers post their slides to the [SlideShare website](//www.slideshare.net/search/slideshow?searchfrom=header&q=apache+software),
-and the [FeatherCast podcast offers audio recordings](//feathercast.apache.org/) of many talks and interviews.
-
-For those who prefer videos, our many volunteers have posted
- - [full videos of all ApacheCon NA 2013 presentations](https://www.youtube.com/user/TheApacheFoundation/playlists), and
- - [select ApacheCon NA 2014 presentations](https://www.youtube.com/playlist?list=PLU2OcwpQkYCzvGxZgVOunTs-3iEao6YJc).
- - [Sessions from ApacheCon 2019 and 2020](https://www.youtube.com/channel/UCLDJ_V9KUOdOFSbDvPfGBxw)
-
-Additional slides, videos and audio recordings can also be found through the
-[ApacheCon Past Conference Resources page](https://wiki.apache.org/apachecon/Past_Conference_Resources).
-
-# ASF Postings
-- [Briefing: The Apache Way](https://www.apache.org/theapacheway/index.html) (paper)
-- [The Apache Way to Sustainable Open Source Success](https://blogs.apache.org/foundation/entry/the-apache-way-to-sustainable) (paper)
-
-# Isabel Drost
- - [Open Source development for students][1]
-
-# Justin Erenkrantz
-
- - [Open Innovation in The Apache Software Foundation][2]
- - [Writing and Distributing Software "The Apache Way"][3]
- - [The Apache Software Foundation: No Jerks Allowed!][4]
- - [Putting It Together][5]
- - [An Overview of The Apache Software Foundation][6]
-
-# Ross Gardler
- - [Community Development at the ASF][7]
- - [The Apache Way and OpenOffice.org][8]
-
-# Jim Jagielski
- - [Communities and Collaboration][9]
- - [Open Source: It's just not for IT anymore][10]
- - More of Jims presentations [here][11] and [here][12]
-
-# Bertrand Delacretaz
-
-Slides and talk recordings are linked from my [Pressbook](https://pinboard.in/u:bdelacretaz/t:pressbook/).
-
-# Shane Curcuru
- - [History and Overview of Various Apache Way Presentations](http://shaneslides.com/2017/04/History-Of-The-Apache-Way/) (annotated list, pre-2017)
- - [Apache Way: Effective Open Source Project Management](http://shaneslides.com/apachecon/TheApacheWay-Intro-ApacheConNA2017.html) ApacheCon 2017 ([video](https://www.youtube.com/watch?v=hpAv54KIgK8))
- - [About: Apache - The Foundation, The Way, The Projects](https://communityovercode.com/2012/05/camelone-2012-presentation/)
- - [Managing Community Open Source Brands](https://communityovercode.com/2012/07/oscon-presentation/)
- - [Improving Your Project's Image And Brand](https://www.slideshare.net/shanecurcuru/improving-your-apache-projects-image-and-brand)
- - [Supporting Apache Brands While Making A Profit](https://events.linuxfoundation.org/sites/events/files/slides/SupportingApacheBrandsWhileMakingAProfit-SCurcuru-ApacheCon2014.pdf) ([video](https://www.youtube.com/watch?v=8cQMhysKeyU))
- - [Successfully Profiting From Apache Projects](https://www.slideshare.net/shanecurcuru/successfully-profiting-from-apache-brands)
- - [Practical Trademark Law For FOSS Projects](https://www.slideshare.net/shanecurcuru/practical-trademark-law-for-foss-projects)
-
-# Nick Burch
- - [The Apache Way (ApacheCon North America 2015 version)](https://home.apache.org/~nick/Talks/ApacheConNA15/TheApacheWay15.pdf)
- - [But we're already open source? Why would we want to bring our project to the ASF?](https://home.apache.org/~nick/Talks/ApacheConNA16/ButWereAlreadyOpen.pdf)
-
-# Andrea Pescetti
- - [Bending the rules: Community over Code over Policy](https://www.slideshare.net/pescetti/bending-the-rules-community-over-code-over-policy-apachecon-2014)
-
-# Daniel Ruggeri
- - [The Apache Way - amalgamation of many other decks](https://people.apache.org/~druggeri/presentations/TheApacheWay.odp) - presented at University of Missouri 2015. Attempt to get everything in one deck.
-
-# J Aaron Farr
- - [Several older Apache Way and related slide decks](https://www.slideshare.net/jaaronfarr/presentations)
-
-# Alan Gates
- - [Training Our Team in the Apache Way](https://www.slideshare.net/alanfgates/keynote-apache-bdeunov2016) Keynote slides from Apache Big Data EU 2016
- - [Hortonworks Engineering Apache Training](https://www.slideshare.net/alanfgates/hortonworks-apache-training) Training material described in keynote above
-
-# Brett Porter
- - [The Apache Way - based on J Aaron Farr's earlier versions](https://www.slideshare.net/brettporter/the-apache-way-dataworks-summit-2017)
-
-# Ismaël Mejía
- - [Construyendo software y comunidades a la manera de Apache (spanish)](https://iemejia.github.io/slides/201806-Construyendo%20software%20y%20comunidades%20a%20la%20manera%20de%20Apache.pdf)
-
-# Piergiorgio Lucidi
- - [The Journey of Apache ManifoldCF: Learning from ASF's Successes (Open Source Summit 2017)](https://www.slideshare.net/PiergiorgioLucidi/the-journey-of-apache-manifoldcf-learning-from-asfs-successes-81289363)
-
-And more at his [slideshare profile](https://www.slideshare.net/PiergiorgioLucidi)
-
-## Committers - please add to this page!
-
-If you are an Apache committer and have presented slides on community topics
-around Apache, please add a link to your information here!
-
-### Slide templates
-
-If you want to prepare a new presentation about any Apache project, feel free to start using [Apache slide templates](https://svn.apache.org/repos/asf/comdev/slide-templates/).
-
- [1]: http://isabel-drost.de/hadoop/slides/christoph.pdf
- [2]: https://www.erenkrantz.com/apachecon/TransferSummit%20-%20Open%20Innovation.pdf
- [3]: https://www.erenkrantz.com/apachecon/OSBC%20-%20No%20Jerks%20Allowed.pdf
- [4]: https://www.erenkrantz.com/apachecon/JASIG%20-%20No%20Jerks%20Allowed.pdf
- [5]: https://www.erenkrantz.com/apachecon/Apache%20Roadshow%20Asia%202009.pdf
- [6]: https://www.erenkrantz.com/apachecon/SAP%20Apache%20Intro.pdf
- [7]: https://www.slideshare.net/bosc2010/gardler-bosc2010-communitydevelopmentattheasf
- [8]: https://www.slideshare.net/rgardler/the-apache-way-and-openofficeorg
- [9]: https://people.apache.org/~jim/presos/IOOS2011/Creating_Community.pdf
- [10]: https://people.apache.org/~jim/presos/OR2011/Open_Source_NotJust.pdf
- [11]: https://people.apache.org/~jim/presos/
- [12]: https://www.slideshare.net/jimjag/
diff --git a/source/speakers/speakers.md b/source/speakers/speakers.md
deleted file mode 100644
index 8e30f9e..0000000
--- a/source/speakers/speakers.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Listing yourself as a Potential Speaker
----
-
-If you're an Apache committer interested in speaking about Apache
-Technologies, Apache Projects or the Apache Software Foundation as a whole,
-we encourage you to get involved and list yourself in our speaker
-application!
-
-## Finding Speakers
-
-If you are organising an event and looking for speakers, see
-[the Apache Speakers homepage](/speakers/) for details.
-
-## Listing yourself as a potential speaker
-
-To list yourself as someone interested in being an Apache speaker, there are
-two steps. The first is to create a FOAF ("friend of a friend") file for yourself that includes
-a couple of key pieces of information. The second is to list yourself in the
-speaking DOAP ("description of a project") file.
-
-### Creating your FOAF file
-
-If you do not already have a FOAF file for yourself, creating one is very easy. Details on how to create a FOAF file, along with a
-handy wizard to guide you through the process, are available at
-[https://people.apache.org/foaf/](https://people.apache.org/foaf/).
-
-Since you are a potential speaker we do require you
-to include a few key bits of information in the FOAF file. These are:
-
- * Your location
- * The projects you are involved in (include foundation-wide ones, too, if you're
- happy to talk about these)
- * Your Twitter ID (so we can point people at your speaking history on
- [Lanyrd](http://lanyrd.com/))
-
-
-### Listing yourself in the Speakers DOAP file
-
-If you haven't already done so, check out the committers directory from
-svn:
-
-```
-svn co https://svn.apache.org/repos/private/committers/
-```
-
-Edit `local-outreach/ApacheSpeakers.rdf` and add yourself in as a
-helper. If your FOAF file is in svn and showing up on people.apache.org,
-add in:
-
-```
-<helper>
- <foaf:Person rdf:resource="urn:org:apache:[your username].rdf" />
-</helper>
-```
-
-If you have your FOAF file externally hosted, the **rdf:resource**
-should point to the URL of the file.
-
-For an apache committer with username "foo", your entry would be one of:
-
-```
-<helper>
- <foaf:Person rdf:resource="urn:org:apache:foo.rdf" />
-</helper>
-<helper>
- <foaf:Person rdf:resource="https://www.example.com/foaf/foo.rdf" />
-</helper>
-```
-
-Within 24 hours of committing your addition to
-*local-outreach/ApacheSpeakers.rdf*, you should appear in the web
-application as a potential speaker! Head over to
-[https://community.zones.apache.org/](https://community.zones.apache.org/)
-a day later to confirm that you're listed properly.
diff --git a/static/.htaccess b/static/.htaccess
deleted file mode 100644
index ba8e153..0000000
--- a/static/.htaccess
+++ /dev/null
@@ -1,7 +0,0 @@
-Redirect /gsoc.html /gsoc/
-Redirect /gsoc-admin-tasks.html /gsoc/gsoc-admin-tasks.html
-Redirect /guide-to-being-a-mentor.html /gsoc/guide-to-being-a-mentor.html
-Redirect /mentee-ranking-process.html /gsoc/mentee-ranking-process.html
-Redirect /use-the-comdev-issue-tracker-for-gsoc-tasks.html /gsoc/use-the-comdev-issue-tracker-for-gsoc-tasks.html
-
-Redirect /mentoring/experiences.html /gsoc/experiences.html
diff --git a/static/css/bootstrap.min.css b/static/css/bootstrap.min.css
deleted file mode 100644
index 83a71b1..0000000
--- a/static/css/bootstrap.min.css
+++ /dev/null
@@ -1,7 +0,0 @@
-/*!
- * Bootstrap v4.6.2 (https://getbootstrap.com/)
- * Copyright 2011-2022 The Bootstrap Authors
- * Copyright 2011-2022 Twitter, Inc.
- * Licensed under MIT (https://github.com/twbs/bootstrap/blob/main/LICENSE)
- */:root{--blue:#007bff;--indigo:#6610f2;--purple:#6f42c1;--pink:#e83e8c;--red:#dc3545;--orange:#fd7e14;--yellow:#ffc107;--green:#28a745;--teal:#20c997;--cyan:#17a2b8;--white:#fff;--gray:#6c757d;--gray-dark:#343a40;--primary:#007bff;--secondary:#6c757d;--success:#28a745;--info:#17a2b8;--warning:#ffc107;--danger:#dc3545;--light:#f8f9fa;--dark:#343a40;--breakpoint-xs:0;--breakpoint-sm:576px;--breakpoint-md:768px;--breakpoint-lg:992px;--breakpoint-xl:1200px;--font-family-sans-serif:-apple-s [...]
-/*# sourceMappingURL=bootstrap.min.css.map */
\ No newline at end of file
diff --git a/static/css/main.css b/static/css/main.css
deleted file mode 100644
index 87b221d..0000000
--- a/static/css/main.css
+++ /dev/null
@@ -1,46 +0,0 @@
-main.cd-main {
- padding-top: 4.5rem;
-}
-
-footer.page-footer {
- bottom: 0;
- color: #fff;
-}
-
-footer.page-footer a {
- color: #000000;
-}
-footer.page-footer a:hover {
- color: #000000;
-}
-
-footer.page-footer .footer-copyright {
- overflow: hidden;
- color: rgba(255,255,255,0.6);
- background-color: rgba(0,0,0,0.2);
-}
-
-.headerlink {
- visibility: hidden;
-}
-
-dt:hover > .headerlink, p:hover > .headerlink, td:hover > .headerlink, h1:hover > .headerlink, h2:hover > .headerlink, h3:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, h6:hover > .headerlink {
- visibility: visible
-}
-
-.child-pages {
- list-style-type: none;
-}
-.page-summary .title {
- font-size:100%;
-}
-
-.page-summary .summary {
- margin-left: 1em;
- font-style: italic;
-}
-
-.published-date {
- font-size: 80%;
- font-style: italic;
-}
\ No newline at end of file
diff --git a/static/doap_ComDev.rdf b/static/doap_ComDev.rdf
deleted file mode 100644
index e8c4d9a..0000000
--- a/static/doap_ComDev.rdf
+++ /dev/null
@@ -1,67 +0,0 @@
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- https://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-<rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="https://comdev.apache.org/">
- <created>2009</created>
- <license rdf:resource="https://www.apache.org/licenses/LICENSE-2.0.txt"/>
- <name>Apache Community Development</name>
- <homepage rdf:resource="https://community.apache.org/"/>
- <asfext:pmc rdf:resource="https://comdev.apache.org/"/>
- <shortdesc>Resources to help people become involved with Apache projects</shortdesc>
- <!--description></description-->
- <bug-database rdf:resource="https://issues.apache.org/jira/browse/COMDEV"/>
- <mailing-list rdf:resource="https://community.apache.org/lists.html"/>
- <repository>
- <GitRepository>
- <location rdf:resource="https://gitbox.apache.org/repos/asf/comdev-site.git"/>
- <browse rdf:resource="https://github.com/apache/comdev-site"/>
- </GitRepository>
- </repository>
- <repository>
- <GitRepository>
- <location rdf:resource="https://gitbox.apache.org/repos/asf/comdev-events-site.git"/>
- <browse rdf:resource="https://github.com/apache/comdev-events-site"/>
- </GitRepository>
- </repository>
- <repository>
- <SVNRepository>
- <location rdf:resource="https://svn.apache.org/repos/asf/comdev/projects.apache.org/"/>
- <browse rdf:resource="https://svn.apache.org/viewvc/comdev/site/projects.apache.org/"/>
- </SVNRepository>
- </repository>
- <repository>
- <SVNRepository>
- <location rdf:resource="https://svn.apache.org/repos/asf/comdev/reporter.apache.org/"/>
- <browse rdf:resource="https://svn.apache.org/viewvc/comdev/site/reporter.apache.org/"/>
- </SVNRepository>
- </repository>
- <repository>
- <SVNRepository>
- <location rdf:resource="https://svn.apache.org/repos/asf/comdev/helpwanted.apache.org/"/>
- <browse rdf:resource="https://svn.apache.org/viewvc/comdev/site/helpwanted.apache.org/"/>
- </SVNRepository>
- </repository>
- <maintainer>
- <foaf:Person>
- <foaf:name>Apache Community Development PMC</foaf:name>
- <foaf:mbox rdf:resource="mailto:dev@community.apache.org"/>
- </foaf:Person>
- </maintainer>
- </Project>
-</rdf:RDF>
diff --git a/static/favicon.ico b/static/favicon.ico
deleted file mode 100644
index cb6dc78..0000000
Binary files a/static/favicon.ico and /dev/null differ
diff --git a/static/images/aceu19_1.jpg b/static/images/aceu19_1.jpg
deleted file mode 100644
index a3109cd..0000000
Binary files a/static/images/aceu19_1.jpg and /dev/null differ
diff --git a/static/images/aceu19_2.jpg b/static/images/aceu19_2.jpg
deleted file mode 100644
index 8e88457..0000000
Binary files a/static/images/aceu19_2.jpg and /dev/null differ
diff --git a/static/images/favicon.ico b/static/images/favicon.ico
deleted file mode 100644
index b6b6c2c..0000000
Binary files a/static/images/favicon.ico and /dev/null differ
diff --git a/static/js/bootstrap.min.js b/static/js/bootstrap.min.js
deleted file mode 100644
index 97206dc..0000000
--- a/static/js/bootstrap.min.js
+++ /dev/null
@@ -1,7 +0,0 @@
-/*!
- * Bootstrap v4.6.2 (https://getbootstrap.com/)
- * Copyright 2011-2022 The Bootstrap Authors (https://github.com/twbs/bootstrap/graphs/contributors)
- * Licensed under MIT (https://github.com/twbs/bootstrap/blob/main/LICENSE)
- */
-!function(t,e){"object"==typeof exports&&"undefined"!=typeof module?e(exports,require("jquery"),require("popper.js")):"function"==typeof define&&define.amd?define(["exports","jquery","popper.js"],e):e((t="undefined"!=typeof globalThis?globalThis:t||self).bootstrap={},t.jQuery,t.Popper)}(this,(function(t,e,n){"use strict";function i(t){return t&&"object"==typeof t&&"default"in t?t:{default:t}}var o=i(e),a=i(n);function s(t,e){for(var n=0;n<e.length;n++){var i=e[n];i.enumerable=i.enumerabl [...]
-//# sourceMappingURL=bootstrap.min.js.map
\ No newline at end of file
diff --git a/static/js/jquery.min.js b/static/js/jquery.min.js
deleted file mode 100644
index 0de648e..0000000
--- a/static/js/jquery.min.js
+++ /dev/null
@@ -1,2 +0,0 @@
-/*! jQuery v3.6.4 | (c) OpenJS Foundation and other contributors | jquery.org/license */
-!function(e,t){"use strict";"object"==typeof module&&"object"==typeof module.exports?module.exports=e.document?t(e,!0):function(e){if(!e.document)throw new Error("jQuery requires a window with a document");return t(e)}:t(e)}("undefined"!=typeof window?window:this,function(C,e){"use strict";var t=[],r=Object.getPrototypeOf,s=t.slice,g=t.flat?function(e){return t.flat.call(e)}:function(e){return t.concat.apply([],e)},u=t.push,i=t.indexOf,n={},o=n.toString,y=n.hasOwnProperty,a=y.toString,l= [...]
diff --git a/static/speakers/talks/Apache_Way_2017.yaml b/static/speakers/talks/Apache_Way_2017.yaml
deleted file mode 100644
index 4191464..0000000
--- a/static/speakers/talks/Apache_Way_2017.yaml
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: "Apache Way: Effective Open Source Project Management"
-teaser: Learn how to manage long-lived diverse open source project communities by following the behaviors of the Apache Way.
-submitter: curcuru
-speakers:
-- curcuru
-abstract: |
- The "Apache Way" is the process by which Apache Software Foundation projects are managed. It has evolved 18 years and has produced over 170 highly successful open source Apache projects. But what is it and how does it work?
-
- Learn the core behaviors that make up the Apache Way, and how they are used in successful Apache projects from core technologies, to big data, to user facing projects.
-
- The behaviors in the Apache Way are required for all Apache projects, but can be simply used by any open source projects. Distributed decision making, open communication, do-ocracy, and diverse communities are the cornerstones.
-
- Benefit from the experience of over 5,000 Apache committers and 170 successful projects by applying these behaviors and techniques in your own projects!
-
-audience: Community managers, developers, project managers involved with FOSS projects.
-slides: http://shaneslides.com/apachecon/TheApacheWay-Intro-ApacheConNA2017.html
-video: https://www.youtube.com/watch?v=hpAv54KIgK8
-topics:
-- apacheway
-- community
-present_at:
-- http://apachecon.com/2017
-present_date: '2017-05-16'
diff --git a/static/speakers/talks/Committed_To_The_Apache_Way.yaml b/static/speakers/talks/Committed_To_The_Apache_Way.yaml
deleted file mode 100644
index 5f43970..0000000
--- a/static/speakers/talks/Committed_To_The_Apache_Way.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Committed To The Apache Way"
-teaser: Learn how being involved in an Apache project is not just about code.
-submitter: sharan
-speakers:
-- sharan
-abstract: |
- 'To be committed' is a strange phrase. In the past it was used to describe people who were sent to mental institutions or 'facilities'. Fast forward to today and words like committed and commitment are used throughout the Open Source world. Are we all a little crazy? - Perhaps!
-
- In this presentation Sharan shares her thoughts and experiences about being a Committer, life at the ASF (facility) and how not being able to code is still OK.
-
-audience: Community managers, developers, project managers involved with FOSS projects.
-slides: http://events.linuxfoundation.org/sites/events/files/slides/Commited%20to%20Apache.pdf
-video: https://www.youtube.com/watch?v=vT-kxmoLs5k&index=25&list=PLbzoR-pLrL6pLDCyPxByWQwYTL-JrF5Rp
-topics:
-- community
-- contributors
-present_at:
-- http://apachecon.com/2017
-present_date: '2017-05-16'
diff --git a/static/speakers/talks/From_Dev_To_User.yaml b/static/speakers/talks/From_Dev_To_User.yaml
deleted file mode 100644
index 58b2af8..0000000
--- a/static/speakers/talks/From_Dev_To_User.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "From dev@ to user@ to the Apache Way"
-teaser: The story of how an existing project community improved by coming to Apache.
-submitter: sblackmon
-speakers:
-- sblackmon
-abstract: |
- This talk will cover the journey of Apache Streams (incubating) beyond a solution solely by and for java developers, toward a solution that can provide value for anyone, anywhere along the experience spectrum, regardless of technical preferences. We'll share feedback that served as concentrate focus on mission and usability.
-
- We'll walk through some of the improvements made to project code and tooling (maven), documentation (website, examples), and usability (command line interface, maven plugins, zeppelin support, network APIs) to move the project from dev@ to user@, and the opportunities we see to increase usability and relevance still further.
-
-audience: Community managers, developers, project managers involved with FOSS projects.
-slides: http://events.linuxfoundation.org/sites/events/files/slides/ApacheConNA2017-Blackmon.pdf
-video: https://www.youtube.com/watch?v=E9A54x6af8o&index=27&list=PLbzoR-pLrL6pLDCyPxByWQwYTL-JrF5Rp
-topics:
-- incubator
-- apacheway
-present_at:
-- http://apachecon.com/2017
-present_date: '2017-05-16'
diff --git a/static/speakers/talks/README.yaml b/static/speakers/talks/README.yaml
deleted file mode 100644
index 7094e51..0000000
--- a/static/speakers/talks/README.yaml
+++ /dev/null
@@ -1,24 +0,0 @@
----
-# YAML format allows comments; each talk/slides gets one file.
-title: "Talk Title: Strings with colons must be quoted"
-teaser: Teaser is one sentence for use on session grids or tweets or the like (where supported).
-submitter: curcuru
-# submitter maps to basename.yaml which is normally an apacheid and lets us lookup the speaker bio, etc.
-speakers:
-- curcuru
-- Court Jester
-# Panels might have more speakers; if string doesn't lookup a basename.yaml, it's just a display name.
-abstract: |
- Abstracts are the full description of a talk, session, or panel that has already been presented.
-
- Abstracts may have line breaks, and some systems may allow **formatting** or the like.
-
- Using the YAML pipe "|" character for a literal multiline scalar means linebreaks are preserved in the abstract.
-
-audience: Brief description of the expected audience for this talk.
-slides: URL.to/posted-slides
-video: URL.to/posted-video?if-any
-
-present_at:
-- URL.to/last-conference-presented-at
-present_date: '2017-05-16'
diff --git a/static/speakers/talks/Tale_Of_Two_Developers.yaml b/static/speakers/talks/Tale_Of_Two_Developers.yaml
deleted file mode 100644
index ce0aa49..0000000
--- a/static/speakers/talks/Tale_Of_Two_Developers.yaml
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: "A Tale of Two Developers: Finding Harmony Between Commercial Software Development and the Apache Way"
-teaser: Learn from the real-life lunchtime dialog between an experienced Apache committer and a new coder.
-submitter: wang
-speakers:
-- wang
-- Alex Leblang
-abstract: |
- Apache community members can reference tenets from the Apache Way such as “community over code” and “openness” as if it were second nature. While they may sound simple, these concepts can be foreign to developers coming to open source for the first time. Success as an Apache contributor stresses skills not emphasized in other types of software development, including reconciling the requirements of the upstream development process with the realities of running a commercial software business.
-
- With the assistance of choreographed Socratic dialogue, our two protagonists, an experienced Apache committer and an enthusiastic young gun contributor, explore the tensions of working on an Apache project as employees of a for-profit company. The audience will learn practical advice and problem solving techniques for working effectively as part of an Apache community. By the end, our greenhorn comes to understand that the yin and yang of commercial software development and the Apache [...]
-
- Our talk contextualizes the Apache Way for developers who are paid to work on open-source full-time, drawn from our real-world experience working at Cloudera. This is presented through a series of short vignettes accompanied by intervening discussion and review slides. Tenets of the Apache Way like meritocracy, community, and hats are introduced and referred to throughout as the backbone to building strong open-source communities. We examine the tension between corporate pressures and [...]
-
- Our two main characters are:
- * Alex, an energetic young developer who is new to open source but not to development. Excited to get stuff done on this new project.
- * Andrew, a long-time Apache committer who takes Alex under his wing and teaches him the importance of open-source.
-
- The outline for our skits are:
- * Act 1: Introduction to Apache and the Apache Way, FAQs from Alex as someone getting started as a new contributor
- * Act 2: How to build consensus when there's conflict (e.g. someone -1's your patch), public communication, demonstrating merit and the path to committership
- * Act 3: No jerks allowed. Andrew does a heel turn and is ruling the project with an iron fist, Alex intervenes in a come-to-jesus/student-becomes-the-teacher moment. Re-emphasize the importance of community, and how dictators are bad for projects.
-
-audience: Community managers, developers, project managers involved with FOSS projects.
-slides:
-video: https://www.youtube.com/watch?v=ea_9qkaTeVw&index=26&list=PLbzoR-pLrL6pLDCyPxByWQwYTL-JrF5Rp
-topics:
-- apacheway
-- developers
-present_at:
-- http://apachecon.com/2017
-present_date: '2017-05-16'
diff --git a/static/speakers/talks/curcuru.yaml b/static/speakers/talks/curcuru.yaml
deleted file mode 100644
index 21763f0..0000000
--- a/static/speakers/talks/curcuru.yaml
+++ /dev/null
@@ -1,10 +0,0 @@
----
-name: Shane Curcuru
-website: http://communityovercode.com/
-twitter: shanecurcuru
-facebook:
-bio: |
- Shane has been involved at the Apache Software Foundation (ASF) since 1999, and serves as Director and VP of Brand Management, setting trademark policies and helping all 200+ Apache projects implement and defend their brands.
-
- Otherwise, Shane is: a father and husband, a friend, a geek, a Member of the ASF, a baker, and a punny guy. Oh, and we have cats. Shane blogs at http://communityovercode.com/ and regularly speaks on FOSS governance and branding topics.
-
diff --git a/static/speakers/talks/sblackmon.yaml b/static/speakers/talks/sblackmon.yaml
deleted file mode 100644
index 8fc92fa..0000000
--- a/static/speakers/talks/sblackmon.yaml
+++ /dev/null
@@ -1,8 +0,0 @@
----
-name: Steve Blackmon
-website:
-twitter: steveblackmon
-facebook:
-bio: |
- VP Technology at People Pattern, previously Director of Data Science at W2O Group, co-founder of Ravel, stints at Boeing, Lockheed Martin, and Accenture. Committer and PMC for Apache Streams (incubating). Experienced user of Spark, Storm, Hadoop, Pig, Hive, Nutch, Cassandra, Tinkerpop, and more.
-
\ No newline at end of file
diff --git a/static/speakers/talks/sharan.yaml b/static/speakers/talks/sharan.yaml
deleted file mode 100644
index 37dfb82..0000000
--- a/static/speakers/talks/sharan.yaml
+++ /dev/null
@@ -1,8 +0,0 @@
----
-name: Sharan Foga
-website:
-twitter:
-facebook:
-bio: |
- Sharan Foga have been involved with the ASF since 2008 and has presented at previous Apachecons (Vancouver 2016, Budapest 2015 & 2014). She enjoys working on community management and related areas and is a Committer and PMC Member for Apache OFBiz and Community Development.
-
\ No newline at end of file
diff --git a/static/speakers/talks/wang.yaml b/static/speakers/talks/wang.yaml
deleted file mode 100644
index 0a67a44..0000000
--- a/static/speakers/talks/wang.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
----
-name: Andrew Wang
-website: http://umbrant.com/
-twitter:
-facebook:
-bio: |
- Andrew Wang is a software engineer at Cloudera on the HDFS team, where he has worked on projects including in-memory caching, transparent encryption, and erasure coding. Previously, he was a PhD student in the AMP Lab at UC Berkeley, where he worked on problems related to distributed systems and warehouse-scale computing. He is a committer and PMC member on the Apache Hadoop project, a committer on Apache Kudu (incubating), and holds masters and bachelors degrees in computer science fr [...]
diff --git a/static/speakers/themes/ASFTheme.kth b/static/speakers/themes/ASFTheme.kth
deleted file mode 100644
index c26618c..0000000
Binary files a/static/speakers/themes/ASFTheme.kth and /dev/null differ