Re: [ansible-devel] Merging GPLv3 and AGPL licensing in a module development

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 mo

Re: [ansible-devel] Merging GPLv3 and AGPL licensing in a module development

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. -- ---

Re: [ansible-devel] Merging GPLv3 and AGPL licensing in a module development

Hi Felix, Thanks for the help. Can you please walk me through the licensing requirements note on this page ? I think the note section is stating the opposite. On Wednesday, 27 April 2022 at 15:01:06 UTC+3 Feli

Re: [ansible-devel] Merging GPLv3 and AGPL licensing in a module development

Hi, > ansible requires every module to be licensed under GPLv3 and > mod_utils under BSD. that is not correct. While the ansible-test sanity checks look for such copyright notices, you can also decide to ignore these sanity check failures. Especially module_utils are often also GPLv3+ licensed in

[ansible-devel] Merging GPLv3 and AGPL licensing in a module development

Hello everyone, I and my team are writing an ansible collection for MAAS which we hope to share with everyone. We are using python-libmaas library to communicate with the MAAS API. python-libmaas is being developed under GNU AGPL and ansible requires every module to be licensed under GPLv3 and