So, nothing derived from those undisclosable sources can be in the source package: period.
As for the binaries, I am personally uncomfortable if you cannot even create a private download of those sources accessible to community members. However, I don't know how to translate my personal discomfort into policy. I will endeavour to get some advice. On Wed, Jan 23, 2013 at 10:36 AM, Masanz, James J. <[email protected]> wrote: > One goal is to have a binary that contains all resources, which can be used > to install cTAKES on a system that does not have an internet connection. > For now we can focus on a first Apache release that doesn't meet that goal, > while pursuing the question with legal. > If legal says we can't do have that kind of binary here, then in the future > we can consider if we will host such a binary on a different site. > > Regards, > James Masanz > >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] >> On Behalf Of Chris Douglas >> Sent: Wednesday, January 23, 2013 3:45 AM >> To: [email protected] >> Cc: [email protected] >> Subject: Re: [VOTE] Apache cTAKES 3.0.0-incubating RC5 release >> >> On Wed, Jan 23, 2013 at 12:47 AM, Jörn Kottmann <[email protected]> >> wrote: >> > No, the OpenNLP did not have any discussion about it with legal. We >> > just came to the conclusion that its not worth spending time on these >> > issues, when we can instead produce our own training data which is >> > compatible with the Apache license. >> >> Understood. Are the compatible training data synthetic? Would you >> recommend a similar course here? >> >> James, is there a reason the models need to be distributed through Apache? >> Your time is your own, but going through legal could delay your release. - >> C >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
