dave2wave opened a new issue, #199: URL: https://github.com/apache/tooling-trusted-release/issues/199
To properly simplify license checks there are certain filetypes or suffixes that should fall into cases: 1. A license header breaks the file because comment lines are not allowed. Examples include `csv`. The list long, but I don't see an exhaustive list from legal. 2. A short form license is allowed. 3. The file is listed in an excludes file in the source repository. (which we do not have.) 4. The file is listed in an excludes block in the `pom.xml` or other build file. Please see https://www.apache.org/legal/src-headers.html#faq-exceptions I think we should consider the following: 1. Add an excludes list to the Project (or Product) metadata. 2. Allow updates to the excludes list during the Candidate stage. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org For additional commands, e-mail: dev-h...@tooling.apache.org
