On Mon, Jun 13, 2016 at 6:04 AM, Cazen Lee (JIRA) <[email protected]> wrote:
> > [ > https://issues.apache.org/jira/browse/QUARKS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327296#comment-15327296 > ] > > Cazen Lee edited comment on QUARKS-139 at 6/13/16 1:04 PM: > ----------------------------------------------------------- > > Hi [~dlaboss] :) > License issue is sensitive. > Further discussion is surely necessary, but I think we should proceed with > http://www.apache.org/legal/resolved.html if we remove the ext folder. > I guess the final schema of our license schema of repo will be one of the > following: > - Put together into one folder(Like Apache Spark - > https://github.com/apache/spark/tree/master/licenses) > - Put together into one file(Like Apache Hive - > https://github.com/apache/hive/blob/master/LICENSE) > > Please advise me if there is a better way. It would be a great help to me > :) > at help to me :) > > I have no experience with build systems, so don't know exactly what is easy to do or possible. I looked into licensing earlier and decided to postpone it until the build system is underway, so I guess now is a good time. The Apache rules on licensing are here http://www.apache.org/dev/licensing-howto.html. There is also a discussion on the list titled "License Review" in April where Justin gave some very helpful advice http://mail-archives.apache.org/mod_mbox/incubator-quarks-dev/201604.mbox/browser . Here's what I think needs to happen from a licensing perspective, but I'm new to this as well, so would appreciate advice from the experts: 1 - The Apache release is really a source code release. It has been recommended that our source release does not have non-Quarks code in it. So, I believe the work underway will pull in these packages as needed, and the source trees and licenses should be removed from ext, etc. as appropriate. 2 - If we want to provide jar files that people can download for convenience, we will need to have all the appropriate licenses for software we include in those jar files. 3 - It seems to me that it would be good if the build system could pick up the right license files, depending on what is to be included in that build. I'm not an expert, but it seems to me that we will need a directory where we keep appropriate licenses somehow and have the system pull the right info into one file or a directory of files in the jar distribution. We should have something like that at least for any jar files we might put up on the Apache site. I am willing to help gather the appropriate license and notice files, check them into the right directory or update build scripts, etc., if I know where to do that. I'm not sure the best way to set up a build system that handles these license files properly. It seems to me that we should at least have a build that creates the jars required to develop Quarks applications, with the appropriate license information in them (see http://www.apache.org/dev/licensing-howto.html#binary). Kathy
