Justin Mclean <jus...@classsoftware.com> wrote on 06/09/2019 09:50:12 AM: > > Sorry to be clearer re the short header issue I suggest you read > [1]. It may be used with mages, minified JavaScript or PDFs, that’s > not the case where it’s been used in your releases and this has been > pointed out several times. If there are other cases where you have > confirmed with legal-discuss that OK to use then please point them > out. While this is only a minor issue, but its vest to comply with > ASF policy. What I consider a little more serious is that issues nee > reoccurring after they have been pointed out. >
Hi Justin, We did discuss this issue on our dev list [2] and the guidance from our mentor [3] was that since we had documented the rationale for using short form headers in additional cases, what we were doing was acceptable. We have started including the URL of our project policy on header file formats [4] in all of our release vote emails to refer voters to the project policy on allowable forms of the license headers. --dave [1] https://www.apache.org/legal/src-headers.html#is-a-short-form-of-the-source-header-available [2] https://lists.apache.org/thread.html/bbec59cc560d446a4239627dcb463bc95fb98be5eb66d525f93e5ef1@%3Cdev.openwhisk.apache.org%3E [3] https://lists.apache.org/thread.html/6d25eb12cbfad05693cda729cff62b06ba45845ad53f5d1a67a2ac97@%3Cdev.openwhisk.apache.org%3E [4] https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md
