Community messaging

[gundalow]

• Write overview doc Docs: Collections overview #3
• Reddit https://www.reddit.com/r/ansible/comments/f6d4ut/community_update_on_ansible_collections/
• Ansible Twitter https://twitter.com/the_gundalow/status/1230170710900977664
• Partner email - Done
• Changes impacting Contributors
• Google Group: ansible-announce - Subset, in particular running from devel. link to ansible-project & Reddit
• Google Group: ansible-project
• Google Group: ansible-devel
• Google Group: ansible-outreach
• Update Collections Blog?
• Twitter Did you know that the @ansible devel branch is about to get a lot smaller (wordsmith to be much scarier)

[cpitre]

I consider the early information provided here as beneficial in staying informed of the changes and the process involved. Being a co-organizer to a couple of Ansible meetups, I'm looking forward to relaying what I learn here to future meetings and meetup boards. Do we have a way to spread this info out to the other Ansible meetup co-organizers? Or is that already covered via the ansible-outreach channel? Thanks!

[gundalow]

@cpitre Thank you for your message.
For meetup I think the main points would be:

• Collections are coming
• The devel branch will be changing, so if you use that, consider the impact.
• mention the documentation we have.

If there any any questions that you, or the meetup members have please let me know and I'll get the FAQ updated.

[gundalow]

@phips thoughts on Twitter Did you know that the @ansible devel branch is about to get a lot smaller? (wordsmith to be much scarier) and link to https://github.com/ansible-collections/overview/edit/master/README.rst

[gundalow]

Collections have been a thing for a while, so closing this.