incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From johndam...@apache.org
Subject [02/97] [abbrv] [partial] incubator git commit: Removed unneeded files.
Date Tue, 08 Nov 2016 21:41:15 GMT
http://git-wip-us.apache.org/repos/asf/incubator/blob/170c4191/bob/guides/community.html
----------------------------------------------------------------------
diff --git a/bob/guides/community.html b/bob/guides/community.html
deleted file mode 100644
index ef1c9c7..0000000
--- a/bob/guides/community.html
+++ /dev/null
@@ -1,427 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-               "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!--
-  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
-
-    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. 
--->
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
-  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-  <link rel="stylesheet" href="../style/bootstrap-1-3-0-min.css" type="text/css" />
-  <link rel="stylesheet" href="../style/style.css" type="text/css" />
-    <link rel="alternate" title="general@incubator.apache.org Archives" type="application/atom+xml" href="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom" />
-    <title>Guide to successful community building (DRAFT) - Apache Incubator</title>
-  
- </head>
- <body>
- <div class="container">
-  <div class="row">
-<div class="span12">
-  <a href="http://www.apache.org/"><img src="http://incubator.apache.org/images/asf_logo_wide_small.png" alt="The Apache Software Foundation" border="0" style="margin-top: 2px" width="62%"/></a>
-</div>
-<div class="span4">
-<a href="http://incubator.apache.org/"><img src="../images/egg-logo2.png" alt="Apache Incubator" border="0"/></a>
-</div>
-</div>
-  <div class="row"><div class="span16"><hr noshade="noshade" size="1"/></div></div>
-  
-  <div class="row">
-   <div class="span4">
-    <form action="http://www.google.com/search" method="get">
-     <input value="incubator.apache.org" name="sitesearch" type="hidden"/>
-     <input size="20" name="q" id="query" type="text" value="search..."
-      onclick="if(this.value == 'search...') {this.value = ''}"/>
-     <input name="Search" value="Go" type="submit"/>
-    </form>
-          <div class="menuheader">General</div>
-    <menu compact="compact">
-          <li><a href="../index.html">Welcome</a></li> 
-          <li><a href="../incubation/Process_Description.html">Incubation Overview</a></li> 
-          <li><a href="../incubation/Incubation_Policy.html">Incubation Policy</a></li> 
-          <li><a href="../guides/index.html">Incubation Guides</a></li> 
-          <li><a href="../incubation/Roles_and_Responsibilities.html">Roles and Responsibilities</a></li> 
-          <li><a href="../faq.html">General FAQ</a></li> 
-          <li><a href="http://wiki.apache.org/incubator">Incubator Wiki</a></li> 
-          <li><a href="../whoweare.html">Who We Are</a></li> 
-          <li><a href="../sitemap.html">Site Map</a></li> 
-            </menu>
-      <div class="menuheader">Status</div>
-    <menu compact="compact">
-          <li><a href="../projects/index.html">Project List</a></li> 
-          <li><a href="../clutch.html">Clutch Report</a></li> 
-          <li><a href="../ip-clearance/index.html">IP Clearance</a></li> 
-          <li><a href="../history/index.html">Incubator History</a></li> 
-            </menu>
-      <div class="menuheader">Entry Guides</div>
-    <menu compact="compact">
-          <li><a href="../guides/proposal.html">Proposal Guide</a></li> 
-            </menu>
-      <div class="menuheader">Podling Guides</div>
-    <menu compact="compact">
-          <li><a href="../guides/committer.html">Podling Committers</a></li> 
-          <li><a href="../guides/ppmc.html">Podling PMC (PPMC)</a></li> 
-          <li><a href="../guides/mentor.html">Podling Mentor</a></li> 
-          <li><a href="../guides/releasemanagement.html">Podling Releases</a></li> 
-          <li><a href="../guides/branding.html">Podling Branding/Publicity</a></li> 
-          <li><a href="../guides/sites.html">Podling Websites</a></li> 
-          <li><a href="../guides/graduation.html">Graduation</a></li> 
-          <li><a href="../guides/retirement.html">Retirement</a></li> 
-            </menu>
-      <div class="menuheader">Other Guides</div>
-    <menu compact="compact">
-          <li><a href="../guides/participation.html">Participation</a></li> 
-          <li><a href="../faq.html">General FAQ</a></li> 
-          <li><a href="../guides/pmc.html">Incubator PMC (IPMC)</a></li> 
-          <li><a href="../guides/chair.html">IPMC Chair</a></li> 
-          <li><a href="../guides/lists.html">Mailing Lists</a></li> 
-          <li><a href="../guides/website.html">Incubator Website</a></li> 
-            </menu>
-      <div class="menuheader">ASF</div>
-    <menu compact="compact">
-          <li><a href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li> 
-          <li><a href="http://www.apache.org/dev/">Developer Documentation</a></li> 
-          <li><a href="http://www.apache.org/foundation/">Foundation</a></li> 
-          <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li> 
-          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li> 
-            </menu>
-    <!-- start Ads Server -->
-    <iframe src="http://www.apache.org/ads/buttonbar.html"
-     style="border-width:0; float: left" frameborder="0" scrolling="no"
-     width="135" height="265"></iframe>
-    <!-- end Ads Server -->
-   </div>
-   
-   <div class="span12">
-            <h2 id='preamble'><img src="../images/redarrow.gif" />Guide to successful community building (DRAFT)</h2>
-<div class="section-content">
-<h3 id='status'>Status - DRAFT</h3>
-<div class="section-content">
-<p>This document is under development.</p>
-<p>
-					Help to improve the system by posting a patch for
-					this document to the incubator section of JIRA or a
-					comment to the <a href="lists.html">general</a> list at
-					incubator.
-				</p>
-</div>
-<h3 id='TOC'>Contents</h3>
-<div class="section-content">
-<ul>
-<li><a href='#preamble'>
-Guide to successful community building (DRAFT)
- </a>
- <ul>
-<li><a href='#status'>
-Status - DRAFT
- </a>
-</li>
-<li><a href='#TOC'>
-Contents
- </a>
-</li>
-<li><a href='#abstract'>
-Abstract
- </a>
-</li>
-</ul>
-</li>
-<li><a href='#introduction'>
-What is an open and diverse community?
- </a>
- <ul>
-<li><a href='#people'>
-People
- </a>
-</li>
-<li><a href='#communication'>
-Communication
- </a>
-</li>
-</ul>
-</li>
-<li><a href='#notes-community'>
-Community Building
- </a>
- <ul>
-<li><a href='#notes-profile'>
-Raising The Profile
- </a>
-</li>
-<li><a href='#notes-recruitment'>
-Building a community by stepping back a little
- </a>
-</li>
-<li><a href='#notes-committers'>
-Helping Developers Become Committers
- </a>
-</li>
-</ul>
-</li>
-</ul>
-</div>
-<h3 id='abstract'>Abstract</h3>
-<div class="section-content">
-<p>
-
-					The intent of this document is to help podlings the
-                    importance of building an open and diverse community for
-                    their project. It gives guidelines on how to accept new
-                    committers and PPMC members, and how to enable more
-                    community involvement, taking off the burden of answering
-                    every question yourself.
-
-				</p>
-</div>
-</div>
-        <h2 id='introduction'><img src="../images/redarrow.gif" />What is an open and diverse community?</h2>
-<div class="section-content">
-<p>
-
-				A major criterion for graduation is to have developed an open
-                and diverse <a href="http://www.apache.org/foundation/glossary.html#Meritocracy">meritocratic</a>
-                community. Time has demonstrated that these kinds of
-                communities are more robust and productive than more closed
-                ones.
-
-			</p>
-<h3 id='people'>People</h3>
-<div class="section-content">
-<p>
-
-					As a project grows, it needs to renew itself by accepting new
-	                committers. A project needs to learn how it can recruit new
-	                developers and committers into the community. Accepting new
-	                committers usually increases the diversity of the project. So,
-	                this process is very beneficial. <a href="#notes-community">Community building</a> requires energy
-	                which could have been spent on code development but this cost
-	                is an important investment for the future of the project.
-
-				</p>
-<p>
-
-					The openness of the community is not only measured by the
-	                number of contributors. Open and respectful discussions on the
-	                mailing lists are vital. Ways to resolve technical conflict
-	                without destroying personal relationships must be learned.
-
-				</p>
-</div>
-<h3 id='communication'>Communication</h3>
-<div class="section-content">
-<p>
-
-					Mailing lists are the life blood of Apache communities. They
-	                are the primary mode of discourse and constitute a public and
-	                historic record of the project. Other forms of communication
-	                (P2P, F2F, personal emails and so on) are secondary. There are
-	                well founded fears about use of these media for project
-	                communication. Though many projects successfully blend other
-	                forms of communications, care needs to be taken since
-	                out-of-band communications have led to difficulties in the
-	                past. The reason is that communications on other than the
-	                public mail aliases exclude parts of the community. Even
-	                publicly advertised IRC chats can be exclusionary due to time
-	                zone constraints or conflicting time commitments by community
-	                members who might want to participate.
-
-				</p>
-<p>
-
-					Apache project mailing lists are public, well indexed and well
-	                archived. This allows anyone to monitor (both in real time and
-	                by browsing the archives) what's happening. Opinions expressed
-	                are public and poor behavior risks a poster's reputation.
-
-				</p>
-<p>
-
-					Private communications tend to be more candid but also more
-	                likely to be ill-judged. Back channel communication tend to be
-	                divisive, excluding some members of the group. This tends to
-	                have a corrosive effect on the collective spirit of the
-	                community. Mistrust builds when opinions backed by blocks of
-	                developers arise fully formed on list.
-
-				</p>
-<p>
-
-					Communication through other channels also reduces the chance
-	                of <a href="http://en.wikipedia.org/wiki/Serendipity">serendipity</a>.
-	                As with most social networks, most subscribers to a mailing
-	                list never post and most posts come from a tiny minority of
-	                subscribers. Some passive subscribers are just interested in
-	                where the project is going but others understand related
-	                fields and have a limited intersection of interest. This
-	                second group will often post when this topic arises on list.
-	                Using public mailing lists to develop designs allows the
-	                chance encounter of ideas which often results in innovation.
-
-				</p>
-<p>
-
-					If alternative forums are used by a project, it is important
-	                to try to minimize the chances of problems arising. All
-	                matters of substance need to be moved back to the mailing
-	                lists. Public records should be kept and posted back to the
-	                list. Regular reminders should be posted to remind people that
-	                other secondary forms of communication exist.
-
-				</p>
-<p>
-
-					There are a limited number of topics such as security issues
-	                and discussions about people which are best handled in
-	                private. As much business of the project as possible should
-	                take place on public lists but the private list is available
-	                for those matters of a sensitive nature. Good netiquette
-	                requires that permission from the poster should be sought
-	                before making public, posts made to a private list. Try to
-	                avoid cross-posting between public and private forums. Take
-	                care not to post a reply to a private post to a public forum
-	                without permission.
-
-				</p>
-<p>
-
-					Learning to use mailing lists effectively is very important.
-	                If this can be achieved, then you have shown to be a lively,
-	                active and successful community. The future looks bright.
-
-				</p>
-</div>
-</div>
-        <h2 id='notes-community'><img src="../images/redarrow.gif" />Community Building</h2>
-<div class="section-content">
-<p>
-
-				Before a podling graduates, it must create a diverse and
-                self-sustaining community. Community building is tough: it
-                takes time, effort and more than a little magic. There is no
-                secret recipe, just hard work. In order to overcome this
-                obstacle, committers may need to devote more time to community
-                building and less to development.
-
-			</p>
-<p>
-
-				The <a href="mailto:community@apache.org">community mailing
-                list</a> is open to all Apache committers. This is the right
-                list for questions about community and on community building.
-                Subscriptions should be from an Apache email address.
-
-			</p>
-<h3 id='notes-profile'>Raising The Profile</h3>
-<div class="section-content">
-<p>
-
-					Sometimes, a podling is just not well-enough known. There
-                    are simply not enough users to allow new developers to be
-                    recruited. Overcoming this means finding ways to raise the
-                    profile of the podling. Some ideas:
-
-				</p>
-<ul>
-					<li>Improve the website</li>
-					<li>Improve the information provided within each release and release more often</li>
-					<li>
-						Committers who blog should join 
-						<a href="http://www.apache.org/dev/committers.html#planetapache">PlanetApache</a>
-					</li>
-					<li>Use grassroots media</li>
-					<li>Encourage downstream distributions to include a packaged version</li>
-					<li>Submit talks to conferences</li>
-					<li><a href="http://www.feathercast.org">Feathercast</a></li>
-					<li>Write articles</li>
-				</ul>
-</div>
-<h3 id='notes-recruitment'>Building a community by stepping back a little</h3>
-<div class="section-content">
-<p>
-
-					If the podling has lots of users but very few new
-                    developers then this means that more work is required to
-                    encourage users to become developers. A common cause of
-                    this is that committers are too quick to create code to
-                    solve user problems. It's good to respond quickly to
-                    requests by users. However, once a project gains momentum,
-                    it may be more productive for the long term health of a
-                    project to encourage users to become more involved at the
-                    expense of user satisfaction.
-
-				</p>
-<p>
-
-					Try to encourage expert users to answer questions. This
-                    may mean intentionally allowing a time gap before
-                    answering user questions. Encourage users to post by
-                    taking the time to deal politely and positively with
-                    misunderstandings and by replying to threads which have
-                    been answered well by a user to confirm that they are
-                    right. Avoid engaging in flame wars on user lists. Ignore
-                    trolls.
-
-				</p>
-<p>
-
-					Try to encourage users to become developers. When they
-                    give a good answer that isn't covered in the
-                    documentation, ask them to submit a patch. When users
-                    suggest a good design or extension, ask for volunteers to
-                    help implement rather than just coding it up.
-
-				</p>
-</div>
-<h3 id='notes-committers'>Helping Developers Become Committers</h3>
-<div class="section-content">
-<p>
-
-					If a podling has no trouble attracting developers but
-                    trouble retaining them long enough for them to become
-                    committers then this highlights an issue with the
-                    recruitment process. To become an Apache committer, a
-                    developer needs to hang around long enough to accumulate a
-                    track record of contributions. This often requires
-                    encouragement and help from existing committers.
-
-				</p>
-<p>
-
-					Promptly reviewing patches is important. The way that
-                    patches are applied is also important. Provide credit in
-                    the commit message and when closing the JIRA. It's also
-                    good to encourage developers by suggesting new related
-                    work they may like to volunteer for.
-
-				</p>
-</div>
-</div>
-       </div>
-   </div>
-  
-   <div class="row"><div class="span16"><hr noshade="noshade" size="1"/></div></div>
-  <div class="row">
-   <div class="span16 footer">
-     Copyright &#169; 2009-2016 The Apache Software Foundation<br />
-     Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br/>
-     Apache Incubator, Apache, the Apache feather logo, and the Apache Incubator project logo are trademarks of The Apache Software Foundation.
-     
-     
-    </div>
-  </div>
- </div> 
- </body>
-</html>

http://git-wip-us.apache.org/repos/asf/incubator/blob/170c4191/bob/guides/entry.html
----------------------------------------------------------------------
diff --git a/bob/guides/entry.html b/bob/guides/entry.html
deleted file mode 100644
index 20e10bb..0000000
--- a/bob/guides/entry.html
+++ /dev/null
@@ -1,219 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-               "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!--
-  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
-
-    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. 
--->
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
-  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-  <link rel="stylesheet" href="../style/bootstrap-1-3-0-min.css" type="text/css" />
-  <link rel="stylesheet" href="../style/style.css" type="text/css" />
-    <link rel="alternate" title="general@incubator.apache.org Archives" type="application/atom+xml" href="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom" />
-    <title>Enter The Incubator (DRAFT) - Apache Incubator</title>
-  
- </head>
- <body>
- <div class="container">
-  <div class="row">
-<div class="span12">
-  <a href="http://www.apache.org/"><img src="http://incubator.apache.org/images/asf_logo_wide_small.png" alt="The Apache Software Foundation" border="0" style="margin-top: 2px" width="62%"/></a>
-</div>
-<div class="span4">
-<a href="http://incubator.apache.org/"><img src="../images/egg-logo2.png" alt="Apache Incubator" border="0"/></a>
-</div>
-</div>
-  <div class="row"><div class="span16"><hr noshade="noshade" size="1"/></div></div>
-  
-  <div class="row">
-   <div class="span4">
-    <form action="http://www.google.com/search" method="get">
-     <input value="incubator.apache.org" name="sitesearch" type="hidden"/>
-     <input size="20" name="q" id="query" type="text" value="search..."
-      onclick="if(this.value == 'search...') {this.value = ''}"/>
-     <input name="Search" value="Go" type="submit"/>
-    </form>
-          <div class="menuheader">General</div>
-    <menu compact="compact">
-          <li><a href="../index.html">Welcome</a></li> 
-          <li><a href="../incubation/Process_Description.html">Incubation Overview</a></li> 
-          <li><a href="../incubation/Incubation_Policy.html">Incubation Policy</a></li> 
-          <li><a href="../guides/index.html">Incubation Guides</a></li> 
-          <li><a href="../incubation/Roles_and_Responsibilities.html">Roles and Responsibilities</a></li> 
-          <li><a href="../faq.html">General FAQ</a></li> 
-          <li><a href="http://wiki.apache.org/incubator">Incubator Wiki</a></li> 
-          <li><a href="../whoweare.html">Who We Are</a></li> 
-          <li><a href="../sitemap.html">Site Map</a></li> 
-            </menu>
-      <div class="menuheader">Status</div>
-    <menu compact="compact">
-          <li><a href="../projects/index.html">Project List</a></li> 
-          <li><a href="../clutch.html">Clutch Report</a></li> 
-          <li><a href="../ip-clearance/index.html">IP Clearance</a></li> 
-          <li><a href="../history/index.html">Incubator History</a></li> 
-            </menu>
-      <div class="menuheader">Entry Guides</div>
-    <menu compact="compact">
-          <li><a href="../guides/proposal.html">Proposal Guide</a></li> 
-            </menu>
-      <div class="menuheader">Podling Guides</div>
-    <menu compact="compact">
-          <li><a href="../guides/committer.html">Podling Committers</a></li> 
-          <li><a href="../guides/ppmc.html">Podling PMC (PPMC)</a></li> 
-          <li><a href="../guides/mentor.html">Podling Mentor</a></li> 
-          <li><a href="../guides/releasemanagement.html">Podling Releases</a></li> 
-          <li><a href="../guides/branding.html">Podling Branding/Publicity</a></li> 
-          <li><a href="../guides/sites.html">Podling Websites</a></li> 
-          <li><a href="../guides/graduation.html">Graduation</a></li> 
-          <li><a href="../guides/retirement.html">Retirement</a></li> 
-            </menu>
-      <div class="menuheader">Other Guides</div>
-    <menu compact="compact">
-          <li><a href="../guides/participation.html">Participation</a></li> 
-          <li><a href="../faq.html">General FAQ</a></li> 
-          <li><a href="../guides/pmc.html">Incubator PMC (IPMC)</a></li> 
-          <li><a href="../guides/chair.html">IPMC Chair</a></li> 
-          <li><a href="../guides/lists.html">Mailing Lists</a></li> 
-          <li><a href="../guides/website.html">Incubator Website</a></li> 
-            </menu>
-      <div class="menuheader">ASF</div>
-    <menu compact="compact">
-          <li><a href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li> 
-          <li><a href="http://www.apache.org/dev/">Developer Documentation</a></li> 
-          <li><a href="http://www.apache.org/foundation/">Foundation</a></li> 
-          <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li> 
-          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li> 
-            </menu>
-    <!-- start Ads Server -->
-    <iframe src="http://www.apache.org/ads/buttonbar.html"
-     style="border-width:0; float: left" frameborder="0" scrolling="no"
-     width="135" height="265"></iframe>
-    <!-- end Ads Server -->
-   </div>
-   
-   <div class="span12">
-            <h2 id='preamble'><img src="../images/redarrow.gif" />Enter The Incubator (DRAFT)</h2>
-<div class="section-content">
-<h3 id='status'>Status - DRAFT</h3>
-<div class="section-content">
-<p>
-This document is under <a href="#help-wanted">development</a>. At the moment, this 
-is just a skeleton outline. 
-          </p>
-</div>
-<h3 id='abstract'>Abstract</h3>
-<div class="section-content">
-<p>
-This document is descriptive not normative. It discusses and describes
-the process of incubator entry and offers some views about how to approach it.
-It is not an inflexible standard but
-represents a consensus condensed from previous discussions on the
-incubator general list.
-          </p>
-</div>
-<h3 id='background'>Background</h3>
-<div class="section-content">
-<p>
-           </p>
-</div>
-<h3 id='help-wanted'>Help Wanted!</h3>
-<div class="section-content">
-<p>
-Help to improve the system by posting a patch for this document to the
-incubator section of JIRA or a comment to the general list at incubator.
-          </p>
-</div>
-</div>
-        <h2 id='understanding'><img src="../images/redarrow.gif" />Understanding The Acceptance Process</h2>
-<div class="section-content">
-<p>
-The acceptance process is simple in theory but complex in practice.
-        </p>
-<p>
-The theory is that candidates are accepted or rejected by a vote on a mailing lists. 
-Anyone can vote (and are <a href="participation.html#general-list">encouraged</a> to do so)
-but only eligable votes are binding on Apache. For candidates 
-<a href="../incubation/Roles_and_Responsibilities.html#Sponsor">Sponsored</a> 
-by the <code>Incubator</code> this means members of the 
-<a href="../incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator PMC</a>.
-        </p>
-<p>
-In practice, the process is more complex for candidates who want to give themselves 
-the best chance of being accepted. 
-        </p>
-<p>
-Apache policy is set by the Board either directly or through it's special committees. 
-The incubation PMC is responsible to the board and so it is the duty of each PMC member
-to vote against a proposal that does not adhere to this policy.
-        </p>
-<p>
-<a href="../incubation/Incubation_Policy.html">Incubation Policy</a> state clearly when a . 
-All policy is decided by PMC vote and so represents an active consensus. Though PMC members
-are free to vote in whatever way they choose, it is reasonable to expect PMC members
-to vote against a proposal that does not satisfy policy. 
-        </p>
-<p>
-However, satisfying current policy is not sufficient. Acceptance is a democractic process
-requiring positive approval by the electorate. The guides and other documentation are not
-policy. They are approved only through lazy consensus. 
-        </p>
-<p>
-See:
-        </p>
-<ul><li>[links to posts and threads]</li></ul>
-</div>
-        <h2 id='note'><img src="../images/redarrow.gif" />Notes On The Process</h2>
-<div class="section-content">
-<h3 id='proposal'>The Proposal</h3>
-<div class="section-content">
-<p>
-        </p>
-</div>
-<h3 id='vote'>The Vote</h3>
-<div class="section-content">
-<p>
-When the proposal seems finished and some sort of consensus has emerged, the
-proposal can be put to the vote. 
-        </p>
-<p>
-The right time is a matter for judgement. Ask the 
-<a href="../incubator/Roles_and_Responsibilites.html#Champion">Champion</a> for advice
-or ask on the mailing list. It is usually best to ensure that the discussions 
-and debates surrounding the proposal are complete before moving to a vote. This may 
-mean move discussions which are not about the proposal to separate threads.
-        </p>
-<p>
-The right duration for the vote is also a matter for judgement [link]. 
-        </p>
-</div>
-</div>
-       </div>
-   </div>
-  
-   <div class="row"><div class="span16"><hr noshade="noshade" size="1"/></div></div>
-  <div class="row">
-   <div class="span16 footer">
-     Copyright &#169; 2009-2016 The Apache Software Foundation<br />
-     Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br/>
-     Apache Incubator, Apache, the Apache feather logo, and the Apache Incubator project logo are trademarks of The Apache Software Foundation.
-     
-     
-    </div>
-  </div>
- </div> 
- </body>
-</html>

http://git-wip-us.apache.org/repos/asf/incubator/blob/170c4191/bob/guides/examples/JDBM.LICENSE
----------------------------------------------------------------------
diff --git a/bob/guides/examples/JDBM.LICENSE b/bob/guides/examples/JDBM.LICENSE
deleted file mode 100644
index de91e09..0000000
--- a/bob/guides/examples/JDBM.LICENSE
+++ /dev/null
@@ -1,48 +0,0 @@
-=========================================================================
-/**
- * JDBM LICENSE v1.00
- *
- * Redistribution and use of this software and associated documentation
- * ("Software"), with or without modification, are permitted provided
- * that the following conditions are met:
- *
- * 1. Redistributions of source code must retain copyright
- *    statements and notices.  Redistributions must also contain a
- *    copy of this document.
- *
- * 2. Redistributions in binary form must reproduce the
- *    above copyright notice, this list of conditions and the
- *    following disclaimer in the documentation and/or other
- *    materials provided with the distribution.
- *
- * 3. The name "JDBM" must not be used to endorse or promote
- *    products derived from this Software without prior written
- *    permission of Cees de Groot.  For written permission,
- *    please contact cg@cdegroot.com.
- *
- * 4. Products derived from this Software may not be called "JDBM"
- *    nor may "JDBM" appear in their names without prior written
- *    permission of Cees de Groot. 
- *
- * 5. Due credit should be given to the JDBM Project
- *    (http://jdbm.sourceforge.net/).
- *
- * THIS SOFTWARE IS PROVIDED BY THE JDBM PROJECT AND CONTRIBUTORS
- * ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
- * NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
- * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL
- * CEES DE GROOT OR ANY CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
- * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
- * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
- * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
- * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
- * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
- * OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- * Copyright 2000 (C) Cees de Groot. All Rights Reserved.
- * Contributions are Copyright (C) 2000 by their associated contributors.
- *
- * $Id: LICENSE.txt,v 1.1 2000/05/05 23:59:52 boisvert Exp $
- */
-=========================================================================
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/170c4191/bob/guides/examples/LICENSE
----------------------------------------------------------------------
diff --git a/bob/guides/examples/LICENSE b/bob/guides/examples/LICENSE
deleted file mode 100644
index e7196a8..0000000
--- a/bob/guides/examples/LICENSE
+++ /dev/null
@@ -1,673 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. 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.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   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 HTTP SERVER SUBCOMPONENTS: 
-
-The Apache HTTP Server includes a number of subcomponents with
-separate copyright notices and license terms. Your use of the source
-code for the these subcomponents is subject to the terms and
-conditions of the following licenses. 
-
-For the mod_mime_magic component:
-
-/*
- * mod_mime_magic: MIME type lookup via file magic numbers
- * Copyright (c) 1996-1997 Cisco Systems, Inc.
- *
- * This software was submitted by Cisco Systems to the Apache Group in July
- * 1997.  Future revisions and derivatives of this source code must
- * acknowledge Cisco Systems as the original contributor of this module.
- * All other licensing and usage conditions are those of the Apache Group.
- *
- * Some of this code is derived from the free version of the file command
- * originally posted to comp.sources.unix.  Copyright info for that program
- * is included below as required.
- * ---------------------------------------------------------------------------
- * - Copyright (c) Ian F. Darwin, 1987. Written by Ian F. Darwin.
- *
- * This software is not subject to any license of the American Telephone and
- * Telegraph Company or of the Regents of the University of California.
- *
- * Permission is granted to anyone to use this software for any purpose on any
- * computer system, and to alter it and redistribute it freely, subject to
- * the following restrictions:
- *
- * 1. The author is not responsible for the consequences of use of this
- * software, no matter how awful, even if they arise from flaws in it.
- *
- * 2. The origin of this software must not be misrepresented, either by
- * explicit claim or by omission.  Since few users ever read sources, credits
- * must appear in the documentation.
- *
- * 3. Altered versions must be plainly marked as such, and must not be
- * misrepresented as being the original software.  Since few users ever read
- * sources, credits must appear in the documentation.
- *
- * 4. This notice may not be removed or altered.
- * -------------------------------------------------------------------------
- *
- */
-
-
-For the  modules\mappers\mod_imagemap.c component:
-
-  "macmartinized" polygon code copyright 1992 by Eric Haines, erich@eye.com
-
-For the  server\util_md5.c component:
-
-/************************************************************************
- * NCSA HTTPd Server
- * Software Development Group
- * National Center for Supercomputing Applications
- * University of Illinois at Urbana-Champaign
- * 605 E. Springfield, Champaign, IL 61820
- * httpd@ncsa.uiuc.edu
- *
- * Copyright  (C)  1995, Board of Trustees of the University of Illinois
- *
- ************************************************************************
- *
- * md5.c: NCSA HTTPd code which uses the md5c.c RSA Code
- *
- *  Original Code Copyright (C) 1994, Jeff Hostetler, Spyglass, Inc.
- *  Portions of Content-MD5 code Copyright (C) 1993, 1994 by Carnegie Mellon
- *     University (see Copyright below).
- *  Portions of Content-MD5 code Copyright (C) 1991 Bell Communications 
- *     Research, Inc. (Bellcore) (see Copyright below).
- *  Portions extracted from mpack, John G. Myers - jgm+@cmu.edu
- *  Content-MD5 Code contributed by Martin Hamilton (martin@net.lut.ac.uk)
- *
- */
-
-
-/* these portions extracted from mpack, John G. Myers - jgm+@cmu.edu */
-/* (C) Copyright 1993,1994 by Carnegie Mellon University
- * All Rights Reserved.
- *
- * Permission to use, copy, modify, distribute, and sell this software
- * and its documentation for any purpose is hereby granted without
- * fee, provided that the above copyright notice appear in all copies
- * and that both that copyright notice and this permission notice
- * appear in supporting documentation, and that the name of Carnegie
- * Mellon University not be used in advertising or publicity
- * pertaining to distribution of the software without specific,
- * written prior permission.  Carnegie Mellon University makes no
- * representations about the suitability of this software for any
- * purpose.  It is provided "as is" without express or implied
- * warranty.
- *
- * CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO
- * THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
- * AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE
- * FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
- * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
- * AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
- * OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
- * SOFTWARE.
- */
-
-/*
- * Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)
- *
- * Permission to use, copy, modify, and distribute this material
- * for any purpose and without fee is hereby granted, provided
- * that the above copyright notice and this permission notice
- * appear in all copies, and that the name of Bellcore not be
- * used in advertising or publicity pertaining to this
- * material without the specific, prior written permission
- * of an authorized representative of Bellcore.  BELLCORE
- * MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
- * OF THIS MATERIAL FOR ANY PURPOSE.  IT IS PROVIDED "AS IS",
- * WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.  
- */
-
-For the  srclib\apr\include\apr_md5.h component: 
-/*
- * This is work is derived from material Copyright RSA Data Security, Inc.
- *
- * The RSA copyright statement and Licence for that original material is
- * included below. This is followed by the Apache copyright statement and
- * licence for the modifications made to that material.
- */
-
-/* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
-   rights reserved.
-
-   License to copy and use this software is granted provided that it
-   is identified as the "RSA Data Security, Inc. MD5 Message-Digest
-   Algorithm" in all material mentioning or referencing this software
-   or this function.
-
-   License is also granted to make and use derivative works provided
-   that such works are identified as "derived from the RSA Data
-   Security, Inc. MD5 Message-Digest Algorithm" in all material
-   mentioning or referencing the derived work.
-
-   RSA Data Security, Inc. makes no representations concerning either
-   the merchantability of this software or the suitability of this
-   software for any particular purpose. It is provided "as is"
-   without express or implied warranty of any kind.
-
-   These notices must be retained in any copies of any part of this
-   documentation and/or software.
- */
-
-For the  srclib\apr\passwd\apr_md5.c component:
-
-/*
- * This is work is derived from material Copyright RSA Data Security, Inc.
- *
- * The RSA copyright statement and Licence for that original material is
- * included below. This is followed by the Apache copyright statement and
- * licence for the modifications made to that material.
- */
-
-/* MD5C.C - RSA Data Security, Inc., MD5 message-digest algorithm
- */
-
-/* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
-   rights reserved.
-
-   License to copy and use this software is granted provided that it
-   is identified as the "RSA Data Security, Inc. MD5 Message-Digest
-   Algorithm" in all material mentioning or referencing this software
-   or this function.
-
-   License is also granted to make and use derivative works provided
-   that such works are identified as "derived from the RSA Data
-   Security, Inc. MD5 Message-Digest Algorithm" in all material
-   mentioning or referencing the derived work.
-
-   RSA Data Security, Inc. makes no representations concerning either
-   the merchantability of this software or the suitability of this
-   software for any particular purpose. It is provided "as is"
-   without express or implied warranty of any kind.
-
-   These notices must be retained in any copies of any part of this
-   documentation and/or software.
- */
-/*
- * The apr_md5_encode() routine uses much code obtained from the FreeBSD 3.0
- * MD5 crypt() function, which is licenced as follows:
- * ----------------------------------------------------------------------------
- * "THE BEER-WARE LICENSE" (Revision 42):
- * <phk@login.dknet.dk> wrote this file.  As long as you retain this notice you
- * can do whatever you want with this stuff. If we meet some day, and you think
- * this stuff is worth it, you can buy me a beer in return.  Poul-Henning Kamp
- * ----------------------------------------------------------------------------
- */
-
-For the srclib\apr-util\crypto\apr_md4.c component:
-
- * This is derived from material copyright RSA Data Security, Inc.
- * Their notice is reproduced below in its entirety.
- *
- * Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
- * rights reserved.
- *
- * License to copy and use this software is granted provided that it
- * is identified as the "RSA Data Security, Inc. MD4 Message-Digest
- * Algorithm" in all material mentioning or referencing this software
- * or this function.
- *
- * License is also granted to make and use derivative works provided
- * that such works are identified as "derived from the RSA Data
- * Security, Inc. MD4 Message-Digest Algorithm" in all material
- * mentioning or referencing the derived work.
- *
- * RSA Data Security, Inc. makes no representations concerning either
- * the merchantability of this software or the suitability of this
- * software for any particular purpose. It is provided "as is"
- * without express or implied warranty of any kind.
- *
- * These notices must be retained in any copies of any part of this
- * documentation and/or software.
- */
-
-For the srclib\apr-util\include\apr_md4.h component:
-
- *
- * This is derived from material copyright RSA Data Security, Inc.
- * Their notice is reproduced below in its entirety.
- *
- * Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
- * rights reserved.
- *
- * License to copy and use this software is granted provided that it
- * is identified as the "RSA Data Security, Inc. MD4 Message-Digest
- * Algorithm" in all material mentioning or referencing this software
- * or this function.
- *
- * License is also granted to make and use derivative works provided
- * that such works are identified as "derived from the RSA Data
- * Security, Inc. MD4 Message-Digest Algorithm" in all material
- * mentioning or referencing the derived work.
- *
- * RSA Data Security, Inc. makes no representations concerning either
- * the merchantability of this software or the suitability of this
- * software for any particular purpose. It is provided "as is"
- * without express or implied warranty of any kind.
- *
- * These notices must be retained in any copies of any part of this
- * documentation and/or software.
- */
-
-
-For the srclib\apr-util\test\testdbm.c component:
-
-/* ====================================================================
- * The Apache Software License, Version 1.1
- *
- * Copyright (c) 2000-2002 The Apache Software Foundation.  All rights
- * reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * 1. Redistributions of source code must retain the above copyright
- *    notice, this list of conditions and the following disclaimer.
- *
- * 2. Redistributions in binary form must reproduce the above copyright
- *    notice, this list of conditions and the following disclaimer in
- *    the documentation and/or other materials provided with the
- *    distribution.
- *
- * 3. The end-user documentation included with the redistribution,
- *    if any, must include the following acknowledgment:
- *       "This product includes software developed by the
- *        Apache Software Foundation (http://www.apache.org/)."
- *    Alternately, this acknowledgment may appear in the software itself,
- *    if and wherever such third-party acknowledgments normally appear.
- *
- * 4. The names "Apache" and "Apache Software Foundation" must
- *    not be used to endorse or promote products derived from this
- *    software without prior written permission. For written
- *    permission, please contact apache@apache.org.
- *
- * 5. Products derived from this software may not be called "Apache",
- *    nor may "Apache" appear in their name, without prior written
- *    permission of the Apache Software Foundation.
- *
- * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
- * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
- * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
- * DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
- * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
- * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
- * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
- * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
- * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
- * SUCH DAMAGE.
- * ====================================================================
- *
- * This software consists of voluntary contributions made by many
- * individuals on behalf of the Apache Software Foundation.  For more
- * information on the Apache Software Foundation, please see
- * <http://www.apache.org/>.
- *
- * This file came from the SDBM package (written by oz@nexus.yorku.ca).
- * That package was under public domain. This file has been ported to
- * APR, updated to ANSI C and other, newer idioms, and added to the Apache
- * codebase under the above copyright and license.
- */
-
-
-For the srclib\apr-util\test\testmd4.c component:
-
- *
- * This is derived from material copyright RSA Data Security, Inc.
- * Their notice is reproduced below in its entirety.
- *
- * Copyright (C) 1990-2, RSA Data Security, Inc. Created 1990. All
- * rights reserved.
- *
- * RSA Data Security, Inc. makes no representations concerning either
- * the merchantability of this software or the suitability of this
- * software for any particular purpose. It is provided "as is"
- * without express or implied warranty of any kind.
- *
- * These notices must be retained in any copies of any part of this
- * documentation and/or software.
- */
-
-For the srclib\apr-util\xml\expat\conftools\install-sh component:
-
-#
-# install - install a program, script, or datafile
-# This comes from X11R5 (mit/util/scripts/install.sh).
-#
-# Copyright 1991 by the Massachusetts Institute of Technology
-#
-# Permission to use, copy, modify, distribute, and sell this software and its
-# documentation for any purpose is hereby granted without fee, provided that
-# the above copyright notice appear in all copies and that both that
-# copyright notice and this permission notice appear in supporting
-# documentation, and that the name of M.I.T. not be used in advertising or
-# publicity pertaining to distribution of the software without specific,
-# written prior permission.  M.I.T. makes no representations about the
-# suitability of this software for any purpose.  It is provided "as is"
-# without express or implied warranty.
-#
-
-For the srclib\pcre\install-sh component:
-
-#
-# Copyright 1991 by the Massachusetts Institute of Technology
-#
-# Permission to use, copy, modify, distribute, and sell this software and its
-# documentation for any purpose is hereby granted without fee, provided that
-# the above copyright notice appear in all copies and that both that
-# copyright notice and this permission notice appear in supporting
-# documentation, and that the name of M.I.T. not be used in advertising or
-# publicity pertaining to distribution of the software without specific,
-# written prior permission.  M.I.T. makes no representations about the
-# suitability of this software for any purpose.  It is provided "as is"
-# without express or implied warranty.
-
-For the pcre component:
-
-PCRE LICENCE
-------------
-
-PCRE is a library of functions to support regular expressions whose syntax
-and semantics are as close as possible to those of the Perl 5 language.
-
-Release 5 of PCRE is distributed under the terms of the "BSD" licence, as
-specified below. The documentation for PCRE, supplied in the "doc"
-directory, is distributed under the same terms as the software itself.
-
-Written by: Philip Hazel <ph10@cam.ac.uk>
-
-University of Cambridge Computing Service,
-Cambridge, England. Phone: +44 1223 334714.
-
-Copyright (c) 1997-2004 University of Cambridge
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-    * Redistributions of source code must retain the above copyright notice,
-      this list of conditions and the following disclaimer.
-
-    * Redistributions in binary form must reproduce the above copyright
-      notice, this list of conditions and the following disclaimer in the
-      documentation and/or other materials provided with the distribution.
-
-    * Neither the name of the University of Cambridge nor the names of its
-      contributors may be used to endorse or promote products derived from
-      this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
-LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-End PCRE LICENCE
-
-
-For the test\zb.c component:
-
-/*                          ZeusBench V1.01
-			    ===============
-
-This program is Copyright (C) Zeus Technology Limited 1996.
-
-This program may be used and copied freely providing this copyright notice
-is not removed.
-
-This software is provided "as is" and any express or implied waranties, 
-including but not limited to, the implied warranties of merchantability and
-fitness for a particular purpose are disclaimed.  In no event shall 
-Zeus Technology Ltd. be liable for any direct, indirect, incidental, special, 
-exemplary, or consequential damaged (including, but not limited to, 
-procurement of substitute good or services; loss of use, data, or profits;
-or business interruption) however caused and on theory of liability.  Whether
-in contract, strict liability or tort (including negligence or otherwise) 
-arising in any way out of the use of this software, even if advised of the
-possibility of such damage.
-
-     Written by Adam Twiss (adam@zeus.co.uk).  March 1996
-
-Thanks to the following people for their input:
-  Mike Belshe (mbelshe@netscape.com) 
-  Michael Campanella (campanella@stevms.enet.dec.com)
-
-*/
-
-For the expat xml parser component:
-
-Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd
-                               and Clark Cooper
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-	
-The above copyright notice and this permission notice shall be included
-in all copies or substantial portions of the Software.
-	
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-====================================================================

http://git-wip-us.apache.org/repos/asf/incubator/blob/170c4191/bob/guides/graduation-timeline.png
----------------------------------------------------------------------
diff --git a/bob/guides/graduation-timeline.png b/bob/guides/graduation-timeline.png
deleted file mode 100644
index 9ba02d5..0000000
Binary files a/bob/guides/graduation-timeline.png and /dev/null differ


---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message