sorry for the late response but I was knocked out by a flu for some days, still down but b2k.
I am not to big of a fan of the procedure for the general onboarding suggested. Since I was managing the onboarding process mostly last year I have some experience. And the procedure layed out above is way way to complicated.
Creating a doodle and a topic for every onboarding call and also collecting contact details in a google doc is way to much work - an inferno. And it creates unnecessary points of failure - like the doodle.
I think the onboarding process should work almost exactly like last year.
1 get in touch
Someone interested writes to the 3 people who onboarding team announced on the contact page. It is Sam, Tim and Me at the moment. http://oscedays.org/contact - If someone write to another person the person should forward it to the onboarding team.
2 arrange a date via email
One of us repyling to them suggesting 3 times to meet. One of us is enough in the call. But of course, the more the better.
3 set up infrastructure, send information and organise contact details
If everything is cool after the call and they want to do it, one of us that made the call is doing the necessary steps:
We should have of course an Onboarding Procedure Topic, where this is described and where we also can make public when we have a call with whom … so others can join if they want to. But I would just say the City not the name of the person or initiative… not before they agreed with it.
The other workflow with the mail to people who are generally interested is good.
Update: I was clicking the last minutes through 3 doodles and I am already confused . . .
Also having an [ONBOARDING] topic for every call in front of us where people can introduce themselve is a nice idea in theory. But I don’t think that it will work! Because people want to check out, what is this, they don’t want to get immediately active. 1/3 or a bit more of all calls last year did not result into a local event.