Point of information.
What is the process right now by which SIGs are created that spells out exactly when a SIG is able to establish an identity with a FAS group? Is it because they need particular infra access?
A SIG is created when it declares that it exists. 
It is meant to be
light weight.
Anyone can request a fas group for tracking their sig members.
Many people request fas groups to help them manage copr groups.
Could I just create a Fedora Curling SIG today and get a FAS group today for it? I’ve done the groundwork.. I know there are enough people to create an international Fedora curling team with Fedora branded curling jackets as an outreach effort. I could probably have a 40 person group this week on a wiki page no problem. But what’s the process that gates getting an associated fas account?
A infra request for it.
The point being, I have deep concerns about tying voting rights to arbitrary FAS groups because there doesn’t seem to be any rhyme or reason to how and when FAS groups are created and removed.
How many SIGs right now are in fact just ghost fas groups and are effectively non-functional with no attachment points for onboarding new contributors?
If you want to tie voting strongly with SIGs, then we need to have SIGs being functional self-governing groups.. and not what they laissez-faire structures as the exist right now.
Perhaps! I know theres been a lot of discussion in the council and
community ops groups around “what is a contributor”. Since a council
goal right now is to grow contributors that seems like a good thing to
have a commonly agreed critera for and if it could be something a
elections app could tell that would be ideal. Right now we had fas
groups for showing that someone cared enough to make a group or get
someone to add them to a group.