It is nice to see everyone is fighting for something good :-) , Well first I do not think anyone in this mailing list is so stupid to give the PMC Chair or whatever based on the number of emails he sends to the list. Let me tell why I think it is a good idea to make Axis2 a TLP.
First if you go back and look at the history why we wanted to make a Synapse a TLP ? (while it is heavily depend on Axis2 and Axiom ). But no one raised their concerns on dependent projects , simply no one talk anything like these their ,we as a community saw the advantages of making a synapse a TLP so we did that. As far as I understand from this thread , we should not have made synapse TLP , rather we should have created a new TLP called ESB and move synapse and other apache ESB projects into that. But we did not do that , why ? , To answer that just go and see the increase in number of download , and see the number of users. That is just two thing I see after making Synapse as TLP. I am happy I also +1 for making Synapse a TLP and it was a good decision. Actually I wanted to make Axis2 a TLP at the same time frame (when Dims was WS PMC chair). Second if you look at all the WS project mailings lists, you will realized more than 90% of the traffics on Axis2 projects. So you can not consider Axis2 as yet another project in Axis2 , rather that is the most active Web service projects in Apache-WS (because in Apache we have some other active Web service projects which are not belong to Apache-WS). Therefore staying inside WS does not make any sense for Axis2. I do not mind renaming WS in to Axis2 , practical speaking WS is Axis2 (not to hurt Axis1). Having said that it is not an issues whether we want to make other projects like Axiom , Neethi into TLPs if we are going to make Axis2 into TLP (as I mentioned earlier we did not discuss them when we move synapse into TLP). Since project like Rampart , Sandesha can not live without Axis2 , we should move them as subproject in Axis2 (if we agree to move as TLP). Talking about C stack , my answer would be Axis2 if would become a TLP , then Java and C version would be two main sub-projects of that (or we can make both of the TLP). For Dims , I am sorry I can not agree that with you that whoever working day to day basis should take the decision. That is totally against the open source development , theoretically open source developers will work on when they have free time (because no one is getting paid open source development , well now its bit different ). For example now I am (not only me all the initial developers) not working on day to day basis (you know why) , so just because that you can not tell me that I can not involve with decision process. Thank you for the reading very long mail. Deepal > Chinthaka, > > What are the problems that will be created? Please enumerate them. How > is it being handled / smoothed over now and what would change > specifically to make the cooperation not happen. > > If you can point your finger to specific scenarios. We can see if we > can come up with specific solutions. (Say common svn area where both > committers can have access). > > Also, Don't mind me, i repeat my mantra for the n-th time again. Those > who are actively working on a day to day basis should be taking the > decisions. What we are doing is not working and i propose we try > something new to see if it will work. > > thanks, > dims > > On Thu, Oct 30, 2008 at 2:59 PM, Eran Chinthaka > <[EMAIL PROTECTED]> wrote: > >> On Thu, Oct 30, 2008 at 2:21 PM, Deepal jayasinghe <[EMAIL PROTECTED]> >> wrote: >> >>> Eran Chinthaka wrote: >>> >>>> I hope I'm still not late to comment on this. >>>> >>>> I'm also with Sanjiva on this issue. Axis2 is just not Axis2 project >>>> alone. Axiom and others are integral parts of it. Couple of >>>> challenges/questions from me. >>>> >>>> 1. Let's take the Glen's proposal on two projects and list down the >>>> developers in each project. >>>> >>> Hehe , then what Apache should do is remove all the TLPs and their PMC's >>> and list down developers in different projects :) >>> >> I think you didn't get what I meant here. According to Glen's suggestion, >> Axiom and Axis2 will be on two different projects. What is the meaning of >> that if its the same people in both the groups. >> >> Also one more concern. I think Axis2/Java is more connected to Axiom than >> Axis2/C. So keeping Axis2/C and Axis2/Java in one project and leaving out >> Axiom makes no sense to me. >> >> Removing all the TLPs in Apache is not by any means analogous to that. >> >> >> >>> The one idea of TLP is to build small communities and improve them , >>> then automatically Apache as a whole will be improved. >>> >> Nice quote Deepal. You have already started to become a philosopher ;) >> >> >>>> So is it worth doing this? I'm extremely sorry if I'm missing >>>> something, but still I can not see a compelling argument to move on to >>>> a new TLP. >>>> >>> As I can see you looking at the problem in differently , >>> >>> its not about >>> who is going to be the PMC chair , or whether we are going to become a >>> PMC in some other list. Its about get more visibility to the projects >>> and enhance the project. >>> >> Wow, what sort of *more* visibility you will get by doing this? Can you >> please elaborate a bit? Will we see thousands of more Axis2 downloads after >> this? Or will see developers competing to send patches to Axis2 and Axiom? >> >> I personally think creating separate TLPs will create more problems and >> unnecessary separation within the community. >> >> Thanks, >> Chinthaka >> >> >> > > > > -- Thank you! http://blogs.deepal.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
