I run a weekly meeting where members of fedora (and rhel and centos) leadership are explicitly invited

This is the first time I'm hearing of this. So apparently onboarding new fesco members isn't the biggest problem here, but rather, that current fesco members don't seem to have gotten invites at all?

Perhaps extend a explicit invite to current members and then add to the onboarding doc to invite new folks?

It's quite possible I've missed people, this is a relatively new activity and we just started ramping up at the end of last year. Nirik, you mention an onboarding doc, which is a thing that doesn't exist yet- though I expect to put information under https://issues.redhat.com/browse/FRCL-1 in the short term. In any case, if it wouldn't be unwelcome, I will go ahead and invite everybody who is in FESCo to the call, and we'll grow from there.

Oh, I meant the fesco onboarding doc: https://docs.fedoraproject.org/en-US/fesco/Updating_Fedora_Engineering_Steering_Committee_Members/

This is the first time I'm hearing of this.

Same :(

Hey folks, following up on the original inquiry. It sounds like people want to get the invite by default, so I've gone ahead and invited everybody listed on https://docs.fedoraproject.org/en-US/fesco/ who wasn't previously included (sorry!). I will, informally, stay on top of FESCO leadership changes to manage the invite, but it would be cool if we had some sort of mechanism I could use that kept itself current (email alias?).

You can look at the FESCo FAS group to identify who is a current member: https://accounts.fedoraproject.org/group/fesco/

I guess also take a snapshot of the FAS group before the election, to keep track of outgoing members

https://pagure.io/fesco/fesco-docs/pull-request/121 adds a "ping bcl" item to the Update SOP. PTAL.

The docs have been updated. I think we can close this now. If experience shows that the manual process is awkward, we can try to figure out something more automatic later.