normalize.css should be as simple as adding this in the LICENSE under the "For the bootstrap component", since that's what is in the bootstrap.css file.
/*! normalize.css v3.0.1 | MIT License | git.io/normalize */ And yes -- we neglected to remove the progress bar license from that file when we removed the source.. I'll have a PR shortly to address a couple of these. We'll chat again on Monday. Thanks, guys... On Fri, Jan 20, 2017 at 6:16 PM, Chris Lemmons <[email protected]> wrote: > I had the same thought. Dan and I have been running RAT ( > https://creadur.apache.org/rat/ ) and it runs clean against 1.8. However, > it gets tricked by things with incorrect apache headers. At one point, we > ran a "fix all" that added apache headers to our files. It was a little > aggressive and caught some dependent files. I don't currently know of a > tool that would find these files. > > For normalize.css, I'm a little confused. Unless I'm missing it somewhere > else, it's only included wholesale as part of bootstrap.css. We do need to > include the dependent license, though, he's right. I'm just not entirely > sure how one goes about finding similar issues. > > WebAppers was just an ordinary mistake. We stripped it from the repo to > avoid messing with the license and didn't get it removed from the LICENSE > file. > > I'm relatively confident that the MaxMind CC-SA is fine, but we probably do > need to run it past Apache Legal. > > Several of the issues he brought up are already fixed in master (due to > them not having the bad header, so they got found there), so that's easy to > backport. I'm hoping there's a tool for auditing, though. > > On Fri, Jan 20, 2017 at 6:01 PM Jan van Doorn <[email protected]> wrote: > >> Saw that… :( >> >> Do we have the same tools that Justin has to check these license things? >> If not, should we ask? >> >> I’ve been focusing on the functionality, not on this license stuff, but >> I’m willing to help out if that can make a difference? >> >> Rgds, >> JvD >> >> >> >> > On Jan 20, 2017, at 5:28 PM, Eric Friedrich (efriedri) < >> [email protected]> wrote: >> > >> > >> > ________________________________________ >> > From: Justin Mclean [[email protected]] >> > Sent: Friday, January 20, 2017 6:20 PM >> > To: [email protected] >> > Subject: Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC8) >> > >> > Hi, >> > >> > Sorry but it’s -1 (binding) as licensing issues and file headers >> reported last release that were not fixed. >> > >> > I checked: >> > - names include incubating >> > - signature and hashes are OK >> > - disclaimer exits >> > - LICENSE still has issues brought up from last release >> > - NOTICE is OK but has wrong year >> > - Source files have ASF header. A couple of files have them incorrectly. >> > - No unexpected binary files in release. >> > >> > While some of the issues brought up in last release have been fixed, >> there a large number that look like they haven’t. >> > >> > LICENSE Is still missing licenses for jQuery UI, normalize.css, angular >> loading bar, lz-string (which also incorrectly has an ASF header on it), >> pretty print (and which also has an incorrectly added ASF header) and >> modernizr. They may be others. Also the dual licensing for select2.js has >> not been dealt with and nor has the licensing of multiple font files. >> > >> > LICENSE also includes WebAppers Progress Bar which as pointed out last >> release is Category B and cannot be included in a source release. >> > >> > Re licensing around the MaxMind DB GeoLite2 Database [1] (under a CC >> share-alike license) also IMO needs to be sorted. I’m not sure it >> classifies as "unmodified media”, best to ask on legal discuss. >> > >> > Thanks, >> > Justin >> > >> > 1. ./traffic_router/core/src/test/resources/geo/GeoLite2-City.mmdb.gz >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >>
