You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm in the process of packaging this Ansible Collection for Fedora and RHEL, however our scanner has flagged that the plugins/module_utils directory is BSD-2-Clause unlike the rest of the repository. This doesn't block us packaging it, as we can just specify both BSD-2-Clause and GPL-3.0, but it would be easier if the same license covered the entire repository. Is there a reason this license mixture has been chosen?
@thebeanogamer, I believe the reason behind the dual licensing was due to a past requirement in the Ansible Collection Inclusion Requirements that needed all module_utils code to be licensed under BSD-2 whereas modules needed GPLv3. I believe this restriction has been eased since then and may be it will be good for us to revisit the new licensing requirements to see if we can make this simpler. Thank you for bringing this to our notice 👍
How can the team help?
I'm in the process of packaging this Ansible Collection for Fedora and RHEL, however our scanner has flagged that the
plugins/module_utils
directory isBSD-2-Clause
unlike the rest of the repository. This doesn't block us packaging it, as we can just specify bothBSD-2-Clause
andGPL-3.0
, but it would be easier if the same license covered the entire repository. Is there a reason this license mixture has been chosen?Details: ?
https://bugzilla.redhat.com/show_bug.cgi?id=2284297#c2
The text was updated successfully, but these errors were encountered: