incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r368953 - in /incubator/public/trunk/site-publish: howtoparticipate.html howtoparticipate.pdf incubation/Incubation_Policy.html incubation/Incubation_Policy.pdf incubation/Process_Description.html incubation/Process_Description.pdf
Date Sat, 14 Jan 2006 02:00:06 GMT
Author: crossley
Date: Fri Jan 13 17:59:58 2006
New Revision: 368953

URL: http://svn.apache.org/viewcvs?rev=368953&view=rev
Log:
Publish recent changes.

Modified:
    incubator/public/trunk/site-publish/howtoparticipate.html
    incubator/public/trunk/site-publish/howtoparticipate.pdf
    incubator/public/trunk/site-publish/incubation/Incubation_Policy.html
    incubator/public/trunk/site-publish/incubation/Incubation_Policy.pdf
    incubator/public/trunk/site-publish/incubation/Process_Description.html
    incubator/public/trunk/site-publish/incubation/Process_Description.pdf

Modified: incubator/public/trunk/site-publish/howtoparticipate.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/howtoparticipate.html?rev=368953&r1=368952&r2=368953&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/howtoparticipate.html (original)
+++ incubator/public/trunk/site-publish/howtoparticipate.html Fri Jan 13 17:59:58 2006
@@ -256,57 +256,58 @@
 <h2 class="underlined_10">Check this first</h2>
 <div class="section">
 <p>Before doing anything, we encourage you to read the incubator website and in particular
our "About" documents.</p>
-<p>If you have other questions, feel free to post them on general@incubator.apache.org</p>
-<p>If you want to help in the development of a specific <a href="projects/">Incubated
Project</a> refer to its development mailing list. The Incubator mailing lists are for
project incubation, not for project development.</p>
+<p>If you have other questions about any aspect of the incubation process, feel free
to post them on general@incubator.apache.org</p>
+<p>To find a Sponsor project and Mentors, then investigate existing Apache project
mailing lists as described in the <a href="incubation/Process_Description.html#Establishment">Establishment</a>
section. Follow links at each of the <a href="http://www.apache.org/foundation/projects.html">Apache
projects</a>.</p>
+<p>If you want to assist with the development of a specific <a href="projects/">Incubating
Project</a> refer to its development mailing list. The Incubator mailing lists are for
project incubation, not for project development.</p>
 <p>In case of generic Project development questions, there is projects@incubator.apache.org</p>
 </div>
-<a name="N10020"></a><a name="Incubator+Project+resources"></a>
+<a name="N1002A"></a><a name="Incubator+Project+resources"></a>
 <h2 class="underlined_10">Incubator Project resources</h2>
 <div class="section">
 <div class="fixme">fixme: Check that all Incubator project resources are listed.</div>
-<a name="N10027"></a><a name="Mailing+lists"></a>
+<a name="N10031"></a><a name="Mailing+lists"></a>
 <h3 class="underlined_5">Mailing lists</h3>
-<p>As with everything else in Apache, most of what goes on happens or is discussed
on electronic mailing lists. Here are the lists associated with this project, and their purposes.</p>
-<a name="N1002D"></a><a name="general%40incubator.apache.org"></a>
+<p>As with everything else in Apache, most of what goes on happens or is discussed
on electronic mailing lists. Here are the lists associated with the Incubator, and their purposes.</p>
+<a name="N10037"></a><a name="general%40incubator.apache.org"></a>
 <h4>general@incubator.apache.org</h4>
-<p>This is where general and public discussion of things about the project take place.
It's also where follow-up messages sent in reply to cvs commit reports get sent (see the next
list). There is a 'digest' form of this list, which collects individual messages and sends
the collection when enough have accumulated or a given amount of time has passed since the
last digest. Anyone may subscribe; only subscribers may post.</p>
+<p>This is where general and public discussion of things about the Incubator take place.
It's also where follow-up messages sent in reply to cvs commit reports get sent (see the next
list). There is a 'digest' form of this list, which collects individual messages and sends
the collection when enough have accumulated or a given amount of time has passed since the
last digest. Anyone may subscribe; only subscribers may post.</p>
 <ul>
 <li>To subscribe, send a message to general-subscribe@incubator.apache.org</li>
 <li>To subscribe to the digest, send a message to general-digest-subscribe@incubator.apache.org</li>
 <li>To unsubscribe, send a message to general-unsubscribe@incubator.apache.org</li>
 </ul>
-<a name="N1003A"></a><a name="projects%40incubator.apache.org"></a>
+<a name="N10044"></a><a name="projects%40incubator.apache.org"></a>
 <h4>projects@incubator.apache.org</h4>
 <p>This is the development mailing list for some of the projects in incubation. Anyone
may subscribe; only subscribers may post.</p>
 <ul>
 <li>To subscribe, send a message to projects-subscribe@incubator.apache.org</li>
 <li>To unsubscribe, send a message to projects-unsubscribe@incubator.apache.org</li>
 </ul>
-<a name="N10045"></a><a name="cvs%40incubator.apache.org"></a>
+<a name="N1004F"></a><a name="cvs%40incubator.apache.org"></a>
 <h4>cvs@incubator.apache.org</h4>
 <p>When changes are made to the code repository, the details are automatically sent
to this list. Its Reply-To is set to the 'general' list, so if you reply to a cvs message
that's where your reply is going to end up. Anyone may subscribe; only subscribers may post.</p>
 <ul>
 <li>To subscribe, send a message to cvs-subscribe@incubator.apache.org</li>
 <li>To unsubscribe, send a message to cvs-unsubscribe@incubator.apache.org</li>
 </ul>
-<a name="N10050"></a><a name="announce%40incubator.apache.org"></a>
+<a name="N1005A"></a><a name="announce%40incubator.apache.org"></a>
 <h4>announce@incubator.apache.org</h4>
 <p>This is the list to which you should be subscribed if you want to be kept apprised
of significant events or milestones in the project's activities, but don't want to track the
full traffic in the 'general' list. Anyone may subscribe; all posts are moderated.</p>
 <ul>
 <li>To subscribe, send a message to announce-subscribe@incubator.apache.org</li>
 <li>To unsubscribe, send a message to announce-unsubscribe@incubator.apache.org</li>
 </ul>
-<a name="N1005B"></a><a name="pmc%40incubator.apache.org"></a>
+<a name="N10065"></a><a name="pmc%40incubator.apache.org"></a>
 <h4>pmc@incubator.apache.org</h4>
 <ul>
 <li>This is a private list for the project management committee. It is not open to
general subscription.</li>
 </ul>
 </div>
-<a name="N10062"></a><a name="Project-specific+resources"></a>
+<a name="N1006C"></a><a name="Project-specific+resources"></a>
 <h2 class="underlined_10">Project-specific resources</h2>
 <div class="section">
 <p>Some <a href="projects/">projects</a> under incubation have their own
mailing lists, or their development discussion occurs on the mailing list of another project.
Check out the project websites to be sure what mailing list is the right one.</p>
-<a name="N1006C"></a><a name="Project+Website+Howto"></a>
+<a name="N10076"></a><a name="Project+Website+Howto"></a>
 <h3 class="underlined_5">Project Website Howto</h3>
 <p>Each project can use whatever documentation system that it chooses. Perhaps use
a fancy documentation management system like Forrest or Maven, or just use simple raw html
pages.</p>
 <p>Keep your source documents in your project Version Control System under http://svn.apache.org/repos/asf/incubator/${project}/trunk/</p>
@@ -319,7 +320,7 @@
 <p>Make sure that your subversion client is properly <a href="http://www.apache.org/dev/version-control.html#https-svn">configured</a>.
This vastly reduces the amount of traffic on the svn email commits, e.g. *.pdf</p>
 <p>See other notes for maintenance of <a href="http://www.apache.org/dev/project-site.html">project
websites</a>.</p>
 </div>
-<a name="N10087"></a><a name="www"></a>
+<a name="N10091"></a><a name="www"></a>
 <h2 class="underlined_10">Updating the top-level website</h2>
 <div class="section">
 <p>How to maintain the top-level Incubator website (including the project status reports).
See the <a href="guides/website.html">website guide</a>.</p>

Modified: incubator/public/trunk/site-publish/howtoparticipate.pdf
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/howtoparticipate.pdf?rev=368953&r1=368952&r2=368953&view=diff
==============================================================================
Binary files - no diff available.

Modified: incubator/public/trunk/site-publish/incubation/Incubation_Policy.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/incubation/Incubation_Policy.html?rev=368953&r1=368952&r2=368953&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/incubation/Incubation_Policy.html (original)
+++ incubator/public/trunk/site-publish/incubation/Incubation_Policy.html Fri Jan 13 17:59:58
2006
@@ -290,7 +290,7 @@
 </ul>
 </li>
 <li>
-<a href="#Exitting+the+Incubator">Exitting the Incubator</a>
+<a href="#Exiting+the+Incubator">Exiting the Incubator</a>
 <ul class="minitoc">
 <li>
 <a href="#Minimum+Exit+Requirements">Minimum Exit Requirements</a>
@@ -448,7 +448,7 @@
 <li>that the Podling continue in Incubation; or</li>
 <li>that the Podling be escalated out of the Incubator.</li>
 </ul>
-<p>Termination and Escalation are discussed in more detail in section "Exitting the
Incubator".</p>
+<p>Termination and Escalation are discussed in more detail in section "Exiting the
Incubator".</p>
 <a name="N100D4"></a><a name="Disputing+an+Assessment"></a>
 <h3 class="underlined_5">Disputing an Assessment&#13;</h3>
 <p>If the Podling or Mentor disagree with an assessment, they MAY request the Incubator
PMC review the report. Such a request MUST include a details of what the Podling and/or Mentor
is disputing, and their reasons for doing so.</p>
@@ -528,10 +528,10 @@
 <p>People using Maven, ForrestBot, or any other tool still have to address the SVN
publishing requirement that the infrastructure team has laid out. If that is done, then we
just run "svn update" in that directory to load the site from SVN.</p>
 <p>The Mentors MUST add the information to the project incubation status file, to describe
the SVN module and the directory which holds the published site.</p>
 </div>
-<a name="N10151"></a><a name="Exitting+the+Incubator"></a>
-<h2 class="underlined_10">Exitting the Incubator</h2>
+<a name="N10151"></a><a name="Exiting+the+Incubator"></a>
+<h2 class="underlined_10">Exiting the Incubator</h2>
 <div class="section">
-<p>This section describes the requirements and process for exitting the Incubator.</p>
+<p>This section describes the requirements and process for exiting the Incubator.</p>
 <a name="N10157"></a><a name="Minimum+Exit+Requirements"></a>
 <h3 class="underlined_5">Minimum Exit Requirements</h3>
 <p>Prior to escalation to the ASF, a Podling needs to show that :</p>
@@ -615,10 +615,10 @@
 <p>If you receive a recommendation for termination then you have a problem. Chances
are that there are either legal or structural problems with your project that in the opinion
of the Incubator PMC are not resolvable within a reasonable time frame. A termination decision
is basically time to close down the project. However, you do have the right to appeal a termination
decision with the Board of Directors and/or your Sponsor. You should be aware that several
Members of the Board are also Members of the Incubator PMC and as such, an appeal is unlikely
to be successful.</p>
 <a name="N101C8"></a><a name="Migration+as+a+Top+Level+Project"></a>
 <h3 class="underlined_5">Migration as a Top Level Project</h3>
-<p>In cases where a Podling has successfully completed Incubation, and is exitting
the Incubator to become a Top Level Project, the Incubator PMC SHALL provide a recommendation
to the board that the Podling is ready to escalate. The recommendation SHALL include a draft
resolution for the board to vote on.</p>
+<p>In cases where a Podling has successfully completed Incubation, and is exiting the
Incubator to become a Top Level Project, the Incubator PMC SHALL provide a recommendation
to the board that the Podling is ready to escalate. The recommendation SHALL include a draft
resolution for the board to vote on.</p>
 <a name="N101CE"></a><a name="Migration+as+a+sub-project"></a>
 <h3 class="underlined_5">Migration as a sub-project</h3>
-<p>In cases where a Podling has successfully completed Incubation, and is exitting
the Incubator to become a sub-project within an already existing Top Level Project, the Incubator
PMC SHALL provide a recommendation to the TLP that the Podling is ready to escalate.</p>
+<p>In cases where a Podling has successfully completed Incubation, and is exiting the
Incubator to become a sub-project within an already existing Top Level Project, the Incubator
PMC SHALL provide a recommendation to the TLP that the Podling is ready to escalate.</p>
 <a name="N101D4"></a><a name="Post-Graduation+Check+List"></a>
 <h3 class="underlined_5">Post-Graduation Check List</h3>
 <p>The list below summarizes steps a project needs to perform after graduation to move
out of the Incubator. <strong>PPMC</strong> refers to the old PPMC for the graduating
project, <strong>PMC</strong> refers to the new PMC under which the graduating
project falls (this might be the former PPMC for a new TLP), and <strong>Project</strong>
refers to the committers on the graduating project.</p>

Modified: incubator/public/trunk/site-publish/incubation/Incubation_Policy.pdf
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/incubation/Incubation_Policy.pdf?rev=368953&r1=368952&r2=368953&view=diff
==============================================================================
Binary files - no diff available.

Modified: incubator/public/trunk/site-publish/incubation/Process_Description.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/incubation/Process_Description.html?rev=368953&r1=368952&r2=368953&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/incubation/Process_Description.html (original)
+++ incubator/public/trunk/site-publish/incubation/Process_Description.html Fri Jan 13 17:59:58
2006
@@ -245,18 +245,19 @@
 <p>Readers should also review the <a href="../incubation/Roles_and_Responsibilities.html">Roles
and Responsibilities</a> document for a description of the various parties involved
in the Incubation process.</p>
 <a name="N10020"></a><a name="Establishment"></a>
 <h3 class="underlined_5">Establishment</h3>
-<p>The first thing you will want to do is find a <strong>Champion</strong>
for your project. One way to do this is to explore the Apache site to find similar projects.
Spend some time reading both the projects' web pages and mailing lists. By simply lurking
on the mailing lists (see Mailing Lists section in this document), you may get ideas about
who you would like to ask to help you with your project proposal. However, Champions must
either be ASF <a href="http://www.apache.org/foundation/members.html">members</a>
or <a href="http://www.apache.org/foundation/index.html">officers</a> (see the
Champion section later in this document for more on Champion criteria and responsibilities).
Once you have found an eligible person who is willing to act as Champion, you can use this
person to help you determine if and how your proposal can complement the ASF. If you and your
Champion are convinced that your candidate project would fit with the "Apache Way", your Champion
can help you 
 to get it established.</p>
+<p>The first thing you will want to do is find a <strong>Champion</strong>
for your project. One way to do this is to explore the existing <a href="http://www.apache.org/foundation/projects.html">Apache
projects</a> to find similar projects. Spend some time reading their project web pages
and mailing lists (follow links at each project website). By simply lurking on the project
mailing lists (and also the <a href="../howtoparticipate.html">general@incubator list</a>
and other Incubating project lists) you may get ideas about who you would like to ask to help
you with your project proposal.</p>
+<p>However, Champions must either be ASF <a href="http://www.apache.org/foundation/members.html">members</a>
or <a href="http://www.apache.org/foundation/index.html">officers</a> (see the
Champion section later in this document for more on Champion criteria and responsibilities).
Once you have found an eligible person who is willing to act as Champion, you can use this
person to help you determine if and how your proposal can complement the ASF. If you and your
Champion are convinced that your candidate project would fit with the "Apache Way", your Champion
can help you to get it established.</p>
 <p>The establishment of a candidate involves the preparation of a project description
(consistent with the candidate description detailed below) endorsed by a <strong>Champion</strong>
.</p>
-<p>A <strong>Candidate</strong> project description should be submitted
to the relevant mailing list(s) of a <strong>Sponsor</strong> (see the Mailing
Lists section in this document). See the <a href="http://jakarta.apache.org/site/newproject.html">Jakarta
Guidelines for New Projects</a> for a list of issues that should be addressed in your
proposal; also see <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages">ASF
Proposal Pages</a> for other examples. Typically a <strong>Candidate</strong>
is submitted under a message tagged with [[PROPOSAL]. Such a message will normally trigger
some discussions on the receiving mailing list(s). Your Champion will be involved in these
discussions acting as your advocate.</p>
-<p>As a proposer you should consider the feedback and attempt to gauge a sense of consensus.
Do not be put off by extended threads under your initial post that have little or nothing
to do with your proposal - however, if you feel that your candidate project is not being addressed,
you may want to specifically request a decision on the Candidate by the Sponsor by posting
a request to the decision making list (either pmc@{project-name}.apache.org or board@apache.org;
see Mailing List section for more details). Sometimes a vote will be announced without you
asking for it (perhaps you have done some homework and have a PMC member assisting you though
the process), other times you may need to cut through discussions and push your request forward
for a decision.</p>
-<a name="N1004B"></a><a name="Acceptance"></a>
+<p>A <strong>Candidate</strong> project description should be submitted
to the relevant mailing list(s) of a <strong>Sponsor</strong> (see the <a href="../howtoparticipate.html">Mailing
Lists</a> section). See the <a href="http://jakarta.apache.org/site/newproject.html">Jakarta
Guidelines for New Projects</a> for a list of issues that should be addressed in your
proposal; also see <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages">ASF
Proposal Pages</a> for other examples. Typically a <strong>Candidate</strong>
is submitted under a message tagged with [[PROPOSAL]. Such a message will normally trigger
some discussions on the receiving mailing list(s). Your Champion will be involved in these
discussions acting as your advocate.</p>
+<p>As a proposer you should consider the feedback and attempt to gauge a sense of consensus.
Do not be put off by extended threads under your initial post that have little or nothing
to do with your proposal - however, if you feel that your candidate project is not being addressed,
you may want to specifically request a decision on the Candidate by the Sponsor by posting
a request to the decision making list (usually pmc@{project-name}.apache.org - see <a href="../howtoparticipate.html">Mailing
Lists</a> section for more details). Sometimes a vote will be announced without you
asking for it (perhaps you have done some homework and have a PMC member assisting you though
the process), other times you may need to cut through discussions and push your request forward
for a decision.</p>
+<a name="N1005D"></a><a name="Acceptance"></a>
 <h3 class="underlined_5">Acceptance</h3>
 <p>The decision to accept a project is taken on a vote by the Sponsor. The format of
this vote will depend on the rules of the entity in question. Here again it helps if you have
a PMC Member (or board member if the Sponsor is the ASF board) aligned with your project (preferably
as your Champion) because you stand a better chance of getting feedback about what is actually
happening. The Sponsor will typically take about 7-10 days before announcing a vote result.</p>
 <p>If that vote is affirmative, the Sponsor will propose to the <strong>Incubator
PMC</strong> (referencing the voting result e-mail) that your candidate project be escalated
to <strong>Podling</strong> status. The Sponsor will assign a <strong>Mentor</strong>
. The Mentor may, or may not, be your original Champion. If not, it is expected your Champion
will remain involved during the rest of the Incubation process, providing as much assistance
as possible.</p>
 <p>The Mentor is there to protect you, but be warned - the Mentor is also holding a
big stick. The Mentor is automatically made a member of the Incubator PMC, and reports to
both the PMC and the Sponsor about your overall health and suitability for eventual inclusion
within the Apache Community (or recommendation to terminate). However, the Mentor (with the
assistance of the Champion) is also looking after you through the incubation.</p>
 <p>One of the roles of the Mentor is to keep away the wolves - and in the case of incubation
the wolf is the Incubator PMC, the policies, the process, and inevitable bureaucracy and delays.
The Mentor can help you by guiding and protecting you from much of this based on his/her experience
in the process and familiarity with the policy and procedures of incubation. In performing
their role, the Mentor is representing the Sponsor.</p>
 <p>Your Sponsor, represented by your Mentor, has specific responsibilities towards
you and the Incubator PMC. There are a bunch of administrative and technical actions to take
care of. Your Mentor is responsible for ensuring that these things happen quickly and efficiently.
Also, your Mentor is going to help you out with the getting in place of the policies and procedures
you use for introducing new comitters, decision making, etc. These aspects will be watched
closely by the Incubator PMC as they provide a good indication of community dynamics, health
and correlation with Apache practices.</p>
-<a name="N10062"></a><a name="Review"></a>
+<a name="N10074"></a><a name="Review"></a>
 <h3 class="underlined_5">Review</h3>
 <p>As your project sorts things out and things stabilize (infrastructure, communications,
decision making) you will inevitably come under an assessment by the Incubator PMC concerning
the exit of your project from the incubator. Keep in mind that exit can be a good things and
bad thing. Exit via escalation to a top-level project or perhaps a subproject of an existing
PMC would typically be viewed as a positive exit. On the other-hand, termination is also an
exit condition that may be considered. With an upcoming assessment it is generally a good
idea to have your STATUS file right up to-date and to ensure that your Mentor is doing his/her
job of evangelizing your project and has good picture of where you are relative to acceptance
or the last assessment point. This information will help the Incubator PMC to recommend the
best action for for your project.</p>
 <p>Conclusion of a review process will be a recommendation (to the Sponsor) of one
of the following:</p>
@@ -266,13 +267,13 @@
 <li>exit via escalation into Apache.</li>
 </ul>
 <p>Note that whilst this is a recommendation, it carries a lot of weight. A Sponsor
will only over-ride the recommendation of the Incubator in exceptional circumstances, and
even then it is likely that the issue in question would be escalated to the ASF board for
their consideration.</p>
-<a name="N10073"></a><a name="Termination"></a>
+<a name="N10085"></a><a name="Termination"></a>
 <h3 class="underlined_5">Termination</h3>
 <p>If you receive a recommendation for termination then you have a problem. Chances
are that there are either legal or structural problems with your project that in the opinion
of the Incubator PMC are not resolvable within a reasonable time frame. A termination decision
is basically time to close down the project. However, you do have the right to appeal a termination
decision with the Board of Directors and/or your Sponsor. You should be aware that several
Members of the Board are also Members of the Incubator PMC and as such, an appeal is unlikely
to be successful.</p>
-<a name="N10079"></a><a name="Continuation"></a>
+<a name="N1008B"></a><a name="Continuation"></a>
 <h3 class="underlined_5">Continuation</h3>
 <p>A recommendation by the Incubator PMC for continuation of incubation shall include
development recommendations. The Incubator PMC has a responsibility to ensure that the recommended
actions are tangible and quantifiable. For example, an assessment could be that your project
has not established a sufficient community to be viable, in which case the Incubator PMC is
obliged to state specific targets that they consider as viable. This does not necessarily
mean that if you meet this target by the next review that you are out of incubation - but
it does give you concrete achievements that you can cite. Your Mentor is also specifically
accountable to you for ensuring that the recommendations for continuation are usable, substantive
and tangible. If this is not the case, you have every right to appeal an Incubator decision
to the Apache Board. However, if your Mentor is doing a good job, neither of these scenarios
should arise.</p>
-<a name="N1007F"></a><a name="Escalation"></a>
+<a name="N10091"></a><a name="Escalation"></a>
 <h3 class="underlined_5">Escalation</h3>
 <p>For Podlings that aim to establish sub-projects or products within existing communities
you are almost home-free. The main issues you need to deal with now is migration of your code
into the target project, something you should be confident in doing based on the contacts
and understanding you gained during initial establishment and incubation.</p>
 <p>For projects aiming to be a Top-Level-Project (TLP), you have an additional obstacle,
namely the ASF Board. While the ASF Board might be your Sponsor, this does not mean they have
formally accepted you as a TLP. To establish a TLP you need to draft a board motion that identifies
the project scope, mission and charter. You can submit the motion to the Board using the board@apache.org
email address. Well-prepared projects will have already developed contacts with members of
the Board so this should not be a surprise agenda item. Keep in mind that the Board can approve
your motion as supplied, amend it, or reject it. If you are rejected then you need to sort
this out with the Incubator PMC and allies you have developed during the incubation process.
In other words, for a TLP objective the Incubator PMC okay is only half of the story.</p>

Modified: incubator/public/trunk/site-publish/incubation/Process_Description.pdf
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/incubation/Process_Description.pdf?rev=368953&r1=368952&r2=368953&view=diff
==============================================================================
Binary files - no diff available.



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


Mime
View raw message