On Jul 30, 2011, at 11:58 AM, Benson Margulies wrote: > On Sat, Jul 30, 2011 at 2:52 PM, Ralph Goers <[email protected]> > wrote: >> The dual license makes a difference because if someone wants to make a >> change that Aether doesn't want it can easily be incorporated here since the >> original class could be taken and modified as necessary. > > Ralph, I'd like to really understand this, so I'm going to waste > everyone' eyeballs on being picky. > > Assume that AEther started out as a substantive, working, code base > inside Apache, and then, subsequently, it had forked out. I see how > your procedure works in that case, since either fork could cherry-pick > from the other. What I don't follow is how it helps given the facts on > the ground. There is no code base inside Apache that is close enough > to AEther to absorb patches, and there never will be, unless Sonatype > grants it. So I don't understand the logic whereby a return to a dual > license helps us, unless it also comes with an SGA. What am I missing?
Let's say you want to change how a class in Aether works. You can take the class from either in modify it if it is under the Apache license. You can then place it somewhere in Maven. After that, it is a matter of figuring out how to wire the modified class so it is used instead of the original. Under the EPL we would have to write a new class from scratch. Just so you know, my vacation is coming to an end and I will be on airplanes sporadically today so if you have other questions you'll have to be patient. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
