The Apache license for this project is in LICENSE.code, which means that wwhrd (and I suppose any other tool using go-license) cannot find it and so reports an unknown license (which is a failure). I've added an exception to my project but thought it worth raising since I don't like exceptions.
How would we feel about renaming LICENSE.code to just LICENSE (and leaving LICENSE.docs alone of course)? My argument for giving the code the "privileged" position is that automated tooling is going to primarily be interested in code (e.g. vendoring) while docs are not typically vendored or subject to automatic inclusion in quite the same way. Even more LICENSE.docs specifically only covers README.md and CONTRIBUTING.md which really aren't going to be vendored I think.
I can make the PR if we think this is a good idea.
As an alternative a symlink LICENSE → LICENSE.code would work too (I guess, I've not actually tried it)
There is an issue on go-license at ryanuber/go-license#16 but its from 2015 so I figured I would start here first.
The Apache license for this project is in
LICENSE.code, which means that wwhrd (and I suppose any other tool using go-license) cannot find it and so reports an unknown license (which is a failure). I've added an exception to my project but thought it worth raising since I don't like exceptions.How would we feel about renaming
LICENSE.codeto justLICENSE(and leavingLICENSE.docsalone of course)? My argument for giving the code the "privileged" position is that automated tooling is going to primarily be interested in code (e.g. vendoring) while docs are not typically vendored or subject to automatic inclusion in quite the same way. Even moreLICENSE.docsspecifically only coversREADME.mdandCONTRIBUTING.mdwhich really aren't going to be vendored I think.I can make the PR if we think this is a good idea.
As an alternative a symlink
LICENSE→LICENSE.codewould work too (I guess, I've not actually tried it)There is an issue on
go-licenseat ryanuber/go-license#16 but its from 2015 so I figured I would start here first.