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 9056164 Automatic Site Publish by Buildbot
9056164 is described below
commit 905616422992be89cc04bd1d8dfb8552007d2dc6
Author: buildbot <[email protected]>
AuthorDate: Thu Apr 23 21:40:16 2020 +0000
Automatic Site Publish by Buildbot
---
output/index.html | 160 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 159 insertions(+), 1 deletion(-)
diff --git a/output/index.html b/output/index.html
index 2cbea37..f2e6d4d 100644
--- a/output/index.html
+++ b/output/index.html
@@ -85,7 +85,165 @@
<!-- Licensed under ALv2 -->
-<p>Content goes here.</p>
+<h3>What is Apache Petri?</h3>
+<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 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", 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>
+<h3>How is Petri different from the Apache Incubator?</h3>
+<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 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).</p>
+<h3>Why does this matter? What is special about The Apache Way?</h3>
+<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>
+<li>Earned Authority (merit);</li>
+<li>Community of Peers;</li>
+<li>Open Communications;</li>
+<li>Consensus Decision Making; and</li>
+<li>Responsible Oversight.</li>
+</ul>
+<p>For more information, see <a
href="https://www.apache.org/theapacheway/";>https://www.apache.org/theapacheway/</a></p>
+<h3>What does “Direct to TLP” entail?</h3>
+<p>The Board makes the ultimate decision, and generally ensures that the
project has:</p>
+<ul>
+<li>Demonstrated vendor neutrality in the community;</li>
+<li>Demonstrated understanding of the Apache Release Policy;</li>
+<li>Completed Contributor Licence Agreements and Software Grant
Agreements;</li>
+<li>Performed a Suitable Name Search;</li>
+<li>Developed a Transition Plan to Move the Project’s Resources to The
ASF;</li>
+<li>Shown how the community will recognize merit; and</li>
+<li>Shown auditable decision making on the provided mailing list.</li>
+</ul>
+<h3>Is Apache Petri right for you?</h3>
+<p>If you are:</p>
+<ol>
+<li>
+<p>An established, diverse community that already releases quickly; or</p>
+</li>
+<li>
+<p>A project with a single ”leader” that seeks to grow to a community-driven
development model; or</p>
+</li>
+<li>
+<p>A company that has an Open Source project with other vendors and wants to
expand and diversify its community...</p>
+</li>
+</ol>
+<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
accept projects that are not
+supported by some form of community.</p>
+<h3>Process</h3>
+<ol>
+<li>What about the Maturity Model? Haven’t other projects bypassed incubation
by meeting these requirements?</li>
+</ol>
+<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
chose to review itself against
+the Apache Maturity Model (<a
href="http://s.apache.org/O4p";>http://s.apache.org/O4p</a>), that addresses the
integrity of a project's code,
+copyright, licenses, releases, community, consensus 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>
+<ol start="2">
+<li>How long does the Petri process take?</li>
+</ol>
+<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 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>
+<ol start="3">
+<li>Do people involved in Petri-mentored projects need to sign ICLAs?</li>
+</ol>
+<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>
+<ol start="4">
+<li>If our project wants to become an official Apache project, what is the
best way to do so?</li>
+</ol>
+<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 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>
+<ol start="5">
+<li>If I propose my project to be mentored by Petri, will it be accepted?</li>
+</ol>
+<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>
+<ol start="6">
+<li>What is the expected intake rate for Petri?</li>
+</ol>
+<p>We anticipate 2-3 communities in the first year, with one per year likely
following that.</p>
+<ol start="7">
+<li>What should the Board expect from a Project that Petri Recommends to
become a TLP?</li>
+</ol>
+<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 under What does “Direct to TLP” entail:</p>
+<ol>
+<li>
+<p>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.</p>
+</li>
+<li>
+<p>Transfer of Registered Trademarks. If there are any registered trademarks
then the transfer agreement will be
+discussed with the VP, Brand in advance.</p>
+</li>
+<li>
+<p>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.</p>
+</li>
+<li>
+<p>Resources. Graduation proposals will include a Transition Plan explaining
the actions that the project intends
+to take once the PMC is established. This may include:</p>
+</li>
+</ol>
+<ul>
+<li>Creating Apache project mailing lists</li>
+<li>Creating Apache issue trackers</li>
+<li>Creating Apache wikis</li>
+<li>Creating Apache code repositories</li>
+<li>Migrating code repositories to Apache</li>
+<li>Creating Apache web presence</li>
+<li>Migrating web presence from Project to Apache</li>
+<li>Rebranding web, code, documentation from Project to Apache Project</li>
+<li>Retiring external Project and redirecting to Apache</li>
+<li>Creating and migrating CI, build, release processes to Apache Project</li>
+<li>Establish processes for release distribution at Apache</li>
+</ul>
+<p>New TLPs should report on their progress towards completing their
Transition Plan in their Board Reports.</p>
+<ol start="5">
+<li>Who will provide guidance once the Petri mentor is gone after the
assessment?</li>
+</ol>
+<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>
+<h3>How can our project/community apply for Apache Petri mentorship?</h3>
+<p>Email <a
href="mailto:[email protected]";>[email protected]</a> (public
list; subscription not required) or <a
href="mailto:[email protected]";>[email protected]</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>
+<h3>If a project wants to move out of the Apache Incubator and into Petri,
what happens?</h3>
+<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 perform any needed changes to
+make that happen.</p>
</div>
