On 7/7/16, 11:16 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>> ... but where the Mavenizer causes the >> distribution Adobe artifacts, Adobe Legal will want to review how it >>looks >> as well before it goes final. > >So they will want to review release candidates and the like? No, there is no release candidate pending at this time. We are making changes during development like any other change to doc or code. Adobe is on holiday this week and I expect to hear from my legal contacts early next week. There are plenty of other bugs to fix before we cut a release candidate so we have time. > >> Do we cause the downloading of Adobe artifacts in TDF and our other >> non-SDK releases? > >Yes. Looks like AIR is download in flex-asjs, flex-falcon, flex-sdk and >npm-flex. The above are SDK releases. I asked about TDF and other things like Squiggly. > >There’s also probably information on how to do so in READMEs or on the >Wiki that may or may not need to be changed in order to comply with Adobe >legal. If you know of them, please list them so we don't forget them. > >Should we just assume unless you change something and/or someone from >Adobe legal asks that everything is compliant? Also that the legal risk >is yours alone as the information has not been shared with the PMC? What >would happen in the event (for what ever reason at some point in the >future) that you are no longer involved in the project? I'm not sure I understand your line of questioning. Don't we make the same assumptions for any other third party, like the Flat fonts, for example? If their legal team contacted someone besides me and asked for a change, wouldn't a similar sequence of events take place? The information was shared not only with the PMC but with the public in my earlier email and this commit. -Alex
