sbp commented on issue #173: URL: https://github.com/apache/tooling-trusted-release/issues/173#issuecomment-2976682845
[According to the ASF release policy](https://www.apache.org/legal/release-policy.html#notice-file), there must be a `NOTICE` file at the top level of any source distribution: > For source packages, `LICENSE` and `NOTICE` MUST be located at the root of the distribution. If you need `airflow-core/NOTICE` to be present as well, I assume that's okay, because the release policy does not say that multiple `NOTICE` files are forbidden. Perhaps we should have that clarified by those who set ASF policy. By the way, `airflow-core/NOTICE` contains messages for Hue and Chakra UI. The Chakra UI message is, I think, unnecessary, [according to the `LICENSE` and `NOTICE` guide](https://infra.apache.org/licensing-howto.html#mod-notice), since Chakra UI is MIT licensed: > elements such as the copyright notifications embedded within BSD and MIT licenses [do not need to be duplicated](https://issues.apache.org/jira/browse/LEGAL-59) in `NOTICE` Whereas, the case of Hue looks more complicated because it is Apache 2.0 licensed and has [an enormous NOTICE file at a non-standard `NOTICE.txt` location](https://github.com/cloudera/hue/blob/master/NOTICE.txt). I think that if you're using Hue then you'd potentially need to duplicate all of `NOTICE.txt` in your own `NOTICE`, in the root at least and perhaps in the `airflow-core` subdirectory too. In ATR we're probably not going to go past the file existence and simple content checking, at least for alpha. Please do keep the feedback about checks coming, because we'd certainly like to get them as accurate and _developer friendly_ as possible. We can't set policy, though! We can certainly start discussion if policy needs to be changed or clarified, and I'd like to do that even if this case regarding multiple `NOTICE` files. -- 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
