This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch dfoulks/gha-site
in repository https://gitbox.apache.org/repos/asf/petri.git
The following commit(s) were added to refs/heads/dfoulks/gha-site by this push:
new 14860d4 Commit build products
14860d4 is described below
commit 14860d45d22283a148ac488fc1991bff8107d1e0
Author: Build Pelican (action) <priv...@infra.apache.org>
AuthorDate: Wed May 29 12:13:53 2024 +0000
Commit build products
---
output/buildstream.html | 16 +++----
output/cookbook.html | 15 +++---
output/faq.html | 123 +++++++++++++++++++++++++-----------------------
output/index.html | 9 ++--
output/mentors.html | 2 +-
output/projects.html | 8 ++--
output/way.html | 1 +
7 files changed, 90 insertions(+), 84 deletions(-)
diff --git a/output/buildstream.html b/output/buildstream.html
index 46d615a..fbbc3b1 100644
--- a/output/buildstream.html
+++ b/output/buildstream.html
@@ -192,7 +192,6 @@ li {
<!-- Licensed under ALv2 -->
-
<h2>About</h2>
<p>BuildStream is an integration build system.
It models dependencies at a project level, enabling projects to use their own
underlying build system.
@@ -201,21 +200,21 @@ The BuildStream implementation uses Remote Execution
concepts directly, even for
<p>BuildStream supports multiple build-systems (e.g. autotools, cmake, cpan,
distutils, make, meson, qmake, pip)
through its plugins.</p>
<h3>Website</h3>
-<p>https://www.buildstream.build</p>
+<p><a
href="https://www.buildstream.build";>https://www.buildstream.build</a></p>
<h3>Mailing Lists</h3>
<ul>
-<li>Developer discussions - d...@buildstream.apache.org</li>
-<li>Private - priv...@buildstream.apache.org</li>
-<li>Commit messages - comm...@buildstream.apache.org</li>
+<li>Developer discussions - <a
href="mailto:d...@buildstream.apache.org";>d...@buildstream.apache.org</a></li>
+<li>Private - <a
href="mailto:priv...@buildstream.apache.org";>priv...@buildstream.apache.org</a></li>
+<li>Commit messages - <a
href="mailto:comm...@buildstream.apache.org";>comm...@buildstream.apache.org</a></li>
</ul>
<h3>Source Code Repository</h3>
-<p>https://github.com/apache/buildstream</p>
+<p><a
href="https://github.com/apache/buildstream";>https://github.com/apache/buildstream</a></p>
<h3>Issue Tracker</h3>
-<p>https://github.com/apache/buildstream/issues</p>
+<p><a
href="https://github.com/apache/buildstream/issues";>https://github.com/apache/buildstream/issues</a></p>
<h3>Wiki</h3>
<p>None</p>
<h3>Releases (not Apache Licensed)</h3>
-<p>https://buildstream.build/install.html</p>
+<p><a
href="https://buildstream.build/install.html";>https://buildstream.build/install.html</a></p>
<h3>Apache Licensing Transitions</h3>
<ul>
<li>An SGA has been provided</li>
@@ -235,6 +234,7 @@ through its plugins.</p>
<li><a
href="https://github.com/apache/petri/blob/master/info.yaml";>info.yaml</a></li>
</ul>
+
</article>
<h2><span class="badge badge-secondary"><a
href="https://github.com/apache/petri/blob/master/content/buildstream.md";
style="color:white">Page Source</a></span></h2>
</div>
diff --git a/output/cookbook.html b/output/cookbook.html
index e3dcedb..094a190 100644
--- a/output/cookbook.html
+++ b/output/cookbook.html
@@ -196,7 +196,7 @@ li {
<p>During its time in Petri a culture may go through a number of transitions.
We track these on a web page.</p>
<h3>About</h3>
<p>This section should describe the project.
-Whenever a community begins to call itself Apache Foo then it needs to provide
a DISCLAIMER. Contact disc...@petri.apache.org for the text.</p>
+Whenever a community begins to call itself Apache Foo then it needs to provide
a DISCLAIMER. Contact <a
href="mailto:disc...@petri.apache.org";>disc...@petri.apache.org</a> for the
text.</p>
<h3>Website</h3>
<p>Provide the current website for the project community. When the community
wishes Petri will guide in the creation of a website on Apache
Infrastructure.</p>
<h3>Mailing Lists</h3>
@@ -212,15 +212,15 @@ This will require an SGA be filed (See below.)</p>
Other Wikis would require other support which should be discussed with your
mentors.</p>
<h3>Releases (not Apache)</h3>
<p>The URL where project releases can be found. The assumption is that
releases will not be Apache releases until late in the process.
-Once an Apache Release has been made then the "not" can be struck.</p>
+Once an Apache Release has been made then the "not" can be
struck.</p>
<h3>Licensing Transitions</h3>
<p>The community needs to undertake some license transitions if their intent
is to become an Apache PMC (TLP).</p>
<ul>
-<li>"No SGA" or "SGA provided". <a
href="https://www.apache.org/licenses/contributor-agreements.html#grants";>Software
License Grant</a></li>
-<li>"No ICLAs" or "ICLAs provided". <a
href="https://www.apache.org/licenses/contributor-agreements.html#clas";>Contributor
License Agreements</a></li>
-<li>"No ASF Headers" or "ASF Headers Applied". <a
href="https://infra.apache.org/apply-license.html";>Applying the Apache
License</a></li>
-<li>"No Apache LICENSE" or "LICENSE approved". <a
href="http://www.apache.org/legal/release-policy.html";>Understanding Release
Policy</a></li>
-<li>"No Apache NOTICE" or "NOTICE approved". <a
href="http://www.apache.org/legal/release-policy.html";>Understanding Release
Policy</a></li>
+<li>"No SGA" or "SGA provided". <a
href="https://www.apache.org/licenses/contributor-agreements.html#grants";>Software
License Grant</a></li>
+<li>"No ICLAs" or "ICLAs provided". <a
href="https://www.apache.org/licenses/contributor-agreements.html#clas";>Contributor
License Agreements</a></li>
+<li>"No ASF Headers" or "ASF Headers Applied". <a
href="https://infra.apache.org/apply-license.html";>Applying the Apache
License</a></li>
+<li>"No Apache LICENSE" or "LICENSE approved". <a
href="http://www.apache.org/legal/release-policy.html";>Understanding Release
Policy</a></li>
+<li>"No Apache NOTICE" or "NOTICE approved". <a
href="http://www.apache.org/legal/release-policy.html";>Understanding Release
Policy</a></li>
</ul>
<h3>Mentors</h3>
<p>A list of your current mentors.</p>
@@ -228,6 +228,7 @@ Once an Apache Release has been made then the "not" can be
struck.</p>
<p>The status information for a community should also be updated in
<a
href="https://github.com/apache/petri/blob/master/info.yaml";>info.yaml</a>.</p>
+
</article>
<h2><span class="badge badge-secondary"><a
href="https://github.com/apache/petri/blob/master/content/cookbook.md";
style="color:white">Page Source</a></span></h2>
</div>
diff --git a/output/faq.html b/output/faq.html
index b08323c..b0cc837 100644
--- a/output/faq.html
+++ b/output/faq.html
@@ -192,42 +192,41 @@ li {
<!-- Licensed under ALv2 -->
-
-<p>[TOC]</p>
-<h1>General</h1>
-<h2>What is Apache Petri?</h2>
-<p>The Apache Petri (as in “petri dish” –where cultures are grown and bloom)
committee
+<div id="toc"><ul><li><a class="toc-href" href="#general"
title="General">General</a><ul><li><a class="toc-href" href="#what is apache
petri?" title="What is Apache Petri?">What is Apache Petri?</a></li><li><a
class="toc-href" href="#how is petri different from the apache incubator?"
title="How is Petri different from the Apache Incubator?">How is Petri
different from the Apache Incubator?</a></li><li><a class="toc-href" href="#why
does this matter? what is special about the apache way?" [...]
+<h1 id="general">General</h1>
+<h2 id="what is apache petri?">What is Apache Petri?</h2>
+<p>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.</p>
-<p>Petri’s mission is to mentor existing external communities (“cultures”)
about
-“The Apache Way” by focusing on community governance that includes discussions
+<p>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.</p>
<p>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.</p>
<p>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”,
+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.</p>
-<h2>How is Petri different from the Apache Incubator?</h2>
+<h2 id="how is petri different from the apache incubator?">How is Petri
different from the Apache Incubator?</h2>
<p>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.</p>
-<p>“Podlings” in the Apache Incubator are provided a complete set of
Foundation-based
+<p>“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
+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
+be the new PMC’s first order of business (i.e. a transition plan would
be part of
the presentation to the Board).</p>
-<h2>Why does this matter? What is special about The Apache Way?</h2>
-<p>The Apache Way is the ASF’s process of community-led development is the
backbone
+<h2 id="why does this matter? what is special about the apache way?">Why does
this matter? What is special about The Apache Way?</h2>
+<p>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:</p>
<ul>
@@ -251,46 +250,46 @@ that defines which licenses are allowable on software
reused within Apache proje
<li>The license, as applied in practice, must not impose significant
restrictions beyond those imposed by the Apache License 2.0.</li>
</ul>
</blockquote>
-<h2>What does “Direct to TLP” entail?</h2>
+<h2 id='what does "direct to tlp" entail?'>What does “Direct to
TLP” entail?</h2>
<p>The Board makes the ultimate decision, and generally ensures that the
project has:</p>
<ul>
<li>Demonstrated
- <a href="https://community.apache.org/projectIndependence.html";>vendor
neutrality</a>
- in the
- <a
href="https://incubator.apache.org/guides/community.html";>community</a>;</li>
+<a href="https://community.apache.org/projectIndependence.html";>vendor
neutrality</a>
+in the
+<a
href="https://incubator.apache.org/guides/community.html";>community</a>;</li>
<li>Demonstrated understanding of the
- <a href="https://www.apache.org/legal/release-policy.html";>Apache Release
Policy</a>
- including <a href="https://infra.apache.org/apply-license.html";>Applying the
Apache License</a>;</li>
+<a href="https://www.apache.org/legal/release-policy.html";>Apache Release
Policy</a>
+including <a href="https://infra.apache.org/apply-license.html";>Applying the
Apache License</a>;</li>
<li>Completed
- <a
href="https://www.apache.org/licenses/contributor-agreements.html";>Contributor
Licence Agreements and Software Grant Agreements</a>;</li>
+<a
href="https://www.apache.org/licenses/contributor-agreements.html";>Contributor
Licence Agreements and Software Grant Agreements</a>;</li>
<li>Performed a
- <a href="https://incubator.apache.org/guides/names.html";>Suitable Name
Search</a>;</li>
+<a href="https://incubator.apache.org/guides/names.html";>Suitable Name
Search</a>;</li>
<li>Developed a
- <a
href="https://incubator.apache.org/guides/transitioning_asf.html";>Transition
Plan</a>
- to move the project's resources to the ASF;</li>
+<a
href="https://incubator.apache.org/guides/transitioning_asf.html";>Transition
Plan</a>
+to move the project's resources to the ASF;</li>
<li>Shown how the community will
- <a href="https://incubator.apache.org/guides/community.html";>recognize
merit</a>; and</li>
+<a href="https://incubator.apache.org/guides/community.html";>recognize
merit</a>; and</li>
<li>Shown auditable decision making on the provided mailing list.</li>
</ul>
-<h2>Is Apache Petri right for you?</h2>
+<h2 id="is apache petri right for you?">Is Apache Petri right for you?</h2>
<p>If you are:</p>
<ul>
<li>An established, diverse community that already releases quickly; or</li>
-<li>A project with a single “leader” that seeks to grow to a community-driven
- development model; or</li>
+<li>A project with a single “leader” that seeks to grow to a
community-driven
+development model; or</li>
<li>A company that has an Open Source project with other vendors and wants to
- expand and diversify its community...</li>
+expand and diversify its community...</li>
</ul>
<p>And you are:</p>
<ul>
<li>Willing to license your project's works under the <a
href="https://www.apache.org/licenses/LICENSE-2.0.html";>Apache License, Version
2</a>.</li>
</ul>
<p>Petri would help the community learn how to integrate governance and
-development “The Apache Way” without interrupting the project’s velocity.</p>
-<p>In keeping with the ASF’s slogan of “Community Over Code”, we are unable to
+development “The Apache Way” without interrupting the
project’s velocity.</p>
+<p>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.</p>
-<h1>Process</h1>
-<h2>What about the Maturity Model? Haven’t other projects bypassed incubation
by meeting these requirements?</h2>
+<h1 id="process_1">Process</h1>
+<h2 id="what about the maturity model? haven't other projects bypassed
incubation by meeting these requirements?">What about the Maturity Model?
Haven’t other projects bypassed incubation by meeting these
requirements?</h2>
<p>In March 2015 Apache Zest (now Polygene) became the first project to enter
the ASF as a Top-Level Project — without entering the Apache Incubator.
As
part of the discussion, the project
@@ -302,21 +301,21 @@ building, and independence, among other qualities.</p>
<p>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.</p>
-<h2>How long does the Petri process take?</h2>
-<p>There’s no “one size fits all” answer here. Some external projects have
+<h2 id="how long does the petri process take?">How long does the Petri process
take?</h2>
+<p>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
+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.</p>
<p>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.</p>
-<h2>Do people involved in Petri-mentored projects need to sign ICLAs?</h2>
+<h2 id="do people involved in petri-mentored projects need to sign iclas?">Do
people involved in Petri-mentored projects need to sign ICLAs?</h2>
<p>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.</p>
-<h2>If our project wants to become an official Apache project, what is the
best way to do so?</h2>
+<h2 id="if our project wants to become an official apache project, what is the
best way to do so?">If our project wants to become an official Apache project,
what is the best way to do so?</h2>
<p>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
@@ -324,34 +323,35 @@ a part of the ASF.</p>
<p>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.</p>
-<h2>If I propose my project to be mentored by Petri, will it be accepted?</h2>
+<h2 id="if i propose my project to be mentored by petri, will it be
accepted?">If I propose my project to be mentored by Petri, will it be
accepted?</h2>
<p>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.</p>
-<h2>What is the expected intake rate for Petri?</h2>
+<h2 id="what is the expected intake rate for petri?">What is the expected
intake rate for Petri?</h2>
<p>We anticipate 2-3 communities in the first year, with one per year likely
following that.</p>
-<h2>What should the Board expect from a Project that Petri Recommends to
become a TLP?</h2>
+<h2 id="what should the board expect from a project that petri recommends to
become a tlp?">What should the Board expect from a Project that Petri
Recommends to become a TLP?</h2>
<p>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 <strong>What does “Direct to TLP” entail</strong>
section:</p>
+items shared above, in the <strong>What does “Direct to TLP”
entail</strong> section:</p>
<ul>
<li><strong>Graduation Resolution</strong>. 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.</li>
+recruited then they will be included in the resolution. Apache
+Members like anyone else are certainly invited to contribute
+to the project.</li>
<li><strong>Transfer of Registered Trademarks</strong>. If there are any
registered
- trademarks then the transfer agreement will be discussed with
- the VP, Brand in advance.</li>
+trademarks then the transfer agreement will be discussed with
+the VP, Brand in advance.</li>
<li><strong>Software Grant</strong>. Petri should collect <a
href="https://www.apache.org/licenses/contributor-agreements.html#grants";>software
grants</a>.</li>
<li><strong>Committers</strong>. 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.</li>
+Petri can make the committers from a prospective community
+Petri committers in order to create accounts.</li>
<li><strong>Resources</strong>. Graduation proposals will include a
<strong>Transition Plan</strong>
- explaining the actions that the project has already taken or intends to take
once
- the PMC is established. This may include:</li>
+explaining the actions that the project has already taken or intends to take
once
+the PMC is established. This may include:
+<ul>
<li>Creating Apache project mailing lists</li>
<li>Creating Apache issue trackers</li>
<li>Creating Apache wikis</li>
@@ -365,29 +365,32 @@ items shared above, in the <strong>What does “Direct to
TLP” entail</strong>
<li>Creating and migrating CI, build, release processes to Apache Project</li>
<li>Establish processes for release distribution at Apache</li>
<li>New TLPs should report on their progress towards completing
- their Transition Plan in their Board Reports.</li>
+their Transition Plan in their Board Reports.</li>
</ul>
-<h2>Who will provide guidance once the Petri mentor is gone after the
assessment?</h2>
+</li>
+</ul>
+<h2 id="who will provide guidance once the petri mentor is gone after the
assessment?">Who will provide guidance once the Petri mentor is gone after the
assessment?</h2>
<p>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.</p>
-<h2>How can our project/community apply for Apache Petri mentorship?</h2>
-<p>Email disc...@petri.apache.org (public list; if you're not subscribe,
+<h2 id="how can our project/community apply for apache petri mentorship?">How
can our project/community apply for Apache Petri mentorship?</h2>
+<p>Email <a
href="mailto:disc...@petri.apache.org";>disc...@petri.apache.org</a> (public
list; if you're not subscribe,
ask explicitly to be Cc'd on replies)
-or priv...@petri.apache.org (private list, only Apache Petri PMC members
-and Apache Members can subscribe) and introduce yourself! We don’t
+or <a href="mailto:priv...@petri.apache.org";>priv...@petri.apache.org</a>
(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.</p>
-<h2>If a project wants to move out of the Apache Incubator and into Petri,
what happens?</h2>
-<p>We don’t recommend leaving the Incubator, if the podling is already
+<h2 id="if a project wants to move out of the apache incubator and into petri,
what happens?">If a project wants to move out of the Apache Incubator and into
Petri, what happens?</h2>
+<p>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
+Petri will then take responsibility for the podling’s resources, and
perform any needed changes to make that happen.</p>
+
</article>
<h2><span class="badge badge-secondary"><a
href="https://github.com/apache/petri/blob/master/content/faq.md";
style="color:white">Page Source</a></span></h2>
</div>
diff --git a/output/index.html b/output/index.html
index 19383cc..0066867 100644
--- a/output/index.html
+++ b/output/index.html
@@ -192,11 +192,9 @@ li {
<!-- Licensed under ALv2 -->
-
<div style="margin-left: 1rem;" class="float-right">
<p><img src="images/logo.svg" alt="Apache Petri Logo" width="300"
height="135"></p>
</div>
-
<p>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
@@ -207,7 +205,7 @@ about ASF policies. The mentoring and education is
conducted on a mailing list.<
<p>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.</p>
-<h2>About "The Apache Way"</h2>
+<h2>About "The Apache Way"</h2>
<ul>
<li><a href="https://www.apache.org/theapacheway/index.html";>The Apache
Way</a></li>
<li><a href="https://s.apache.org/GhnI";>Sustainable Open Source</a></li>
@@ -218,11 +216,11 @@ external community.</p>
<h2>Which communities are currently mentored by Apache Petri?</h2>
<p>None Currently</p>
<h2>How can our project/community apply for Apache Petri mentorship?</h2>
-<p>Email disc...@petri.apache.org (public list; subscription not required) or
priv...@petri.apache.org (private list,
+<p>Email <a
href="mailto:disc...@petri.apache.org";>disc...@petri.apache.org</a> (public
list; subscription not required) or <a
href="mailto:priv...@petri.apache.org";>priv...@petri.apache.org</a> (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.</p>
<h2>Do you have additional questions?</h2>
-<p>Please read our <a href="/faq">FAQ</a> or ask questions on
disc...@petri.apache.org</p>
+<p>Please read our <a href="/faq">FAQ</a> or ask questions on <a
href="mailto:disc...@petri.apache.org";>disc...@petri.apache.org</a></p>
<h2>Petri Repositories and Issue Tracking</h2>
<ul>
<li><a href="https://github.com/apache/petri";>Website</a></li>
@@ -234,6 +232,7 @@ questionnaires, but may introduce these should the need
arise.</p>
<li><a href="https://projects.apache.org/project.html?petri";>petri.rdf</a></li>
</ul>
+
</article>
<h2><span class="badge badge-secondary"><a
href="https://github.com/apache/petri/blob/master/content/index.md";
style="color:white">Page Source</a></span></h2>
</div>
diff --git a/output/mentors.html b/output/mentors.html
index 62d94af..555f67d 100644
--- a/output/mentors.html
+++ b/output/mentors.html
@@ -192,7 +192,6 @@ li {
<!-- Licensed under ALv2 -->
-
<h2>Introduction</h2>
<p>Mentors at Apache Petri provides insight into the Apache Way and general
oversight of the learning process
for projects within the Apache Petri.</p>
@@ -208,6 +207,7 @@ for projects within the Apache Petri.</p>
<li>Sander Striker (striker)</li>
</ul>
+
</article>
<h2><span class="badge badge-secondary"><a
href="https://github.com/apache/petri/blob/master/content/mentors.md";
style="color:white">Page Source</a></span></h2>
</div>
diff --git a/output/projects.html b/output/projects.html
index cb15d21..ce35444 100644
--- a/output/projects.html
+++ b/output/projects.html
@@ -192,7 +192,6 @@ li {
<!-- Licensed under ALv2 -->
-
<h2>Project Status</h2>
<ul>
<li>Machine readable status <a
href="https://petri.apache.org/info.yaml";>info.yaml</a> -- <a
href="https://github.com/apache/petri/blob/master/content/info.yaml";>source</a></li>
@@ -202,9 +201,12 @@ li {
<p>No cultures currently in Petri.</p>
<h2>Past Cultures</h2>
<ul>
-<li><a href="buildstream">BuildStream</a> -- <a
href="https://github.com/apache/petri/blob/master/content/pages/buildstream.md";>source</a></li>
-</ul>
+<li>
+<p><a href="buildstream">BuildStream</a> -- <a
href="https://github.com/apache/petri/blob/master/content/pages/buildstream.md";>source</a></p>
<p>BuildStream is an integration build system. It models dependencies at a
project level, enabling projects to use their own underlying build system</p>
+</li>
+</ul>
+
</article>
<h2><span class="badge badge-secondary"><a
href="https://github.com/apache/petri/blob/master/content/projects.md";
style="color:white">Page Source</a></span></h2>
diff --git a/output/way.html b/output/way.html
index 7eb0ffb..f287f97 100644
--- a/output/way.html
+++ b/output/way.html
@@ -218,6 +218,7 @@ li {
</li>
</ul>
+
</article>
<h2><span class="badge badge-secondary"><a
href="https://github.com/apache/petri/blob/master/content/way.md";
style="color:white">Page Source</a></span></h2>
</div>
