3wordchant: Created page with "'''CWG onboarding 2025-07-23''' ''Eduardo, Melissa, Calix'' Checkins Mural: https://miro.com/app/board/uXjVLdZtJc0=/ Agenda: * Review onboarding process * Single sign-on / unified member profile E: Previous onboarding process was confusing. Want to make people more involved in the community. Request not obligation. Self-signon, not coupled, but could be coupled with united member profile. Last: what happens if we provide identity to our members as..."

2025-07-23T16:01:36Z

Created page with "'''CWG onboarding 2025-07-23''' ''Eduardo, Melissa, Calix'' Checkins Mural: <nowiki>https://miro.com/app/board/uXjVLdZtJc0=/</nowiki> Agenda: * Review onboarding process * Single sign-on / unified member profile E: Previous onboarding process was confusing. Want to make people more involved in the community. Request not obligation. Self-signon, not coupled, but could be coupled with united member profile. Last: what happens if we provide identity to our members as..."

New page

'''CWG onboarding 2025-07-23'''

''Eduardo, Melissa, Calix''

Checkins

Mural: <nowiki>https://miro.com/app/board/uXjVLdZtJc0=/</nowiki>

Agenda:

* Review onboarding process

* Single sign-on / unified member profile

E: Previous onboarding process was confusing. Want to make people more involved in the community. Request not obligation. Self-signon, not coupled, but could be coupled with united member profile. Last: what happens if we provide identity to our members as a community?

E: (intro to new onboarding process)

C: How does the new process affect the amount of work for CWG members?

E: Intention is to reduce it.

E: How does SSO affect this?

M: First step - make the wiki page, don't change anything else, put link to the wiki page in announcements.

E: Yes, wiki page is the only concrete page up til now.

M: Keep email the same as now?

E/M: Eventually reduce email, move to wiki page.

C: (an intro to SSO)

4 categories:

# SSO already: wiki

# SSO possible but not yet deployed: Mastodon

# SSO unclear / improbable: git.coop, share.mayfirst.org, opencollective

# SSO possible through self-hosting: Loomio, Zulip, Matrix.

M: Loomio is the biggest problem with SSO, it's the one we really want people onto. Zulip is only active people in working groups.

E: Didn't remember we had so many services. Would be clearer for me if we make a sequence of "what would be the priority to make things work with SSO".

E: Mastodon next priority?

C: Yes. Social / education plan needs to be developed.

C: meet.coop does automation around SSO, automating creation of SSO accounts - in their case based on opencollective contributions. We could do similar, or automate based on form submission / approval, instead.

C: one note - believe no SSO for opencollective.

E: Without changing anything yet in terms of tech - what we can do is start organising the message that today goes in an email, on the wiki. "Welcome possible new member", this is what you need to do to become a member.

E: Next step: with SSO. CWG creates SSO account, user fills in profile, data propagates to other platforms. Series of small steps. Slowly moving processes into creation of account.

Checkout

Community Working Group Onboarding Notes 2025-07-23 - Revision history