Is there any way for the RAT tool to acknowledge the "minified" ASF header that is approved for use in .js (and other files)?
See "short form" approved here: https://www.apache.org/legal/src-headers.html Kind regards, Matt From: "Ying Chun Guo" <guoyi...@cn.ibm.com> To: dev@openwhisk.apache.org Date: 02/12/2018 08:18 AM Subject: Re: Release policy compliance: Adding license headers and the excluded files Hi, Bertrand Thank you for the inputs. My original thought was to maintain different Rat exclusions for different repo because they may have different files. If we want to maintain a unique version, we may need to collect all exclusions in all the repo together and maintain a set. Sometimes it's difficult to tell whether a file shall be excluded or not. Hope you can help review after the collection is ready. OpenWhisk has a repo in github to track release documents and scripts. Here it is: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Drelease_blob_master_README.md&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS478q2gZlAJj4Zw&m=tuRJI4eVUHlqHACnIGwvLgDqy1D9dIaSeLjOME3KJJg&s=RqfPKNiDPwlE1yljo6i5RctCRB6jXLLbQ5gickneycE&e= . I think these information can be documented here: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Drelease_blob_master_docs_work-5Fitems.md-232-2Dverify-2Dthe-2Dcompliance-2Dof-2Dthe-2Dsource-2Dcode-2Dopen-2Dissue&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS478q2gZlAJj4Zw&m=tuRJI4eVUHlqHACnIGwvLgDqy1D9dIaSeLjOME3KJJg&s=t34yGdwcAE-qLfsKcS0ueeVqUAffslBtsP_kxQmK2fk&e= . Best regards Ying Chun Guo (Daisy) -----Bertrand Delacretaz <bdelacre...@apache.org> wrote: ----- To: dev@openwhisk.apache.org From: Bertrand Delacretaz <bdelacre...@apache.org> Date: 02/09/2018 06:41PM Subject: Re: Release policy compliance: Adding license headers and the excluded files Hi Daisy, On Thu, Feb 8, 2018 at 1:24 PM, Ying Chun Guo <guoyi...@cn.ibm.com> wrote: > ...I use Apache Rat to audit license headers. I use wskdeploy repo as the trial repo. > I reported an issue ( https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Dwskdeploy_issues_716&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o&m=m3ygIAacPw2tdx9MhWLfpLzsW1V32RO3z5g6A2YFWCo&s=zY3fWnnLVXjHDVQvYS73Db0ljWoQg4OaYlqNm1mbjWE&e= ) > to wskdeploy including a report generated by Apache Rat. In the report, all the files > with unapproved licenses will be listed... This sounds great. What you want basically is that for any build that's meant to create a release: -Rat should run -The build should fail if Rat reports any anomalies -The Rat exclusions should ideally be defined in the same way for all modules, for consistency -The Rat exclusions should be commented to indicate why each exclusion (or family of exclusions) is here I think this should be documented in a "coding standards" or "release management" page, does OpenWhisk have this already? -Bertrand (with my incubation mentor hat on)
