Otis, et al There are several things that in my view make HttpClient not yet ready for a full-blown TLP status:
* Please correct me if I am wrong, but I always thought that TLPs were supposed to support multiple platforms, hence their top level status. Whereas I can certainly imagine HttpClient implemented in straight C or C++ (or any other language), I just do not think we'll have enough resources to actively develop anything but a Java version in the foreseeable future * I can hardly think of any subproject within HttpClient project. Ability to host sub-project within a project is one of the primary criteria for promoting a project to the top level. I do not think we qualify * As useful and feature rich HttpClient has become, let's face it, it's not exactly a masterpiece of design elegancy. Being a TLP would make HttpClient de facto Apache's official HTTP client. Frankly, I do not think HttpClient in its present form deserves it. There's still lots to be done before it possibly could. There are different ways of seeing things, and I certainly can be wrong here, but I do think HttpClient should stay within Jakarta for the release 3.0 and 4.0 Oleg On Sun, 2004-02-01 at 15:46, otisg wrote: > I am a HttpClient user and a Lucene committer. > I don't see any problems in HttpClient moving out of Commons. > However, before you waste time doing that, talk to people > involved in moving projects from Jakarta and making them Top > Level Projects (TLP). Ant, Log4j, etc. have made this move, so > you may want to skip the 'Commons -> Jakarta' move and just do > the 'Commons -> TLP' move. > > Either of the two moves would bring HttpClient more visibility, > and I think HttpClient needs and deserves it. > > Otis Gospodnetic > > > > > > ________________________________________________ > Get your own "800" number > Voicemail, fax, email, and a lot more > http://www.ureach.com/reg/tag > > > ---- On Sat, 31 Jan 2004, Michael Becke ([EMAIL PROTECTED]) > wrote: > > > Hello All, > > > > There has been some discussion lately of promoting HttpClient > out of > > commons, making it a regular Jakarta project. Before any such > move is > > made we would need to come to a consensus, and vote, within > the > > HttpClient community. At this point I would like to encourage > everyone > > to put in their 2 cents. What does everyone think? > > > > In particular I would like to hear from all the regular > committers, > > contributors, and users. How do you think this move would > effect > > HttpClient's visibility, community, and organization? > > > > Mike > > > > > > > --------------------------------------------------------------------- > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
