[Active vote] Include ansible.mariadb collection in the Ansible community package

Project Discussions
,
1

The context:

  • It was decided to clone ansible.mariadb from ansible.mysql [RESOLVED] Should ansible.mysql be split into separate MySQL and MariaDB collections? and continue mariadb related development in ansible.mariadb
  • ansible.mariadb 6.0.0 has been released and published on Galaxy Ansible Galaxy
  • ansible.mysql is included in the package. No changes were made to its clone (ansible.mariadb) that could violate the inclusion requirements; no changes to code were made except of removal of 3 modules that don’t support MariaDB. Only name change related changes were made Pull requests · ansible-collections/ansible.mariadb · GitHub
  • ansible.mysql hasn’t been affected at all, it still supports both MySQL and MariaDB. All incompatible changes will be made properly via major releases in future.
  • maintainers will be the same as for ansible.mysql + eRadical

As it’s basically a clone and a continuation of ansible.mysql which is already included, thus, I think this collection doesn’t have to go through the standard inclusion process and can be included directly.

The inclusion PR Add the ansible.mariadb collection to Ansible 13 and 14 by Andersson007 · Pull Request #705 · ansible-community/ansible-build-data · GitHub

Starting a vote here to include it bypassing the standard inclusion review process.

2 Likes
2

The poll ends on July, 20th
@SteeringCommittee please vote

[Steering Committee vote] Include ansible.mariadb in the Ansible community package
  • Yes (bypass the standard inclusion review process as it’s a clone of an included collection and it’s well maintained)
  • No (go through the standard inclusion process)
0 voters
[Community vote] Include ansible.mariadb in the Ansible community package
  • Yes (bypass the standard inclusion review process as it’s a clone of an included collection and it’s well maintained)
  • No (go through the standard inclusion process)
0 voters
1 Like