On Thu, 2007-04-05 at 13:48 +0100, sebb wrote: > Much the same applies to JMeter, except that it would be difficult to > see it as a Commons component, and I'm not keen on JMeter leaving ASF. > > There was a proposal a while back to create a Testing TLP, but I could > not see the point of moving at the time so I did not try to make that > happen (but equally did not veto it). > > Since JMeter uses Httpclient, and both projects are alive but have few > developers, maybe there is some way we can help each other out? > > Sebastian
Hi Sebastian I personally see Commons' move to TLP as a rather shortsighted and awkward ways of forcing POI out of Jakarta and ORO and Regexp into Commons. It reminds me too much of events I have been firsthand witness to, and the way short term gains can easily turn into huge long term losses. But so be it. I can offer you a helping hand with the JMeter's move out of Jakarta either to a TLP of its own or to Testing TLP, and probably some hacking on HTTP related stuff or migration to Maven2. To free up some bandwidth for this work, though, I think I should finally make good on my promises and to discontinue any hands-on involvement in development of the Commons HttpClient 3.x code line (barring fixing critical bugs). This also means some one else will have to step up to assume the role of the RM for Commons HttpClient 3.1 henceon. Oleg > On 05/04/07, Ortwin Glück <[EMAIL PROTECTED]> wrote: > > Oleg, > > > > Honestly I don't really care WHERE this project is happening. If under > > Commons, TLP, in Webservices, on sf.net or Savannah. The important thing > > is THAT it is going on. For me all the surrounding organizational crap > > is more of a burden than it helps to get a project forward. > > > > Odi > > > > Oleg Kalnichevski wrote: > > > Mike, Odi, Roland and all > > > > > > It appears we have some really tough decisions forced upon us. It looks > > > quite probable that Jakarta Commons will become a TLP in the very near > > > future, which implies it is just a matter of time the remaining projects > > > of Jakarta will be forced to choose whether they want to go TLP or to > > > die. We all know in its present form the project is unlikely to be > > > viable as a TLP. So, we basically have just a few options, all seem > > > ugly. > > > > > > (1) Attempt to go TLP and risk the possibility of never becoming viable > > > as a TLP. > > > > > > (2) Go back to Commons and wait for the next trend in the social > > > engineering to hit us. > > > > > > (3) Seek a new home elsewhere within ASF. Curiously enough our largest > > > and the most active user base within ASF appears to be the Webservices > > > TLP, not Jakarta. > > > > > > (4) Pretend nothing is happening and hope this whole hooplah will fade > > > away the same way Jakarta Silk did. > > > > > > (5) Pull the plug. Do something else like raising pigeons or something. > > > > > > Evil Comrade Oleg > > > > > > > > > -- > > [web] http://www.odi.ch/ > > [blog] http://www.odi.ch/weblog/ > > [pgp] key 0x81CF3416 > > finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416 > > > > --------------------------------------------------------------------- > > 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]
