# Proposal: Closing the Ansible Network Slack instance

**URL:** <https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993>\
**Category:** Project Discussions\
**Tags:** mindshare, community-wg-nextmtg, network\
**Created:** [July 22, 2025, 5:42pm UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993 "2025-07-22T17:42:51Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 22, 2025, 5:42pm UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/1 "2025-07-22T17:42:51Z")

</div>

Hi folks

Following on from [Proposal: Consolidating Ansible discussion platforms](https://forum.ansible.com/t/proposal-consolidating-ansible-discussion-platforms/6812), we are considering what to do with the Ansible Network Slack instance (which you’ve likely never heard of).

As the Forum has critical mass of people, and the Ansible Network slack instance is very quiet, we are proposing archiving the Slack instance, and bring everybody to #network part of the Forum

## Poll

_Poll ([view on site](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/1))_

## What do you think

The Slack and Forum is here for our Community, so please do let us know what you think

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 23, 2025, 3:36am UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/2 "2025-07-23T03:36:21Z")

</div>

[@network-wg](https://forum.ansible.com/groups/network-wg) [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) new vote on future it the Ansible Network Slack instance.  
Thanks in advance for your vote and any ideas how we can better support Network Automation.

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 23, 2025, 3:38am UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/3 "2025-07-23T03:38:20Z")

</div>

The last message in the `general` channels in the Ansible Network Slack channel was in May, and hasn’t been answered.

There is more discussion in the `devel` channel, though that’s because that channel has a bridge with the Network Matrix channel.

---

<div class="post-metadata">

**Author:** ![Christophe\_F](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/christophe_f/32/8270_2.png) [@Christophe\_F](https://forum.ansible.com/u/Christophe_F)\
**Post date:** [July 23, 2025, 6:02am UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/4 "2025-07-23T06:02:57Z")

</div>

Hi  
Never heatd of Ansible slack instance but it’s exactly what I was looking for…

Network Automation Forum and other Network communities are really active on slack and are very useful, maybe ansible network slack instance just lacks communication on it ?

What is the url to join ? It would certainly have more success with communication of this instance through other slack communities

But also having different place for the same purpose is not very good, we have to concentrate people on the same place… and nowadays slack seems more convenient

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [July 23, 2025, 8:55am UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/5 "2025-07-23T08:55:26Z")

</div>

Personally, I’m in favor of Forum (that has worked great so far), so +1 to closing the channel.  
Fragmentation (esp. with ghost towns) is not good.

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [July 23, 2025, 3:37pm UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/6 "2025-07-23T15:37:15Z")

</div>

I don’t want to vote since I’m neither active on Slack nor into networking. So the correct answer (“never heard of it”) might give a wrong impression.

That said, I think we should focus on the forum. Is this channel run by RedHat employees? I’m sorry if this is a stupid question, but since I’m not active on Slack I don’t know how it works.

I guess we can’t (and shouldn’t!) forbid people to open communication channels about Ansible on Slack, or reddit or serverfault or whatever. But we™ should focus on the forum, IMHO.

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 24, 2025, 11:23am UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/7 "2025-07-24T11:23:53Z")

</div>

## Ansible Network Slack statistics

I’ve just pulled some stats from the Ansible Network Slack instance, since 1st Jan 2025

### Where the communication is happening

- 86% Direct Messages
- 12% Private channels
- 2% pubic channels

### Activity

- Logged in users 26-56/month
- Users posting: 5-12/month

This is a fragmented community, away from the rest of Ansible. I’m suprised to see that DMs (Direct Messages) are 86% of this years traffic. It’s good that people can directly message, though nobody else benefits from that discussion.

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [July 27, 2025, 11:31pm UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/8 "2025-07-27T23:31:40Z")

</div>

Kill it with fire 🔥

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 30, 2025, 6:57pm UTC](https://forum.ansible.com/t/proposal-closing-the-ansible-network-slack-instance/43993/9 "2025-07-30T18:57:47Z")

</div>

Hi folks,  
Thanks to those that have provided their input.

When I did a `@here` (notify all) in the `#general` channel in Slack last week, the only responses were

- 2x 👍
- 1x person saying that Slack was good for DMs.

From the poll above, 4 people said they used to use Ansible Network Slack, though don’t anymore.

So it seems like nobody till miss that Slack instance.

What can we do to give Network Engineers the best experience on the Ansible Forum?

As a Slack Admin, I can email all the members of the Slack instance, though before that I’d like to check if there is anything we can improve first.

@Akram @dafmendo @zachp As previous users of Network Slack, what can we do to improve the Forum even more. How would you promote the Forum to those still on Slack?
