This process creates much formality and has a high entry barrier. This can be already deterring. Just to read through this stuff makes me fear to maybe have overlooked something, and it takes time. Tickets and comparable stuff also create pressures to contribute - people think twice before doing that. They do not know what is to come once they open the ticket (or comparable activities), but at the same time, they would need to actively retreat after. People don’t like to do that (=entry barrier, deterrence).
Also, many (if not most) SIGs / WGs are tailored to their upstream - this is the nature of Fedora. Thus, there is no central organization/approach when it comes to understand why they do, what they do, how they do and thus if they fit me. I do not think that any central point of “how to” can fit all Fedora groups given their differently-organized upstream. It creates just work and entry barriers - and maybe even misinterpretations.
When people come through development, they are likely to end up in the devel mailing list. It has a quite simple rule: introduce yourself! Tell who you are, what you can, what you want to do and what your motivations are. Quite helpful to help you to find yourself in the devel list (and related people/groups) I think.
Why not do the same for non-developers?
We officially made discourse to our central point of interaction: If people are new, let them add a topic where they elaborate the same things as when they introduce themselves to the devel mailing list: if WG/SIG seek contributors, they shall check the “newcomers” category (which we then need to create) and see if there is someone they might make aware of themselves. They can identify and explain best.
Also, this way we motivate SIGs/WGs to review discourse more actively. If they don’t seek contribution, it is their own decision. And having more people reviewing discourse makes also more people to outreach to other Fedora elements (even if just by becoming aware of them).
We might find people who weekly check the newcomer category and maybe make people aware if they should maybe rather go to the devel mailing list, or make suggestions and at least say hello (effectively this would be the JOIN SIG, but also the contributors/volunteers of the quarterly intro topics; I can help here).
I tend to assume that this approach would replace the quarterly introduction topics, and create an introduction topic for each user. I know, more topics, but easy to sort if we had a category for it: and we never had so many newcomers that the amount of topics would be problematic. It’s just a few here and there.
Saying informally “hello” at a place, where people with related affinities are, seems to be what people intuitively appreciate: why stopping this in intro topics after the initial “hello & welcome”? At “Hello & welcome” (no entry barrier - but be careful what you ask them to tell in order to keep it that way!) is where the “flow” can begin intuitively, and where we can foster it to intuitively continue/develop (and where SIGs/WGs can make aware of themselves easily and without much efforts).
A permanently pinned topic for newcomers might be an additional incentive/facilitator.
Just an alternative perspective 
