Collections added to the ansible tarball after the inclusion criteria were available

gistfile1.txt

2.10.0a1 => 2.10
================

cisco.nso
community.digitalocean
community.docker
community.fortios
community.google
community.hashi_vault
community.hrobot
community.kubevirt
community.mysql
community.okd
community.postgresql
community.proxysql
community.routeros
community.skydive
cyberark.conjur
dellemc.os10
dellemc.os6
dellemc.os9
gluster.gluster
hetzner.hcloud
infinidat.infinibox
mellanox.onyx
netapp_eseries.santricity:

Notes: many of the community.* collections are not tied to another company; they are maintained by users (of postgresql, for instance) rather than a company.  Notable exceptions would be fortios, routeros, and skydive (although, those companies aren't as big as cisco, dell, netapp)

2.10 => 3.0
===========

ansible.utils
community.sops
dellemc.openmanage
inspur.sm
kubernetes.core
sensu.sensu_go
t_systems_mms.icinga_director

Notes: ansible.utils was important for partners as, like netcommon, it provides reusable functions that Ifty's team expected many partners to want to use.

3.0 => 4.0
==========

dellemc.enterprise_sonic
hpe.nimble
netapp.azure
netapp.cloudmanager
netapp.um_info


I left ansible during the ansible-5 development cycle