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 3367cb8 Automatic Site Publish by Buildbot
3367cb8 is described below
commit 3367cb81d625f0f4b2495f4a94aa06f8ba879f64
Author: buildbot <[email protected]>
AuthorDate: Mon Dec 9 23:33:20 2019 +0000
Automatic Site Publish by Buildbot
---
output/faq.html | 258 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 258 insertions(+)
diff --git a/output/faq.html b/output/faq.html
new file mode 100644
index 0000000..3ebcd01
--- /dev/null
+++ b/output/faq.html
@@ -0,0 +1,258 @@
+<!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 charset="utf-8">
+ <meta name="viewport" content="width=device-width,
+ initial-scale=1, shrink-to-fit=no">
+ <link rel="shortcut icon"
href="https://www.apache.org/favicons/favicon.ico";>
+
+ <link rel="stylesheet"
+
href="https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css";
+
integrity="sha384-ggOyR0iXCbMQv3Xipma34MD+dH/1fQ784/j6cY/iJTQUOhcWr7x9JvoRxT2MZw1T"
+ crossorigin="anonymous">
+ <link rel="stylesheet"
+
href="https://cdnjs.cloudflare.com/ajax/libs/github-markdown-css/3.0.1/github-markdown.min.css";
+ >
+ <link rel="stylesheet" href="theme/css/apache.css">
+
+
+
+ </head>
+
+ <body id="index" class="home">
+ <nav class="navbar navbar-expand-lg navbar-dark bg-primary">
+ <img src="https://www.apache.org/foundation/press/kit/feather.svg";
+ width="30" height="30" class="d-inline-block align-top"
+ alt="Apache">
+ <a class="navbar-brand" href="/">Apache Petri</a>
+ <button class="navbar-toggler" type="button"
+ data-toggle="collapse" data-target="#navbarSupportedContent"
+ aria-controls="navbarSupportedContent" aria-expanded="false"
+ aria-label="Toggle navigation">
+ <span class="navbar-toggler-icon"></span>
+ </button>
+
+ <div class="collapse navbar-collapse" id="navbarSupportedContent">
+ <ul class="navbar-nav mr-auto">
+ <li class="nav-item active">
+ <a class="nav-link" href="/">Home</a>
+ </li>
+ <li class="nav-item active">
+ <a class="nav-link" href="#">tbd-links</a>
+ </li>
+ </ul>
+ <div class="navbar-nav">
+ <div class="nav-item dropdown dropdown-menu-right active">
+ <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown"
+ role="button" data-toggle="dropdown" aria-haspopup="true"
+ aria-expanded="false">About</a>
+ <div class="dropdown-menu" aria-labelledby="navbarDropdown">
+ <a class="dropdown-item"
href="https://www.apache.org/";>Foundation</a>
+ <div class="dropdown-divider"></div>
+ <a class="dropdown-item"
+ href="https://www.apache.org/licenses/";>License</a>
+ <a class="dropdown-item"
+
href="https://www.apache.org/foundation/sponsorship.html";>Sponsorship</a>
+ <a class="dropdown-item"
+ href="https://www.apache.org/foundation/thanks.html";>Thanks</a>
+ <div class="dropdown-divider"></div>
+ <a class="dropdown-item"
+ href="https://www.apache.org/security/";>Security</a>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ </nav>
+
+ <h1>Apache Petri - FAQ</h1>
+
+
+ <!-- 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 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>
+<h2>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 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>
+<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 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>
+<h2>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 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>
+<h2>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 company that has an Open Source project with other vendors and wants to
expand and diversify its community...</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
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 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>
+<h2>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 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>
+<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>
+<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>
+<h2>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>
+<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>
+<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>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.</li>
+<li>Transfer of Registered Trademarks. If there are any registered trademarks
then the transfer agreement will be discussed with the VP, Brand in
advance.</li>
+<li>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.</li>
+<li>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:</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>
+<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 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 <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>
+<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
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>
+
+
+
+ <footer class="navbar-expand-lg navbar-light bg-light">
+ <div class="footer" id="footer">
+ <div class="row">
+ <div class="col-sm">
+ <address id="about" class="vcard body">
+ Apache Software Foundation<br/>
+ <a href="https://www.apache.org/";>www.apache.org</a>
+ </address>
+ </div>
+ <div class="col-sm">
+ <ul>
+ <li>link 1</li>
+ <li>link 2</li>
+ </ul>
+ </div>
+ <div class="col-sm">
+ <ul>
+ <li>link 3</li>
+ <li>link 4</li>
+ </ul>
+ </div>
+ </div>
+
+ <div class="container-fluid">
+ Copyright © 2019 The Apache Software Foundation,
+ Licensed under the
+ <a href="https://www.apache.org/licenses/LICENSE-2.0";>Apache
+ License, Version 2.0.</a>
+ <br/>
+ Apache and the Apache feather logo are trademarks of
+ <a href="https://www.apache.org/";>The Apache Software Foundation.</a>
+ </div><!-- #container-fluid -->
+
+ </div>
+ </footer>
+
+ <script src="https://code.jquery.com/jquery-3.3.1.slim.min.js";
+
integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo"
+ crossorigin="anonymous"></script>
+ <script
+
src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.7/umd/popper.min.js";
+
integrity="sha384-UO2eT0CpHqdSJQ6hJty5KVphtPhzWj9WO1clHTMGa3JDZwrnQq4sF86dIHNDz0W1"
+ crossorigin="anonymous"></script>
+ <script
+
src="https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/js/bootstrap.min.js";
+
integrity="sha384-JjSmVgyd0p3pXB1rRibZUAYoIIy6OrQ6VrjIEaFf/nJGzIxFDsf4x0xIM+B07jRM"
+ crossorigin="anonymous"></script>
+ </body>
+</html>
\ No newline at end of file
![https://www.apache.org/foundation/press/kit/feather.svg"](https://www.apache.org/foundation/press/kit/feather.svg"){kind=link}