Re: [VOTE] Axis2 as TLP

Asankha, I totally agree the transports need to be buildable and 
releasable as an entities by themselves.

However, a TLP does not correspond to one piece of code. TLP == community 
to me. So right now the transports are in the WS TLP but we now can 
release them separately. I see no reason that would change even with the 
transports being under the axis2 TLP.

So, +1 to making the transports also into a separate subproject. Whether 
that's under axis2 or ws, I really see no difference. YMMV.

Sanjiva.

Asankha C. Perera wrote:
> I am -1 (binding) on this proposal as it is.
> 
> I am not for, or against Axis2 becoming a TLP, but I am strongly opposed 
> to moving the transports to within Axis2, as it would make it difficult 
> to develop and release new versions of them independently of the Axis2 
> trunk and release cycles - which are known to be long and painful.
> 
> Apache Synapse folks developed some of these transports as they are 
> highly dependent on these, and they frequently require quick fixes at 
> transport level to be able to add new features and handle various 
> issues. Thus the ability to get a new version of the transports released 
> when needed is immensely important for Apache Synapse among other 
> issues. In addition as a developer, I have to admit that I hate to build 
> Axis2 trunk each time I want to commit changes to a transport, as it 
> takes ages to build and fills up the M2 repo and finally fails many 
> times due to various issues. The interface between a transport and 
> anything else is clear, and you do not need to stick it deep into a 
> parent codebase to keep both working.
> 
> We also have had length discussions on this for a long time, and 
> agreement from *all* the key players involved in this discussion, to 
> make the new WS-transports sub project outside of Axis2 - with 
> independent release cycles etc. I do not want to make this VOTE thread a 
> discussion, but wanted everyone to be aware on the effect of these 
> actions on those who develop and use this piece of software.
> 
> asankha
> 
> [1] http://markmail.org/message/uvhz22bqnkjq3wmf
> [2] http://markmail.org/message/fr73nj32lchlgbxi
> [3] http://markmail.org/message/okzimikvmbhimflr
> 
> 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] http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal


-- 
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/