hc-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rola...@apache.org
Subject svn commit: r613516 - /httpcomponents/project/src/site/apt/charter.apt
Date Sun, 20 Jan 2008 07:49:01 GMT
Author: rolandw
Date: Sat Jan 19 23:48:59 2008
New Revision: 613516

URL: http://svn.apache.org/viewvc?rev=613516&view=rev
Log:
new draft charter, plus history and TLP resolution

Modified:
    httpcomponents/project/src/site/apt/charter.apt

Modified: httpcomponents/project/src/site/apt/charter.apt
URL: http://svn.apache.org/viewvc/httpcomponents/project/src/site/apt/charter.apt?rev=613516&r1=613515&r2=613516&view=diff
==============================================================================
--- httpcomponents/project/src/site/apt/charter.apt (original)
+++ httpcomponents/project/src/site/apt/charter.apt Sat Jan 19 23:48:59 2008
@@ -32,59 +32,127 @@
     ----------
     ----------
 
-Project Charter
+Charter (Draft $Revision$)
 
-* Project scope
+  The Apache HttpComponents project is responsible for creating and
+  maintaining a toolset of low level Java components focused on HTTP
+  and associated protocols.
+
+  We develop and maintain a component called <<HttpCore>>, which addresses
+  the basic needs for communicating via HTTP on the client and server side.
+  HttpCore defines a framework for extending the provided functionality
+  beyond the basic needs.
+
+  We develop and maintain a component called <<HttpClient>>, which builds
+  on HttpCore and adds functionality typically required for client-side
+  HTTP communication. In particular, HttpClient adds support for cookies,
+  authentication, and client-side connection management.
+
+  <<HttpCore>> and <<HttpClient>> are at the center of the
+  Apache HttpComponents project. All other activities orbit around this duo.
+
+  We maintain the codebase of the Jakarta Commons HttpClient, also known as
+  Commons HttpClient 3.1, until such time that the new HttpClient based on
+  HttpCore is considered ready for use in production systems.
+
+  We are looking for new components that build upon and extend the
+  functionality of the existing ones.
+  We are also looking for new components that complement the
+  functionality of the existing ones and make them more useful
+  or easier to use.
+
+  We are open to give a home to applications that derive a significant part
+  of their functionality from our components, if approached by such projects.
+
+
+
+History
+
+  The history of the HttpComponents starts with the now retired
+  {{{http://jakarta.apache.org/slide/}Jakarta Slide}} project.
+  Slide was a WebDAV server including a client component, and the
+  WebDAV protocol builds on HTTP. There was interest in using the
+  client-side HTTP implementation independently of Slide.
+  The code was spun off from Slide in 2001 to become the HttpClient
+  subproject of the Jakarta Commons.
+
+  Since it generated a disproportional amount of traffic on the
+  Commons mailing lists, HttpClient activity was moved to separate
+  mailing lists. This started the dissociation of HttpClient from
+  Commons.
+  The shortcomings in the design of HttpClient, as explained in the
+  {{{./commons-httpclient-lessons.html}Lessons Learned}},
+  created interest in redesigning the API from scratch.
+  To that end, the Jakarta HttpComponents project was created in 2005.
+  The tasks of the new project were to develop a successor for
+  HttpClient 3.x and to maintain the existing codebase until the
+  new one is ready to take over.
+
+  The {{{http://commons.apache.org/}Commons}}, cradle of HttpClient,
+  left Jakarta in 2007 to become an independent Top Level Project.
+  Later in the same year, the HttpComponents project also left Jakarta
+  to become an independent Top Level Project, taking the responsibility
+  for maintaining HttpClient 3.x with it.
+  The TLP resolution is presented below.
+
+
+Resolution
+
+  The Apache HttpComponents project was established
+  as an Apache top level project in November 2007,
+  when the Apache Board approved the following resolution:
+
+~~ The following is a verbatim copy of the TLP resolution.
+~~ DO NOT EDIT, not even to fix typos
+------------------------------
+Establish the Apache HttpComponents project
+
+WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and
+consistent with the Foundation's purpose to establish a Project Management Committee charged
with
+the creation and maintenance of open-source software related to a toolset of low level Java
+components focused on HTTP and associated protocols, and of applications based on these components,
+for distribution at no charge to the public.
+
+NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as
"Apache
+HttpComponents Project", be and hereby is established pursuant to Bylaws of the Foundation;
and be
+it further
+
+RESOLVED, that the Apache HttpComponents Project be and hereby is responsible for the creation
and
+maintenance of a toolset of low level Java components focused on HTTP and associated protocols,
and
+of applications based on these components; and be it further
+
+RESOLVED, that the office of "Vice President, Apache HttpComponents" be and hereby is created,
the
+person holding such office to serve at the direction of the Board of Directors as the chair
of the
+Apache HttpComponents Project, and to have primary responsibility for management of the projects
+within the scope of responsibility of the Apache HttpComponents Project; and be it further
+
+RESOLVED, that the persons listed immediately below be and hereby are appointed to serve
as the
+initial members of the Apache HttpComponents Project:
+
+    * Oleg Kalnichevski <olegk AT apache DOT org>
+    * Sebastian Bazley <sebb AT apache DOT org>
+    * Erik Abele <erikabele AT apache DOT org>
+    * Ortwin Gl├╝ck <oglueck AT apache DOT org>
+    * Roland Weber <rolandw AT apache DOT org>
+    * Ant Elder <antelder AT apache DOT org>
+    * Paul Fremantle <pzf AT apache DOT org>
+    * Asankha Perera <asankha AT apache DOT org>
+
+NOW, THEREFORE, BE IT FURTHER RESOLVED, that Erik Abele be appointed to the office of Vice
+President, Apache HttpComponents, to serve in accordance with and subject to the direction
of the
+Board of Directors and the Bylaws of the Foundation until death, resignation, retirement,
removal or
+disqualification, or until a successor is appointed; and be it further
+
+RESOLVED, that the Apache HttpComponents Project be and hereby is tasked with the migration
and
+rationalization of the Apache Jakarta HttpComponents subproject; and be it further
+
+RESOLVED, that the Apache HttpComponents Project be and hereby is tasked with the migration
and
+maintenance of the codebase formerly known as Apache Jakarta Commons HttpClient until it
is
+obsoleted by the components of the Apache HttpComponents Project; and be it further
+
+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.
+------------------------------
 
-    * Apache HttpComponents is responsible for the creation and maintenance of a toolset
of low 
-    level Java components focused on HTTP and associated protocols, and of applications based
on 
-    these components
-
-    * Apache HttpComponents continues the development of Apache HttpClient (formerly Jakarta
Commons 
-    HttpClient) based on the toolset of HTTP components. This tool focuses on the client
side of 
-    HTTP.
-
-    * Apache HttpComponents is additionally charged with the maintenance of the existing
Jakarta 
-    Commons HttpClient component.
-
-    * Apache HttpComponents collaborates with other projects to develop specialized HTTP
services 
-    for production use based on the toolset of HTTP components.
-
-* Targeted specifications and standards
-
-    * RFC1945 Hypertext Transfer Protocol -- HTTP/1.0
-
-    * RFC2616 Hypertext Transfer Protocol -- HTTP/1.1
-
-    * RFC2617 HTTP Authentication: Basic and Digest Access Authentication
-
-    * RFC2109 HTTP State Management Mechanism -- Cookies
-
-    * RFC2965 HTTP State Management Mechanism -- Cookie2
-
-    * A standard for robot exclusion <http://www.robotstxt.org/wc/norobots-rfc.html>
- robots.txt parser 
-
-* Initial set of committers
-
-    PMC Chair
-
-    * Erik Abele
-
-    []
-
-    PMC
- 
-    * Sebastian Bazley
-
-    * Ortwin Glueck
-
-    * Roland Weber
-
-    * Ant Elder
-
-    * Paul Fremantle
-
-    * Asankha Perera
-
-    * Oleg Kalnichevski
 



Mime
View raw message