Digging into Saxon, I’m stuck on the CERN NOTICE. We are going to have to ask on legal-discuss to get approval to use Saxon. I will open a LEGAL JIRA shortly.
A CERN license for something called COLT got approved, but instructions seem to be to ask for any other CERN code. I think we have the option of not bundling Saxon and downloading it as part of the install if we want to go down that road. IMO, it could be the quickest way to get out the door. I don’t know how often these smaller downloads fail during the install vs the big ones like the main package or the AIR SDK. -Alex On 12/29/14, 1:43 PM, "Alex Harui" <aha...@adobe.com> wrote: >Other than Saxon, I think I’m mostly done fixing up LICENSE and NOTICE so >that it matches the way we packaged prior releases. I hope to finish >Saxon and check it all in tonight or tomorrow. Then it needs review and >we might find a few more things we need to change. > >Then we need to decide whether we want the install scripts to prompt folks >to accept Saxon or not, and whether we should continue to have folks >approve OSMF and SWFObject like we currently do. Again, if we guess wrong >here, I can’t imagine it would be seen as putting the foundation at risk, >but maybe we’ll get lucky and someone will provide an answer or Om will >remember some conversation about it when creating the Installer. > >-Alex > >On 12/29/14, 1:15 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > >>Hi, >> >>> Do you have the cycles to create a suggested fix for both? >> >>As I said I will have later this week, but Alex is currently looking into >>it and would need to check in what he's done first I think. >> >>One of my earlier posts in this thread had details on what the likely >>changes would be. >> >>Thanks, >>Justin >
