On 22.10.2007, at 20:27, Oleg Kalnichevski wrote:
Erik Abele wrote:
...
Fwiw, as said, although JMeter might not fit 100% and there might
be no other suitable examples right now doesn't mean we need to
restrict the scope ultimately...
Example: let's say a java tool to test the compliance of HTTP
implementations gets proposed at the Incubator - I wouldn't have
an issue with sponsoring that if it intends to have its final home
at the HttpComponents TLP.
I have to say the idea of bringing JMeter into the same TLP took me
completely by surprise.
Don't misunderstand me, I didn't mean to advocate that JMeter moves
into the same TLP:
...
Aye, I also think that it would be better off as an own TLP.
--
...
The reason I'm not keen for JMeter to go TLP is mainly the lack of
committer community. In Jakarta there are still some committers
(apart
from the HC crowd) who can (and do) test releases and vote on them.
That's the real pity IMHO and might be a blocker before going TLP :(
I do not see it thins way. Sebastian and Alf alone are worth 10
committers. The highest commit rate in Jakarta. And I think enough
people expressed interest in being on JMeter PMC [1] to make the
TLP viable.
While that may be true, the absolutely lowest bar for a separate
PMC / TLP is three independent committers (not necessarily PMC
members, see Incubator docs).
Though we shouldn't mingle this discussion with the HttpC TLP
proposal - let's keep it separate and first focus on this one :)
Cheers,
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
