You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hc.apache.org by gg...@apache.org on 2017/10/07 21:20:12 UTC
svn commit: r1811447 [1/3] - in /httpcomponents/site: ./
httpcomponents-asyncclient-4.0.x/ httpcomponents-asyncclient-4.1.x/
httpcomponents-client-4.3.x/ httpcomponents-client-4.5.x/
httpcomponents-client-5.0.x/ httpcomponents-core-4.4.x/ httpcomponent...
Author: ggregory
Date: Sat Oct 7 21:20:11 2017
New Revision: 1811447
URL: http://svn.apache.org/viewvc?rev=1811447&view=rev
Log:
Updated project website for HttpCore 4.4.8 GA release
Modified:
httpcomponents/site/bylaws.html
httpcomponents/site/charter.html
httpcomponents/site/commons-httpclient-lessons.html
httpcomponents/site/dev-docs.html
httpcomponents/site/downloads.cgi
httpcomponents/site/downloads.html
httpcomponents/site/get-involved.html
httpcomponents/site/goals.html
httpcomponents/site/httpcomponents-asyncclient-4.0.x/download.html
httpcomponents/site/httpcomponents-asyncclient-4.0.x/examples.html
httpcomponents/site/httpcomponents-asyncclient-4.0.x/index.html
httpcomponents/site/httpcomponents-asyncclient-4.0.x/quickstart.html
httpcomponents/site/httpcomponents-asyncclient-4.1.x/download.html
httpcomponents/site/httpcomponents-asyncclient-4.1.x/examples.html
httpcomponents/site/httpcomponents-asyncclient-4.1.x/index.html
httpcomponents/site/httpcomponents-asyncclient-4.1.x/quickstart.html
httpcomponents/site/httpcomponents-client-4.3.x/android-port.html
httpcomponents/site/httpcomponents-client-4.3.x/download.html
httpcomponents/site/httpcomponents-client-4.3.x/examples.html
httpcomponents/site/httpcomponents-client-4.3.x/index.html
httpcomponents/site/httpcomponents-client-4.3.x/logging.html
httpcomponents/site/httpcomponents-client-4.3.x/ntlm.html
httpcomponents/site/httpcomponents-client-4.3.x/primer.html
httpcomponents/site/httpcomponents-client-4.3.x/quickstart.html
httpcomponents/site/httpcomponents-client-4.5.x/android-port.html
httpcomponents/site/httpcomponents-client-4.5.x/download.html
httpcomponents/site/httpcomponents-client-4.5.x/examples.html
httpcomponents/site/httpcomponents-client-4.5.x/index.html
httpcomponents/site/httpcomponents-client-4.5.x/logging.html
httpcomponents/site/httpcomponents-client-4.5.x/ntlm.html
httpcomponents/site/httpcomponents-client-4.5.x/primer.html
httpcomponents/site/httpcomponents-client-4.5.x/quickstart.html
httpcomponents/site/httpcomponents-client-5.0.x/download.html
httpcomponents/site/httpcomponents-client-5.0.x/examples-async.html
httpcomponents/site/httpcomponents-client-5.0.x/examples.html
httpcomponents/site/httpcomponents-client-5.0.x/index.html
httpcomponents/site/httpcomponents-client-5.0.x/logging.html
httpcomponents/site/httpcomponents-client-5.0.x/quickstart.html
httpcomponents/site/httpcomponents-core-4.4.x/download.html
httpcomponents/site/httpcomponents-core-4.4.x/examples.html
httpcomponents/site/httpcomponents-core-4.4.x/index.html
httpcomponents/site/httpcomponents-core-5.0.x/download.html
httpcomponents/site/httpcomponents-core-5.0.x/examples.html
httpcomponents/site/httpcomponents-core-5.0.x/index.html
httpcomponents/site/index.html
httpcomponents/site/issue-tracking.html
httpcomponents/site/license.html
httpcomponents/site/mail-lists.html
httpcomponents/site/mail.html
httpcomponents/site/news.html
httpcomponents/site/poweredby.html
httpcomponents/site/project-info.html
httpcomponents/site/source-repository.html
httpcomponents/site/status.html
httpcomponents/site/team-list.html
Modified: httpcomponents/site/bylaws.html
URL: http://svn.apache.org/viewvc/httpcomponents/site/bylaws.html?rev=1811447&r1=1811446&r2=1811447&view=diff
==============================================================================
--- httpcomponents/site/bylaws.html (original)
+++ httpcomponents/site/bylaws.html Sat Oct 7 21:20:11 2017
@@ -1,30 +1,18 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Jun 12, 2013 ( $Revision$ ) -->
-<!-- $HeadURL: https://svn.apache.org/repos/asf/httpcomponents/maven-skin/trunk/src/main/resources/META-INF/maven/site.vm $ -->
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Apache HttpComponents - Apache HttpComponents Bylaws</title>
- <style type="text/css" media="all">
+<?xml version="1.0" standalone="yes"?>
+<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></meta><title>Apache HttpComponents - Apache HttpComponents Bylaws</title><style type="text/css" media="all">
@import url("./css/maven-base.css");
@import url("./css/maven-theme.css");
@import url("./css/site.css");
- </style>
- <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20130612" />
- <meta http-equiv="Content-Language" content="en" />
-
- </head>
- <body class="composite">
+ </style><link rel="stylesheet" href="./css/print.css" type="text/css" media="print"></link><meta name="Date-Revision-yyyymmdd" content="20130612"></meta><meta http-equiv="Content-Language" content="en"></meta></head><body class="composite">
<div id="banner">
- <a href="http://www.apache.org/" id="bannerLeft">
- <img src="http://www.apache.org/images/asf_logo_wide.gif" alt="Apache" />
+ <a shape="rect" id="bannerLeft" href="http://www.apache.org/">
+ <img src="http://www.apache.org/images/asf_logo_wide.gif" alt="Apache"></img>
</a>
- <a href="./" id="bannerRight">
- <img src="images/logos/httpcomponents.png" alt="HttpComponents" />
+ <a shape="rect" id="bannerRight" href="./">
+ <img src="images/logos/httpcomponents.png" alt="HttpComponents"></img>
</a>
<div class="clear">
- <hr/>
+ <hr></hr>
</div>
</div>
<div id="breadcrumbs">
@@ -32,16 +20,16 @@
<div class="xleft">
<span id="publishDate">Last Published: 2013-06-12</span>
- | <span id="projectVersion">Version: 7-SNAPSHOT</span>
+  | <span id="projectVersion">Version: 7-SNAPSHOT</span>
</div>
- <div class="xright"> <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>
+ <div class="xright"> <a shape="rect" class="externalLink" href="http://www.apache.org/" title="Apache">Apache</a>
|
- <a href="index.html" title="HttpComponents">HttpComponents</a>
+ <a shape="rect" href="index.html" title="HttpComponents">HttpComponents</a>
</div>
<div class="clear">
- <hr/>
+ <hr></hr>
</div>
</div>
<div id="leftColumn">
@@ -49,112 +37,78 @@
<h5>HttpComponents</h5>
- <ul>
- <li class="none">
- <a href="index.html" title="Home">Home</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/licenses/" class="externalLink" title="License">License</a>
- </li>
- <li class="none">
- <a href="downloads.cgi" title="Download">Download</a>
- </li>
- <li class="none">
- <a href="mail.html" title="Mailing Lists">Mailing Lists</a>
- </li>
- <li class="none">
- <a href="user-docs.html" title="User documents">User documents</a>
- </li>
- <li class="none">
- <a href="dev-docs.html" title="Developer documents">Developer documents</a>
- </li>
- <li class="none">
- <a href="http://wiki.apache.org/HttpComponents/" class="externalLink" title="Wiki (external)">Wiki (external)</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/security/" class="externalLink" title="Security">Security</a>
- </li>
- </ul>
+ <ul><li class="none">
+ <a shape="rect" href="index.html" title="Home">Home</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/licenses/" title="License">License</a>
+ </li><li class="none">
+ <a shape="rect" href="downloads.cgi" title="Download">Download</a>
+ </li><li class="none">
+ <a shape="rect" href="mail.html" title="Mailing Lists">Mailing Lists</a>
+ </li><li class="none">
+ <a shape="rect" href="user-docs.html" title="User documents">User documents</a>
+ </li><li class="none">
+ <a shape="rect" href="dev-docs.html" title="Developer documents">Developer documents</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://wiki.apache.org/HttpComponents/" title="Wiki (external)">Wiki (external)</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/security/" title="Security">Security</a>
+ </li></ul>
<h5>Overview</h5>
- <ul>
- <li class="none">
- <a href="index.html" title="About">About</a>
- </li>
- <li class="none">
- <a href="news.html" title="News">News</a>
- </li>
- <li class="none">
- <a href="poweredby.html" title="Powered by">Powered by</a>
- </li>
- <li class="none">
- <a href="get-involved.html" title="Get Involved">Get Involved</a>
- </li>
- </ul>
+ <ul><li class="none">
+ <a shape="rect" href="index.html" title="About">About</a>
+ </li><li class="none">
+ <a shape="rect" href="news.html" title="News">News</a>
+ </li><li class="none">
+ <a shape="rect" href="poweredby.html" title="Powered by">Powered by</a>
+ </li><li class="none">
+ <a shape="rect" href="get-involved.html" title="Get Involved">Get Involved</a>
+ </li></ul>
<h5>Components</h5>
- <ul>
- <li class="none">
- <a href="httpcomponents-client-ga/index.html" title="HttpClient (GA)">HttpClient (GA)</a>
- </li>
- <li class="none">
- <a href="httpcomponents-client-dev/index.html" title="HttpClient (DEV)">HttpClient (DEV)</a>
- </li>
- <li class="none">
- <a href="httpcomponents-core-ga/index.html" title="HttpCore (GA)">HttpCore (GA)</a>
- </li>
- <li class="none">
- <a href="httpcomponents-core-dev/index.html" title="HttpCore (DEV)">HttpCore (DEV)</a>
- </li>
- <li class="none">
- <a href="httpcomponents-asyncclient-dev/index.html" title="HttpAsyncClient (DEV)">HttpAsyncClient (DEV)</a>
- </li>
- </ul>
+ <ul><li class="none">
+ <a shape="rect" href="httpcomponents-client-ga/index.html" title="HttpClient (GA)">HttpClient (GA)</a>
+ </li><li class="none">
+ <a shape="rect" href="httpcomponents-client-dev/index.html" title="HttpClient (DEV)">HttpClient (DEV)</a>
+ </li><li class="none">
+ <a shape="rect" href="httpcomponents-core-ga/index.html" title="HttpCore (GA)">HttpCore (GA)</a>
+ </li><li class="none">
+ <a shape="rect" href="httpcomponents-core-dev/index.html" title="HttpCore (DEV)">HttpCore (DEV)</a>
+ </li><li class="none">
+ <a shape="rect" href="httpcomponents-asyncclient-dev/index.html" title="HttpAsyncClient (DEV)">HttpAsyncClient (DEV)</a>
+ </li></ul>
<h5>Legacy</h5>
- <ul>
- <li class="none">
- <a href="httpclient-legacy/index.html" title="Commons HttpClient">Commons HttpClient</a>
- </li>
- </ul>
+ <ul><li class="none">
+ <a shape="rect" href="httpclient-legacy/index.html" title="Commons HttpClient">Commons HttpClient</a>
+ </li></ul>
<h5>Project</h5>
- <ul>
- <li class="none">
- <a href="status.html" title="Status">Status</a>
- </li>
- <li class="none">
- <a href="charter.html" title="Charter">Charter</a>
- </li>
- <li class="none">
+ <ul><li class="none">
+ <a shape="rect" href="status.html" title="Status">Status</a>
+ </li><li class="none">
+ <a shape="rect" href="charter.html" title="Charter">Charter</a>
+ </li><li class="none">
<strong>Bylaws</strong>
- </li>
- <li class="none">
- <a href="goals.html" title="Goals">Goals</a>
- </li>
- </ul>
+ </li><li class="none">
+ <a shape="rect" href="goals.html" title="Goals">Goals</a>
+ </li></ul>
<h5>Project Documentation</h5>
- <ul>
- <li class="collapsed">
- <a href="project-info.html" title="Project Information">Project Information</a>
- </li>
- </ul>
+ <ul><li class="collapsed">
+ <a shape="rect" href="project-info.html" title="Project Information">Project Information</a>
+ </li></ul>
<h5>ASF</h5>
- <ul>
- <li class="none">
- <a href="http://www.apache.org" class="externalLink" title="ASF Home Page">ASF Home Page</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/foundation/" class="externalLink" title="Foundation">Foundation</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/foundation/sponsorship.html" class="externalLink" title="Sponsor Apache">Sponsor Apache</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/foundation/thanks.html" class="externalLink" title="Thanks">Thanks</a>
- </li>
- </ul>
- <a href="http://www.apache.org/events/current-event.html" title="ApacheCon" class="poweredBy">
- <img class="poweredBy" alt="ApacheCon" src="http://www.apache.org/events/current-event-125x125.png" />
+ <ul><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org" title="ASF Home Page">ASF Home Page</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/foundation/" title="Foundation">Foundation</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/foundation/sponsorship.html" title="Sponsor Apache">Sponsor Apache</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/foundation/thanks.html" title="Thanks">Thanks</a>
+ </li></ul>
+ <a shape="rect" class="poweredBy" href="http://www.apache.org/events/current-event.html" title="ApacheCon">
+ <img class="poweredBy" alt="ApacheCon" src="http://www.apache.org/events/current-event-125x125.png"></img>
</a>
- <a href="http://maven.apache.org/" title="Maven" class="poweredBy">
- <img class="poweredBy" alt="Maven" src="http://maven.apache.org/images/logos/maven-feather.png" />
+ <a shape="rect" class="poweredBy" href="http://maven.apache.org/" title="Maven">
+ <img class="poweredBy" alt="Maven" src="http://maven.apache.org/images/logos/maven-feather.png"></img>
</a>
@@ -162,27 +116,26 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- ==================================================================== --><!-- 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. --><!-- ==========================
========================================== --><!-- --><!-- 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/>. --><div class="section"><h2>Apache HttpComponents Bylaws (Draft $Revision$)<a name="Apache_HttpComponents_Bylaws_Draft_Revision"></a></h2><p>This page defines the Bylaws for the Apache HttpComponents project. These Bylaws are established by the Apache HttpComponents PMC and apply for operation of this project only. The Apache Software Foundation has its own set of <a class="externalLink" href="http://www.apache.org/foundation/bylaws.html">ASF Bylaws</a>, which define PMCs in section 6.4. Since we are an Apache project, it will be useful for you to understand <a class="externalLink" href="http://www.apache.org/foundation/how-it-works.html">How the ASF Works</a>.</p><p>We have a <a href="./ch
arter.html">Charter</a> that states what we do. These Bylaws explain how we do it.</p></div><div class="section"><h2>Project Management Committee<a name="Project_Management_Committee"></a></h2><p>The Project Management Committee (PMC) was established by the ASF Board in November 2007 and is responsible to the ASF Board for oversight of the HttpComponents project. One PMC member is chosen to serve as the PMC chair. The PMC chair is the primary contact to the Apache Board and responsible for submitting the HttpComponents <a class="externalLink" href="http://wiki.apache.org/HttpComponents/BoardReports">board reports</a>.</p><p>The authoritative list of PMC members is maintained in <a class="externalLink" href="https://svn.apache.org/repos/private/committers/board/committee-info.txt">committee-info.txt</a> and accessible to all Apache committers. The public list of members on our website is informal and may temporarily run out of sync when PMC members fluctuate.</p><p>The PMC can vote i
n new PMC members. Candidates are typically found among the committers of the project and must be nominated by a current PMC member. Candidates are not strictly required to be committers of the project, but only Apache committers can be nominated. A candidate voted in has to accept the role of PMC member in order to join the PMC. If the role is not accepted immediately, the vote result remains effectual for one year after the candidate has been notified. During this time, the candidate can accept the role and join the PMC without a new voting.</p><p>PMC members may retire from the PMC and change to the status of emeritus PMC by request. An emeritus PMC can request to be reinstated as a PMC member. This does not require a vote. PMC members, including the PMC chair, may be removed from the PMC by a majority vote of the PMC. Removed PMC members can subsequently be nominated as candidates and voted in to the PMC like any other Apache committer.</p><p>The PMC chair may retire from the ro
le of PMC chair without retiring from the PMC. When the PMC chair retires from that role, the PMC choses a new chair.</p><p>Changes to the PMC require due <a class="externalLink" href="http://www.apache.org/foundation/records/minutes/2002/board_minutes_2002_12_18.txt">notice</a> to the Apache Board. The PMC chair informs the board of the change via mail. Acknowledgement of the mail by a director starts a 72 hour period, after which the change becomes effective and committee-info.txt is updated. Thus, retirement and reinstatement are subject to 72 hour delays. Changes to the role of PMC chair are typically handled by a resolution that is approved at the next board meeting.</p></div><div class="section"><h2>PMC Decision Making<a name="PMC_Decision_Making"></a></h2><p>Decisions by the Project Management Committee (PMC) are made on behalf of the ASF and must satisfy formal requirements. PMC decisions are established by Binary Voting. Discussions for finding a consensus on the decision a
re expected to take place prior to the voting. The voting is necessary to formally record the decision. Discussions and voting should take place on the public project mailing lists. Where public discussion of a topic is not appropriate, the private mailing list is used instead.</p><p>PMC decisions include, but are not limited to:</p><ul><li>changing the Project Charter and Bylaws</li><li>voting in new PMC members and project committers</li><li>approving release artifacts</li><li>establishing new subprojects</li><li>requesting Apache resources (mailing lists, issue tracking,...)</li><li>...</li></ul><p>Binary Voting allows only for the votes +1 (approval) and -1 (objection). An objection must include the reason, otherwise it is counted as invalid. There are consensus decisions and majority decisions. A consensus decision passes if there is a minimum of three binding +1 votes and no binding -1 vote. A majority decision passes if there is a minimum of three binding +1 votes and at leas
t 75% of the binding votes are +1. For PMC decisions, only the votes of the PMC members are binding. <b>All</b> community members are encouraged to vote on public PMC decisions, to display the community support for or concern about the decision. All votes, binding and non-binding, will be recorded in the result mail.</p><p>All PMC decisions are consensus decisions, with the following exceptions. Removing a PMC member from the PMC is a majority decision. If it is deemed necessary to break a stalemate, the PMC can decide by majority that one specific decision shall be voted on as a majority rather than a consensus decision. Necessity to fall back to either of these majority decision rules would indicate a serious community problem within the PMC.</p><p>A week is deemed a fair length for voting on a PMC decision. For technical decisions such as approving release artifacts, the voting period can be reduced to no less than 72 hours. The length of the voting period for PMC decisions must
be indicated in the mail that starts the voting.</p></div><div class="section"><h2>Community Decision Making<a name="Community_Decision_Making"></a></h2><p>Community decisions are consensus driven. The preferred way to establish consensus is through discussion on the public mailing lists. To gather additional input from community members, polls can be run on the same or other mailing lists. Voting on community decisions should be restricted to cases where it is necessary or desirable to formally record the consensus, for example when a long-term project plan is approved. Discussions and voting must take place on the public project mailing lists.</p><p>Community Voting is non-binary, typical vote values are:</p><ul><li>+1: active support, the voter intends to spend time on the subject</li><li>+0: passive support, the voter will not spend time on the subject</li><li>-0: disfavor, the voter doesn't like the idea but can live with it</li><li>-1: objection, the voter is strongly opposing
the idea (requires a reason or an alternative)</li></ul><p>There are consensus decisions and majority decisions. A consensus decision passes if there is a minimum of three binding +1 votes and no binding -1 vote. A majority decision passes if there is a minimum of three binding +1 votes and more than 50% of the binding votes are +1. For community decisions, only the votes of the project committers are binding. <b>All</b> community members are encouraged to vote on community decisions, to display the community support for or concern about the decision. All votes, binding and non-binding, will be recorded in the result mail. If there is strong opposition from non-binding voters, a decision will be reconsidered even if it formally passes.</p><p>As a rule of thumb, "If" questions are consensus decisions while "How" and "When" questions are majority decisions. For example, it is a consensus decision <i>if</i> a new feature should be implemented. It is a maj
ority decision <i>how</i> an issue in the code should be solved, or <i>when</i> the next release of a deliverable will be cut. If it is not clear and cannot be established by discussion whether a decision should be by consensus or majority, the PMC chooses the kind of decision to make. The preference is for consensus decisions.</p><p>Community Voting is of an informal nature. Depending on the subject of the voting, some of the vote values may be omitted. There may also be multiple options with the same value to choose from, or additional room for comments, or other modifications. For example, a vote on creating a new mailing list may include a field for the preferred mailing list name, or multiple +1 options for the name candidates discussed prior to the vote. The occasional fractional vote, like -0.9 or +10, is rounded towards 0.</p><p>Even if only vote values +1 and -1 are offered, Community Voting differs from PMC Binary Voting in the required vote result for majority decisions (
50% vs. 75%) and in the group of binding voters (committers vs. PMC members). All mails to start a voting must therefore point out which votes will be binding.</p><p>A week is deemed a fair length for voting on community decisions. Depending on the subject and community involvement during the discussion, the voting period may be reduced to no less than 72 hours, extended beyond one week, extended while the vote is running, or left open. Remember that community voting is informal. We prefer common sense over formalities.</p></div><div class="section"><h2>Vetos<a name="Vetos"></a></h2><p>A binding vote of -1 on a consensus decision is also called a veto. Additional discussions and actions to address the reason for the veto are expected. When this is achieved, the veto will be withdrawn or changed to an approval. If concerns cannot be addressed within the voting period, the voting should be repeated after the issues have been resolved.</p><p>A non-binding vote of -1 is not a veto. Howe
ver, it is evaluated based on the merits of the reason given in the vote. If possible, the reason will be addressed within the voting period or afterwards.</p><p>Note that committers and PMC members typically have an in-depth knowledge of the project and long experience in running projects at Apache. They may be aware of facts or requirements that are unknown to the community at large. This is the reason why vetos are given more weight than non-binding -1 votes.</p></div><div class="section"><h2>Release Labels<a name="Release_Labels"></a></h2><p>We use version numbers with two or three digits and labels <i>alpha</i>, <i>beta</i>, <i>RC</i>. The version numbers are used as follows:</p><ul><li>4.0 - a major version. Major versions include significant API changes and enhancements. They should be expected to be incompatible with previous versions.</li><li>4.1 - a minor version. Minor versions include compatible enhancements, but can also include minor API changes. While we try to mainta
in API compatibility for minor versions, there may be cases where we prefer to fix a problem in the API by implementing an incompatible change.</li><li>4.0.1 - a bugfix release. Bugfix releases are compatible with the respective major or minor version.</li></ul><p>Development of major and minor versions typically passes through the following phases:</p><ul><li><i>alpha</i> - API is instable, functionality untested</li><li><i>beta</i> - API is stable, test coverage improving</li><li><i>RC</i> - API is stable, test coverage good</li><li><i>final</i> - no significant bugs uncovered since last RC</li></ul><p>In the alpha phase, functionality is implemented and the API drafted. When the API has stabilized and covers the intended functionality for the next major or minor version, the API is frozen and development moves to the beta phase.</p><p>In the beta phase, the implementation is stabilized by improving the test coverage and refining the API specification. Compatible API changes are s
till expected. If significant problems with the API are uncovered, incompatible changes can be introduced with a deprecation cycle. That means that there is at least one compatible beta release in which parts of the API are marked as deprecated. The deprecated parts of the API can then be removed in a subsequent release.</p><p>The RC (release candidate) phase starts when the developers consider the codebase stable and mature. The API is kept stable, even compatible enhancements will be minimized. Activity during the RC phase is focused on improving the documentation and test coverage. If some major or many minor bugs are detected, these are fixed in a new RC release.</p><p>The final release of a major or minor version is published if bug reports for the RC releases are ebbing away. While the previous releases include the alpha, beta, or RC label in their name, a final release is published with the two digit version number without a suffix. The final release is moved to a branch in t
he source repository for maintenance. Bugs are fixed for that version in compatible bugfix releases off the branch. Issues that require an API change can only be addressed in the next minor or major version, which is developed on the trunk.</p></div><div class="section"><h2>Code Review<a name="Code_Review"></a></h2><p>The two styles for code review at Apache are review-then-commit (RTC) and commit-then-review (CTR). Not only the program code is reviewed, but also the contents of the website and the Wiki. </p><p>With RTC, a patch is published in the issue tracker, then reviewed by the developers, and committed to the source repository only afterwards. Lazy consensus is sufficient, there is no need for formal voting or three opinions in favor.</p><p>With CTR, a change is committed to the source repository directly. Developers receive the change notification on the commits mailing list and review the repository contents. If there is a major problem with the change, any committer can ve
to the change by sending a -1 reply to the commit message. After a veto, the change is reverted as soon as possible in the source repository and the reason for the veto will be discussed. Minor problems are not handled with a veto and revert, but by discussion on the mailing list and followup patches.</p><p>We use both RTC and CTR, and common sense to decide between the two. Some simple rules are:</p><ul><li>changes to Charter and Bylaws are RTC and require formal PMC approval</li><li>updates to the Wiki are CTR</li><li>code contributions by non-committers are RTC</li><li>simple bug fixes are CTR</li><li>documentation improvements are CTR</li><li>updates to the website are CTR</li><li>code changes in an unstable development phase are CTR. Unstable phases are <i>alpha</i> for all changes and <i>beta</i> if the API remains compatible.</li><li>major code changes in a stable development phase are RTC. Stable phases are <i>beta</i> for the API, <i>RC</i> for all the code, and maintenance
in the branch of a final release.</li><li>committers looking for feedback on an idea use RTC</li><li>changes to an experimental branch or sandbox are CTR</li></ul></div>
+ <div class="section"><h2>Apache HttpComponents Bylaws (Draft $Revision$)<a shape="rect" name="Apache_HttpComponents_Bylaws_Draft_Revision"></a></h2><p>This page defines the Bylaws for the Apache HttpComponents project. These Bylaws are established by the Apache HttpComponents PMC and apply for operation of this project only. The Apache Software Foundation has its own set of <a shape="rect" class="externalLink" href="http://www.apache.org/foundation/bylaws.html">ASF Bylaws</a>, which define PMCs in section 6.4. Since we are an Apache project, it will be useful for you to understand <a shape="rect" class="externalLink" href="http://www.apache.org/foundation/how-it-works.html">How the ASF Works</a>.</p><p>We have a <a shape="rect" href="./charter.html">Charter</a> that states what we do. These Bylaws explain how we do it.</p></div><div class="section"><h2>Project Management Committee<a shape="rect" name="Project_Management_Committee"></a></h2><p>The Project Management Committee
(PMC) was established by the ASF Board in November 2007 and is responsible to the ASF Board for oversight of the HttpComponents project. One PMC member is chosen to serve as the PMC chair. The PMC chair is the primary contact to the Apache Board and responsible for submitting the HttpComponents <a shape="rect" class="externalLink" href="http://wiki.apache.org/HttpComponents/BoardReports">board reports</a>.</p><p>The authoritative list of PMC members is maintained in <a shape="rect" class="externalLink" href="https://svn.apache.org/repos/private/committers/board/committee-info.txt">committee-info.txt</a> and accessible to all Apache committers. The public list of members on our website is informal and may temporarily run out of sync when PMC members fluctuate.</p><p>The PMC can vote in new PMC members. Candidates are typically found among the committers of the project and must be nominated by a current PMC member. Candidates are not strictly required to be committers of the project,
but only Apache committers can be nominated. A candidate voted in has to accept the role of PMC member in order to join the PMC. If the role is not accepted immediately, the vote result remains effectual for one year after the candidate has been notified. During this time, the candidate can accept the role and join the PMC without a new voting.</p><p>PMC members may retire from the PMC and change to the status of emeritus PMC by request. An emeritus PMC can request to be reinstated as a PMC member. This does not require a vote. PMC members, including the PMC chair, may be removed from the PMC by a majority vote of the PMC. Removed PMC members can subsequently be nominated as candidates and voted in to the PMC like any other Apache committer.</p><p>The PMC chair may retire from the role of PMC chair without retiring from the PMC. When the PMC chair retires from that role, the PMC choses a new chair.</p><p>Changes to the PMC require due <a shape="rect" class="externalLink" href="http
://www.apache.org/foundation/records/minutes/2002/board_minutes_2002_12_18.txt">notice</a> to the Apache Board. The PMC chair informs the board of the change via mail. Acknowledgement of the mail by a director starts a 72 hour period, after which the change becomes effective and committee-info.txt is updated. Thus, retirement and reinstatement are subject to 72 hour delays. Changes to the role of PMC chair are typically handled by a resolution that is approved at the next board meeting.</p></div><div class="section"><h2>PMC Decision Making<a shape="rect" name="PMC_Decision_Making"></a></h2><p>Decisions by the Project Management Committee (PMC) are made on behalf of the ASF and must satisfy formal requirements. PMC decisions are established by Binary Voting. Discussions for finding a consensus on the decision are expected to take place prior to the voting. The voting is necessary to formally record the decision. Discussions and voting should take place on the public project mailing l
ists. Where public discussion of a topic is not appropriate, the private mailing list is used instead.</p><p>PMC decisions include, but are not limited to:</p><ul><li>changing the Project Charter and Bylaws</li><li>voting in new PMC members and project committers</li><li>approving release artifacts</li><li>establishing new subprojects</li><li>requesting Apache resources (mailing lists, issue tracking,...)</li><li>...</li></ul><p>Binary Voting allows only for the votes +1 (approval) and -1 (objection). An objection must include the reason, otherwise it is counted as invalid. There are consensus decisions and majority decisions. A consensus decision passes if there is a minimum of three binding +1 votes and no binding -1 vote. A majority decision passes if there is a minimum of three binding +1 votes and at least 75% of the binding votes are +1. For PMC decisions, only the votes of the PMC members are binding. <b>All</b> community members are encouraged to vote on public PMC decisions
, to display the community support for or concern about the decision. All votes, binding and non-binding, will be recorded in the result mail.</p><p>All PMC decisions are consensus decisions, with the following exceptions. Removing a PMC member from the PMC is a majority decision. If it is deemed necessary to break a stalemate, the PMC can decide by majority that one specific decision shall be voted on as a majority rather than a consensus decision. Necessity to fall back to either of these majority decision rules would indicate a serious community problem within the PMC.</p><p>A week is deemed a fair length for voting on a PMC decision. For technical decisions such as approving release artifacts, the voting period can be reduced to no less than 72 hours. The length of the voting period for PMC decisions must be indicated in the mail that starts the voting.</p></div><div class="section"><h2>Community Decision Making<a shape="rect" name="Community_Decision_Making"></a></h2><p>Communi
ty decisions are consensus driven. The preferred way to establish consensus is through discussion on the public mailing lists. To gather additional input from community members, polls can be run on the same or other mailing lists. Voting on community decisions should be restricted to cases where it is necessary or desirable to formally record the consensus, for example when a long-term project plan is approved. Discussions and voting must take place on the public project mailing lists.</p><p>Community Voting is non-binary, typical vote values are:</p><ul><li>+1: active support, the voter intends to spend time on the subject</li><li>+0: passive support, the voter will not spend time on the subject</li><li>-0: disfavor, the voter doesn't like the idea but can live with it</li><li>-1: objection, the voter is strongly opposing the idea (requires a reason or an alternative)</li></ul><p>There are consensus decisions and majority decisions. A consensus decision passes if there is a minimum
of three binding +1 votes and no binding -1 vote. A majority decision passes if there is a minimum of three binding +1 votes and more than 50% of the binding votes are +1. For community decisions, only the votes of the project committers are binding. <b>All</b> community members are encouraged to vote on community decisions, to display the community support for or concern about the decision. All votes, binding and non-binding, will be recorded in the result mail. If there is strong opposition from non-binding voters, a decision will be reconsidered even if it formally passes.</p><p>As a rule of thumb, "If" questions are consensus decisions while "How" and "When" questions are majority decisions. For example, it is a consensus decision <i>if</i> a new feature should be implemented. It is a majority decision <i>how</i> an issue in the code should be solved, or <i>when</i> the next release of a deliverable will be cut. If it is not clear and cannot be established by discussion whether
a decision should be by consensus or majority, the PMC chooses the kind of decision to make. The preference is for consensus decisions.</p><p>Community Voting is of an informal nature. Depending on the subject of the voting, some of the vote values may be omitted. There may also be multiple options with the same value to choose from, or additional room for comments, or other modifications. For example, a vote on creating a new mailing list may include a field for the preferred mailing list name, or multiple +1 options for the name candidates discussed prior to the vote. The occasional fractional vote, like -0.9 or +10, is rounded towards 0.</p><p>Even if only vote values +1 and -1 are offered, Community Voting differs from PMC Binary Voting in the required vote result for majority decisions (50% vs. 75%) and in the group of binding voters (committers vs. PMC members). All mails to start a voting must therefore point out which votes will be binding.</p><p>A week is deemed a fair len
gth for voting on community decisions. Depending on the subject and community involvement during the discussion, the voting period may be reduced to no less than 72 hours, extended beyond one week, extended while the vote is running, or left open. Remember that community voting is informal. We prefer common sense over formalities.</p></div><div class="section"><h2>Vetos<a shape="rect" name="Vetos"></a></h2><p>A binding vote of -1 on a consensus decision is also called a veto. Additional discussions and actions to address the reason for the veto are expected. When this is achieved, the veto will be withdrawn or changed to an approval. If concerns cannot be addressed within the voting period, the voting should be repeated after the issues have been resolved.</p><p>A non-binding vote of -1 is not a veto. However, it is evaluated based on the merits of the reason given in the vote. If possible, the reason will be addressed within the voting period or afterwards.</p><p>Note that committe
rs and PMC members typically have an in-depth knowledge of the project and long experience in running projects at Apache. They may be aware of facts or requirements that are unknown to the community at large. This is the reason why vetos are given more weight than non-binding -1 votes.</p></div><div class="section"><h2>Release Labels<a shape="rect" name="Release_Labels"></a></h2><p>We use version numbers with two or three digits and labels <i>alpha</i>, <i>beta</i>, <i>RC</i>. The version numbers are used as follows:</p><ul><li>4.0 - a major version. Major versions include significant API changes and enhancements. They should be expected to be incompatible with previous versions.</li><li>4.1 - a minor version. Minor versions include compatible enhancements, but can also include minor API changes. While we try to maintain API compatibility for minor versions, there may be cases where we prefer to fix a problem in the API by implementing an incompatible change.</li><li>4.0.1 - a bugfi
x release. Bugfix releases are compatible with the respective major or minor version.</li></ul><p>Development of major and minor versions typically passes through the following phases:</p><ul><li><i>alpha</i> - API is instable, functionality untested</li><li><i>beta</i> - API is stable, test coverage improving</li><li><i>RC</i> - API is stable, test coverage good</li><li><i>final</i> - no significant bugs uncovered since last RC</li></ul><p>In the alpha phase, functionality is implemented and the API drafted. When the API has stabilized and covers the intended functionality for the next major or minor version, the API is frozen and development moves to the beta phase.</p><p>In the beta phase, the implementation is stabilized by improving the test coverage and refining the API specification. Compatible API changes are still expected. If significant problems with the API are uncovered, incompatible changes can be introduced with a deprecation cycle. That means that there is at least o
ne compatible beta release in which parts of the API are marked as deprecated. The deprecated parts of the API can then be removed in a subsequent release.</p><p>The RC (release candidate) phase starts when the developers consider the codebase stable and mature. The API is kept stable, even compatible enhancements will be minimized. Activity during the RC phase is focused on improving the documentation and test coverage. If some major or many minor bugs are detected, these are fixed in a new RC release.</p><p>The final release of a major or minor version is published if bug reports for the RC releases are ebbing away. While the previous releases include the alpha, beta, or RC label in their name, a final release is published with the two digit version number without a suffix. The final release is moved to a branch in the source repository for maintenance. Bugs are fixed for that version in compatible bugfix releases off the branch. Issues that require an API change can only be addre
ssed in the next minor or major version, which is developed on the trunk.</p></div><div class="section"><h2>Code Review<a shape="rect" name="Code_Review"></a></h2><p>The two styles for code review at Apache are review-then-commit (RTC) and commit-then-review (CTR). Not only the program code is reviewed, but also the contents of the website and the Wiki. </p><p>With RTC, a patch is published in the issue tracker, then reviewed by the developers, and committed to the source repository only afterwards. Lazy consensus is sufficient, there is no need for formal voting or three opinions in favor.</p><p>With CTR, a change is committed to the source repository directly. Developers receive the change notification on the commits mailing list and review the repository contents. If there is a major problem with the change, any committer can veto the change by sending a -1 reply to the commit message. After a veto, the change is reverted as soon as possible in the source repository and the reaso
n for the veto will be discussed. Minor problems are not handled with a veto and revert, but by discussion on the mailing list and followup patches.</p><p>We use both RTC and CTR, and common sense to decide between the two. Some simple rules are:</p><ul><li>changes to Charter and Bylaws are RTC and require formal PMC approval</li><li>updates to the Wiki are CTR</li><li>code contributions by non-committers are RTC</li><li>simple bug fixes are CTR</li><li>documentation improvements are CTR</li><li>updates to the website are CTR</li><li>code changes in an unstable development phase are CTR. Unstable phases are <i>alpha</i> for all changes and <i>beta</i> if the API remains compatible.</li><li>major code changes in a stable development phase are RTC. Stable phases are <i>beta</i> for the API, <i>RC</i> for all the code, and maintenance in the branch of a final release.</li><li>committers looking for feedback on an idea use RTC</li><li>changes to an experimental branch or sandbox are CTR
</li></ul></div>
</div>
</div>
<div class="clear">
- <hr/>
+ <hr></hr>
</div>
<div id="footer">
<div class="xleft">Apache HttpComponents, Commons HttpClient, Apache, the Apache feather logo, and the Apache HttpComponents project logo are trademarks of The Apache Software Foundation.</div>
-<br/>
+<br clear="none"></br>
<div class="xleft">All other marks mentioned may be trademarks or registered trademarks of their respective owners.</div>
<div class="xright">Copyright © 2005-2013
- <a href="http://www.apache.org/">Apache Software Foundation</a>.
+ <a shape="rect" href="http://www.apache.org/">Apache Software Foundation</a>.
All Rights Reserved.
</div>
<div class="clear">
- <hr/>
+ <hr></hr>
</div>
</div>
- </body>
-</html>
+ </body></html>
Modified: httpcomponents/site/charter.html
URL: http://svn.apache.org/viewvc/httpcomponents/site/charter.html?rev=1811447&r1=1811446&r2=1811447&view=diff
==============================================================================
--- httpcomponents/site/charter.html (original)
+++ httpcomponents/site/charter.html Sat Oct 7 21:20:11 2017
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at 2017-09-04 ( $Revision$ ) -->
+<!-- Generated by Apache Maven Doxia at 2017-10-07 ( $Revision$ ) -->
<!-- $HeadURL: https://svn.apache.org/repos/asf/httpcomponents/maven-skin/trunk/src/main/resources/META-INF/maven/site.vm $ -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
@@ -11,7 +11,7 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20170904" />
+ <meta name="Date-Revision-yyyymmdd" content="20171007" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -31,7 +31,7 @@
<div class="xleft">
- <span id="publishDate">Last Published: 2017-09-04</span>
+ <span id="publishDate">Last Published: 2017-10-07</span>
| <span id="projectVersion">Version: 1-SNAPSHOT</span>
</div>
<div class="xright"> <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>
@@ -219,7 +219,8 @@ obsoleted by the components of the Apach
RESOLVED, that all responsibilities pertaining to the Apache Jakarta HttpComponents subproject and
the former Apache Jakarta Commons HttpClient codebase encumbered upon the Apache Jakarta Project are
-hereafter discharged.</pre></div></div>
+hereafter discharged.
+</pre></div></div>
</div>
</div>
<div class="clear">
Modified: httpcomponents/site/commons-httpclient-lessons.html
URL: http://svn.apache.org/viewvc/httpcomponents/site/commons-httpclient-lessons.html?rev=1811447&r1=1811446&r2=1811447&view=diff
==============================================================================
--- httpcomponents/site/commons-httpclient-lessons.html (original)
+++ httpcomponents/site/commons-httpclient-lessons.html Sat Oct 7 21:20:11 2017
@@ -1,30 +1,18 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Jun 12, 2013 ( $Revision$ ) -->
-<!-- $HeadURL: https://svn.apache.org/repos/asf/httpcomponents/maven-skin/trunk/src/main/resources/META-INF/maven/site.vm $ -->
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Apache HttpComponents - Lessons Learned - Jakarta Commons HttpClient</title>
- <style type="text/css" media="all">
+<?xml version="1.0" standalone="yes"?>
+<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></meta><title>Apache HttpComponents - Lessons Learned - Jakarta Commons HttpClient</title><style type="text/css" media="all">
@import url("./css/maven-base.css");
@import url("./css/maven-theme.css");
@import url("./css/site.css");
- </style>
- <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20130612" />
- <meta http-equiv="Content-Language" content="en" />
-
- </head>
- <body class="composite">
+ </style><link rel="stylesheet" href="./css/print.css" type="text/css" media="print"></link><meta name="Date-Revision-yyyymmdd" content="20130612"></meta><meta http-equiv="Content-Language" content="en"></meta></head><body class="composite">
<div id="banner">
- <a href="http://www.apache.org/" id="bannerLeft">
- <img src="http://www.apache.org/images/asf_logo_wide.gif" alt="Apache" />
+ <a shape="rect" id="bannerLeft" href="http://www.apache.org/">
+ <img src="http://www.apache.org/images/asf_logo_wide.gif" alt="Apache"></img>
</a>
- <a href="./" id="bannerRight">
- <img src="images/logos/httpcomponents.png" alt="HttpComponents" />
+ <a shape="rect" id="bannerRight" href="./">
+ <img src="images/logos/httpcomponents.png" alt="HttpComponents"></img>
</a>
<div class="clear">
- <hr/>
+ <hr></hr>
</div>
</div>
<div id="breadcrumbs">
@@ -32,16 +20,16 @@
<div class="xleft">
<span id="publishDate">Last Published: 2013-06-12</span>
- | <span id="projectVersion">Version: 7-SNAPSHOT</span>
+  | <span id="projectVersion">Version: 7-SNAPSHOT</span>
</div>
- <div class="xright"> <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>
+ <div class="xright"> <a shape="rect" class="externalLink" href="http://www.apache.org/" title="Apache">Apache</a>
|
- <a href="index.html" title="HttpComponents">HttpComponents</a>
+ <a shape="rect" href="index.html" title="HttpComponents">HttpComponents</a>
</div>
<div class="clear">
- <hr/>
+ <hr></hr>
</div>
</div>
<div id="leftColumn">
@@ -49,112 +37,78 @@
<h5>HttpComponents</h5>
- <ul>
- <li class="none">
- <a href="index.html" title="Home">Home</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/licenses/" class="externalLink" title="License">License</a>
- </li>
- <li class="none">
- <a href="downloads.cgi" title="Download">Download</a>
- </li>
- <li class="none">
- <a href="mail.html" title="Mailing Lists">Mailing Lists</a>
- </li>
- <li class="none">
- <a href="user-docs.html" title="User documents">User documents</a>
- </li>
- <li class="none">
- <a href="dev-docs.html" title="Developer documents">Developer documents</a>
- </li>
- <li class="none">
- <a href="http://wiki.apache.org/HttpComponents/" class="externalLink" title="Wiki (external)">Wiki (external)</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/security/" class="externalLink" title="Security">Security</a>
- </li>
- </ul>
+ <ul><li class="none">
+ <a shape="rect" href="index.html" title="Home">Home</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/licenses/" title="License">License</a>
+ </li><li class="none">
+ <a shape="rect" href="downloads.cgi" title="Download">Download</a>
+ </li><li class="none">
+ <a shape="rect" href="mail.html" title="Mailing Lists">Mailing Lists</a>
+ </li><li class="none">
+ <a shape="rect" href="user-docs.html" title="User documents">User documents</a>
+ </li><li class="none">
+ <a shape="rect" href="dev-docs.html" title="Developer documents">Developer documents</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://wiki.apache.org/HttpComponents/" title="Wiki (external)">Wiki (external)</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/security/" title="Security">Security</a>
+ </li></ul>
<h5>Overview</h5>
- <ul>
- <li class="none">
- <a href="index.html" title="About">About</a>
- </li>
- <li class="none">
- <a href="news.html" title="News">News</a>
- </li>
- <li class="none">
- <a href="poweredby.html" title="Powered by">Powered by</a>
- </li>
- <li class="none">
- <a href="get-involved.html" title="Get Involved">Get Involved</a>
- </li>
- </ul>
+ <ul><li class="none">
+ <a shape="rect" href="index.html" title="About">About</a>
+ </li><li class="none">
+ <a shape="rect" href="news.html" title="News">News</a>
+ </li><li class="none">
+ <a shape="rect" href="poweredby.html" title="Powered by">Powered by</a>
+ </li><li class="none">
+ <a shape="rect" href="get-involved.html" title="Get Involved">Get Involved</a>
+ </li></ul>
<h5>Components</h5>
- <ul>
- <li class="none">
- <a href="httpcomponents-client-ga/index.html" title="HttpClient (GA)">HttpClient (GA)</a>
- </li>
- <li class="none">
- <a href="httpcomponents-client-dev/index.html" title="HttpClient (DEV)">HttpClient (DEV)</a>
- </li>
- <li class="none">
- <a href="httpcomponents-core-ga/index.html" title="HttpCore (GA)">HttpCore (GA)</a>
- </li>
- <li class="none">
- <a href="httpcomponents-core-dev/index.html" title="HttpCore (DEV)">HttpCore (DEV)</a>
- </li>
- <li class="none">
- <a href="httpcomponents-asyncclient-dev/index.html" title="HttpAsyncClient (DEV)">HttpAsyncClient (DEV)</a>
- </li>
- </ul>
+ <ul><li class="none">
+ <a shape="rect" href="httpcomponents-client-ga/index.html" title="HttpClient (GA)">HttpClient (GA)</a>
+ </li><li class="none">
+ <a shape="rect" href="httpcomponents-client-dev/index.html" title="HttpClient (DEV)">HttpClient (DEV)</a>
+ </li><li class="none">
+ <a shape="rect" href="httpcomponents-core-ga/index.html" title="HttpCore (GA)">HttpCore (GA)</a>
+ </li><li class="none">
+ <a shape="rect" href="httpcomponents-core-dev/index.html" title="HttpCore (DEV)">HttpCore (DEV)</a>
+ </li><li class="none">
+ <a shape="rect" href="httpcomponents-asyncclient-dev/index.html" title="HttpAsyncClient (DEV)">HttpAsyncClient (DEV)</a>
+ </li></ul>
<h5>Legacy</h5>
- <ul>
- <li class="none">
- <a href="httpclient-legacy/index.html" title="Commons HttpClient">Commons HttpClient</a>
- </li>
- </ul>
+ <ul><li class="none">
+ <a shape="rect" href="httpclient-legacy/index.html" title="Commons HttpClient">Commons HttpClient</a>
+ </li></ul>
<h5>Project</h5>
- <ul>
- <li class="none">
- <a href="status.html" title="Status">Status</a>
- </li>
- <li class="none">
- <a href="charter.html" title="Charter">Charter</a>
- </li>
- <li class="none">
- <a href="bylaws.html" title="Bylaws">Bylaws</a>
- </li>
- <li class="none">
- <a href="goals.html" title="Goals">Goals</a>
- </li>
- </ul>
+ <ul><li class="none">
+ <a shape="rect" href="status.html" title="Status">Status</a>
+ </li><li class="none">
+ <a shape="rect" href="charter.html" title="Charter">Charter</a>
+ </li><li class="none">
+ <a shape="rect" href="bylaws.html" title="Bylaws">Bylaws</a>
+ </li><li class="none">
+ <a shape="rect" href="goals.html" title="Goals">Goals</a>
+ </li></ul>
<h5>Project Documentation</h5>
- <ul>
- <li class="collapsed">
- <a href="project-info.html" title="Project Information">Project Information</a>
- </li>
- </ul>
+ <ul><li class="collapsed">
+ <a shape="rect" href="project-info.html" title="Project Information">Project Information</a>
+ </li></ul>
<h5>ASF</h5>
- <ul>
- <li class="none">
- <a href="http://www.apache.org" class="externalLink" title="ASF Home Page">ASF Home Page</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/foundation/" class="externalLink" title="Foundation">Foundation</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/foundation/sponsorship.html" class="externalLink" title="Sponsor Apache">Sponsor Apache</a>
- </li>
- <li class="none">
- <a href="http://www.apache.org/foundation/thanks.html" class="externalLink" title="Thanks">Thanks</a>
- </li>
- </ul>
- <a href="http://www.apache.org/events/current-event.html" title="ApacheCon" class="poweredBy">
- <img class="poweredBy" alt="ApacheCon" src="http://www.apache.org/events/current-event-125x125.png" />
+ <ul><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org" title="ASF Home Page">ASF Home Page</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/foundation/" title="Foundation">Foundation</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/foundation/sponsorship.html" title="Sponsor Apache">Sponsor Apache</a>
+ </li><li class="none">
+ <a shape="rect" class="externalLink" href="http://www.apache.org/foundation/thanks.html" title="Thanks">Thanks</a>
+ </li></ul>
+ <a shape="rect" class="poweredBy" href="http://www.apache.org/events/current-event.html" title="ApacheCon">
+ <img class="poweredBy" alt="ApacheCon" src="http://www.apache.org/events/current-event-125x125.png"></img>
</a>
- <a href="http://maven.apache.org/" title="Maven" class="poweredBy">
- <img class="poweredBy" alt="Maven" src="http://maven.apache.org/images/logos/maven-feather.png" />
+ <a shape="rect" class="poweredBy" href="http://maven.apache.org/" title="Maven">
+ <img class="poweredBy" alt="Maven" src="http://maven.apache.org/images/logos/maven-feather.png"></img>
</a>
@@ -162,27 +116,26 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- ==================================================================== --><!-- 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. --><!-- ==========================
========================================== --><!-- --><!-- 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/>. --><div class="section"><h2>Lessons Learned<a name="Lessons_Learned"></a></h2><p>The HttpComponents project was undertaken following our experience in developing and supporting Jakarta Commons HttpClient. The shortcomings and inefficiencies listed below emerged during our work with HttpClient and prompted our action. HttpComponents is an attempt to address these issues.</p><div class="section"><h3><a name="Monolithic_design_of_Commons_HttpClient">Monolithic design of Commons HttpClient</a></h3><ul><li>The use patterns of Commons HttpClient have evolved much since its first release. We have found HttpClient used in applications it was never specifically designed for: in spiders, in server si
de services such as HTTP proxies or light-weight HTTP connectors. Essentially we saw HttpClient users trying to use it as a toolkit of generic HTTP components. In some areas the original monolithic design of Commons HttpClient proved quite lacking.</li><li>HttpClient has a rich set of features. Some of them, however, are used infrequently in a limited number of specific cases, and represent unnecessary code bloat for a sizable percentage of HttpClient users. Moreover, some of those infrequently used features in Commons HttpClient were introduced at the expense of the API clarity. There are some core HTTP components that are required by all HTTP services whether they be on the client or on the server side. More application specific aspects of HTTP, however, cannot be adequately represented by one monolithic library. </li></ul></div><div class="section"><h3><a name="Inherent_API_deficiencies_of_Commons_HttpClient">Inherent API deficiencies of Commons HttpClient</a></h3><ul><li>HttpMet
hod interface, one of the most fundamental interfaces in Commons HttpClient, is inherently flawed. It tightly couples the HTTP request and HTTP response and implies one to one relationship between the two, which is not always the case.</li><li>Abuse of inheritance. HttpMethodBase class contains the greatest chunk of processing logic in HttpClient. It inseparably couples the logic of generating HTTP requests and processing HTTP responses. This makes it virtually impossible to create a custom implementation of an HttpMethod interface, essentially rendering it useless. In practice all HTTP methods must be derived from HttpMethodBase class.</li><li>The fact that all HTTP methods in practical terms must be derived from one common base (HttpMethodBase) has a number of side effects. For instance, if one needs to introduce a common behavior across all standard HTTP methods, one would have to subclass all the existing subclasses of the HttpMethodBase: GetMethod, PostMethod, etc.</li></ul></d
iv><div class="section"><h3><a name="External_dependencies">External dependencies</a></h3><ul><li>One of the most frequently cited complaints is its dependency on Commons Logging and Commons Codec. We would like to give the users an option to use core HTTP components without any external libraries and a minimal footprint.</li></ul></div></div>
+ <div class="section"><h2>Lessons Learned<a shape="rect" name="Lessons_Learned"></a></h2><p>The HttpComponents project was undertaken following our experience in developing and supporting Jakarta Commons HttpClient. The shortcomings and inefficiencies listed below emerged during our work with HttpClient and prompted our action. HttpComponents is an attempt to address these issues.</p><div class="section"><h3><a shape="rect" name="Monolithic_design_of_Commons_HttpClient">Monolithic design of Commons HttpClient</a></h3><ul><li>The use patterns of Commons HttpClient have evolved much since its first release. We have found HttpClient used in applications it was never specifically designed for: in spiders, in server side services such as HTTP proxies or light-weight HTTP connectors. Essentially we saw HttpClient users trying to use it as a toolkit of generic HTTP components. In some areas the original monolithic design of Commons HttpClient proved quite lacking.</li><li>HttpClient
has a rich set of features. Some of them, however, are used infrequently in a limited number of specific cases, and represent unnecessary code bloat for a sizable percentage of HttpClient users. Moreover, some of those infrequently used features in Commons HttpClient were introduced at the expense of the API clarity. There are some core HTTP components that are required by all HTTP services whether they be on the client or on the server side. More application specific aspects of HTTP, however, cannot be adequately represented by one monolithic library. </li></ul></div><div class="section"><h3><a shape="rect" name="Inherent_API_deficiencies_of_Commons_HttpClient">Inherent API deficiencies of Commons HttpClient</a></h3><ul><li>HttpMethod interface, one of the most fundamental interfaces in Commons HttpClient, is inherently flawed. It tightly couples the HTTP request and HTTP response and implies one to one relationship between the two, which is not always the case.</li><li>Abuse of i
nheritance. HttpMethodBase class contains the greatest chunk of processing logic in HttpClient. It inseparably couples the logic of generating HTTP requests and processing HTTP responses. This makes it virtually impossible to create a custom implementation of an HttpMethod interface, essentially rendering it useless. In practice all HTTP methods must be derived from HttpMethodBase class.</li><li>The fact that all HTTP methods in practical terms must be derived from one common base (HttpMethodBase) has a number of side effects. For instance, if one needs to introduce a common behavior across all standard HTTP methods, one would have to subclass all the existing subclasses of the HttpMethodBase: GetMethod, PostMethod, etc.</li></ul></div><div class="section"><h3><a shape="rect" name="External_dependencies">External dependencies</a></h3><ul><li>One of the most frequently cited complaints is its dependency on Commons Logging and Commons Codec. We would like to give the users an option t
o use core HTTP components without any external libraries and a minimal footprint.</li></ul></div></div>
</div>
</div>
<div class="clear">
- <hr/>
+ <hr></hr>
</div>
<div id="footer">
<div class="xleft">Apache HttpComponents, Commons HttpClient, Apache, the Apache feather logo, and the Apache HttpComponents project logo are trademarks of The Apache Software Foundation.</div>
-<br/>
+<br clear="none"></br>
<div class="xleft">All other marks mentioned may be trademarks or registered trademarks of their respective owners.</div>
<div class="xright">Copyright © 2005-2013
- <a href="http://www.apache.org/">Apache Software Foundation</a>.
+ <a shape="rect" href="http://www.apache.org/">Apache Software Foundation</a>.
All Rights Reserved.
</div>
<div class="clear">
- <hr/>
+ <hr></hr>
</div>
</div>
- </body>
-</html>
+ </body></html>
Modified: httpcomponents/site/dev-docs.html
URL: http://svn.apache.org/viewvc/httpcomponents/site/dev-docs.html?rev=1811447&r1=1811446&r2=1811447&view=diff
==============================================================================
--- httpcomponents/site/dev-docs.html (original)
+++ httpcomponents/site/dev-docs.html Sat Oct 7 21:20:11 2017
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at 2017-09-04 ( $Revision$ ) -->
+<!-- Generated by Apache Maven Doxia at 2017-10-07 ( $Revision$ ) -->
<!-- $HeadURL: https://svn.apache.org/repos/asf/httpcomponents/maven-skin/trunk/src/main/resources/META-INF/maven/site.vm $ -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
@@ -11,7 +11,7 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20170904" />
+ <meta name="Date-Revision-yyyymmdd" content="20171007" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -31,7 +31,7 @@
<div class="xleft">
- <span id="publishDate">Last Published: 2017-09-04</span>
+ <span id="publishDate">Last Published: 2017-10-07</span>
| <span id="projectVersion">Version: 1-SNAPSHOT</span>
</div>
<div class="xright"> <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>
@@ -175,14 +175,16 @@
<groupId>org.apache.httpcomponents</groupId>
<artifactId>maven-site-skin</artifactId>
<version>1.1</version>
- </skin></pre></div>
+ </skin>
+</pre></div>
<p>The skin contains an updated version of the default Maven template. The template checks the site.xml file for the presence of the following custom tag:</p>
<div class="source">
<pre> <custom>
<footer>
Optional HTML-formatted text goes here
</footer>
- </custom></pre></div>
+ </custom>
+</pre></div>
<p>If the tag is found, its contents are added to the footer just before the copyright statement. Example usage:</p>
<div class="source">
<pre> <custom>
@@ -192,7 +194,8 @@
<br/>
<div class="xleft">All other marks mentioned may be trademarks or registered trademarks of their respective owners.</div>
</footer>
- </custom></pre></div></div>
+ </custom>
+</pre></div></div>
<div class="section">
<h2><a name="Editting_APT_documents"></a>Editting APT documents</h2>
<p>The APT syntax is documented at <a class="externalLink" href="http://maven.apache.org/doxia/references/apt-format.html">http://maven.apache.org/doxia/references/apt-format.html</a></p></div>
Modified: httpcomponents/site/downloads.cgi
URL: http://svn.apache.org/viewvc/httpcomponents/site/downloads.cgi?rev=1811447&r1=1811446&r2=1811447&view=diff
==============================================================================
--- httpcomponents/site/downloads.cgi (original)
+++ httpcomponents/site/downloads.cgi Sat Oct 7 21:20:11 2017
@@ -1,6 +1,6 @@
-#!/bin/sh
-# Wrapper script around mirrors.cgi script
-# (we must change to that directory in order for python to pick up the
-# python includes correctly)
-cd /www/www.apache.org/dyn/mirrors
-/www/www.apache.org/dyn/mirrors/mirrors.cgi $*
+#!/bin/sh
+# Wrapper script around mirrors.cgi script
+# (we must change to that directory in order for python to pick up the
+# python includes correctly)
+cd /www/www.apache.org/dyn/mirrors
+/www/www.apache.org/dyn/mirrors/mirrors.cgi $*
Modified: httpcomponents/site/downloads.html
URL: http://svn.apache.org/viewvc/httpcomponents/site/downloads.html?rev=1811447&r1=1811446&r2=1811447&view=diff
==============================================================================
--- httpcomponents/site/downloads.html (original)
+++ httpcomponents/site/downloads.html Sat Oct 7 21:20:11 2017
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at 2017-09-14 ( $Revision$ ) -->
+<!-- Generated by Apache Maven Doxia at 2017-10-07 ( $Revision$ ) -->
<!-- $HeadURL: https://svn.apache.org/repos/asf/httpcomponents/maven-skin/trunk/src/main/resources/META-INF/maven/site.vm $ -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
@@ -11,7 +11,7 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20170914" />
+ <meta name="Date-Revision-yyyymmdd" content="20171007" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -31,7 +31,7 @@
<div class="xleft">
- <span id="publishDate">Last Published: 2017-09-14</span>
+ <span id="publishDate">Last Published: 2017-10-07</span>
| <span id="projectVersion">Version: 1-SNAPSHOT</span>
</div>
<div class="xright"> <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>
Modified: httpcomponents/site/get-involved.html
URL: http://svn.apache.org/viewvc/httpcomponents/site/get-involved.html?rev=1811447&r1=1811446&r2=1811447&view=diff
==============================================================================
--- httpcomponents/site/get-involved.html (original)
+++ httpcomponents/site/get-involved.html Sat Oct 7 21:20:11 2017
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at 2017-09-04 ( $Revision$ ) -->
+<!-- Generated by Apache Maven Doxia at 2017-10-07 ( $Revision$ ) -->
<!-- $HeadURL: https://svn.apache.org/repos/asf/httpcomponents/maven-skin/trunk/src/main/resources/META-INF/maven/site.vm $ -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
@@ -11,7 +11,7 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20170904" />
+ <meta name="Date-Revision-yyyymmdd" content="20171007" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -31,7 +31,7 @@
<div class="xleft">
- <span id="publishDate">Last Published: 2017-09-04</span>
+ <span id="publishDate">Last Published: 2017-10-07</span>
| <span id="projectVersion">Version: 1-SNAPSHOT</span>
</div>
<div class="xright"> <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>