Overview
The Ansible forum is organized a little differently from many forums you may have visited. It’s structured around tags rather than a deep category hierarchy. These tags aren’t just decorative flair as they often are on social media, though. They actually act more like “subcategories” — or, you can think of each tag as equivalent to a mailing list.
The main category on this site is Project Discussions. In this category, most tags represent _specific Ansible projects. “Watching” a tag is like joining that project’'s mailing list (whether you’re primarily getting email or on-site notifications). We encourage you to do that for projects and topics you’re interested in.
Other categories have their own rules, and own sets of tags — these sets are called “tag groups”, and you can see the list on the Tags page.
Where do I post and what tag do I pick?
-
Does your topic relate to an Ansible project, such as awx, ansible-core, or collections?
🡆 Project Discussions, with the corresponding tag.
-
Is your topic about Ansible development, but you’re not sure what tag to use?
🡆 Project Discussion, tagged with dev.
-
Need help solving a user problem?
🡆 Get Help, tagged with the appropriate help tag.
-
Do you want to chit-chat, soclalize, or share something fun?
🡆 Social Space.
Also consider Ansible Chat, to use Matrix for real-time conversations.
-
Do you have something to announce that’s going to be relevant to a large set of the Ansible user and contributor community?
🡆 News & Announcements — pick from #project-news, meetups, Events, #polls, or releases as appropriate. (Note that this category is limited to editors.)
-
Need help with this site, want to report a problem, or have a suggestion?
🡆 This category, Forum Guide & Feedback — pick from #problem, or #idea. Or, help others by contributing a new forum guide!
Cross-Posting with Multiple Tags
Most categories require at least one tag from that category’s main tag group. You can also add other tags — that’s a good way to broaden a topic if there are multiple facets — for example, something that touches both awx and documentation.
Tags Across Categories
Note that some tags exist in multiple categories — this is intentional, and lets you follow a topic like awx across project discussions, announcements, get help.
Subscribing to Tags
You can adjust your notification settings for each tag. Watching means you’ll get a notification for every new topic and for every reply. Tracking means you’ll see a counter of unread replies, but you won’t get individual notification.
Tag notifications can also be managed all in one place in Preferences: Tags & Teams:
We recommend Watching all tags for the projects you’re involved with (or interested in), just like subscribing to team mailing lists. Or, if you find that too noisy, try Tracking — that way, you won’t get notifications for each post, but topics with new activity will show up on your Unread list.
Subscribing to Categories
You can also watch a whole category, which will send you everything that you haven’t more specifically demoted to a lower-level of notification (via tag or individual topic). The interface for changing your notification preferences for Categories is similar to that for Tags.
Since other categories have different overall functions, they have different defaults. As a new site user, you’ll be set to Watching First Post for :category_news: News & Announcements.
Subscribing to (or Muting) Individual Topics
You will also find a bell icon to the right of the messages in each topic thread. You can use the settings there to watch (or mute) an individual topic, overriding the tag and category default.
In general, more specific notification settings override the more general ones, so if you set a topic to Watching you’ll get notifications even if it’s in a Muted tag or category — and vice versa, so you can mute a noisy topic in an area you normally watch.
Credits
A big thanks to Fedora for the original version of this page.
