Fedora Discussion 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”.
The main category on this site is Project Discussion. In this category, most tags represent specific teams. “Watching” a tag is like joining that team’s mailing list (whether you’re primarily getting email or on-site notifications). I encourage you to do that for teams 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.
🡆 Project Discussion, with the corresponding tag.
Is your topic about Fedora Linux development, but you’re not sure what tag to use?
Is your topic about the “beyond building the bits” parts of Fedora?
Do you want to chit-chat, soclalize, or share something fun?
Also consider Fedora Chat, our Matrix-based platform for real-time conversations.
Do you have something to announce that’s going to be relevant to a large set of the Fedora user and contributor community?
Something specific to a particular team workflow which doesn’t quite fit the way the rest of the site works?
🡆 Your team may have a subcategory under Team Workflows. Fedora Magazine’s article submission process is a good example here?
Need help solving a technical problem, or want to report a bug?
🡆 Visit Ask Fedora. (We’re looking at merging the two sites, but aren’t ready yet.)
Need help with this site, want to report a problem, or have a suggestion?
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 #design and #docs, or #cloud and #server.
Note that some tags exist in multiple categories — this is intentional, and lets you follow a topic like #cloud across project discussions, announcements, and even proposed Fedora Magazine articles.
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:
I recommend Watching all tags for teams 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.
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.
In Project Discussion, there are separate #mindshare and #engineering tags meant for broader discussion — think of the latter a little like the traditional Fedora Devel mailing list, and the former as an equivalent for everything on that side of the org chart — that might be a little more manageable than following all Project Discussions. But if you want to, you can!
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 News & Announcements, and to Tracking for the Podcast and Community Blog subcategories. If you’re interested in following Fedora more closely (but don’t necessarily want to hear about every comment on each blog post) you may want to change the Community Blog setting to Watching First Post as well.
And, subcategories under Team Workflows are Muted by default — each one there has its own specific purpose and you’ll know if you want to follow it.
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.