New collection review: community.dns #22
Replies: 5 comments 10 replies
-
Thank you for your submission, @felixfontein. The items in the checklist can be in one of the following states:
Feel free to ask any questions and provide feedback. Thanks in advance for your understanding and patience. For details about the following points, refer to the Collection Requirements. Every comment should say whether the reviewer expects it to be addressed, or whether it's optional. Public availability and communication:
Standards and documentation:
Collection management:
Tests:
|
Beta Was this translation helpful? Give feedback.
-
Public availability and communication:
Standards and documentation:
Collection management:
Tests:
|
Beta Was this translation helpful? Give feedback.
-
@felixfontein thanks for the submission! I think some (or all) of the imports mentioned above can be added intentionally. Generally the collection's state LGTM for inclusion. |
Beta Was this translation helpful? Give feedback.
-
+1 for inclusion |
Beta Was this translation helpful? Give feedback.
-
This collection will be included in Ansible 5: ansible-community/ansible-build-data#70 |
Beta Was this translation helpful? Give feedback.
-
The community.dns collection provides tools for working with DNS:
Ansible Galaxy: https://galaxy.ansible.com/community/dns
GitHub: https://github.com/ansible-collections/community.dns
Issues Tracker: https://github.com/ansible-collections/community.dns/issues
GitHub Handles: @felixfontein
Is the collection part of Automation Hub: No
I think we meet the Collection Requirements.
Note: the collection contains the Public Suffix List, which is licensed under Mozilla Public License (everything else in the collection is GPL v3+). It does not not use Exhibit B of the MPL, which prevents usage with other licenses such as GPL, so I think it should be OK to include this in Ansible (but IANAL).
Beta Was this translation helpful? Give feedback.
All reactions