-
Notifications
You must be signed in to change notification settings - Fork 9
[Vote ended on 2022-05-23] Adopt process for renaming collections included in Ansible #102
Comments
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
I don't like removing the redirects so soon, but I'll vote +1 overall. |
Ok, we have 5 x +1 from SC members, and 1 x +1 from community members. That means the quorum was not reached :-( @ansible-community/steering-committee maybe we can still get some votes today to figure out whether this is acceptable or not? If there are no further votes I'm afraid this motion has failed. |
+1 |
+1. TY for bringing this forward |
+1 |
Thanks for the additional votes! Counting votes: 8 x +1 from Steering Committee, (markuman, felixfontein, mariolenz, Andersson007, jamescassell, gundalow, cidrblock, briantist), 1 x +1 from community (rainerleber) Could someone please confirm this? |
I've counted the same, so I confirm. |
Cool, thanks! Then I'll merge the PR and close this as resolved. |
Summary
I propose adopting the process for renaming collections included in Ansible as described in ansible-community/ansible-build-data#121. This means, merge that PR, and (as a first case) use it to handle the community.sap → community.sap_libs rename.
(Background: #98)
Please vote with +1 for adopting the new process, or -1 for not adopting it. The deadline is in one week since we then have a chance to still use this process for the SAP collections before Ansible 6 feature freeze.
(CC @rainerleber)
The text was updated successfully, but these errors were encountered: