skywalking-eyes compatibility issue with some "Weak Copyleft" Licenses #11391
Replies: 3 comments 8 replies
-
Hi, Catalog B in the ASF means it is usually acceptable as the runtime dependency, but sometimes with some conditions. @kezhenxu94 What do you think we accept this as a compatible list? Or add an additional accept list for the end users? |
Beta Was this translation helpful? Give feedback.
-
What do you think if we add a new section |
Beta Was this translation helpful? Give feedback.
-
Thanks @Two-Hearts for the contribution. The PR apache/skywalking-eyes#171 is merged so I think we can close this discussion. @kezhenxu94 @wu-sheng Does skywalking-eyes have a plan to release a new version recently? |
Beta Was this translation helpful? Give feedback.
-
Hi team,
I am a maintainer from the CNCF Notary Project. We are using skywalking-eyes to detect non-compliant licenses in a few repositories.
After the skywalking-eyes version was upgraded from v0.4.0 to v0.5.0 by dependabot in a PR, we noticed the CI check failed due to a dependency's license MPL v2.0 is not in the skywalking-eyes compatibility list, see the detailed logs for context.
According to ASF 3RD PARTY LICENSE POLICY, MPL v2.0 may be accepted in a few conditions although it is under the "Weak Copyleft" Licenses.
Is it acceptable to add MPL v2.0 to skywalking-eyes compatibility list?
Maybe MPL v2.0 is not the only case for this kind of issue. To make license check policy configurable and flexible, is it possible to add a new section to the skywalking-eyes compatibility list for Category-b, which makes it configurable to "Weak Copyleft" Licenses?
If not, do you have any suggestions on mitigating the CI failing issue?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions