dave2wave commented on issue #153: URL: https://github.com/apache/tooling-trusted-release/issues/153#issuecomment-2967493425
While we do have heuristics using a `.rat-excludes` fits with use of RAT. It could also be used with the internal check. The question to ask is how to provide this file. It could be a url as part of project configuration, or it could be a special file uploaded with the release. I think we need to discuss the name so that it is proper. The exclude could be about two types of files: 1. Files or directories where files do not support license headers. These automatically follow the LICENSE file and this is allowed. 2. Files that have an incompatible license. These should not be in an excludes, but there might be reasons to allow these in a convenience binary. I think this pattern must be discouraged, but I've seen this be abused. We do have a few implicit excludes which should be combined with a project excludes like LICENSE, NOTICE, and we need to add DISCLAIMER. These have special checks. -- 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 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
