Hi Henri I apologize for the late response (I reckoned you already had your plate full with the ongoing SD Magazine issue, anyway).
The project site is virtually the only thing that has not been promoted yet. HttpClient project already has its own mailing lists, SVN repository and Bugzilla entry. There's absolutely nothing that prevents us from physically moving HttpClient project site up to the SPL. The reason I am personally a little hesitant to see this happen before the final 3.0 release is the fact that HttpClient is currently undergoing a more fundamental transformation than a simple promotion from Commons to the subproject level. In the future we want to see HttpClient evolve from being a monolithic client side library into a toolset of generic HTTP components suitable for building client, proxy and server side HTTP services. That would constitute a significant expansion of the originally stated project goals and may well warrant the project rebranding under a new project name. (Most likely we may consider dropping 'client' from the HttpClient name or some such thing) The situation is far from being simple, though. A lot will depend on whether we succeed in generating enough interest amongst peer Apache and Jakarta projects. If no project expresses any interest in reusing HTTP components we are developing, we may well keep them folded into HttpClient library and keep everything as is. Alternatively we can consider donating application agnostic http-commons, http-cookies, http-auth code back to Commons and concentrating on developing higher-level services off Jakarta Http(Client) while maintaining common HTTP components in Jakarta Commons. So, there is a lot of questions to be answered. There's already enough uncertainty and I therefore would rather avoid making moves that may result in even more confusion. Presently I am really trying my very best to get as much of http-commons <http://svn.apache.org/repos/asf/jakarta/httpclient/trunk/http-common/> shaped up as possible, with a major push planned for the Easter break, in order to have enough substance to approach Commons, Tomcat, and possibly Geronimo folks and see if they express any interest in working together. Based on the feedback we will make final arrangements in the project structure, vote on project name change, if necessary, and happily proceed to establish our presence as a full-fledged SLP. What do you think? Oleg On Sat, Mar 19, 2005 at 01:22:00AM -0500, Henri Yandell wrote: > With hindsight I should have asked this question last year. Why > exactly are you waiting for a release of 3.0 to goto SLP level? Some > marketing reason? > > If it's in terms of finding resource to handle the move, then the > revent move of JCS has shown me that it's quite simple. It doesn't all > have to happen at the same time (Jetspeed still live in Jakarta's CVS > is an example there) and amounts to: > > * Request mailing list change. Scripted now and seems to be quite simple. > * Moving the site at Jakarta, and adding a redirect. > * Promotng HttpClient on the main Jakarta site. > * An svn move. > * Potential wiki stuff. > > I'm completely happy to help with most of this and am wondering why we > don't just go ahead and move HttpClient up (pretty sure it got the > vote many months ago). > > Hen > > On Fri, 25 Feb 2005 15:25:07 +0100, Oleg Kalnichevski <[EMAIL PROTECTED]> > wrote: > > Hi Henri, > > > > Things are gradually progressing (without much publicity, though) > > > > We have been quite busy working on the high level component architecture > > for Jakarta HttpClient, which we are planning to hold a formal voting > > upon quite soon: > > > > http://wiki.apache.org/jakarta-httpclient/HttpClientApiRedesign > > > > This document present a fairly good overview of how we envisage > > HttpClient's evolution from what it is today, a monolithic client-side > > library, into a toolset of loosely coupled components suitable for > > client, proxy and server side development. > > > > Technically speaking HttpClient 3.0 has not been released yet. We have > > just got the first release candidate out the door, and it may take a few > > more months and a few more RCs before the final 3.0 release. > > > > So, we have not been sitting idle. We have been just keeping a low > > profile. > > > > Cheers, > > > > Oleg > > > > > > On Fri, 2005-02-25 at 00:32 -0500, Henri Yandell wrote: > > > With so many parts of Jakarta moving around this quarter, I'm trying > > > to keep a better eye on where things are. > > > > > > Last I recall, HttpClient was waiting on the now-released 3.0 version > > > before moving to a sub-project level project (secondary level project, > > > whatever, I just like SLP as an acronym). Is the move now underway at > > > all? > > > > > > Hen > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
