Hi Geir, On Mon, 2005-11-07 at 06:44 -0500, Geir Magnusson Jr. wrote: > On Nov 7, 2005, at 5:40 AM, Mark Wielaard wrote: > > On Sun, 2005-11-06 at 08:44 -0500, Geir Magnusson Jr. wrote: > >> Lets not count our chickens here. The LGPL policy is still in the > >> works, and may not allow anything but limited-time optional > >> dependencies, and no re-distrubution of LGPL-ed artifacts. > > > > But that is all we need for now don't we? > > No, because we want to be able to distribute complete tested > implementations of J2SE, right? :)
It is a start don't you agree? And one that would help us forward now. In the end we want to combine all the projects to make up a complete free J2SE replacement. That will indeed take more work and cooperation. But this seems like a nice start. > > Of course we should lobby for more freedom. > > I won't take that bait :0 I am not sure I am following you. If it is the word freedom, then replace it with flexibility. What we want if that the board allows us to combine and distribute the various projects. The above is a good first step since lots of people want to use and depend on LGPL-covered works. Over time we would like to have more compromises of course. Just like we compromised with GNU Classpath and added an exception statement to the GPLv2. If we could get something similar for the ASL to make it compatible with the GPL for the harmony code covered by the ASLv2 that would be ideal imho. > > But the main thing is to make sure there are no roadblocks for > > collaboration between the different free sofware projects. > > Indeed! That's why I'm so certain that interoperability of modules > and componentization will be so beneficial for us. Sure, but then we must be sure that we can combine these modules and components into a larger work in a way that makes both the GNU and Apache communities happy. > > If the board really refuses to allow us to distributed a fully > > integrated system containing all parts we can always put the whole > > collection up somewhere else. But we will cross that bridge when we > > get there. Lets first put together the whole system. > > Someone can always take the various works and post somewhere else, > but we'll distribute what we test, and we won't be able to use Apache > TCKs to test something we're not distributing from here. Then lets make sure we can all distribute it from here. But also think carefully whether we are a development group or a distributor. Most GNU/Linux distributions are much better at shipping stuff then we development communities. Cheers, Mark -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/
signature.asc
Description: This is a digitally signed message part
