Tricky Ozone Licensing questions (LGPL? or GPL?)

Folks,

I know the following questions are directed to Ozone-db's
owners/maintainers, but I thought someone else would find 
the answers useful. Here goes.

I understand the licensing agreement that Ozone-db has put 
forth and I have read the FAQ section about this topic. But 
I have a situation that might complicate and/or add 
confusion to its explanation.

What if I want to fix/add work to the Ozone-db Core (that I 
also want to make public) that has not yet been 
incorporated/rejected by the Ozone-db sourceforge 
maintainers. Lets also say that I did not make any changes 
to Ozone-db API class files. Since Ozone-db requires the 
server side JVM to load both the Ozone-db jar and my API 
jar, I cannot separate (into two JVMs) the Ozone-db Core 
from my client API application [In keeping with GPL].

What is the ruling on this? I believe I understand GPL and
LGPL pretty well. I also know that the final ruling is up to
the persons(s) who own the code.

Is my only salvation- to lobby my fixes/changes into CVS and 
wait until they hopefully get added?

It is greatly appreciated if the folks in charge could make
a ruling on this. Viva Ozone!

Best Regards,

- Thomas



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click