On 10/16/07, Adrian Woodhead <[EMAIL PROTECTED]> wrote: > > Thanks for your reply, Xavier, comments below: > > Xavier Hanin wrote: > > It could be interesting to have one more resolver but first a question: > do > > you use a svn client library (like SVNKit) or the svn command line, or > > subversion java binding? Depending on SVNKit is incompatible with the > > allowed licenses at the ASF for instance. > > > I am using the SVNKit Java library. I thought from their licensing > description that it would be compatible with ASF as their library is > allowed to be used as long as the project using it is open source, which > Ivy is. However, would an incompatibility arise if you shipped Ivy with > it, in that people using it would then have to provide the code for > their project, which isn't a requirement of the ASF license?
Yes, that's the point. Even with a more flexible license it could still be a problem if the license is not a known and widely adopted license, there is good chance that here at the ASF we wouldn't be able to use it. I'm not a > licensing expert so I'm assuming someone on this list knows more... So > if you say this is incompatible with ASF then I guess all discussion of > me submitting patches etc. ends here? For inclusion in Ivy, I'm afraid so. > Then there is the problem of maintenance... to maintain the code you need > > commit rights, and we can't grant commit rights on the basis of only one > > contribution. So you'd need to provide patches to maintain the code... > > Moreover, if you finally give up on maintaining the code, we (Ivy team) > > would have to maintain it. So we'd need to see how the code looks like, > how > > is it tested and documented. > > > Understood. > > What I can recommend since you have the approval of your technical > director > > is to open a JIRA issue and attach a patch to our code base with your > svn > > resolver implementation. Please remember to check the box about > transfering > > rights to the ASF, so that we can apply the patch if we agree on that. > Then > > even if we do not include your patch, any user in the community would be > > able to use it (as long as you use the ASL), so it isn't lost. > OK, would you still want me to do this if I use SVNKit? Let's say that even if there is no chance to get included it's the poor man way to share your code. But using another hosting solution (see below) is a better solution. > Another > > option would be to contribute it to ivytools where there is the first > > version of a svn resolver. The problem is that ivytools is not > maintained > > anymore, and thus I doubt it would gain much momentum over there. > > > True. I could try contact the people behind ivytools and see if there is > anyone there willing to get it going again for Ivy 2.0. Another option I > guess would be releasing it somewhere else separately..... Contacting people behind Ivy tools is very simple: you're talking to one :-) If you give me your sourceforge id I can give commit rights on ivytools. The problem is that the site is not maintained, so I don't know if it's a good idea unless you are willing to do some work for the site too. If you prefer to release it separately, this is a pretty good option too. Keep us informed anyway, and we will at least add a link to your resolver in the Ivy links section if you host it somewhere. Xavier Adrian > > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
