This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/petri-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new d6a99bf Automatic Site Publish by Buildbot
d6a99bf is described below
commit d6a99bfc906670537049f46429db2bded893b773
Author: buildbot <us...@infra.apache.org>
AuthorDate: Thu Mar 25 17:15:43 2021 +0000
Automatic Site Publish by Buildbot
---
output/buildstream.html | 16 +++++++-------
output/cookbook.html | 15 +++++++------
output/faq.html | 55 +++++++++++++++++++++++++----------------------
output/feeds/all.atom.xml | 2 +-
output/index.html | 9 ++++----
output/mentors.html | 2 +-
output/projects.html | 8 ++++---
output/sitemap.xml | 12 +++++------
8 files changed, 62 insertions(+), 57 deletions(-)
diff --git a/output/buildstream.html b/output/buildstream.html
index 2d66c46..91e5da3 100644
--- a/output/buildstream.html
+++ b/output/buildstream.html
@@ -181,7 +181,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.
@@ -190,21 +189,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>d...@buildstream.apache.org</li>
-<li>priv...@buildstream.apache.org</li>
-<li>comm...@buildstream.apache.org</li>
+<li><a
href="mailto:d...@buildstream.apache.org";>d...@buildstream.apache.org</a></li>
+<li><a
href="mailto:priv...@buildstream.apache.org";>priv...@buildstream.apache.org</a></li>
+<li><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)</h3>
-<p>https://buildstream.build/install.html</p>
+<p><a
href="https://buildstream.build/install.html";>https://buildstream.build/install.html</a></p>
<h3>Licensing Transitions</h3>
<ul>
<li>SGA provided</li>
@@ -228,6 +227,7 @@ through its plugins.</p>
<li><a
href="https://github.com/apache/petri-site/blob/master/content/pages/buildstream.md";>view
source</a></li>
</ul>
+
</div>
<footer class="navbar-expand-lg navbar-light bg-light">
diff --git a/output/cookbook.html b/output/cookbook.html
index fbab77a..d0e0bea 100644
--- a/output/cookbook.html
+++ b/output/cookbook.html
@@ -185,7 +185,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>
@@ -201,15 +201,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>
@@ -221,6 +221,7 @@ Once an Apache Release has been made then the "not" can be
struck.</p>
<li><a
href="https://github.com/apache/petri-site/blob/master/content/pages/cookbook.md";>view
source</a></li>
</ul>
+
</div>
<footer class="navbar-expand-lg navbar-light bg-light">
diff --git a/output/faq.html b/output/faq.html
index c0cef74..8713ddc 100644
--- a/output/faq.html
+++ b/output/faq.html
@@ -181,7 +181,6 @@ li {
<!-- Licensed under ALv2 -->
-
<h1>General</h1>
<h2>What is Apache Petri?</h2>
<p>The Apache Petri (as in “petri dish” –where cultures are grown and bloom)
committee
@@ -243,21 +242,21 @@ that defines which licenses are allowable on software
reused within Apache proje
<p>The Board makes the ultimate decision, and generally ensures that the
project has:</p>
<ul>
<li>Demonstrated
- <a href="http://community.apache.org/projectIndependence.html";>vendor
neutrality</a>
- in the
- <a
href="http://incubator.apache.org/guides/community.html";>community</a>;</li>
+<a href="http://community.apache.org/projectIndependence.html";>vendor
neutrality</a>
+in the
+<a href="http://incubator.apache.org/guides/community.html";>community</a>;</li>
<li>Demonstrated understanding of the
- <a href="http://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="http://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="http://incubator.apache.org/guides/transitioning_asf.html";>Transition
Plan</a>
- to move the project's resources to the ASF;</li>
+<a href="http://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="http://incubator.apache.org/guides/community.html";>recognize
merit</a>; and</li>
+<a href="http://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>
@@ -265,9 +264,9 @@ that defines which licenses are allowable on software
reused within Apache proje
<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>
+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>
@@ -280,7 +279,7 @@ 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>
<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
+the ASF as a Top-Level Project — without entering the Apache Incubator. As
part of the discussion, the project
<a
href="https://mail-private.apache.org/members/private-arch/board/201502.mbox/%3CCADmm%2BKf9A1O%2B%3DKOd9__sDF2-kMh9b3iy3cf4NCRUnSDOPDq92w%40mail.gmail.com%3E";>chose
to review itself</a>
(private link) against the
@@ -327,19 +326,20 @@ 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>
<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>
@@ -353,7 +353,9 @@ 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>
+</li>
</ul>
<h2>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
@@ -362,9 +364,9 @@ 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,
+<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
+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>
@@ -380,6 +382,7 @@ perform any needed changes to make that happen.</p>
<li><a
href="https://github.com/apache/petri-site/blob/master/content/pages/faq.md";>view
source</a></li>
</ul>
+
</div>
<footer class="navbar-expand-lg navbar-light bg-light">
diff --git a/output/feeds/all.atom.xml b/output/feeds/all.atom.xml
index 57a7ab5..b588c13 100644
--- a/output/feeds/all.atom.xml
+++ b/output/feeds/all.atom.xml
@@ -1,2 +1,2 @@
<?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom";><title>Apache Petri</title><link
href="https://petri.apache.org/"; rel="alternate"></link><link
href="https://petri.apache.org/feeds/all.atom.xml";
rel="self"></link><id>https://petri.apache.org/</id><updated>2021-03-25T17:12:43Z</updated></feed>
\ No newline at end of file
+<feed xmlns="http://www.w3.org/2005/Atom";><title>Apache Petri</title><link
href="https://petri.apache.org/"; rel="alternate"></link><link
href="https://petri.apache.org/feeds/all.atom.xml";
rel="self"></link><id>https://petri.apache.org/</id><updated>2021-03-25T17:15:43Z</updated></feed>
\ No newline at end of file
diff --git a/output/index.html b/output/index.html
index 6e84da5..2729fbb 100644
--- a/output/index.html
+++ b/output/index.html
@@ -181,11 +181,9 @@ li {
<!-- Licensed under ALv2 -->
-
<div class="float-right">
<p><img src="images/logo.svg" alt="Apache Petri Logo" width="300px"
height="135px"></p>
</div>
-
<h2>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
@@ -197,7 +195,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>
@@ -210,11 +208,11 @@ external community.</p>
<li><a href="/buildstream">BuildStream</a></li>
</ul>
<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-site";>Website</a></li>
@@ -230,6 +228,7 @@ questionnaires, but may introduce these should the need
arise.</p>
<li><a
href="https://github.com/apache/petri-site/blob/master/content/pages/index.md";>view
source</a></li>
</ul>
+
</div>
<footer class="navbar-expand-lg navbar-light bg-light">
diff --git a/output/mentors.html b/output/mentors.html
index a910231..e2c4962 100644
--- a/output/mentors.html
+++ b/output/mentors.html
@@ -181,7 +181,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>
@@ -201,6 +200,7 @@ for projects within the Apache Petri.</p>
<li><a
href="https://github.com/apache/petri-site/blob/master/content/pages/mentors.md";>view
source</a></li>
</ul>
+
</div>
<footer class="navbar-expand-lg navbar-light bg-light">
diff --git a/output/projects.html b/output/projects.html
index 0c13797..562997c 100644
--- a/output/projects.html
+++ b/output/projects.html
@@ -181,7 +181,6 @@ li {
<!-- Licensed under ALv2 -->
-
<h2>Project Status</h2>
<ul>
<li>Machine readable status <a
href="https://petri.apache.org/info.yaml";>petri.yaml</a> -- <a
href="https://github.com/apache/petri-site/blob/master/content/info.yaml";>source</a></li>
@@ -189,14 +188,17 @@ li {
</ul>
<h2>Current Cultures</h2>
<ul>
-<li><a href="buildstream">BuildStream</a> -- <a
href="https://github.com/apache/petri-site/blob/master/content/pages/buildstream.md";>source</a></li>
-</ul>
+<li>
+<p><a href="buildstream">BuildStream</a> -- <a
href="https://github.com/apache/petri-site/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>
<h3>Petri Website Markdown Source</h3>
<ul>
<li><a
href="https://github.com/apache/petri-site/blob/master/content/pages/projects.md";>view
source</a></li>
</ul>
+
</div>
<footer class="navbar-expand-lg navbar-light bg-light">
diff --git a/output/sitemap.xml b/output/sitemap.xml
index 4d77fde..f6c33af 100644
--- a/output/sitemap.xml
+++ b/output/sitemap.xml
@@ -5,42 +5,42 @@ xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";>
<url>
<loc>https://petri.apache.org/pages/buildstream.html</loc>
-<lastmod>2021-03-25T17:12:43-00:00</lastmod>
+<lastmod>2021-03-25T17:15:43-00:00</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://petri.apache.org/pages/cookbook.html</loc>
-<lastmod>2021-03-25T17:12:43-00:00</lastmod>
+<lastmod>2021-03-25T17:15:43-00:00</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://petri.apache.org/pages/faq.html</loc>
-<lastmod>2021-03-25T17:12:43-00:00</lastmod>
+<lastmod>2021-03-25T17:15:43-00:00</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://petri.apache.org/pages/index.html</loc>
-<lastmod>2021-03-25T17:12:43-00:00</lastmod>
+<lastmod>2021-03-25T17:15:43-00:00</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://petri.apache.org/pages/mentors.html</loc>
-<lastmod>2021-03-25T17:12:43-00:00</lastmod>
+<lastmod>2021-03-25T17:15:43-00:00</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://petri.apache.org/pages/projects.html</loc>
-<lastmod>2021-03-25T17:12:43-00:00</lastmod>
+<lastmod>2021-03-25T17:15:43-00:00</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
