As Brian mentions, we had a default rule in the ansible/ansible repo that module_utils had to be BSD, but in some circumstances we allowed them to be in other licenses when their source or dependencies required it. The reason for the BSD license was to not force every module that imported those module_utils to inherit the GPL license, for authors that wanted to distribute their module under a different but compatible license. But that decision to use BSD for module_utils doesn't necessarily apply outside the scope of ansible/ansible.
If you are using python-libmaas in module_utils, they would have to inherit that license as well. Licensing is tricky when it comes to software, so it's always wise to consult a lawyer. The FSF interprets the GPL to mean that anything that imports a GPL library is a derivative work, and must inherit the GPL license. On Wed, Apr 27, 2022 at 8:55 AM Brian Coca <bc...@redhat.com> wrote: > To clarify, this requirement was part of the ansible package up to > version 2.9 and the split to collections and it is still a requirement > for ansible-core, but not for the current ansible package which is > community maintained and includes ansible-core + a set of selected > collections. > > > > -- > ---------- > Brian Coca > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-devel/CACVha7eUw9dYV%2Bd1GfY%2BPMDepfo-4FaKLhvtKM4WnUUF3XZTLA%40mail.gmail.com > . > -- Matt Martz @sivel sivel.net -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CAD8N0v_m4YOU9n9WyGZ8n9jcEnbjA%3DrdwbkvfFMi1pYHsqPEJw%40mail.gmail.com.
