You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@incubator.apache.org by po...@apache.org on 2017/07/06 00:20:53 UTC
[22/51] incubator git commit: Continuing progress on converting to
asciidoc.
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/mentor.xml
----------------------------------------------------------------------
diff --git a/pages/guides/mentor.xml b/pages/guides/mentor.xml
new file mode 100644
index 0000000..d4f493f
--- /dev/null
+++ b/pages/guides/mentor.xml
@@ -0,0 +1,290 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+Licensed 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
+
+http://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.
+
+
+
+
+
+
+
+
+most of this page got split.
+-->
+
+<!DOCTYPE document
+[
+<!ENTITY root-path '..'> <!-- The path to the incubator root -->
+]>
+
+<document>
+ <properties>
+ <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org Archives</atom>
+ <title>Projects</title>
+ </properties>
+ <body>
+ <section id="Incubating+Project+and+Mentor+Guides">
+ <title>Mentor Guide</title>
+ <p>This document targets any Incubating Project member, but
+ especially Mentors, who have to ensure that some things get done.
+ For a general description of the role of a mentor on an incubating
+ project see the
+ <a href="/incubation/Roles_and_Responsibilities.html#Mentor">Roles and Responsibilities
+</a>document.
+ </p><p>
+ This guide is a descriptive and at times
+discursive document. It describes established practices.
+It is informational not normative. Policy is laid down in the
+<a href="/incubation/Incubation_Policy.html">Incubation Policy</a>.
+ </p>
+ <section id='TOC'><title>Contents</title><toc/></section>
+ </section>
+ <section id="Overview">
+ <title>Overview</title>
+ <p>
+ After the Podling has been accepted by the Incubator PMC, one of the mentors
+ <a href="/incubation/Incubation_Policy.html#Setting+Up+a+New+Podling">sets up</a>
+ the Podling; <em>i.e.</em> adds the podling metadata, creates the initial Podling status page, and
+ either creates or requests that
+ other resources (mail lists, subversion, bug tracker, <em>etc.</em>)
+ be created.
+ </p>
+ </section>
+ <section id="Sending+in+an+Incubation+Report">
+ <title>Add to Incubation Summary file</title>
+ <p>
+ Add the podling to the podling summary file in
+ the "incubator" SVN at <code>content/podlings.xml</code>
+ (e.g. copy the entry from another podling that also has status="current")
+ and see <a href="website.html">instructions</a>.
+ </p>
+ <p>
+ Please do this step ASAP after Acceptance. Other setup procedures utilize
+ this metadata.
+ </p>
+ <p>
+ Add a 'reporting' tag (after 'description') with the attribute 'monthly="true"'
+ and the appropriate "group" attribute, based on the month in which the podling
+ entered incubation (1 for January, April, July, October, 2 for February, May,
+ August, November or 3 for March, June, September, December). The text content
+ of the 'reporting' tag must contain the initial list of reporting months,
+ starting with the month after the podling entered incubation. For example:
+ <code><reporting group="2" monthly="true">June, July, August</reporting></code>
+ Once the first three reports are complete, the monthly attribute should be removed
+ and the list of months removed as well.
+ </p>
+ <p>
+ The first report might be
+ very short. However it is better that the Incubator PMC can help to
+ guide through the early setup stages.
+ For more details see the
+ <a href="ppmc.html#Incubator+ASF+Board+Reports">PPMC Guide</a>.
+ </p>
+ </section>
+ <section id="Initialize+Podling+Status+Page">
+ <title>Initialize Podling Status Page</title>
+ <p>
+ A mentor needs to
+ <a href="website.html#Edit+your+project+status+page">create the
+ web page</a> that will track the project's status.
+ A mentor will also need to update it until
+ <a href="ppmc.html#Project+Status+Updates">others in the
+ the project's PPMC can update it</a>.
+ </p><p>
+ The status
+ page is the incubator's record of the progress made.
+ It MUST be kept update to date during incubation.
+ Some of the information is available from the proposal.
+ As the startup process continues and resources are
+ created the status SHOULD be updated.
+ </p><p>
+ The template contains lists of actions which may be needed
+ to start up a podling. All those which do not apply should
+ be deleted.
+ </p><p>
+ The status page is a useful aid to workflow. Volunteers
+ can use it to sign up to the various tasks and monitor their
+ progress. Once the mailing lists are set up and prospective
+ committers subscribe then these may be used for discussion.
+ </p>
+ </section>
+ <section id='request-required-resources'><title>Request Required Resources</title>
+ <p>
+ The proposal should include a list of required resources. All of these will
+ require active set up. Some are created by infrastructure after an appropriate
+ request, others can be set up by any IPMC members (typically mentors).
+ </p><p>
+ Mailing lists should be created first. Other resources typically
+ post information to these lists.
+ </p>
+ <section id='request-mailing-lists'><title>Request Mailing Lists</title>
+ <p>
+ Apache mailing lists require volunteer moderators. New moderators can be
+ <a href='http://www.apache.org/dev/committers.html#mailing-list-moderators'>changed later</a>
+ but at least one volunteer is required before the mailing lists can be set up.
+ Moderation is a reasonably
+ <a href='http://www.apache.org/dev/committers.html#mail-moderate'>easy task</a>
+ though moderators may want to set up
+ <a href='http://spamassassin.apache.org/'>spam filtering</a>.
+ Having at least three moderators is recommended to spread the load.
+ </p><p>
+ The proposal should contain the rest of the information that needs to be collected
+ before the mailing lists can be requested. Incubator is the responsible top level project.
+ So the domain <code>MUST</code> be <code>incubator.apache.org</code>.
+ For example:
+ </p>
+ <ul>
+ <li>dev@${podling}.incubator.apache.org</li>
+ <li>commits@${podling}.incubator.apache.org</li>
+ <li>private@${podling}.incubator.apache.org</li>
+ </ul>
+ <p>
+ For initial community building it is usually appropriate to only have
+ a "dev" list, to keep the discussions focussed. Later add a "user" list
+ if needed.
+ </p>
+ <note>
+ Commits under <code>http://svn.apache.org/repos/asf/incubator/<em>${podling}</em></code>
+ will be emailed to <code>commits@${podling}.incubator.apache.org</code>.
+ Any deviation will
+ require special configuration in the <code>asf-mailer.conf</code> file by the IPMC.
+ </note>
+ <p>
+ Mailing lists creation is a task for the <a href='#who-infra'>infrastructure team</a>. The
+ infrastructure team offers a tool that simplifies the creation of mailing lists. You can access the
+ <a href="https://infra.apache.org/officers/mlreq/incubator" target="_new">Incubator Mailing List Request Form</a>
+ to request a list. A notification will be sent to private@incubator when the lists have been created.
+ </p>
+ <p>
+ Remember to update the project status file with mailing list details. Prospective committers
+ and mentors will need to subscribe. Email them once the status file has been updated. Inform
+ any existing mailing lists or forums previously used by the project.
+ </p>
+ <p>
+ Once the <code>commits</code> list is created, the project MUST review
+ the <code>/incubator/${podling}</code> tree, since any commits made prior
+ to the list's creation will have generated no email trail.
+ </p>
+ <section id='mail-archives'><title>Mail Archives</title>
+ <p>
+ Archives at <a href='http://mail-archives.apache.org'>http://mail-archives.apache.org</a> for the public
+ mailing lists will be setup as part of the mailing list creation process. No action is
+ required by Mentors. The archives will be <a href='http://mail-archives.apache.org/mod_mbox/'>visible</a>
+ as soon as posts have been made (and moderated) to these lists.
+ </p>
+ <p>
+ You can also leverage <a href="https://lists.apache.org" target="_new">lists.apache.org</a> for
+ mailing list archives. There is a login link in the top right corner, which allows you to respond to
+ threads from within the web application.
+ </p>
+ <p>
+ Many projects are independently archived externally (for example, at
+ <a href='http://www.mail-archive.com/'>The Mail Archive</a> and
+ <a href='http://marc.info/?q=about'>MARC</a>)
+ Independent archives help to
+ increase project visibility as well as preserving a independent historic record.
+ These subscriptions are not automatically created. If desired, subscribe manually.
+ </p><p>
+ Subscriptions to news-to-mailing-list bridges (for example, <a href='http://www.nabble.com'>Nabble</a>)
+ must also be created manually. Subscribing helps accessibility and visibility but Nabble news
+ users may not be aware that they are posting to a mailing list.
+ </p>
+ </section>
+ <section id='mail-admin'><title>Mailing List Administration</title>
+ <p>
+ Apache uses <a href='http://www.ezmlm.org/'>ezmlm</a>. See the
+ <a href='http://www.ezmlm.org/man/ezmlmman.html'>manual</a> and
+ committer <a href='http://www.apache.org/dev/committers.html#mail'>mail FAQ</a>
+ for more details.
+ </p>
+ </section>
+ <section id='transition-mailing-lists'><title>Mailing List Transition</title>
+ <p>
+ Independent mailing lists and groups are perfectly acceptable but development should
+ happen on the official mailing lists at Apache. If a project has existing mailing lists,
+ forums or groups the community needs to consider their future and plan for the transition
+ to the official Apache mailing lists.
+ </p><p>
+ It may be useful to move development first to the official lists followed gradually
+ by the user resources.
+ </p>
+ <p>
+ Note that subscribers of external mailing lists will not be automatically subscribed
+ to the new Incubator project mailing lists. Instead, a note should be posted to the
+ old external mailing list asking them to subscribe to the new list. If possible, add
+ a footer to the old mailing list with some instructions.
+ </p>
+ </section>
+ <section id='request-issue-tracking'><title>Issue Tracking</title>
+ <p>
+ If any Mentor has project-creation karma (in the issue tracking system to be used)
+ then they should execute.
+ If no Mentor has the required karma then file an INFRA issue using the 'new jira project'
+ type (not bug or request)
+ </p>
+ <p>
+ Remember to post an email announcing that the issue tracker is available.
+ </p>
+ </section>
+ </section>
+
+
+ <section id='glossary'><title>Glossary</title>
+ <section id='who-committers'><title>Prospective Committers</title>
+ <p>
+ These are the people listed as initial committers in the proposal.
+ </p>
+ </section>
+
+ <section id='who-infra'><title>Infrastructure Team</title>
+ <p>
+ Tasks that cannot safely be delegated to projects are handled by the Apache
+ <a href='http://www.apache.org/dev/infra-volunteer.html'>Infrastructure team</a>.
+ The relevant instructions
+ <a href='http://www.apache.org/dev/infra-contact'>MUST be followed</a>.
+ JIRA is typically used to
+ manage workflow. This allows progress to be easily tracked.
+ </p>
+ </section>
+ <section id='who-auth-karma'><title>Incubator Access Authorization</title>
+ <p>
+ Special karma is required to authorize incubator access for committers.
+ This karma is limited to:
+ </p>
+ <ul>
+ <li>PMC Chairs (past and present)</li>
+ <li>Selected people in the Infrastructure team</li>
+ </ul>
+ <p>
+ If any mentor has karma then they should authorize the committer.
+ To grant authorization, update:
+ </p>
+ <source>
+ infrastructure/trunk/subversion/authorization/asf-authorization-template
+ </source>
+ <p>
+ Edit the file to add the new committer to the podling authorization:
+ </p>
+ <source>
+ {podling}={mentor1},{mentor2},{new-committer}
+ </source>
+ <p>
+ If no mentor has karma then an email should be posted to the IPMC private
+ list requesting that the grant is performed. One of the IPMCers with karma
+ will authorize the committer.
+ </p>
+ </section>
+ </section>
+
+ </body>
+</document>
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/names.xml
----------------------------------------------------------------------
diff --git a/pages/guides/names.xml b/pages/guides/names.xml
new file mode 100644
index 0000000..23caf15
--- /dev/null
+++ b/pages/guides/names.xml
@@ -0,0 +1,366 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+Licensed 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
+
+http://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.
+-->
+<document>
+ <properties>
+ <title>Podling Name Search Guide</title>
+ <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org Archives</atom>
+ <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+ </properties>
+ <body>
+ <section>
+ <title>Podling Name Search Guide</title>
+ <ul>
+ <li>
+ <a href="#intro">Introduction</a>
+ <ul>
+ <li><a href="#meet-the-team">Meet The Apache Branding Team</a></li>
+ <li><a href="#trademarks">Trademarks</a></li>
+ <li><a href="#alv2">Trademarks And The Apache License</a></li>
+ <li><a href="#naming-hints">What Makes A Name Good</a></li>
+ <li><a href="#name-search">Podling Suitable Name Search</a></li>
+ </ul>
+ </li>
+ <li>
+ <a href="#search">Conducting A Suitable Name Search</a>
+ <ul>
+ <li>
+ <a href="#elimination">Eliminate Unsuitable Names</a>
+ <ul>
+ <li><a href="#main-sequence">The Main Sequence</a></li>
+ <li><a href="#ethical-suitability">Appropriateness</a></li>
+ <li><a href="#uniqueness-what-and-why">Unique Enough Names</a></li>
+ <li>
+ <a href="#uniqueness-how-to">How To Collect Evidence Of Uniqueness</a>
+ <ul>
+ <li><a href="#evidence-oss">Evidence Of Open Source Adoption</a></li>
+ <li><a href="#evidence-registration">Evidence Of Registration</a></li>
+ <li><a href="#evidence-web">Evidence Of Use On The World Wide Web</a></li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </section>
+
+ <section id='intro'>
+ <title>Introduction</title>
+ <p>
+ This guide is <strong>not</strong> <em>legal advice</em> or <em>legal opinion</em>:
+ <strong>do not</strong> use it as a substitute.
+ Its aims are education and information <strong>only</strong>.
+ </p><p>
+ This process filters out unsuitable names early,
+ reducing the legal resources required and
+ limiting the potential disruption to a community of a forced name change
+ later. A smooth path, but not the only one. If there are reasons
+ why this road isn't right for your podling,
+ consult <a href='http://mail-archives.apache.org/mod_mbox/incubator-general/'>incubator general</a>.
+ </p>
+ <section id="meet-the-team">
+ <title>Meet The Apache Branding Team</title>
+<p>
+Names <a href='http://www.apache.org/foundation/marks/#whoweare'>fall</a> within the responsibilities of the
+<a href='http://www.apache.org/foundation/'>V.P., Brand Management</a> (and
+<a href='http://www.apache.org/foundation/marks/#whoweare'>team</a>). Please start by reading:</p>
+ <ul>
+ <li>the <a href='http://www.apache.org/foundation/marks/' rel='tag'>Apache Trademark Policy</a> <br/>(which introduces trademarks and outlines our policy);</li>
+ <li>the <a href='http://www.apache.org/foundation/marks/faq/' rel='tag'>Apache Trademark FAQs</a> <br/>(which answers questions asked by downstream consumers); and</li>
+ <li>the <a href='http://www.apache.org/foundation/marks/pmcs.html'>Apache Project Branding Requirements</a> <br/>(which guides PMCs).</li>
+ </ul>
+ <p>For podlings in the Incubator, naming issues are managed co-operatively by the Brand and Incubator communities.
+Rules for podlings include all branding requirements for PMCs, plus a few extras.
+ </p>
+ </section>
+ <section id="trademarks">
+ <title>Trademarks</title>
+ <p>
+Trademark law is a complex subject.
+Distinctive differences from other intellectual property laws (such as patent or copyright) mean that
+intuition or knowledge gained from other areas may not be applicable.
+The <a href='http://www.apache.org/foundation'>Apache Software Foundation</a> is
+a <a href='http://www.apache.org/foundation/faq.html#is-ASF-a-corporation'>US corporation</a>.
+Developing some understanding of the basic principles of US trademark law is therefore important.
+ </p><p>
+Please read:
+ </p>
+ <ul>
+ <li><a href='http://www.apache.org/foundation/marks/#principles'>Description of key trademark principles</a> for Apache projects;</li>
+ <li><abbr title='United States Patent and Trademark Office'>USPTO</abbr> trademark
+ <ul>
+ <li><a href='http://www.uspto.gov/trademarks/index.jsp'>home</a> page</li>
+ <li><a href='http://www.uspto.gov/trademarks/basics/index.jsp'>basics</a>, and follow the links for materials;</li>
+ </ul></li>
+ <li><a href='http://en.wikibooks.org/wiki/US_Trademark_Law'>US Trademark Law</a> WikiBook; and</li>
+ <li><a href='http://www.ifosslr.org/ifosslr/article/view/11/37'>Passport Without A Visa: Open Source Software Licensing and Trademarks
+ </a> by Tiki Dare and Harvey Anderson
+ in the <a href='http://www.ifosslr.org/'>International Free and Open Source Software Law Review</a>.</li>
+ </ul>
+ </section>
+
+ <section id="alv2">
+ <title>Trademarks And The Apache License</title>
+ <p>
+Like <a href='http://www.ifosslr.org/ifosslr/article/view/11/37'>many</a>
+<a href='http://www.opensource.org' rel='tag'>open source</a> licenses, the
+<a href='http://www.apache.org/licenses/LICENSE-2.0.html'>Apache License, Version 2.0</a>
+focuses on granting copyright and patent rights to the public.
+The <em>trademark</em> section permits only very limited trademark rights.
+ </p>
+ <blockquote cite='http://www.apache.org/licenses/LICENSE-2.0.html#trademarks'>
+ <p><strong>6. Trademarks.</strong>
+This License does not grant permission to use the trade names, trademarks,
+service marks, or product names of the Licensor, except as required for
+reasonable and customary use in describing the origin of the Work and
+reproducing the content of the NOTICE file.
+ </p>
+ </blockquote>
+ <p class='attribution'><a href='http://www.apache.org/licenses/LICENSE-2.0.html#trademarks'>Apache License, Version 2.0
+ </a></p>
+ <p>
+All Apache projects share the Apache License. This issues standard <strong>copy</strong>
+and <strong>patent</strong> rights to
+downstream consumers. <strong>Trademark</strong> rights for Apache products are issued and managed independently,
+beyond the Apache License. This allows Apache communities to use trademark law to protect their reputation and that of the
+<a href='http://www.apache.org/foundation/'>Foundation</a>, within the broader
+framework provided by the Brand team.
+ </p>
+ </section>
+
+ <section id='naming-hints'>
+ <title>What Makes A Name Good</title>
+ <p>Good names for commercial products or <code>UNIX</code> utilities have tended to work less well here at Apache.
+ Many successful Apache project names are memorable, unusual and a little
+ <a href='http://www.sdtimes.com/TOP_FIVE_HEAD_SCRATCHINGEST_NAMES_FOR_APACHE_PROJECTS/By_Victoria_Reitano/About_APACHE_and_HADOOP_and_HARMONY_and_MYSQL_and_OODT_and_YAY/35959'>whimsical</a>.
+ These qualities also happen to be useful when it comes to securing trademark protection.
+ Have fun. Be creative.
+ </p>
+ </section>
+ <section id="name-search">
+ <title>Podling Suitable Name Search</title>
+ <p>
+The initial <a href='http://incubator.apache.org/guides/proposal.html'>proposal</a>
+establishes a working name for the new podling.
+Often some discussion and filtering of suitable names happens during the election
+process but this proposed name is <strong>not</strong> final, only <em>provisional</em>.
+The community may choose to change it. Or the community may discover that the name is unsuitable:
+in which case a suitable new name must be found.
+ </p><p>
+A podling needs to discover whether a name is suitable.
+The Incubator community calls this process the <em>suitable name search</em>.
+This avoids any potential confusion with phrases like
+<em>trademark search</em> with technical meanings in the trademark community.
+Please be careful with language. In particular:
+</p>
+<ul>
+<li>avoid using loaded technical legal terms;</li>
+<li>use plain, simple English to describe what you did and what you found;</li>
+<li>avoid speculation; and</li>
+<li>don't offer <em>advice</em> or <em>opinions</em>.</li>
+ </ul>
+
+ <p>
+A suitable name search must be successfully completed before a podling can graduate.
+This isn't the only way one might be done, just a smooth path.
+</p><p>
+Names are an essential part of building a brand and community.
+Switching names wastes the efforts put into establishing the original name.
+Therefore complete this task as soon as possible.
+</p>
+
+ </section>
+ </section>
+
+ <section id='search'>
+ <title>Conducting A Suitable Name Search</title>
+ <p>The aim - to find a name that is acceptable to the community and is not unsuitable.</p>
+ <p>
+A suitable name search has public and private elements.
+The <a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>tracker</a> provides the public record.
+Incubator best practice evolves over time, documentation lags.
+The public records of past searches are a primary source of guidance.
+Review now the records of previous searches, beginning with the most recent then working back.
+ </p><p>
+ The public record consists of <em>actions</em> (how you searched) and <em>facts</em> (what your search found). In particular,
+ in <strong>all</strong> public forums (mailing lists, issue trackers and so on):
+ </p>
+
+ <ul>
+ <li><strong>Do not</strong> speculate.</li>
+ <li><strong>Do not</strong> use loaded technical legal language.</li>
+ <li><strong>Do not</strong> offer
+ <ul>
+ <li>opinions,</li>
+ <li>advice,</li>
+ <li>interpretation, or</li>
+ <li>analysis.</li>
+ </ul>
+ </li>
+ </ul>
+
+ <p>
+Use the public lists in the Incubator to ask questions about <em>how</em> the search should be conducted.
+Once the information is collected and collated, then ask the trademark team to help interpret and analyse these results
+on the private lists, copying in the PPMC. Finally discuss the results of your investigation on the private PPMC list.
+Whether a name is suitable or unsuitable (or somewhere in between) should be recorded when the issue is closed.
+ </p>
+ <section id='elimination'>
+ <title>Eliminate Unsuitable Names</title>
+ <p>To be suitable, a name needs to be</p>
+ <ul>
+ <li>judged <em>appropriate</em> by the wider community; and</li>
+ <li><em>unique enough</em> to avoid confusion</li>
+ </ul>
+ <p>
+Facts and activities performed are <a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>recorded</a> for the public.
+Interpretation and analysis of these facts happens on private mailing lists, the PPMC private in the first instance.
+Whether the name proved suitable or unsuitable should be entered into the public record
+but take care to use our language (<em>ethically unsuitable</em> or
+<em>not unique enough</em>) and to avoid loaded legal terms.
+ </p>
+
+ <section id='main-sequence'><title>The Main Sequence</title>
+ <p>
+Every podling is unique, but using a <a href='http://outreach.atnf.csiro.au/education/senior/astrophysics/stellarevolution_mainsequence.html'>cosmic</a>
+metaphor, most fit into a main sequence. For podlings on the main sequence,
+most of the bugs should have been squashed and rough edges documented away, so expect a smooth journey.
+Away from the main sequence, process may need to be grown, documentation is likely be sparse
+and progress less smooth.
+ </p><p>
+The main sequence is described here. This well known path is
+appropriate for almost all podlings.
+If there are good reasons to think that your podling is a special case, discuss this with the
+<a href='http://mail-archives.apache.org/mod_mbox/incubator-general/'>Incubator community</a>
+and reach consensus on the way forward.
+ </p>
+ </section>
+
+ <section id='ethical-suitability'>
+ <title>Appropriateness</title>
+ <p>
+Some names are not appropriate for open source projects.
+Acceptability under
+<a href='http://www.law.cornell.edu/uscode/15/1052.shtml'>US Trademark Law</a> is a good base line.
+This excludes marks that
+ </p>
+ <blockquote cite='http://www.law.cornell.edu/uscode/15/1052.shtml'>
+Consists of or comprises immoral, deceptive, or scandalous matter;
+or matter which may disparage or falsely suggest a connection with persons,
+living or dead, institutions, beliefs, or national symbols, or bring them into contempt, or disrepute;
+ </blockquote>
+ <p class='attribution'><a href='http://www.law.cornell.edu/uscode/15/1052.shtml'>US Code 15:1052
+ </a></p>
+ <p>
+Proposals with inappropriate names are unlikely to pass the initial hustings but spend a few moments considering
+whether anything has been missed. Check for alternative meanings, perhaps in foreign languages.
+ </p>
+ </section>
+ <section id='uniqueness-what-and-why'><title>Unique Enough Names</title>
+ <p>
+The name needs be unique enough to avoid confusion with software that already exists.
+For the community to be able to protect its reputation for quality and openness,
+its name needs to unique enough to have potential as a trademark.
+ </p>
+ <p>
+But this isn't only about being able to register trademark protection.
+Ethics also plays a role. Even where a name may offer enough protection, existing adoption
+of the name by an active community may mean that the choice needs to be eliminated on ethical grounds.
+There is some judgment involved in this decision. So, involve the wider Incubator community if a name is already
+used.
+ </p>
+ </section>
+ <section id='uniqueness-how-to'>
+ <title>How To Collect Evidence Of Uniqueness</title>
+ <p>
+To decide whether a potential name is <em>unique enough</em> to be suitable
+</p>
+<ol>
+<li>Collect evidence about current name usage.</li>
+<li><a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>Record</a> the facts.</li>
+<li>Analyse and interpret these facts; in private with help from the brand team.</li>
+<li>Reach consensus about whether the name is unique enough.</li>
+<li><a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>Record</a> whether the name is suitable.</li>
+<li>If unsuitable then the community should pick a more unique name and repeat this process.</li>
+</ol>
+ <section id="evidence-oss">
+ <title>Evidence Of Open Source Adoption</title>
+ <p>
+Existing adoption amongst another active open source community may give ethical
+reasons for eliminating a name. This is an example of a condition with a fractal
+boundary. Not every name which has been used before need be eliminated as unsuitable
+but this is an issue which needs to be discussed more widely and
+a consensus reached with the broad
+<a href='http://mail-archives.apache.org/mod_mbox/incubator-general/'>Incubator community</a>.
+ </p>
+ <p>
+Look for evidence of existing adoption amongst open source communities by searching well known
+foundries (for example <a href='http://www.github.com'>GitHub</a> and
+<a href='http://www.sourceforge.net'>Sourceforge</a>)
+and the web (use several search engines for example <a href='http://www.bing.com'>Bing</a>,
+<a href='http://www.google.com'>Google</a> and <a href='http://www.yahoo.com'>Yahoo</a>).
+Review recent <a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>records</a>
+for contemporary details about where to search.
+<a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>Record</a> each search and describe the results.
+ </p>
+ <p>
+If the name been used by the same community before it arrived at Apache, that's fine but should be noted in the
+<a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>record</a>.
+ </p>
+ </section>
+ <section id="evidence-registration">
+ <title>Evidence Of Registration</title>
+ <p>
+A number of online resources exist which may help to discover evidence of
+competing registered trademarks.
+Not every trademark is registered. Not every registered trademark is listed in these resources.
+Even if evidence is found of existing registrations,
+this does not necessary eliminate the proposed name. Just
+<a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>record</a> the facts.
+Leave analysis and interpretation to private lists.
+When a search returns a large number of hits, focus on live registrations related to software.
+</p><p>
+The foremost online resource is <abbr title='Trademark Electronic Search System'>TESS</abbr> run by
+<abbr title='United States Patent and Trademark Office'>USPTO</abbr>. Before using
+TESS, please browse the documentation links from
+<a href='http://www.uspto.gov/trademarks/index.jsp'>USPTO trademark home</a>.
+ </p>
+ <p>
+Other resources which allow cheap searches of their databases exist but are often
+ephemeral. Review the <a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>records</a>
+for the state of this art.
+ </p>
+ </section>
+ <section id="evidence-web">
+ <title>Evidence Of Use On The World Wide Web</title>
+ <p>
+Registration of trademark is not required. Rights may also be obtained by use of a mark in commerce.
+ </p><p>
+Use a variety of web search engines (for example, <a href='http://www.bing.com'>bing</a>, <a href='http://www.google.com'>google</a>
+and <a href='http://search.yahoo.com'>yahoo</a>) to survey usage on the world wide web.
+</p><ul>
+<li>The
+results returned by a search for the name itself may provide evidence of well known usages of the term.</li>
+<li>The results returned by searching for the name and <code>software</code> may provide evidence of
+existing use in trade. You may also want to search for the name and key functionality the software provides
+ and name and <code>open source</code></li>
+</ul>
+ </section>
+ </section>
+ </section>
+ </section>
+
+ </body>
+</document>
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/participation.ad
----------------------------------------------------------------------
diff --git a/pages/guides/participation.ad b/pages/guides/participation.ad
new file mode 100644
index 0000000..f0a3536
--- /dev/null
+++ b/pages/guides/participation.ad
@@ -0,0 +1,119 @@
+//Licensed 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
+//
+//http://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.
+= Guide to Participation
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+This document is descriptive, not normative. It aims to help those who are new
+to the Incubator learn its ways and netiquette.
+
+== General Netiquette
+
+The usual advice applies. If you are not familiar with the way mailing lists
+work at Apache, read link:http://jakarta.apache.org/site/mail.html[this].
+
+Please ensure that your mail client is correctly configured. In particular, post only plain
+text emails to these lists. Apache spam filters may reject HTML emails.
+
+The incubator is a public meeting place with a diverse and ever-changing community.
+Creating social bonds and establishing a reputation is important. Please be polite,
+courteous and diplomatic.
+
+When in doubt - ask on link:lists.html#general+at+incubator.apache.org[general.AT.incubator.apache.org].
+
+== Ways To Participate
+=== On The General Mailing List
+
+The *general.AT.incubator.apache.org* is an public list with open subscription.
+All are encouraged to subscribe, read and post their opinions in the usual way.
+
+Anyone can by their words influence the decision-making process and may vote on
+link:http://www.apache.org/foundation/voting.html[VOTE threads].
+However (as is usual) only the votes of those on the
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[Incubator PMC] are binding.
+
+=== As A User
+
+A link:http://www.apache.org/foundation/how-it-works.html#users[user]
+is anyone who uses our software. Most Apache projects have active user
+communities who are willing to provide help. This is not always the case with incubator podlings.
+
+To gain the maximum benefit from any immature project (as many podlings are),
+adopt an active attitude.
+Read link:http://jakarta.apache.org/site/contributing.html[On Contributing]
+and
+link:http://jakarta.apache.org/site/understandingopensource.html[Understanding Open Source].
+Become a link:#developer[developer] (in the Apache meaning of the term).
+
+=== As A Developer
+
+At Apache, a link:http://www.apache.org/foundation/how-it-works.html#developers[developer]
+(aka contributor) is anyone who actively helps to develop our software. This includes more than just coders
+and documenters. For example, anyone who joins in discussions on the mailing lists or answers questions
+from users is also a developer.
+
+Apache is a link:http://www.apache.org/foundation/how-it-works.html#decision-making[_DO_-ocracy]. The first step along the road leading to
+link:#committer[committership] is to become a developer. For more information start with
+link:http://www.apache.org/foundation/how-it-works.html[How Apache Works]
+and the link:http://www.apache.org/dev/[developer documentation].
+
+=== As A Committer
+
+A link:/incubation/Roles_and_Responsibilities.html#Committers[committer]
+is anyone with write access to the source repository. Election to committership in the Incubator
+works a little differently from the process that is usual elsewhere at Apache.
+
+Once a podling has been bootstrapped, link:#developer[developers] are nominated
+and election to committer happens in the link:ppmc.html#Voting+in+a+new+committer[usual way].
+
+When a proposal is just a link:/incubation/Roles_and_Responsibilities.html#Candidate[candidate],
+there are two possible approaches (for those interested in committership).
+
+The proposal typically
+link:proposal.html#template-initial-committers[contains] a list of initial committers.
+When a podling is bootstrapped, this list is used by the mentors to set up initial accounts.
+So, one way to become a committer for a podling is to be listed on the proposal as an initial
+committer.
+
+The right way to express interest is by a post to the list with a brief introduction.
+Piling onto a proposal (by adding your own name as an initial committer) is impolite.
+Read
+link:http://mail-archives.apache.org/mod_mbox/incubator-general/200607.mbox/%3cC73C6D24-3216-4EB4-8846-1218B38CC594@gbiv.com%3e[this thread].
+
+A podling needs to learn how to recruit new committers from its developers. So,
+another way is to show up on the list and start helping with the development.
+This path will help the podling more than adding your name to the list of initial committers.
+
+=== As A Mentor
+
+Anyone with knowledge of open source or Apache can participate as a informal mentor
+for a podling. Development is open and anyone with an interest is encouraged to
+subscribe.
+
+Eligibility to act as a formal
+link:/incubation/Roles_and_Responsibilities.html#Mentor[Mentor] is
+link:/incubation/Incubation_Policy#Mentor[limited]. The best way for an eligible
+individual to become a Mentor is to post a note introducing him- or herself
+and volunteering their services to *general.AT.incubator.apache.org*
+during the development of the link:proposal.html[proposal].
+
+=== On The Incubator PMC
+
+Apache Members are encouraged to join the
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[Incubator PMC]. Post a note to the Incubator PMC private list.
+
+Those who aren't members may be elected in the usual Apache way. These elections are held on private lists.
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/pmc.ad
----------------------------------------------------------------------
diff --git a/pages/guides/pmc.ad b/pages/guides/pmc.ad
new file mode 100644
index 0000000..a5a009e
--- /dev/null
+++ b/pages/guides/pmc.ad
@@ -0,0 +1,34 @@
+//Licensed 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
+//
+//http://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.
+= The Incubator PMC
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+== Joining the IPMC
+
+Joining the IPMC is just like any other PMC, once enough merit and community involvement is performed, PMC members will take notice and may vote on you to join.
+
+Foundation members may willingly join the IPMC at any time, to express desire send an email to *private.AT.incubator.apache.org*
+
+== Members
+
+A full list of IPMC members can be found at link:http://home.apache.org/phonebook.html?pmc=incubator[home.apache.org/phonebook.html?pmc=incubator]
+
+== Roles and Responsibilities of the IPMC
+
+The full list of expectations of an IPMC member can be found on the
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[Roles & Responsibilities Page]
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/podling_bootstrap.ad
----------------------------------------------------------------------
diff --git a/pages/guides/podling_bootstrap.ad b/pages/guides/podling_bootstrap.ad
new file mode 100644
index 0000000..8bff099
--- /dev/null
+++ b/pages/guides/podling_bootstrap.ad
@@ -0,0 +1,334 @@
+<section id='bootstrap'><title>[DRAFT] Podling Bootstrap</title>
+<p>
+<strong>NOTE</strong> This section is a DRAFT under development.
+</p>
+<p>
+Following podling creation, it needs to be bootstrapped. Here are some of
+the tasks:
+
+- Ensure link:#mentors-ipmc[Mentors are on the IPMC][<code>Mentors</code>]
+- Add podling to link:#Sending+in+an+Incubation+Report[reporting schedule] [<code>IPMC member</code>]
+- link:#Initialize+Podling+Status+Page[Initialize project status page] [<code>IPMC member</code>]
+- Start link:#orientation'>orientation</a> [<code><a href='#who-committers[Prospective committers]</code>]
+- Start <code>CLA</code> and <code>CCLA</code> submission [<code>link:#who-committers[Prospective committers]</code>]
+- Start link:#initial-ip-clearance[IP Clearance]
+[<code>IPMC member</code>]
+- Request Required Resources
+** link:#request-mailing-lists'>Mailing Lists</a> [<a href='#who-infra[Infrastructure Team]]
+** Consider and plan link:#transition-mailing-lists[transition to official mailing lists]
+
+- link:#Set+Up+Repository[Subversion] [IPMC]
+- link:#request-issue-tracking'>Issue Tracking</a> [<a href='#who-infra[Infrastructure Team]]
+** Consider and plan link:#issue-tracking-transition[issue tracking transition]
+
+- link:#create-website'>Create website</a> [<code><a href='#who-committers[Prospective committers]</code>]
+** Consider and plan link:#web-site-transition[web site transition]
+
+<section id='mentors-ipmc'><title>Mentors MUST be on the IPMC</title>
+<p>
+Mentors link:/incubation/Incubation_Policy.html#Mentor[MUST] be on the IPMC.
+Any prospective Mentors who are not yet on the IPMC should ask to be added (by election).
+Email the application to <code>private@incubator.apache.org</code>.
+</p>
+<note>
+This process may take a few days.
+</note>
+</section>
+
+<section id='submit-cla'><title>CLA and CCLA Submission</title>
+<p>
+Prospective committers need to submit a
+Contributor License Agreement
+(link:http://www.apache.org/licenses/#clas[CLA]).
+This process can take a while so it is recommended that committers start to submit
+these as soon as the podling is accepted.
+</p>
+</section>
+
+<section id='initial-ip-clearance'><title>IP Clearance</title>
+<section id='initial-up-clearance-general'><title>Background</title>
+<p>
+Existing codebases need to be imported through the standard IP clearance
+process. This means that a Software Grant Agreement
+(link:http://www.apache.org/licenses/#grants[SGA])
+or Contributor License Agreement
+(link:http://www.apache.org/licenses/#clas[CLA])
+need to be submitted
+for all copyright owners. This process may take a while so it is best to
+start as soon as the podling is accepted.
+</p>
+<p>
+The acceptance of the initial codebases is approved by the
+IPMC as part of the acceptance motion. So, no vote is required by the
+PPMC. Otherwise, follow the standard IP clearance
+link:#poding-ip-clearance[process for podlings].
+</p>
+</section>
+<section id='initial-provenance'><title>Establishing Provenance</title>
+<p>
+Paperwork needs to be submitted to Apache that grants a legal license on the code
+to the Apache Software Foundation.
+As a rule of thumb, if all the material contributors to the code
+are joining the podling as initial contributors, then CLAs (individual or corporate)
+are all you need. The individuals must submit the 'individual' CLA (ICLA).
+If there are employers involved who might claim
+rights in the code, then corporate CLAs (CCLAs) are needed for those employers.
+</p><p>
+If, on the other hand, there are material contributors who are <strong>
+not</strong> joining the podling as initial contributors, or if there
+are additional corporate entities who can claim rights in the code,
+then SGAs are required from those individuals or corporations.
+</p>
+<p>
+The foregoing is only a rule of thumb. Generally, the mentors of a new project
+will need to consult with general@incubator.apache.org or the Apache legal team
+about the particular circumstances.
+</p>
+<p>
+It may take some time to track down all contributors. It is not necessary to
+have paperwork on file for all contributions before the code is imported.
+It may be necessary to reverse some patches and rewrite areas of code if
+contributors cannot be found or at not happy about given Apache written
+permission to use their code.
+</p><p>
+No releases are possible until the provenance of all the code to be release
+has been clearly established and the relevant paperwork filed with Apache. It is
+therefore important to keep the status updated.
+</p><p>
+Receipts of ICLAs, CCLAs, and SGAs are recorded by the secretary in
+the private foundation repository. Reading is restricted to members and officers
+of the foundation. If there is no officer or member available then ask on the
+general list.
+</p>
+</section>
+<section id='initial-import-code-dump'><title>Initial Code Dump</title>
+<p>
+For corporate contributions, the SGA or CCLA MUST be completed, submitted
+and received before the code is imported.
+</p><p>
+For contributions composed of patches from individual contributors,
+it is safe to import the code once the major contributors (by volume)
+have completed ICLAs or SGAs.
+</p><p>
+In either case, the code to be imported should be attached to a JIRA
+and then imported. It is recommended that the previous version
+control system is tagged so that the imported version is precisely known.
+</p><p>
+A public record MUST be made of the code imported. If the import is not
+attached to JIRA then it MUST be committed to version control.
+</p>
+<section id='svn-history'><title>Importing History</title>
+<p>
+The incoming code can either be committed as a snapshot or as a complete version
+control export including history (provided that the import is available in a format
+readable by subversion).
+Importing with history allows existing open source projects who want to maintain
+older versions at Apache to easily perform source diffs and so on. Import just the
+latest code allows a clean break to be made with the past. The choice is left to
+the community of the incoming project.
+</p><p>
+The infrastructure team will perform the import including
+mapping IDs but it is an operation that requires skill, time and care. In this case,
+please ask the infrastructure team politely.
+</p>
+</section>
+</section>
+<section id='crypto-audit'><title>Audit Cryptography</title>
+<p>
+Before the code base is committed into an Apache repository, the contribution
+link:http://www.apache.org/dev/crypto.html[MUST] be checked
+and any restricted cryptography reported appropriately. Read and follow
+link:http://www.apache.org/dev/crypto.html[this guide].
+</p>
+</section>
+<section id='initial-clean-up'>
+<title>Initial Clean Up</title>
+<p>
+Once a JIRA has been created, the source should be cleaned up.
+</p>
+<p>
+- Ensure source files use the standard Apache boilerplates.
+This may mean replacing existing license headers. The
+tools in
+<code>
+https://svn.apache.org/repos/private/committers/tools
+</code>
+and
+<code>
+https://svn.apache.org/repos/private/committers/relicense
+</code>
+may be useful.
+
+- Ensure that NOTICE and LICENSE documents are present and
+correct
+
+- Add any required notices. Consider moving copyright
+attributions from source documents to the NOTICE. Read
+<a href='http://www.apache.org/legal/src-headers.html'>
+Apache policy on headers
+</a>
+.
+
+- Audit the source for any potential licensing issues. Any
+which are found should either resolved immediately (when
+required) or noted in the status document for later.
+
+It is recommended that the initial clean up be is started
+before the code is committed. It MUST be completed before any
+releases are cut.
+</p>
+<section id='clean-up-best-practice'>
+<title>Clean Up Best Practice</title>
+<p>
+It is recommended that version control is used to create a
+public record of the process. This will assist anyone
+auditing the code provenance (now or in the future) to
+easily perform due diligence without contacting the people
+who performed the clean up. The clean up process should
+therefore clearly document (using version control) the
+evolution of the IP licensing.
+</p>
+<p>
+Particular care needs to be taken with commit messages
+during clean up. The intended audience needs to include
+lawyers and code auditors. Members of the public need to be
+able to follow and understand the process from these
+messages alone.
+</p>
+<p>
+It is therefore recommended that the initial source is
+(after being expanded from the archive) checked in as is
+into a special directory (
+<code>${project}/trunk/import</code>
+is suggested). The original packaging, copyright statements
+and license notices should be preserved. A standard Apache
+LICENSE and appropriate NOTICE should be added at the top
+for the copyright for the collective work (see
+<a href='http://www.apache.org/legal/src-headers.html'>
+policy
+</a>
+). Take particular care with this commit message. As with
+any patch that contains code which is not the original work
+of the committer, the JIRA url (for the artifact imported)
+needs to be included together with notes about the original
+copyright owner and any associated paperwork. The fact that
+this is a exact import including original headers should be
+noted to stop any queries about these foreign headers.
+</p>
+<p>
+The cleanup should then proceed in a number of commits. If
+the source provenance is complex, break the process up into
+a number of logical steps committing each in turn with a
+good message.
+</p>
+<p>
+In particular, take care when relocating copyright
+statements and license notices into the NOTICE in the root
+directory: consider moving each copyright owner individually
+so that it is easier to audit. (See
+<a
+href='http://www.apache.org/legal/src-headers.html#notice'>
+policy
+</a>
+.)
+</p>
+<p>
+Once a section of code has been cleaned up
+(and link:#repackaging[repackaged],
+if necessary) normal development can begin.
+</p>
+</section>
+</section>
+<section id='repackaging'><title>On Repackaging</title>
+<p>
+It is recommended - but not mandated - that source is repackaged
+under the Apache namespace. There is no need to use the incubator
+namespace. For example, Java source might be repackaged to
+<code>org.apache.foo.Bar</code> or a DTD to <code>http://dtd.apache.org/foo/bar</code>.
+</p><p>
+Existing open source projects moving to Apache may well need to consider
+carefully how they will approach this transition.
+</p>
+</section>
+<section id='documents-clean-up'><title>Update Documents</title>
+<p>
+Check the documentation for references to the old home of the project and update them
+with references to Apache.
+</p><p>
+Read
+link:http://incubator.apache.org/guides/branding.html[Branding Guide].
+Ensure that appropriate disclaimers are added to the appropriate documentation.
+Consider adding a <code>DISCLAIMER</code> text document.
+</p>
+<section id='build-clean-up'><title>Update Build</title>
+<p>
+If the project uses link:http://maven.apache.org[Apache Maven], the pom will
+need to be updated to reflect that the project is now at Apache. In particular:
+</p>
+<ul>
+<li>Update <code>mailingLists</code>
+<li>Update <code>organization</code>
+<li>Update <code>url</code>
+<li>Update <code>issueManagement</code>
+<li>Check <code>licenses</code>
+<li>Update <code>scm</code>
+<li>Update <code>groupId</code>
+<li>Update <code>manifestEntries</code>. It is recommended that the
+standard Apache settings are used
+<li>Update <code>developers</code> to use apache IDs (when known)
+<li>Update <code>distributionManagement</code>
+<li>Consider specifying a link:http://maven.apache.org/pom.html#relocation[relocation]
+</ul>
+<p>
+If the project uses link:http://ant.apache.org[Apache Ant], the build script
+will probably need to be updated. In particular:
+</p>
+<ul>
+<li>Ensure any MANIFESTs generated refer to Apache. It is recommended that the
+standard Apache settings are used.
+<li>Check that <code>LICENSE</code>, <code>NOTICE</code> and - if appropriate -
+<code>DISCLAIMER</code> documents are copied into binary artifacts
+</ul>
+</section>
+</section>
+</section>
+<section id='orientation'><title>Orientating New Committers: Understanding Apache</title>
+<p>
+When a committer is elected by a typical top level project, the nominator
+and other PMC members educate the new committer about Apache. In the Incubator, this
+inductive must be performed by the Mentors. This process is one of the most important
+for the long term health of a project.
+</p><p>
+Apache works on the principle that discussions should happen on the most open forum
+available. Unless the matter involves a sensitive matter (such as security or
+personal issues), it should be raised on an open mailing list (typically the podling dev list
+or the incubator general list). Use of the incubator private list should be reserved
+for official notifications and sensitive topics.
+</p><p>
+Mentors need to take care. During the initial bootstrapping a habit may develop
+of emailing private list. It is important to break this habit as soon as the mailing
+lists are available.
+</p><p>
+Netiquette about the correct use of <code>cc</code>'s may also be difficult to
+effectively impart. During the bootstrap process there are a number of occasions
+where <code>cc</code>'s are required. The typical usage is to copy in a private
+listing to indicate that the action has the lazy permission of the committee.
+<code>cc</code>'s are very commonly used to create inefficient ad-hoc mailing lists in
+the commercial world. Except for a small number of defined processes, <code>cc</code>'s
+are frowned upon at Apache. Mentor need to encourage questions to be asked first
+on the public lists of the project then raised (if necessary) to the general
+incubator list.
+</p><p>
+TODO: content, links, prose, reconsider name for this section
+</p>
+</section>
+
+<section id='issue-tracking-transition'><title>Issue Tracking Transition</title>
+<p>
+Issues for Apache projects should be tracked on Apache hardware. Some projects arrive
+with existing issues tracking. So, in the end these need to be replaced (for new development
+at least) by the Apache issues tracker. Options need to be discussed publically on list
+and a consensus reached about the best transition strategy.
+</p>
+</section>
+</section>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/podling_sourcecontrol.ad
----------------------------------------------------------------------
diff --git a/pages/guides/podling_sourcecontrol.ad b/pages/guides/podling_sourcecontrol.ad
new file mode 100644
index 0000000..7de15a0
--- /dev/null
+++ b/pages/guides/podling_sourcecontrol.ad
@@ -0,0 +1,108 @@
+//Licensed 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
+//
+//http://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.
+= Podling Source Control
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+== Set Up Podling Source Repository
+
+The most important responsibility for mentors is to set up the
+podling source repository. Podlings can choose between svn and
+git for source control. For git, podlings may use repositories hosted at Apache, or within GitHub in the Apache organization.
+
+=== Set up GIT Repository
+
+Requests for new git repos are done via link:https://reporeq.apache.org/[reporeq.apache.org].
+This service will initialize a new repository, setup github mirrors and enable integrations for that repository.
+
+Historically, the Foundation's policy
+is to grant access to git repositories broadly to the incubator group,
+not narrowly podling-by-podling. So, once the repository
+exists, incubator group members gain access without further work. Once
+the podling graduates, a dedicated ldap group will be created to manage
+access and only those members will be given access.
+
+
+==== Set Up SVN Repository
+
+If the podling chooses svn, you must create the
+repository and give read/write access to the repository
+to all the committers for the podling. This involves requesting
+new committer accounts and granting access to mentors and existing
+Apache committers.
+
+Setting up a podling subversion repository has two steps: Creating the SVN space
+and configuring the authorization (in both svn and git).
+
+Create the workspace in svn. This requires commit access to the
+incubator svn repository. Podlings are given their own subdirectory
+of the incubator svn repository. To create the podling subdirectory,
+the mentor executes the svn command to create a remote directory: `svn mkdir https://svn.apache.org/repos/asf/incubator/{podling}`
+
+Create the workspace authorization in asf-authorization-template.
+This requires commit access to `infrastructure-puppet` to modify the file
+`https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob;f=modules/subversion_server/files/authorization/asf-authorization-template`.
+Please follow the procedures in the link:https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo[infrastructure puppet workflow] document.
+
+Edit the file to add the podling repository in alphabetical order, e.g.
+
+[source]
+====
+{podling}={mentor1},{mentor2}
+====
+
+In the section listing all the projects (again in alphabetical order)
+add the podling directory and permissions, to enable the podling for its
+eventual website:
+
+[source]
+====
+[/incubator/{podling}]
+@{podling} = rw
+...
+====
+
+This is a convenient time to add link:#Authorize+Committers[authorization] for committers
+who have accounts.
+
+link:#who-auth-karma[Authorization] karma is restricted. If no Mentor
+has this karma then post an email to IPMC private list requesting that this
+is actioned.
+
+=== Authorize Committers
+
+The process to add committers to the podling depends on whether
+the new committer is already an Apache committer and whether
+the new committer is in the list of original committers:
+
+- The committer is in the list of original committers in the
+podling proposal to the incubator and is not already an Apache
+committer:
+** Ask developers to send their ICLA to secretary@apache.org according to
+link:http://apache.org/licenses/#submitting[standard procedure.]
+Note that ICLA forms must be signed, either by hand or by digital signature.
+** Developers should choose an Apache id that is not already listed
+link:http://people.apache.org/committer-index.html[here.]
+** Developers should enter their preferred Apache id on the ICLA
+and enter the podling name in the "notify" field of the ICLA.
+- The committer is in the list of original committers in the
+podling proposal to the incubator and is already an Apache committer, only
+link:#who-auth-karma[incubator authorization] is required.
+- The committer was voted by the PPMC and approved by the incubator PMC:
+
+Perform one of the above procedures depending on whether the
+committer is already an Apache committer on another project.
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/ppmc-offer.txt
----------------------------------------------------------------------
diff --git a/pages/guides/ppmc-offer.txt b/pages/guides/ppmc-offer.txt
new file mode 100644
index 0000000..27b8978
--- /dev/null
+++ b/pages/guides/ppmc-offer.txt
@@ -0,0 +1,58 @@
+Dear Joe Bob
+
+In recognition of your demonstrated commitment to, and alignment with, the
+goals of the Apache Frizzle project, the Frizzle PPMC has voted to offer you
+membership in the Frizzle PPMC ("Podling Project Management Committee").
+
+Please let us know if you accept by subscribing to the private alias [by
+sending mail to private-subscribe@frizzle.incubator.apache.org], and posting
+a message to private@frizzle.incubator.apache.org.
+
+The PPMC is the Incubator podling version of a project PMC ("Project
+Management Committee") that for every top-level project is tasked by the
+Apache Board of Directors with official oversight and binding votes in
+that project. When Frizzle graduates from the Incubator to a top-level
+project, the project PMC is usually formed from the membership of the PPMC.
+Note that while participation in the PMC after graduation is not
+guaranteed, simply continuing your constructive and active participation
+is usually sufficient.
+
+As a PPMC member, and later as a PMC member, you are responsible for
+continuing the general project, code, and community oversight that you
+have exhibited so far. The votes of the PPMC are not legally binding;
+votes of the Incubator PMC are. However, many of the PPMC members
+are also Incubator PMC members, so they implicitly cast binding votes
+when we vote on PPMC issues. While this is an important legal
+distinction, it shouldn't enter your thinking when working on the PPMC -
+members should treat every decision as if it were legally binding for the ASF.
+Also, in day-to-day activities, the Incubator PMC member vs PPMC member
+distinction should be invisible -- we are peers.
+
+All PPMC members are subscribed to the project's private mail list, which
+is used to discuss issues unsuitable for an open, public forum, such as
+people issues (e.g. new committers, problematic community members, etc.),
+security issues, and the like. It can't be emphasized enough that
+care should be taken to minimize the use of the private list, discussing
+everything possible on the appropriate public list.
+
+The private PPMC list is *private* - it is strictly for the use of the
+PPMC. Messages are not to be forwarded to anyone else without the express
+permission of the PPMC. Also note that any Member of the Foundation has
+the right to review and participate in any PPMC or PMC list, as a PMC
+and PPMC are acting on behalf of the Membership.
+
+Finally, the PPMC (and assuming graduation, the PMC) is not meant to create
+a hierarchy within the committership or the community. In fact, a goal is to
+add all committers over time to the PPMC/PMC, as our belief is that those who
+do the work should get a binding vote. Therefore, in our day-to-day
+interactions with the rest of the community, we continue to interact as
+peers, where every reasonable opinion is considered, and all community
+members are invited to participate in our public voting. If there ever
+is a situation where the PMC/PPMC's view differs significantly from that
+of the rest of the community, this is a symptom of a problem that needs to
+be addressed.
+
+With the expectation of your acceptance, welcome!
+
+The Apache Frizzle PPMC
+
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/ppmc.ad
----------------------------------------------------------------------
diff --git a/pages/guides/ppmc.ad b/pages/guides/ppmc.ad
new file mode 100644
index 0000000..cc67126
--- /dev/null
+++ b/pages/guides/ppmc.ad
@@ -0,0 +1,246 @@
+//Licensed 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
+//
+//http://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.
+= Apache Incubator: Podling Project Management Committee
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+== Podling Project Management Committee (PPMC)
+The Podling Project Management Committee (PPMC) helps a
+Podling learn how to govern itself. It works like a PMC but
+reports to the Incubator PMC instead of to the ASF Board.
+Initially, it is composed of the Podling's mentors and initial
+committers. The PPMC is directly responsible for the oversight
+of the podling and it also decides who to add as a PPMC member.
+
+For general information about PMCs, see the link:http://www.apache.org/dev/pmc.html[PMC FAQ].
+
+== Private Mail List
+
+A private mail list, named private@*project*, lets the PPMC discuss confidential topics.
+*Most communication should be on the Podling's dev list!*
+The private list is used only for confidential discussions that
+should not be made public, such as the suitability of a
+particular individual to become a committer or a member of the
+PPMC. See the ASF *How it Works* section titled
+link:http://www.apache.org/foundation/how-it-works.html#confidential[Balancing confidentiality and public discussion].
+
+The mentors should verify that all PPMC members are actually
+subscribed to the private list. Mailing list moderators can
+request the list of subscribers using ezmlm commands, and any
+subscriber can send a "ping - please reply" message to check
+who is actually "listening" to the PPMC list.
+
+*Don't mix private and public lists in posts!*
+
+- Don't post to both the dev and private lists. Each member of the PPMC should be on the dev list, so posting to dev is sufficient.
+- Likewise, don't post to both the Incubator general and Incubator private lists. Each member of the Incubator PMC is on the Incubator general list, so posting to general is sufficient.
+
+[NOTE]
+====
+The lists used to be named *project*-ppmc or
+pmc@*tlp*, so you may see those names referenced in other ASF
+documentation or in the mail list archives. It was
+link:/official/mailing-lists.html#july-2005[resolved]
+that these lists should be named *private*
+to make it clear that they should be used for confidential discussion,
+not as a general purpose way to contact (P)PMC members.
+====
+
+== Podling Status Reports
+On a regular basis, reports from each incubating project are
+aggregated and sent to the ASF Board. Watch the Incubator general
+mail list for when these become due.
+
+The Incubator reports to the ASF Board monthly and includes
+status for a subset of the incubating projects. Currently new
+Podlings report to the Incubator monthly for the first three
+months, then quarterly thereafter. The link:../report-groups.txt[reporting schedule] is generated from podlings.xml.
+
+The PPMC does not have to fill out the report itself; the PPMC
+is just responsible for making sure that it gets filled out. In
+fact, it is better to discuss the report on the dev list and ask
+Podling developers to contribute to it. If Mentors disagree with
+the posted report, they should say so; otherwise, the Incubator
+PMC will assume that it speaks for the community.
+
+Please add the following items:
+- Project name and one-line summary.
+- Date of entry to the Incubator.
+- Top three items to resolve before graduation.
+
+Here are the points to be addressed:
+- Is there anything that the Incubator PMC or ASF Board specifically needs to address?
+- Are there any legal, infrastructure, cross-project or personal issues that need to be addressed? (Are there any stumbling blocks that impede the podling?)
+- Check that the project's Incubation link:../projects/index.html[Status] file up to date. (Also provide the URL.)
+- What has been done (releases, milestones, etc.) since the last report?
+- What are the plans and expectations for the next period?
+- Are there any recommendations for how incubation could run more smoothly for you?
+- etc. (your own thoughts on what is important would be helpful!)
+
+It is required for mentors to sign off on podling reports.
+- Mentors must sign off on the podling report. If there is no mentor sign off, the report from that podling will not be accepted and they will be moved to monthly, expected to report next month.
+
+Podling reports get added to the Incubator wiki
+- All podling reports must be added to the link:http://wiki.apache.org/incubator/[Incubator wiki]
+- Follow the instructions in your monthly reminder, and post on the <Month><Year> page, with the provided template
+
+== Project Status Page
+In addition to the quarterly status reports, each Podling has a
+page on the Incubator web site that tracks the status
+(see the link:http://incubator.apache.org/projects/index.html[complete list] for examples). Instructions for updating the status page
+are in the link:website.html[Incubator web site guide]
+under link:website.html#Edit+your+project+status+page[Edit your project status report].
+
+This is one of the primary link:mentor.html#Overview[sources] of information about your podling's
+status to the Incubator PMC and to the general public. Be sure to
+keep it updated as your podling progresses!
+
+== Maintaining Podling Roster
+Podling rosters are maintained in Whimsy. Going forward, the content in *projects/$podling.xml*
+is considered deprecated.
+
+link:https://whimsy.apache.org/roster/ppmc/[Click Here to access the Whimsy Roster Tool for PPMCs]
+
+== Adding new committers
+
+Adding new committers is one of the most important functions
+of any PMC, and Incubator podlings are no different.
+
+There are no ASF wide rules on how to decide when to make someone
+a committer, podlings need to agree an approach that works for them.
+Some ASF projects have a high bar requiring significant contributions before
+someone is considered, other projects grant it more freely to anyone
+who shows interest in contributing. Some projects use formal [DISCUSS] and
+[VOTE] threads on the private mailing list, others use a more lazy consensus
+approach. For more information see,
+link:http://www.apache.org/foundation/glossary.html#CommitAccess[commit access] and the ASF *How it Works* document, which explains
+link:http://www.apache.org/foundation/how-it-works.html#meritocracy[ meritocracy] and
+ link:http://www.apache.org/foundation/how-it-works.html#roles[ roles].
+
+The podling Incubator reports should document any new committers
+added since the last report.
+
+Once the decision has been made the proposer offers committership
+to the nominee. If the nominee accepts the responsibility of being
+a committer for the project, the nominee formally becomes an
+Apache committer.
+
+The proposer then asks an Incubator PMC member (typically one of
+the mentors) to follow the
+link:http://www.apache.org/dev/pmc.html#newcommitter[documented]
+link:http://www.apache.org/dev/pmc.html#SVNaccess[procedures]
+to complete the process. If the nominee is already an Apache
+committer on another project, the Incubator PMC member simply
+link:http://www.apache.org/dev/pmc.html#SVNaccess[updates]
+the SVN authorization settings to include the nominee as a committer
+on the podling.
+
+The proposer then directs the new committer to the
+link:http://www.apache.org/dev/[Apache developer's pages],
+to the
+link:http://incubator.apache.org/[Apache Incubator site]
+and to the Incubator
+link:committer.html[Committers Guide] for important additional
+information.
+
+For projects which wish to have all
+committers also be PPMC members, the "Voting in a new PPMC member"
+guide below should then be followed, noting that if desired it
+is possible to run a joint committership and PPMC vote, providing
+that the guidance for both is followed.
+
+== Voting in a new PPMC member
+It should be a goal of a podling to have all committers participate
+in the PPMC. The PPMC should take an active role in watching
+committers develop into community participants, identify those who
+are participating at a community level, not just a technical one,
+and approach them with an offer of PPMC membership.
+
+Any member of the PPMC can propose a new member of the PPMC. The
+proposal should be discussed in private on the PPMC private alias,
+with a subject line of [DISCUSS] Joe Bob PPMC membership. If there
+is consensus that the proposed member is suitable, then there should
+be a formal vote in the PPMC private alias, with the subject line of
+[VOTE] Joe Bob PPMC membership.
+
+If the vote is successful, the proposer
+should send a message to the PPMC private alias, with
+the subject line of [VOTE][RESULT] Joe Bob PPMC membership. The
+message id of the [VOTE][RESULT] message should be preserved for
+notifying the Incubator PMC.
+The nominating PPMC member should send a message to
+the IPMC (link:mailto:private@incubator.apache.org[private@incubator.apache.org]) with a reference to
+the vote result's message id of the following form:
+
+[source]
+--
+To: private at incubator.apache.org
+CC: private at PODLING.incubator.apache.org
+Subject: [NOTICE] *Joe Bob* for Podling PPMC
+Body:
+
+Joe Bob has been voted as a new member of the Podling PPMC. the vote thread is at: *link to the vote thread*
+--
+
+*It should noted that there is a grace period of 72 hours from when the
+above NOTICE is sent to the Incubator PMC to when the proposed member
+is formally invited. This is an important part of the overall
+process. Failure to do this can result in an embarassing situation
+for people involved.*
+
+After 72 hours, Joe Bob
+should be invited to join the PPMC, using a sample message like
+link:ppmc-offer.txt[this].
+
+Once the proposed member has accepted, the moderator for the
+PPMC mail alias will accept the new member's subscription request.
+
+The new member should be directed to
+link:ppmc.html[this page] for PPMC membership information.
+
+The nominating member should also update the PPMC membership
+section of the Podling's status file. For projects which choose to
+always make new committers also PPMC members, simply updating
+the committer list and ensuring that a statement such as
+"The PPMC consists of all the committers and mentors listed here"
+is generally sufficient.
+
+== Adding new mentors
+
+At times, it may be desirable to add a new mentor to a podling.
+Under all circumstances, a mentor must be an IPMC member.
+
+IPMC members are free to volunteer to be a mentor to a podling
+as they see fit. To do so, they should mail the podling stating
+their intentions. The podling should then decide if it wants to
+add the new mentor or not. If a decision has been reached to
+add the mentor, then all podling documentation should be updated
+to reflect the change (podlings.xml, projects/{podling}.xml) and
+the incubator be notified of the change as well.
+
+If a podling is in a position where they feel they need to add a new mentor,
+they may want to drop a mail on the general incubator mailing list to try
+to recruit a new mentor.
+
+== PPMC and Binding Votes
+
+The only time when a PPMC member's vote is binding is for the addition of
+new PPMC members and committers. Release votes are only binding to IPMC
+members.
+
+The binding status of a person's vote is not related to the mailing list
+that the vote is occurring on.
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/press-kit.ad
----------------------------------------------------------------------
diff --git a/pages/guides/press-kit.ad b/pages/guides/press-kit.ad
new file mode 100644
index 0000000..fc95d2a
--- /dev/null
+++ b/pages/guides/press-kit.ad
@@ -0,0 +1,108 @@
+//Licensed 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
+//
+//http://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.
+= Podling Press Kit
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+== Apache Incubator Graphics
+
+This page contains various graphical assets that are intended to be used by Apache Incubator podlings and their communities.
+The Apache Software Foundation owns all Apache-related trademarks, service marks, and graphic logos. You can read our link:http://www.apache.org/foundation/marks/[formal Trademark Policy] that addresses allowable uses and how to contact us for permissions.
+The Apache Incubator provides two main types of graphic:
+
+- Incubator Graphics - the official Apache Incubator logo
+- “Powered By” Apache Incubator Logos - to be used by Apache Incubator podlings
+
+Please note that each Apache podling provides and maintains their own official project logo on their homepage. The best place to ask for a copy of a project logo is on their dev@ mailing list.
+
+= Downloadable Graphics
+
+This section contains downloadable graphics of the Apache Incubator logo.
+
+REMINDER: all graphics/images/logos are trademarks of the ASF, and must not be used without appropriate attribution and permission from the ASF. Please see our formal Trademark Policy for more details. In particular, as a vendor-neutral public charity that provides independent governance to all Apache projects, you must use care when displaying the feather, and ensure it's clear that it's referring to the ASF as an independent organization.
+
+=== Official Incubator Logo
+
+This is the latest version of the Apache Incubator logo, as launched in March 2017. This logo is to be used on ALL podling pages during the incubation process.
+
+image:/images/incubator_feather_egg_logo.png[]
+
+link:/images/SVG/apache_incubator.svg[SVG] | link:/images/PDF/apache_incubator.pdf[PDF] | link:/images/EPS/apache_incubator_RGB.eps[EPS - RGB] | link:/images/EPS/apache_incubator_CMYK.eps[EPS - CMYK]
+
+=== Red-On-White Version of Logo
+
+The red-on-white version of the Apache Incubator Logo is
+
+image:/images/incubator_feather_egg_logo_red_crop.png[]
+
+link:/images/SVG/apache_incubator_red.svg[SVG] | link:/images/PDF/apache_incubator_red.pdf[PDF] | link:/images/EPS/apache_incubator_red_RGB.eps[EPS - RGB] | link:/images/EPS/apache_incubator_red_CMYK.eps[EPS - CMYK]
+
+=== Black-On-White Version of Logo
+
+The black-on-white version of the Apache Incubator Logo is
+
+image:/images/incubator_feather_egg_logo_wb_crop.png[]
+
+link:/images/SVG/apache_incubator_black.svg[SVG] | link:/images/PDF/apache_incubator_black.pdf[PDF] | link:/images/EPS/apache_incubator_black_RGB.eps[EPS - RGB] | link:/images/EPS/apache_incubator_black_CMYK.eps[EPS - CMYK]
+
+=== White-On-Black Version of Logo
+
+The white-on-black version of the Apache Incubator Logo is
+
+image:/images/incubator_feather_egg_logo_bw_crop.png[]
+
+link:/images/SVG/apache_incubator_white.svg[SVG] | link:/images/PDF/apache_incubator_white.pdf[PDF] | link:/images/EPS/apache_incubator_white_RGB.eps[EPS - RGB] | link:/images/EPS/apache_incubator_white_CMYK.eps[EPS - CMYK]
+
+== "Powered By" Apache Incubator Podling Logos
+
+Inspired by the ASF’s “Powered by Apache” logo [LINK], the “Apache Incubator Podling” logo was created to maintain the unique identity of each Apache podling whilst undergoing development in the Apache Incubator. All Apache podlings and their communities are encouraged to proudly display “Apache Incubator Podling” assets on their Websites, documentation, marketing materials, etc.
+Guidelines for the appropriate use of the “Powered By Apache” logos include:
+
+- The standalone “Powered By” Apache Incubator and “Apache Incubator Podling” circular banded logos may be used standalone with just the Apache Incubator logomark (denoting general use of an Apache Incubator podling) or in combination with an official Apache podling logo;
+- The official podling logo may not be altered in any way other than removing/separating the name(s) where applicable as approved by the associated Podling Project Management Committee (PPMC);
+- The appropriate trademark symbol(s), such as ® or ™, associated with the podling's logo --if applicable-- must be included in the logo;
+- The “Powered By” logo's circular band format, font, and color must not be altered in any way;
+- The logo and/or its contents must not be rotated, animated, distorted, or otherwise altered, nor should it be used as a graphic element, background, or pattern;
+- The logo and/or its contents must not be translated or localized, nor should it have versioning numbers or other unauthorized words added to it;
+- The preferred background color for the logo is white, however, the logo may appear on colored, black, or image/photographic backgrounds providing the logo's legibility is not compromised;
+- The logo may be sized and produced in multiple file formats as required by the Podling Project Management Committee, with a preferred minimum size of 80 pixels high in Web/online applications (where possible) to ensure legibility;
+- The logo may not, under any circumstances, be incorporated with a third party's company name, product name, or logo(s), or adopt marks and/or logos that are confusingly similar to or imply improper association with The Apache Software Foundation;
+- Third parties and programs are not allowed to use official Apache project or podling logos and/or create alternate logos or identifying marks relating to any Apache project without written permission from the associated Podling Project Management Committee and/or ASF Brand Management.
+- We have a link:https://www.apache.org/foundation/marks/faq/#poweredby[trademark use policy for the "Powered By" phrase]
+
+In addition, official Apache Project pages and documentation on apache.org must utilize the appropriate trademark symbols on the respective Project logo, along with the following footnote: "Apache, Apache [PODLING NAME], and the Apache [PODLING NAME] logo are registered trademarks or trademarks of The Apache Software Foundation in the U.S. and/or other countries."
+
+=== Template and Usage
+
+==== Standalone "Powered By" Apache Incubator Logo
+image:/images/incubator_ring_logo.png[height=200]
+
+==== Per-Project Powered By Logos
+
+Logos for individual podlings, such as the ones below, are available in jpg, psd, and eps format. They can be retrieved by requesting:
+
+image:/images/incubator_power_ring.jpg[height=200]
+image:/images/incubator_ring_airflow.jpg[height=200]
+
+For example, creating the “Apache Incubator Podling” logo for Apache Airflow can be accomplished by retrieving the Airflow logo from link:http://airflow.incubator.apache.org/_images/pin_large.png[http://airflow.incubator.apache.org/_images/pin_large.png]
+If you are unable to find the logo you are looking for, please contact the podling’s mailing list.
+
+==== Template For the Creation of Powered By Logos
+image:/images/template_airflow.jpg[height=200]
+image:/images/template_hawq.jpg[height=200]
+image:/images/template_spot.jpg[height=200]
+
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org