> On Aug 5, 2013, at 11:54, Manuel van den Berg > <[email protected]> wrote: > > Thx Matt for pointing that out. So that brings a number of options for any > such dependency: > - Replacing the dependency with an alternative with an appropriate license > - Putting the dependency outside the Apache project as a kind of plugin > (which is what Kasper proposed, I think) > - Negotiating a more liberal license with the copyright holder. > > Correct?
Correct > > -- Manuel > >> -----Original Message----- >> From: Matt Franklin [mailto:[email protected]] >> Sent: Monday, August 05, 2013 14:04 >> To: [email protected] >> Subject: Re: Incubator PMC/Board report for Aug 2013 ([ppmc]) >> >> On Mon, Aug 5, 2013 at 5:10 AM, Manuel van den Berg < >> [email protected]> wrote: >> >>>>> Correct. We cannot produce any kind of release that includes GPL >>>>> code or binaries. >>> >>> Probably a silly question from my side. >>> I see the point that GPL dependencies cannot be part of an Apache >>> project, because of the legal implications of the GPL license. >>> But isn't LGPL different in this respect? Doesn't the "L" in LGPL >>> allow us to ship a LGPL'ed library in binary form in MetaModel? >> >> "The LGPL is ineligible primarily due to the restrictions it places on larger >> works, violating the third license criterion. Therefore, LGPL-licensed works >> must not be included in Apache products." >> >> This comes from the legal page on licenses; a great resource: >> http://www.apache.org/legal/resolved.html >> >> >>> -- Manuel >>> >>>>> >>>>>> >>>>>> An option could be to NOT include the MetaModel-Access module in >>>>>> the Apache codebase at all. Instead let us at Human Inference >>>>>> release it as a third party module. We already do this with the >>>>>> SAS module [1] and will start doing it with the dBase module [2] >>>>>> , for the same reason. This is obviously not an attempt from our >>>>>> side to exclude these modules from the apache space, but just >>>>>> because we don't control that licensed code and we would like to >>>>>> retain (in some form) the wide connectivity of MetaModel, also after >> moving to Apache. >>>>> >>>>> It is an acceptable work around though it would be better if we >>>>> could refactor to a non-GPL dependency that accomplishes the same >> function. >>>> >>>> Agreed, but for Access connectivity I don't think there really is >>>> such a >>> thing. >>>> Of course there is the good ol' Sun ODBC-JDBC driver that makes >>>> "some >>> kind >>>> of" connectivity possible, but my impression is that metadata >>>> support is horrible and we can't really make it work without. >>>> >>>>> >>>>>> >>>>>> [1] Also LGPL; SassyReader - http://sassyreader.eobjects.org [2] >>>>>> Also LGPL; Recently made a fork of that module from the old >>>>>> MetaModel project, but compatible with the new Apache namespace >>>>>> at http://eobjects.org/svn/DeeBaseReader/trunk/ (does not have a >>>>>> website or something like that yet). >>>>>> >>>>>> 2013/8/4 Dave Fisher <[email protected]>: >>>>>>> There should be some discussion about IP clearance in advance >>>>>>> of a first >>>>>> release. >>>>>>> >>>>>>> Has the podling discussed how to properly handle GPL >>>>>>> dependencies like >>>>>> Jackcess? These will need to be optional in an Apache Release. >>>>>>> >>>>>>> Regards, >>>>>>> Dave >>>>>>> >>>>>>>> On Aug 4, 2013, at 12:22 AM, Henry Saputra wrote: >>>>>>>> >>>>>>>> Any volunteer to prepare report this month? >>>>>>>> >>>>>>>> Arvind's recommendation is great but we will try baby steps to >>>>>>>> prepare >>>>>> the >>>>>>>> complete report. >>>>>>>> >>>>>>>> We just need to say that all INFRA work is done and we are >>>>>>>> start >>>>>> ramping >>>>>>>> up on development. >>>>>>>> Also website and wiki is up and running so people can start >>>>>>>> visiting to >>>>>> get >>>>>>>> more info. >>>>>>>> >>>>>>>> - Henry >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Aug 2, 2013 at 9:20 AM, Marvin <[email protected]> >>> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Dear podling, >>>>>>>>> >>>>>>>>> This email was sent by an automated system on behalf of the >>>>>>>>> Apache Incubator PMC. >>>>>>>>> It is an initial reminder to give you plenty of time to >>>>>>>>> prepare your quarterly board report. >>>>>>>>> >>>>>>>>> The board meeting is scheduled for Wed, 21 August 2013, >>>>>>>>> 10:30:00:00 >>>>>> PST. >>>>>>>>> The report >>>>>>>>> for your podling will form a part of the Incubator PMC report. >>>>>>>>> The Incubator PMC requires your report to be submitted 2 >>>>>>>>> weeks before the board meeting, >>>>>> to >>>>>>>>> allow >>>>>>>>> sufficient time for review and submission (Wed, Aug 7th). >>>>>>>>> >>>>>>>>> Please submit your report with sufficient time to allow the >>>>>>>>> incubator >>>>>> PMC, >>>>>>>>> and >>>>>>>>> subsequently board members to review and digest. Again, the >>>>>>>>> very >>>>>> latest you >>>>>>>>> should submit your report is 2 weeks prior to the board meeting. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> The Apache Incubator PMC >>>>>>>>> >>>>>>>>> Submitting your Report >>>>>>>>> ---------------------- >>>>>>>>> >>>>>>>>> Your report should contain the following: >>>>>>>>> >>>>>>>>> * Your project name >>>>>>>>> * A brief description of your project, which assumes no >>>>>>>>> knowledge of >>>>>> the >>>>>>>>> project >>>>>>>>> or necessarily of its field >>>>>>>>> * A list of the three most important issues to address in the >>>>>>>>> move >>>>>> towards >>>>>>>>> graduation. >>>>>>>>> * Any issues that the Incubator PMC or ASF Board might >>>>>>>>> wish/need to be aware of >>>>>>>>> * How has the community developed since the last report >>>>>>>>> * How has the project developed since the last report. >>>>>>>>> >>>>>>>>> This should be appended to the Incubator Wiki page at: >>>>>>>>> >>>>>>>>> http://wiki.apache.org/incubator/August2013 >>>>>>>>> >>>>>>>>> Note: This manually populated. You may need to wait a little >>>>>>>>> before >>>>>> this >>>>>>>>> page is >>>>>>>>> created from a template. >>>>>>>>> >>>>>>>>> Mentors >>>>>>>>> ------- >>>>>>>>> Mentors should review reports for their project(s) and sign >>>>>>>>> them off >>>>>> on the >>>>>>>>> Incubator wiki page. Signing off reports shows that you are >>>>>>>>> following >>>>>> the >>>>>>>>> project - projects that are not signed may raise alarms for >>>>>>>>> the >>>>>> Incubator >>>>>>>>> PMC. >>>>>>>>> >>>>>>>>> Incubator PMC >>>
