I'm not quite sure I understand what steps you are planning to execute. Inline are my questions:
On 9/19/16, 4:37 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >- Missing text of MIT license for OpenFL. Fix add header to OpenFL and >add pointer to license text in LICENSE file. AIUI, parts of OpenFL code was used for portions of Matrix.as. We are not consuming their entire release artifacts or even entire files. Are you proposing to get the OpenFL community to accept headers on their source files by submitting a pull request on their repos and then replicating that header under the ASF header in Matrix.as? That's fine with me. And are you going to have the build download their LICENSE.md file from their repo and adjust our LICENSE to point to it? That's fine with me too. >- Missing copyright and full fix of Flat UI. Fix is to and add pointer to >license text in LICENSE file. Again, we are not consuming an entire artifact or file. Are you proposing to submit a pull request to the Flat UI folks to have them put a correct MIT license in their repo or README.md? And then adjust our build to download that and point to it from our LICENSE? That's fine with me. >- Patch file header issue. This is been discussed in another thread. >Several PMC members have suggested keeping the original license header. >Without the header this may be a licensing error, with the header it’s >just a documentation issue. Fix is keep original license header until >resolved. I've been unable to find a volunteer to donate the end result to CreateJS, but I still think that's the best course of action. Unless there are objections to donating these files to CreateJS, when my manager returns in about 3 weeks I will seek permission to make the donation so we can avoid debating this issue and maybe get some positive attention from the CreateJS community. >- I also like to bring the file more in line with policy and include >pointers to the actual license text as described here [9]. If we do the steps above, what else will need a pointer? And, if you have time, what policy document requires pointers? AIUI, the how-to is only a how-to and not a policy document and certainly allows copied of licenses. > >There are also some issues with the binaries which I’ve raised (including >in the 0.6 releases) but I’ve not had the chance to double check the >current ones. [5][6][7][8] Now is a good time to make adjustments. Let us know in a similar fashion what changes you propose. Thanks, -Alex > >Thanks, >Justin > >1. >https://lists.apache.org/thread.html/4d922a002ce5a680f26779b4f9102b69e2387 >ae3bdb747779ecdd993@%3Cdev.flex.apache.org%3E >2. >https://lists.apache.org/thread.html/013d7d58896d066bcb1f68d3e2935f5c25c83 >106c4a208f2e3a9c6d9@%3Cdev.flex.apache.org%3E >3. >https://lists.apache.org/thread.html/95ba7d9eb5a83cfa8411b933d00ba6fde4c8b >982feecc823e7fdbdc4@%3Cdev.flex.apache.org%3E >4. >https://lists.apache.org/thread.html/db1ec380d40d5685d50fe75430662a7e5c6cf >985752f82acf4bec0d1@%3Cdev.flex.apache.org%3E >5.https://lists.apache.org/thread.html/d136caad460a14426ac8edad4cab2a17b66 >fdaa17a6652615b575d50@1462088622@%3Cdev.flex.apache.org%3E >6. >https://lists.apache.org/thread.html/b903356e6441eb07d4884661f32c08646d45e >f21c1196b44866d2240@1458953301@%3Cdev.flex.apache.org%3E >7. >https://lists.apache.org/thread.html/bfd9c51786364580da0f52b9ba2d1861b425f >502c4bb4d68ea2e1977@1459236160@%3Cdev.flex.apache.org%3E >8. >https://lists.apache.org/thread.html/4a755aa87d0e83794b446876c2d63861ccc87 >f319a375c5f2092adb5@1459422236@%3Cdev.flex.apache.org%3E >9. http://www.apache.org/dev/licensing-howto.html#permissive-deps >
