Delete content directory

3 years ago · 8e6ca8f066
--- a/content/.htaccess
+++ b/content/.htaccess
@ -1,3 +0,0 @@
 RewriteEngine On
 RewriteCond %{HTTPS} off
 RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
--- a/content/README.md
+++ b/content/README.md
@ -1 +0,0 @@
 This is the top level of the content tree
--- a/content/archive.ezmd
+++ b/content/archive.ezmd
@ -1,3 +0,0 @@
 Title: Apache Download Mirrors
 [insertfile "include/archive.ezt"]
--- a/content/blogs.ezmd
+++ b/content/blogs.ezmd
@ -1,23 +0,0 @@
 Title: Blogs
 version: 1.0
 <!-- Licensed under ALv2 -->
 ### Foundation
 [for foundation]
 #### Post
 [[][foundation.title]]([foundation.href])
 [format "raw"][foundation.content][end]
 [end]
 ### Planet
 [for planet]
 [[][planet.title]]([planet.href])
 [end]
 ### Conferences
 [for conferences]
 [[][conferences.title]]([conferences.href])
 [end]
--- a/content/board.ezmd
+++ b/content/board.ezmd
@ -1,6 +0,0 @@
 Title: Apache Board of Directors
 version: 1.0
 <!-- Licensed under ALv2 -->
 [for board]
 - [[][board.name]](mailto:[board.key_id]@apache.org)[end]
--- a/content/closer.ezmd
+++ b/content/closer.ezmd
@ -1,3 +0,0 @@
 Title: Apache Download Mirrors
 [insertfile "include/closer.ezt"]
--- a/content/committees.ezmd
+++ b/content/committees.ezmd
@ -1,8 +0,0 @@
 Title: Apache Committees
 version: 1.0
 <!-- Licensed under ALv2 -->
 | Committee   | Chair       | Paragraph       |
 | ----------- | ----------- | ----------- |
 [for committees][if-any committees.pmc][else]| [committees.display_name] | [committees.chair] | [committees.paragraph] |
 [end][end]
--- a/content/docs/dir_1/test1.txt
+++ b/content/docs/dir_1/test1.txt
@ -1 +0,0 @@
 Test file
--- a/content/docs/dir_2/test1.txt
+++ b/content/docs/dir_2/test1.txt
@ -1 +0,0 @@
 Test file
--- a/content/docs/test1.txt
+++ b/content/docs/test1.txt
@ -1 +0,0 @@
 Test file
--- a/content/downloads.ezmd
+++ b/content/downloads.ezmd
@ -1,18 +0,0 @@
 Title: Download Releases
 # Releases
 [[]TOC]
 ## Keys
 [[]KEYS]([release-keys])
 [for release]
 ## [release.name]
 [for release.release]* [[][release.release.release]](https://www.apache.org/dyn/closer.lua/[release-project]/[release.version]/[release.release.release])
  -- ([[]signature](https://downloads.apache.org/[release-project]/[release.version]/[release.release.signature]))
  -- ([[]checksum](https://downloads.apache.org/[release-project]/[release.version]/[release.release.checksum]))
  -- ([release.release.fsize])
  -- ([release.release.dtm])
 [end][end]
--- a/content/eccn.ezmd
+++ b/content/eccn.ezmd
@ -1,20 +0,0 @@
 Title: Export Notification
 version: 1.0
 asf_headings: False
 <!-- Licensed under ALv2 -->
 ## Structure
 We have ECCN.
 ### Project -- Contact
 - Product
  - Version / ECCN Classification / Controlled Sources
 ## Project Notifications
 [for eccn]
 ### [[][eccn.name]]([eccn.href])[if-any eccn.contact] -- [eccn.contact][end]
 [if-any eccn.product][for eccn.product]  - [eccn.product.name]
 [for eccn.product.versions]    - [eccn.product.versions.version] / [eccn.product.versions.eccn]
 [for eccn.product.versions.source]    / [[][eccn.product.versions.source.manufacturer]]([eccn.product.versions.source.href] "[eccn.product.versions.source.why]")
 [end][end][end][end][end]
--- a/content/faq.md
+++ b/content/faq.md
@ -1,237 +0,0 @@
 Title: Apache Petri - FAQ
 source_button: yes
 <!-- Licensed under ALv2 -->
 [TOC]
 # General
 ## What is Apache Petri?
 The Apache Petri (as in “petri dish” –where cultures are grown and bloom) committee
 assists external project communities interested in becoming an Apache project to
 learn how The Apache Software Foundation (ASF) works, its views on community, and
 how to build a healthy community for the long -term.
 Petri’s mission is to mentor existing external communities (“cultures”) about
 “The Apache Way” by focusing on community governance that includes discussions
 about ASF policies. The mentoring and education is conducted on a mailing list.
 The primary goal is to reach a point where a recommendation to the ASF Board can
 be made to construct a new Apache Project Management Committee (PMC) for the
 external community.
 In the Incubator model, projects graduate to become Apache Top-Level Projects (TLPs).
 Under Petri, projects can become TLPs under a process described as “direct to TLP”,
 which is an alternative path to that used by the Apache Incubator. Apache Petri aims
 to shepherd projects and their communities to a point of confidence that the
 ASF Board will welcome the community to the Apache family of projects as a
 Top-Level Project.
 ## How is Petri different from the Apache Incubator?
 Apache Petri provides an alternative process to Incubation that would be suitable
 for some projects and their communities. Petri provides educational resources, and
 mentors external groups on their path to becoming an official project of the ASF.
 The primary goal is to reach a point where a recommendation to the ASF Board can
 be made to construct a PMC for the community.
 “Podlings” in the Apache Incubator are provided a complete set of Foundation-based
 resources upon their acceptance into the Incubator. Since Petri will begin
 mentoring the community “where they live”, it will not provide an initial set of
 resources. Over time, as part of the education process and shift of the community
 towards the Foundation, resources will be provided as appropriate. It is expected
 that once a PMC is constructed, any resources not hosted at the Foundation will
 be the new PMC’s first order of business (i.e. a transition plan would be part of
 the presentation to the Board).
 <h2 id="whats-special">Why does this matter? What is special about The Apache Way?
 <a class="headerlink" href="#whats-special" title="Permanent link">¶</a></h2>
 The Apache Way is the ASF’s process of community-led development is the backbone
 of all Apache projects, and emulated by many Open Source foundations. The Apache
 Way comprises:
 * Earned Authority (merit);
 * Community of Peers;
 * Open Communications;
 * Consensus Decision Making; and
 * Responsible Oversight.
 For more information, see [The Apache Way](https://www.apache.org/theapacheway/).
 The Apache Software Foundation's mission is to provide software for the public good.
 Quoting from [The Apache Way to Sustainable Open Source Success](https://s.apache.org/GhnI):
 > To allow us to deliver on this part of the mission, it is critical that we adopt a
 > license that uses the law to protect the software curated here at the Foundation.
 > For us that license is the [Apache License, Version 2](https://www.apache.org/licenses/LICENSE-2.0.html).
 > In addition, we adopt an [inbound licensing policy](https://apache.org/legal/resolved.html)
 > that defines which licenses are allowable on software reused within Apache projects. This policy can be summarized as:
 >
 > * The license must meet the [Open Source Definition (OSD)](https://opensource.org/osd).
 > * The license, as applied in practice, must not impose significant restrictions beyond those imposed by the Apache License 2.0.
 ## What does “Direct to TLP” entail?
 The Board makes the ultimate decision, and generally ensures that the project has:
 * Demonstrated
  [vendor neutrality](https://community.apache.org/projectIndependence.html)
  in the
  [community](https://incubator.apache.org/guides/community.html);
 * Demonstrated understanding of the
  [Apache Release Policy](https://www.apache.org/legal/release-policy.html)
  including [Applying the Apache License](https://infra.apache.org/apply-license.html);
 * Completed
  [Contributor Licence Agreements and Software Grant Agreements](https://www.apache.org/licenses/contributor-agreements.html);
 * Performed a
  [Suitable Name Search](https://incubator.apache.org/guides/names.html);
 * Developed a
  [Transition Plan](https://incubator.apache.org/guides/transitioning_asf.html)
  to move the project's resources to the ASF;
 * Shown how the community will
  [recognize merit](https://incubator.apache.org/guides/community.html); and
 * Shown auditable decision making on the provided mailing list.
 ## Is Apache Petri right for you?
 If you are:
 * An established, diverse community that already releases quickly; or
 * A project with a single “leader” that seeks to grow to a community-driven
  development model; or
 * A company that has an Open Source project with other vendors and wants to
  expand and diversify its community...
 And you are:
 * Willing to license your project's works under the [Apache License, Version 2](https://www.apache.org/licenses/LICENSE-2.0.html).
 Petri would help the community learn how to integrate governance and
 development “The Apache Way” without interrupting the project’s velocity.
 In keeping with the ASF’s slogan of “Community Over Code”, we are unable to
 accept projects that are not supported by some form of community.
 # Process
 ## What about the Maturity Model? Have other projects bypassed incubation by meeting these requirements?
 In March 2015 Apache Zest (now Polygene) became the first project to enter
 the ASF as a Top-Level Project &mdash; without entering the Apache Incubator. As
 part of the discussion, the project
 [chose to review itself](https://mail-private.apache.org/members/private-arch/board/201502.mbox/%3CCADmm%2BKf9A1O%2B%3DKOd9__sDF2-kMh9b3iy3cf4NCRUnSDOPDq92w%40mail.gmail.com%3E)
 (private link) against the
 [Apache Maturity Model](http://s.apache.org/O4p), that addresses the integrity
 of a project's code, copyright, licenses, releases, community, consensus
 building, and independence, among other qualities.
 The Apache Maturity Model will not be a requirement for communities (as the
 Model does not have broad consensus as a true and thorough viewpoint), but
 the Model may provide a helpful guide for some.
 ## How long does the Petri process take?
 There’s no “one size fits all” answer here. Some external projects have
 applied to the Apache Board to become TLPs, and have become TLPs without
 going through either Petri or the Incubator. Historically, every project’s
 experience and time spent in the Apache Incubator varies, depending on its
 specific needs and circumstances; this has ranged from less than one year
 to more than three years.
 Similarly, some projects undergoing Petri mentorship will take longer
 than others. Petri is more about education about The Apache Way of project
 governance and Apache Policy, and less about process.
 ## Do people involved in Petri-mentored projects need to sign ICLAs?
 No, unless the projects intend to apply for TLP status and migrate their
 source control to ASF hardware. This applies both to Incubator podlings
 and direct-to-TLP applicants.
 ## If our project wants to become an official Apache project, what is the best way to do so?
 There is more than one way to do so: not all incoming projects will be
 mentored by Petri. Traditionally, the Apache Incubator has been the entry
 path for external projects, codebases, and communities wishing to become
 a part of the ASF.
 Petri's primary goal is preparing a community for Direct-to-TLP; moving
 from Petri to become a podling undergoing development in the Apache Incubator
 is a possibility, but not mandated.
 ## If I propose my project to be mentored by Petri, will it be accepted?
 That depends. First, there have to be available mentors. Second, the Petri
 PMC may have to rate-limit intake, especially at first, in order not to
 stretch itself too thin with its oversight duties. This is true of the
 entire ASF: the Board may put intake of new TLPs on hold from time to
 time, though it has never yet done that to date.
 ## What is the expected intake rate for Petri?
 We anticipate 2-3 communities in the first year, with one per year likely following that.
 ## What should the Board expect from a Project that Petri Recommends to become a TLP?
 This list is only complete in that we are considering what the Board
 currently seems to require and it is as always up to the Board the
 requirements for any particular TLP. In addition to the list of
 items shared above, in the **What does “Direct to TLP” entail** section:
 * **Graduation Resolution**. If there are Apache Members involved or
  recruited then they will be included in the resolution. Apache
  Members like anyone else are certainly invited to contribute
  to the project.
 * **Transfer of Registered Trademarks**. If there are any registered
  trademarks then the transfer agreement will be discussed with
  the VP, Brand in advance.
 * **Software Grant**. Petri should collect [software grants](https://www.apache.org/licenses/contributor-agreements.html#grants).
 * **Committers**. Petri can collect ICLAs in advance of going to TLP.
  Petri can make the committers from a prospective community
  Petri committers in order to create accounts.
 * **Resources**. Graduation proposals will include a **Transition Plan**
  explaining the actions that the project has already taken or intends to take once
  the PMC is established. This may include:
  * Creating Apache project mailing lists
  * Creating Apache issue trackers
  * Creating Apache wikis
  * Creating Apache code repositories
  * Migrating code repositories to Apache
  * Applying the Apache License
  * Creating Apache web presence
  * Migrating web presence from Project to Apache
  * Rebranding web, code, documentation from Project to Apache Project
  * Retiring external Project and redirecting to Apache
  * Creating and migrating CI, build, release processes to Apache Project
  * Establish processes for release distribution at Apache
  * New TLPs should report on their progress towards completing
    their Transition Plan in their Board Reports.
 ## Who will provide guidance once the Petri mentor is gone after the assessment?
 This assumes that the Mentor is no longer interested in the community
 once it is assessed. Even if this were true TLPs have a range of Apache
 committees and resources available. If necessary the Board can provide
 additional guidance through the normal reporting process as the Board
 does for every PMC.
 ## How can our project/community apply for Apache Petri mentorship?
 Email discuss@petri.apache.org (public list; if you're not subscribe,
 ask explicitly to be Cc'd on replies)
 or private@petri.apache.org (private list, only Apache Petri PMC members
 and Apache Members can subscribe) and introduce yourself! We don’t
 have any forms or questionnaires, but may introduce these should
 the need arise.
 ## If a project wants to move out of the Apache Incubator and into Petri, what happens?
 We don’t recommend leaving the Incubator, if the podling is already
 established there; podlings should strive to graduate. In the event
 a community is unwilling to wait for graduation, and Petri has
 accepted them, then the Incubator will need to retire the podling.
 Petri will then take responsibility for the podling’s resources, and
 perform any needed changes to make that happen.
--- a/content/featured.ezmd
+++ b/content/featured.ezmd
@ -1,13 +0,0 @@
 Title: Featured
 version: 1.0
 <!-- Licensed under ALv2 -->
 ## Projects
 [for featured_projs]
 <img alt="Logo" width="100" src="https://www.apache.org/[featured_projs.logo]"/> [[]Apache [featured_projs.display_name]]([featured_projs.site])
 [end]
 ## Podlings
 [for featured_pods]
 <img alt="Logo" width="100" src="https://www.apache.org/[featured_pods.logo]"/> [[]Apache [featured_pods.name]]([featured_pods.homepage])
 [end]
--- a/content/images/logo.png
+++ b/content/images/logo.png
--- a/content/images/logo.svg
+++ b/content/images/logo.svg
--- a/content/include/archive.ezt
+++ b/content/include/archive.ezt
@ -1,34 +0,0 @@
 <h1 id="verify">Verify the integrity of the files<a class="headerlink" href="#verify" title="Permanent link">&para;</a></h1>
 <p>It is essential that you verify the integrity of the downloaded file using
 the PGP signature (<code>.asc</code> file) or a hash (<code>.md5</code> or <code>.sha*</code> file). Please read <a href="/info/verification.html">Verifying Apache Software
 Foundation Releases</a> for more information on why
 you should verify our releases.</p>
 <p>The PGP signature can be verified using PGP or GPG. First download the
 <code>KEYS</code> as well as the <code>asc</code> signature file for the relevant distribution.
 Make sure you get these files from the main distribution site, rather than
 from a mirror. Then verify the signatures using</p>
 <div class="codehilite"><pre><span class="c">% gpg --import KEYS</span>
 <span class="c">% gpg --verify downloaded_file.asc downloaded_file</span>
 </pre></div>
 <p><em>or</em></p>
 <div class="codehilite"><pre><span class="c">% pgpk -a KEYS</span>
 <span class="c">% pgpv downloaded_file.asc</span>
 </pre></div>
 <p><em>or</em></p>
 <div class="codehilite"><pre><span class="c">% pgp -ka KEYS</span>
 <span class="c">% pgp downloaded_file.asc</span>
 </pre></div>
 <p>Alternatively, you can verify the MD5 hash on the file. A unix
 program called <code>md5</code> or <code>md5sum</code> is included in many unix distributions. It
 is also available as part of
 <a href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>.
 Windows users can get binary md5 programs from
 <a href="http://www.fourmilab.ch/md5/">here</a>,
 <a href="http://www.pc-tools.net/win32/freeware/console/">here</a> , or
 <a href="http://www.slavasoft.com/fsum/">here</a>.</p>
--- a/content/include/closer.ezt
+++ b/content/include/closer.ezt
@ -1,67 +0,0 @@
 <p>[if-any logo] <a href="[link]"><img alt="[logo]" src="[logo]" /></a> [end] We suggest the following mirror
 site for your download:</p>
 <p><a href="[preferred][path_info]"><strong>[preferred][path_info]</strong></a> </p>
 <p>Other mirror sites are suggested below.</p>
 <p>It is essential that you <a href="#verify">verify the integrity</a> of the downloaded file using
 the PGP signature (<code>.asc</code> file) or a hash (<code>.md5</code> or <code>.sha*</code> file).</p>
 <p>Please only use the backup mirrors to download KEYS, PGP signatures and hashes (SHA* etc)
 <p>[if-any http]</p>
 <h1 id="http">HTTP<a class="headerlink" href="#http" title="Permanent link">&para;</a></h1>
 <p>[for http] <a href="[http][path_info]"><strong>[http][path_info]</strong></a> <br></br>[end]</p>
 <p>[end]</p>
 <p>[if-any ftp]</p>
 <h1 id="ftp">FTP<a class="headerlink" href="#ftp" title="Permanent link">&para;</a></h1>
 <p>[for ftp] <a href="[ftp][path_info]"><strong>[ftp][path_info]</strong></a> <br></br>[end]</p>
 <p>[end]</p>
 <h1 id="backup">Backup Sites<a class="headerlink" href="#backup" title="Permanent link">&para;</a></h1>
 <p>Please only use the backup mirrors to download KEYS, PGP signatures and hashes (SHA* etc)
 <p>[if-any backup] [for backup] <a href="[backup][path_info]"><strong>[backup][path_info]</strong></a> <br></br>[end] [end]</p>
 <p>The <a href="http://www.apache.org/mirrors/">full listing of mirror sites</a> is also
 available.</p>
 <h1 id="become">Becoming a mirror<a class="headerlink" href="#become" title="Permanent link">&para;</a></h1>
 <p>The procedure for setting up new mirrors is described in <a href="http://www.apache.org/info/how-to-mirror.html">How to become a
 mirror</a>.</p>
 <h1 id="verify">Verify the integrity of the files<a class="headerlink" href="#verify" title="Permanent link">&para;</a></h1>
 <p>It is essential that you verify the integrity of the downloaded file using
 the PGP signature (<code>.asc</code> file) or a hash (<code>.md5</code> or <code>.sha*</code> file). Please read <a href="/info/verification.html">Verifying Apache Software
 Foundation Releases</a> for more information on why
 you should verify our releases.</p>
 <p>The PGP signature can be verified using PGP or GPG. First download the
 <code>KEYS</code> as well as the <code>asc</code> signature file for the relevant distribution.
 Make sure you get these files from the main distribution site, rather than
 from a mirror. Then verify the signatures using</p>
 <div class="codehilite"><pre><span class="c">% gpg --import KEYS</span>
 <span class="c">% gpg --verify downloaded_file.asc downloaded_file</span>
 </pre></div>
 <p><em>or</em></p>
 <div class="codehilite"><pre><span class="c">% pgpk -a KEYS</span>
 <span class="c">% pgpv downloaded_file.asc</span>
 </pre></div>
 <p><em>or</em></p>
 <div class="codehilite"><pre><span class="c">% pgp -ka KEYS</span>
 <span class="c">% pgp downloaded_file.asc</span>
 </pre></div>
 <p>Alternatively, you can verify the hash on the file.</p>
 <p>Hashes can be calculated using GPG:</p>
 <div class="codehilite"><pre><span class="c">% gpg --print-md SHA256 downloaded_file</span>
 </pre></div>
 <p>The output should be compared with the contents of the SHA256 file.
 Similarly for other hashes (SHA512, SHA1, MD5 etc) which may be provided.</p>
 <p>Windows 7 and later systems should all now have certUtil:</p>
 <div class="codehilite"><pre><span class="c">% certUtil -hashfile pathToFileToCheck [HashAlgorithm]</span>
 </pre></div>
 <p>HashAlgorithm choices: MD2 MD4 MD5 SHA1 SHA256 SHA384 SHA512</p>
 <p>Unix-like systems (and macOS) will have a utility called
 md5, md5sum or shasum</p>
--- a/content/index.ezmd
+++ b/content/index.ezmd
@ -1,37 +0,0 @@
 Title: What is Apache Petri?
 version: 1.0
 <!-- Licensed under ALv2 -->
 ![[]Apache Petri Logo](images/logo.svg) {.float-right}
 The Apache Template is an effort to show how to use **Pelican ASF**
 Here are various data inclusions:
 ["Title: %0, Version: %1" title version]
 [include "projects/projects.snippet"]
 {{ relative_source_path }} - {{ version }} - [{ board[1].name }] - {{ tester }}
 [{ ci[boardchair][roster] }] - [{ ci[tac][chair] }] - [{ ci[infrastructureadministrator][roster] }]
 [{ board[30].name }] - [{ eccn[11].product[0].name }] - [{ eccn[11].product[0].versions[0].version }]
 ## About "The Apache Way" {#the-way}
 - [[]The Apache Way](https://www.apache.org/theapacheway/index.html)
 - [[]Sustainable Open Source](https://s.apache.org/GhnI)
 - [[]How it Works](https://www.apache.org/foundation/how-it-works.html)
 - [[]Merit](https://www.apache.org/foundation/how-it-works.html#meritocracy)
 - [[]Success at Apache](https://blogs.apache.org/foundation/category/SuccessAtApache)
 Please read our [[]FAQ](/faq)
 ## Repositories and Issue Tracking
 - [[]Website](https://github.com/apache/template-site)
 - [[]Issues](https://github.com/apache/template-site/issues)
 <p>["Title: %0, Version: %1" title version]</p>
--- a/content/links.md
+++ b/content/links.md
@ -1,6 +0,0 @@
 title: Links
 <!-- Licensed under ALv2 -->
 ## Project Status
 - [Cookbook](projects/cookbook)
--- a/content/mentors.md
+++ b/content/mentors.md
@ -1,25 +0,0 @@
 title: Mentors at Apache Petri
 <!-- Licensed under ALv2 -->
 <script type="text/javascript">
 </script>
 <style></style>
 <iframe></iframe>
 ## Introduction
 Mentors at Apache Petri provides insight into the Apache Way and general oversight of the learning process
 for projects within the Apache Petri.
 ## Current mentors
 - Daniel Gruno (humbedooh)
 - Daniel Shahaf (danielsh)
 - Dave Fisher (wave)
 - David Nalley (ke4qqq)
 - Greg Stein (gstein)
 - Justin Erenkrantz (jerenkrantz)
 - Ross Gardler (rgardler)
 - Sander Striker (striker)
--- a/content/project_list.ezmd
+++ b/content/project_list.ezmd
@ -1,11 +0,0 @@
 Title: Apache Project List
 version: 1.0
 source_button: yes
 <!-- Licensed under ALv2 -->
 # Projects
 | Column 1    | Column 2    | Column 3    | Column 4    | Column 5    | Column 6    |
 | ----------- | ----------- | ----------- | ----------- | ----------- | ----------- |
 | [for pl_0][is pl_0.letter pl_0.display_name]**[pl_0.letter]**[else][[][pl_0.display_name]]([pl_0.site])[end]<br>[end] | [for pl_1][is pl_1.letter pl_1.display_name]**[pl_1.letter]**[else][[][pl_1.display_name]]([pl_1.site])[end]<br>[end] | [for pl_2][is pl_2.letter pl_2.display_name]**[pl_2.letter]**[else][[][pl_2.display_name]]([pl_2.site])[end]<br>[end] | [for pl_3][is pl_3.letter pl_3.display_name]**[pl_3.letter]**[else][[][pl_3.display_name]]([pl_3.site])[end]<br>[end] | [for pl_4][is pl_4.letter pl_4.display_name]**[pl_4.letter]**[else][[][pl_4.display_name]]([pl_4.site])[end]<br>[end] | [for pl_5][is pl_5.letter pl_5.display_name]**[pl_5.letter]**[else][[][pl_5.display_name]]([pl_5.site])[end]<br>[end] |
--- a/content/projects.ezmd
+++ b/content/projects.ezmd
@ -1,8 +0,0 @@
 Title: Apache Projects
 version: 1.0
 <!-- Licensed under ALv2 -->
 | Office    | Individual  |
 |-----------|-------------|  [for projects]
 | V.P., [if-any projects.site][[][end]Apache [projects.display_name][if-any projects.site]]([projects.site])[end] | [projects.chair] |[end]
--- a/content/projects/cookbook.md
+++ b/content/projects/cookbook.md
@ -1,53 +0,0 @@
 title: Cookbook
 <!-- Licensed under ALv2 -->
 ## Petri Cookbook
 [TOC]
 This describes a project community cookbook.
 ### About
 This section should describe the project.
 Whenever a community begins to call itself Apache Foo then it needs to provide a DISCLAIMER. Contact discuss@petri.apache.org for the text.
 [TOC]
 ### Website
 Provide the current website for the project community.
 ### Mailing Lists
 List the mailing lists used by the community.
 ### Source Code Repository
 Provide the url to the source code repository. This will usually require an SGA be filed (See below.)
 ### Issue Tracker
 Provide the address to your issue tracker. The ASF offers both JIRA and GitHub issue trackers. Bugzilla is also an option for older projects.
 ### Wiki
 Provide the address to your project wiki, if any. The ASF offers both Confluence and GitHub wikis.
 Other Wikis would require other support which should be discussed with your mentors.
 ### Releases
 The URL where project releases can be found.
 ### Licensing Transitions
 The community needs to undertake some license transitions.
 - "No SGA" or "SGA provided". [Software License Grant](https://www.apache.org/licenses/contributor-agreements.html#grants)
 - "No ICLAs" or "ICLAs provided". [Contributor License Agreements](https://www.apache.org/licenses/contributor-agreements.html#clas)
 - "No ASF Headers" or "ASF Headers Applied". [Applying the Apache License](https://infra.apache.org/apply-license.html)
 - "No Apache LICENSE" or "LICENSE approved". [Understanding Release Policy](http://www.apache.org/legal/release-policy.html)
 - "No Apache NOTICE" or "NOTICE approved". [Understanding Release Policy](http://www.apache.org/legal/release-policy.html)
 ### Mentors
 List your current mentors.
--- a/content/projects/projects.snippet
+++ b/content/projects/projects.snippet
@ -1,4 +0,0 @@
 ## Project Status
 - [[]Cookbook](projects/cookbook)
--- a/content/tweets.ezmd
+++ b/content/tweets.ezmd
@ -1,9 +0,0 @@
 Title: Tweets
 version: 1.0
 <!-- Licensed under ALv2 -->
 [for twitter]
 ## Tweet
 [twitter.id]
 [twitter.text]
 [end]