axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepal jayasinghe <>
Subject Re: [VOTE] Axis2 as TLP
Date Thu, 27 Nov 2008 15:26:24 GMT
keith chapman wrote:
> -1 (binding)
> As the discussion shows we are clearly not ready yet. 
What is your definition for ready ? do you think any project which
graduated as TLPs were ready ? . Not only that we can find a number of
project which are in TLP still not ready (compared to Axis2 ).  Honestly
I do not know the Apache policy for graduating a project as TLP ,
specially what level of ready they are looking for. If we wait till
project to be get ready before moving to TLP I am sure Apache will not
have any of the TLPs.

And if you vote based on that (ready or not ready) I know you will never
+1 for Axis2 as TLP.
> I guess making Axis2 a
> TLP at the moment will just increase the complexity than giving any added
> value.
I do not understand this , do you think after we move Axiom , rampart
and Neethi from Axis2 to WS complexity increased ? of course not. More
and more people started to use Axiom and Neethi after that. I think even
ODE will not use Axiom unless we move that as a TLP in WS (top level
subproject in WS).

Thank you!
> Thanks,
> Keith.
> On Thu, Nov 20, 2008 at 9:03 PM, Glen Daniels <> wrote:
>> Folks:
>> Discussion seems to have died down about the TLP proposal, and I think we
>> heard a lot of valuable viewpoints during the conversation.  At this point,
>> I think it's time to VOTE on the idea and see where we're at.
>> I've described what we're voting on on the wiki page [1], and will include
>> it here as well:
>> * Restructure Axis2 as an independent TLP, containing subprojects that
>> *directly* relate to Axis2 - these include all the Modules and Transports.
>> This ends up being a reasonably sized and well-focused project.
>> * Once Axis2 is split out, we'll move the "sub-sub-projects" inside
>> WS-Commons (Axiom, Neethi, XmlSchema) up to be WS subprojects. This will
>> also involve making sure that the SVN authorizations are appropriately
>> granular.
>> * We'll then do a review of the remaining projects inside WS and based on
>> that, decide whether any further action is needed. Such actions might
>> include promoting more projects to TLPs, or retiring stagnant codebases.
>> Please chime in with your VOTE on this (and indicate binding/non-binding
>> depending on whether you are a PMC member).
>> Here's my +1 (binding).
>> Thanks,
>> --Glen
>> [1]

Thank you!

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message