Social.coop - User contributions [en]

Community Working Group Ops Team

2026-05-15T17:22:02Z

3wordchant: Melissa → at-large. And update compensation.

The Community Working Group ops team consists of up to 5 operational members and 3 volunteer "at large" members. The current team is elected to a one year term, and has a mandate until May 9, 2021, at which point the mandate shall be renewed.

'''Operational Members:''' Operational members rotate in an [[/social.coop/community/docs/-/wikis/Guide-for-CWG-Ops-Team-"On-Call"|on-call]] moderator role for the social.coop Mastodon instance, and attend monthly meeting. The coordinator is responsible for scheduling, tracking tasks, and coordinating with other working groups.

Compensation is currently based on a stipend, which we figure out and distribute annually around the end of the calendar year.

Current Members:

* Sam Whited
* [[User:Dphiffer|Dan Phiffer]]
* Django
* Hollie
* [[User:3wordchant|3wordchant]]

'''At-Large Members:''' At large members are elected volunteers who are invited to the monthly meetings and have voting seats in the Ops Team Loomio group, but do not take on-call shifts or other responsibilities.

Current Members:

* Melissa Santos

'''Team Charter Full Text'''

The process for selecting new team members will follow the following steps:

# A Check Poll will be launched in the Community Working Group to collect expressions of interest from potential new team members.
# Prospective team members will be asked to submit a short written statement to the existing Operations Team, which will review them and vote via ranked choice.
# The Operations Team will confirm the interest of the chosen candidates, and then submit a proposal to the Community Working Group to ratify their appointment to the Operations Team.
# We will also put an open call in the full membership group for folks interested in sitting in one of the two “at large” seats, and elect those seats via a vote from the full membership via approval voting.

'''Roles:'''

'''Community Ops Team Members [5 roles]'''

Responsibilities:

* Attend a monthly ops team call
* Perform work delegated at ops team call by next Ops Team call.
* Participate in decision-making and problem-solving between calls on the Ops Team Loomio group.
* Participate in "On-Call" rotation: [1 week shifts]
* Check and process new membership applications daily. [30 seconds to 10 minutes, depending on volume].
* Receive and respond to reports from members and off-instance folks.[variable]
* Toot announcements and welcomes from the official account, and respond to inquiries. [at least 1 announcement per shift, minimum]
* Pass-on documentation for next On-Call Staff [~30 minutes]

Compensation: 7.20GBP/month for attending the monthly call + 21.60gbp/On-Call Shift

'''Ops Team Coordinator [2 roles]'''

Responsibilities:

Standard Ops Team Member Responsibilities, plus...

* Schedule Monthly Ops Team Call
* Attend inter-working groups call to share updates, make requests of other working groups, receive requests, etc. [1 hour prep, 1 hour meeting monthly]
* Track Assignments, etc.

Compensation: Ops Team Member Comp + 14.40GBP/mo Selection: Elected by the Ops Team from their membership.

'''At Large Members [2]'''

Purpose: To provide a non-operational member perspective in the ops team, and to be a way for folks interested in the work but not sure if they want to commit to the role to get a sense of it.

Responsibilities:

* Attend the monthly Ops Team call and participate in Ops team Loomio as a voting member of the team.
* Compensation: Volunteer

'''Group Liasons [1+]'''

Purpose: This is a seat for a representative of each of the other working groups Operations Teams to occupy to ensure clear communication between groups.

Responsibilities: Attend the monthly Ops Team meeting and convey key information from their "home" Working Group.

Compensation: Volunteer, but compensated from “home” operations team if an Ops Team member.

=== Tutorials ===
If you are new to the community working group ops team, or an existing team member looking for a refresher, the following tutorials can help you figure out how to sign up for the various tools we use and get stuff done! If you find errors while following their steps, please edit them!

* [[Onboarding New Community Working Group Ops Team Members|Onboarding New Members]]
* [[Adding New Users to Meet.coop]]

HOWTO: Manually add a Keycloak SSO user

2026-05-13T21:51:39Z

3wordchant: Created page with "Screenshot of the user creation form in Keycloak Screenshot of the credential reset dialogue in Keycloak # Go to https://auth.social.coop # Log in with username <code>admin</code>, password in <code>pass</code> # Change to the social.coop "realm" in the drop-down on the top right # Click "Users" in the left-hand side-bar # Click "Add user" at the top # Fill out the form. ## U..."

[[File:Screenshot of user creation form.png|thumb|Screenshot of the user creation form in Keycloak]]
[[File:Keycloak credential reset.png|thumb|Screenshot of the credential reset dialogue in Keycloak]]
# Go to https://auth.social.coop
# Log in with username <code>admin</code>, password in <code>pass</code>
# Change to the social.coop "realm" in the drop-down on the top right
# Click "Users" in the left-hand side-bar
# Click "Add user" at the top
# Fill out the form.
## Use the same email address and username as on Mastodon.
## Be sure to check "Email verified"
# Click "Create"
# Go to the "Credentials" tab
# Click "Credential Reset" in the top-right
# Start typing "Password" and choose "Update Password" from the list
# Change "Expires In" to '''30 days'''
# Click "Send Email"
Now, the user will get an automated email with a link to set their initial password.

File:Keycloak credential reset.png

2026-05-13T21:50:19Z

3wordchant:

Screenshot of the "Credential reset" dialogue in Keycloak

File:Screenshot of user creation form.png

2026-05-13T21:45:12Z

3wordchant:

Screenshot of Keycloak UI showing the user creation form

Onboarding New Community Working Group Ops Team Members

2026-04-06T22:30:42Z

3wordchant:

''Feel free to do any or all of the Step 0 / Step 1 tasks during the onboarding meeting, so that the new member can see how you handle them (such as accepting them to Loomio or Meet.coop).''

== Step 0: Preparation ==
Ask the new member for:

# An e-mail address to be used for social.coop stuff (usually a personal e-mail)
# Their preferred <code>@social.coop</code> email forwarding address (usually the same as their Mastodon username)
# Their existing account usernames (they may not have all of these) on:
## Mastodon
## Mayfirst Nextcloud: https://share.mayfirst.org
## Loomio
## Social.coop SSO

== Step 1: account set-up ==

# Set up a <code>@social.coop</code> email forwarding address (see [[Setup a user@social.coop forwarding email address]]; '''NOTE:''' as of April 6 2026 possibly only [[Tech Working Group|TWG]] can do this). This is used for registering on <code>git.coop</code>, and the <code>registrations@social.coop</code> forwarder)
# Invite the new member to Zulip; click "Invite to organization" in the right-hand sidebar and either generate an invite link and send it to them, or have Zulip send directly by e-mail
# Invite the new member to the two teams on Mayfirst Nextcloud, by entering their email address here (usually their personal email):
## Social Coop https://share.mayfirst.org/apps/contacts/circle/ca95M5J2a4wQ6FR5symutQnUTO9ypjs
## Social.Coop CWG https://share.mayfirst.org/apps/contacts/circle/R9iugod2CKu5z1UdNxGGZ7V319PO8zy
# Invite the new member to Loomio, by clicking "Invite" on these pages, then finding the new members' username, or entering their email:
## Top-level Social.coop https://www.loomio.com/g/ibncxoDR/members
## Community Working Group https://www.loomio.com/g/0uqIXEbc/members
## Community WG Operations Team https://www.loomio.com/socialcoop-community-wg-operations-team/
# Add the new member as a moderator on the Mastodon instance: find their account in the [https://social.coop/admin/accounts?origin=local moderation "Accounts" list]
# Contact the new member:
## Send them the passwords for:
### The <code>registrations@social.coop</code> login on https://mail.zoho.eu — and let them know that they can add this to email clients using an "app password" in Zoho plus these settings: https://www.zoho.com/mail/help/imap-access.html
### The Social.coop admin account on Mastodon <code>@SocialCoop@social.coop</code> (NOTE: as of April 6th 2026, we're not sure where to find this login)
## Ask the new member to register on:
### https://git.coop '''using their <code>@social.coop</code> email forwarding address'''
### Social.coop Single Sign On; the easiest way for them to do this is to try to log into this very wiki, then click the "Register" link https://wiki.social.coop/index.php?title=Special:UserLogin&returnto=Main+Page

== Step 2: account set-up: continued ==
Once the new member has registered on https://git.coop , invite them to the <code>social.coop/community/operations</code> "project" here: https://git.coop/social.coop/community/operations/-/project_members

And, once the new member is in the Social.coop Loomio group, set them as an administrator by finding their name here, then clicking the 3 dots icon next to them, and clicking "Make administrator"

== Step 3: on-boarding meeting 🏄 ==
Once this is all done, have an on-boarding meeting with the member!

Things to cover in the meeting include:

* '''Accepting a Loomio user'''
** Make sure you set their title
** Go over how to verify that they are a social.coop member in cases where it's not immediately obvious
* '''How to log into the @SocialCoop@social.coop admin account''' and monitor it for replies
** What sorts of things do we post from here?
** '''NOTE:''' As of April 6th 2026, we're not sure what kinds of things we post here!
* '''Accepting a meet.coop user'''
** Possibly add them as a user on our meeting room so it shows up in their dashboard and they don't have to bookmark it
** '''NOTE:''' As of April 6th 2026, this is currently not working, stand by
* '''Show them the compensation log''' in Google Drive and grant them edit access
** '''NOTE:''' As of April 6th 2026, this has probably moved to Mayfirst Nextcloud, but are we even using it?
* '''Accepting a new social.coop member'''
** Verify that an Opencollective account exists
** We're not verifying that the user is actually paying us, they haven't had the opportunity to set up a donation yet and even if they have and didn't do it we're not cops, we trust our members to do what's right if and when they can.
** When do we do a "more info needed" email?
** When do we ''not'' accept a member?
** When do we just accept them right away?
** How do we send these emails (show them the templates and use this opportunity to have them create a custom one for acceptances)
** Show them the labels we use for all this, and remind them to always leave a comment about what they did so we don't get confused later
* '''Moderation'''
** Make sure they have multi-factor authentication enabled and show them how to use it if they're unfamiliar with the concept
** Explain the four kinds of reoports (reports of our users, reports by our users of other users, reports by our users of our users, reports by other users of other users) and how handling them differers
** Show them some old reports (maybe we should collect some to link here in case there aren't any good ones recently?)
** If there are any open reports, show them how to handle one or let them think through it
** When to contact the user and/or reporter?
** When to connect the user and reporter and ask that they handle it
** The three gates
** Other deescalation principals?

Community Working Group Ops Team

2026-03-03T16:22:24Z

3wordchant: Update ops team members based on Zulip chat https://socialcoop.zulipchat.com/#narrow/channel/511155-CWG/topic/Current.20ops.20team.20members/with/576737245

The Community Working Group ops team consists of up to 5 operational members and 3 volunteer "at large" members. The current team is elected to a one year term, and has a mandate until May 9, 2021, at which point the mandate shall be renewed.

'''Operational Members:''' Operational members rotate in an [[/social.coop/community/docs/-/wikis/Guide-for-CWG-Ops-Team-"On-Call"|on-call]] moderator role for the social.coop Mastodon instance, and attend monthly meeting. The coordinator is responsible for scheduling, tracking tasks, and coordinating with other working groups.

Compensation is currently $10/month + $30/week on-call shift + $20/month for coordinators.

Current Members:

* <s>Emi Do (Communications Coordinator)</s> (on a break)
* Matt Noyes (Team Coordinator)
* Sam Whited
* [[User:Dphiffer|Dan Phiffer]]
* Django
* Hollie
* [[User:3wordchant|3wordchant]]

'''At-Large Members:''' At large members are elected volunteers who are invited to the monthly meetings and have voting seats in the Ops Team Loomio group, but do not take on-call shifts or other responsibilities.

Current Members:

* Melissa Santos

'''Team Charter Full Text'''

The process for selecting new team members will follow the following steps:

# A Check Poll will be launched in the Community Working Group to collect expressions of interest from potential new team members.
# Prospective team members will be asked to submit a short written statement to the existing Operations Team, which will review them and vote via ranked choice.
# The Operations Team will confirm the interest of the chosen candidates, and then submit a proposal to the Community Working Group to ratify their appointment to the Operations Team.
# We will also put an open call in the full membership group for folks interested in sitting in one of the two “at large” seats, and elect those seats via a vote from the full membership via approval voting.

'''Roles:'''

'''Community Ops Team Members [5 roles]'''

Responsibilities:

* Attend a monthly ops team call
* Perform work delegated at ops team call by next Ops Team call.
* Participate in decision-making and problem-solving between calls on the Ops Team Loomio group.
* Participate in "On-Call" rotation: [1 week shifts]
* Check and process new membership applications daily. [30 seconds to 10 minutes, depending on volume].
* Receive and respond to reports from members and off-instance folks.[variable]
* Toot announcements and welcomes from the official account, and respond to inquiries. [at least 1 announcement per shift, minimum]
* Pass-on documentation for next On-Call Staff [~30 minutes]

Compensation: 7.20GBP/month for attending the monthly call + 21.60gbp/On-Call Shift

'''Ops Team Coordinator [2 roles]'''

Responsibilities:

Standard Ops Team Member Responsibilities, plus...

* Schedule Monthly Ops Team Call
* Attend inter-working groups call to share updates, make requests of other working groups, receive requests, etc. [1 hour prep, 1 hour meeting monthly]
* Track Assignments, etc.

Compensation: Ops Team Member Comp + 14.40GBP/mo Selection: Elected by the Ops Team from their membership.

'''At Large Members [2]'''

Purpose: To provide a non-operational member perspective in the ops team, and to be a way for folks interested in the work but not sure if they want to commit to the role to get a sense of it.

Responsibilities:

* Attend the monthly Ops Team call and participate in Ops team Loomio as a voting member of the team.
* Compensation: Volunteer

'''Group Liasons [1+]'''

Purpose: This is a seat for a representative of each of the other working groups Operations Teams to occupy to ensure clear communication between groups.

Responsibilities: Attend the monthly Ops Team meeting and convey key information from their "home" Working Group.

Compensation: Volunteer, but compensated from “home” operations team if an Ops Team member.

=== Tutorials ===
If you are new to the community working group ops team, or an existing team member looking for a refresher, the following tutorials can help you figure out how to sign up for the various tools we use and get stuff done! If you find errors while following their steps, please edit them!

* [[Onboarding New Community Working Group Ops Team Members|Onboarding New Members]]
* [[Adding New Users to Meet.coop]]

Community Working Group Ops Team

2025-10-30T13:18:08Z

3wordchant:

The Community Working Group ops team consists of up to 5 operational members and 3 volunteer "at large" members. The current team is elected to a one year term, and has a mandate until May 9, 2021, at which point the mandate shall be renewed.

'''Operational Members:''' Operational members rotate in an [[/social.coop/community/docs/-/wikis/Guide-for-CWG-Ops-Team-"On-Call"|on-call]] moderator role for the social.coop Mastodon instance, and attend monthly meeting. The coordinator is responsible for scheduling, tracking tasks, and coordinating with other working groups.

Compensation is currently $10/month + $30/week on-call shift + $20/month for coordinators.

Current Members:

* Emi Do (Communications Coordinator)
* Matt Noyes (Team Coordinator)
* Sam Whited
* Eduardo
* [[User:Dphiffer|Dan Phiffer]]
* Django
* Hollie
* [[User:3wordchant|3wordchant]]

'''At-Large Members:''' At large members are elected volunteers who are invited to the monthly meetings and have voting seats in the Ops Team Loomio group, but do not take on-call shifts or other responsibilities.

Current Members:

* Melissa Santos

'''Team Charter Full Text'''

The process for selecting new team members will follow the following steps:

# A Check Poll will be launched in the Community Working Group to collect expressions of interest from potential new team members.
# Prospective team members will be asked to submit a short written statement to the existing Operations Team, which will review them and vote via ranked choice.
# The Operations Team will confirm the interest of the chosen candidates, and then submit a proposal to the Community Working Group to ratify their appointment to the Operations Team.
# We will also put an open call in the full membership group for folks interested in sitting in one of the two “at large” seats, and elect those seats via a vote from the full membership via approval voting.

'''Roles:'''

'''Community Ops Team Members [5 roles]'''

Responsibilities:

* Attend a monthly ops team call
* Perform work delegated at ops team call by next Ops Team call.
* Participate in decision-making and problem-solving between calls on the Ops Team Loomio group.
* Participate in "On-Call" rotation: [1 week shifts]
* Check and process new membership applications daily. [30 seconds to 10 minutes, depending on volume].
* Receive and respond to reports from members and off-instance folks.[variable]
* Toot announcements and welcomes from the official account, and respond to inquiries. [at least 1 announcement per shift, minimum]
* Pass-on documentation for next On-Call Staff [~30 minutes]

Compensation: 7.20GBP/month for attending the monthly call + 21.60gbp/On-Call Shift

'''Ops Team Coordinator [2 roles]'''

Responsibilities:

Standard Ops Team Member Responsibilities, plus...

* Schedule Monthly Ops Team Call
* Attend inter-working groups call to share updates, make requests of other working groups, receive requests, etc. [1 hour prep, 1 hour meeting monthly]
* Track Assignments, etc.

Compensation: Ops Team Member Comp + 14.40GBP/mo Selection: Elected by the Ops Team from their membership.

'''At Large Members [2]'''

Purpose: To provide a non-operational member perspective in the ops team, and to be a way for folks interested in the work but not sure if they want to commit to the role to get a sense of it.

Responsibilities:

* Attend the monthly Ops Team call and participate in Ops team Loomio as a voting member of the team.
* Compensation: Volunteer

'''Group Liasons [1+]'''

Purpose: This is a seat for a representative of each of the other working groups Operations Teams to occupy to ensure clear communication between groups.

Responsibilities: Attend the monthly Ops Team meeting and convey key information from their "home" Working Group.

Compensation: Volunteer, but compensated from “home” operations team if an Ops Team member.

=== Tutorials ===
If you are new to the community working group ops team, or an existing team member looking for a refresher, the following tutorials can help you figure out how to sign up for the various tools we use and get stuff done! If you find errors while following their steps, please edit them!

* [[Onboarding New Community Working Group Ops Team Members|Onboarding New Members]]
* [[Adding New Users to Meet.coop]]

User:3wordchant

2025-10-30T13:17:48Z

3wordchant: Created page with "I'm <code>[https://social.coop/@3wordchant @3wordchant]</code> – I also help run the <code>[https://social.coop/@coopcloud @coopcloud]</code> and <code>[https://social.coop/@wikicafe @wikicafe]</code> accounts. I'm a member of the Community Working Group Ops Team (since mid-2025) and the Tech Working Group (since mid-2023). You can contact me by DM on Mastodon, email to <code>[mailto:3wordchant@social.coop 3wordchant@social.coop]</code>, or Matrix on <code>@3..."

I'm <code>[https://social.coop/@3wordchant @3wordchant]</code> – I also help run the <code>[https://social.coop/@coopcloud @coopcloud]</code> and <code>[https://social.coop/@wikicafe @wikicafe]</code> accounts.

I'm a member of the [[Community Working Group Ops Team]] (since mid-2025) and the [[Tech Working Group]] (since mid-2023).

You can contact me by DM on Mastodon, email to <code>[mailto:3wordchant@social.coop 3wordchant@social.coop]</code>, or Matrix on <code>@3wc:autonomic.zone</code>.

Community Working Group Ops Team

2025-10-30T13:11:35Z

3wordchant:

The Community Working Group ops team consists of up to 5 operational members and 3 volunteer "at large" members. The current team is elected to a one year term, and has a mandate until May 9, 2021, at which point the mandate shall be renewed.

'''Operational Members:''' Operational members rotate in an [[/social.coop/community/docs/-/wikis/Guide-for-CWG-Ops-Team-"On-Call"|on-call]] moderator role for the social.coop Mastodon instance, and attend monthly meeting. The coordinator is responsible for scheduling, tracking tasks, and coordinating with other working groups.

Compensation is currently $10/month + $30/week on-call shift + $20/month for coordinators.

Current Members:

* Emi Do (Communications Coordinator)
* Matt Noyes (Team Coordinator)
* Sam Whited
* Eduardo
* [[User:Dphiffer|Dan Phiffer]]
* Django
* Hollie
* 3wordchant

'''At-Large Members:''' At large members are elected volunteers who are invited to the monthly meetings and have voting seats in the Ops Team Loomio group, but do not take on-call shifts or other responsibilities.

Current Members:

* Melissa Santos

'''Team Charter Full Text'''

The process for selecting new team members will follow the following steps:

# A Check Poll will be launched in the Community Working Group to collect expressions of interest from potential new team members.
# Prospective team members will be asked to submit a short written statement to the existing Operations Team, which will review them and vote via ranked choice.
# The Operations Team will confirm the interest of the chosen candidates, and then submit a proposal to the Community Working Group to ratify their appointment to the Operations Team.
# We will also put an open call in the full membership group for folks interested in sitting in one of the two “at large” seats, and elect those seats via a vote from the full membership via approval voting.

'''Roles:'''

'''Community Ops Team Members [5 roles]'''

Responsibilities:

* Attend a monthly ops team call
* Perform work delegated at ops team call by next Ops Team call.
* Participate in decision-making and problem-solving between calls on the Ops Team Loomio group.
* Participate in "On-Call" rotation: [1 week shifts]
* Check and process new membership applications daily. [30 seconds to 10 minutes, depending on volume].
* Receive and respond to reports from members and off-instance folks.[variable]
* Toot announcements and welcomes from the official account, and respond to inquiries. [at least 1 announcement per shift, minimum]
* Pass-on documentation for next On-Call Staff [~30 minutes]

Compensation: 7.20GBP/month for attending the monthly call + 21.60gbp/On-Call Shift

'''Ops Team Coordinator [2 roles]'''

Responsibilities:

Standard Ops Team Member Responsibilities, plus...

* Schedule Monthly Ops Team Call
* Attend inter-working groups call to share updates, make requests of other working groups, receive requests, etc. [1 hour prep, 1 hour meeting monthly]
* Track Assignments, etc.

Compensation: Ops Team Member Comp + 14.40GBP/mo Selection: Elected by the Ops Team from their membership.

'''At Large Members [2]'''

Purpose: To provide a non-operational member perspective in the ops team, and to be a way for folks interested in the work but not sure if they want to commit to the role to get a sense of it.

Responsibilities:

* Attend the monthly Ops Team call and participate in Ops team Loomio as a voting member of the team.
* Compensation: Volunteer

'''Group Liasons [1+]'''

Purpose: This is a seat for a representative of each of the other working groups Operations Teams to occupy to ensure clear communication between groups.

Responsibilities: Attend the monthly Ops Team meeting and convey key information from their "home" Working Group.

Compensation: Volunteer, but compensated from “home” operations team if an Ops Team member.

=== Tutorials ===
If you are new to the community working group ops team, or an existing team member looking for a refresher, the following tutorials can help you figure out how to sign up for the various tools we use and get stuff done! If you find errors while following their steps, please edit them!

* [[Onboarding New Community Working Group Ops Team Members|Onboarding New Members]]
* [[Adding New Users to Meet.coop]]

Tech Working Group

2025-10-29T18:13:59Z

3wordchant:

{{Working Group
|Description=all things hosting, site maintenance, and development.
|Members=User:Flancian,User:Edsu,User:Todrobbins,User:Dphiffer,User:3wordchant
}}
[[Category:Working Group]]
The Tech Working Group are responsible for maintaining hosted services like Mastodon and this wiki. Ideally there would be more documentation here about how we do this (someday soon).

If you have questions or issues to report you can:

* post to the [https://www.loomio.com/g/Mtb0FrvX/social-coop-tech-working-group Tech Working Group section of Loomio]
* send an email to tech.group@social.coop
* add an issue to the [https://git.coop/social.coop/tech/operations/-/issues operations issue tracker] (requires a git.coop account)
* send a message to the [[Matrix]] Tech Chat room
* add to the Discussion for this wiki page

We always welcome new TWG members and participation from the co-op. If you'd like to get involved check out the [[Calendars|calendar]] of events for our next meeting or inquire in Matrix.

== Subpages ==

{{#ask:
[[Part Of::{{SUBJECTPAGENAME}}]]
|?Has Description=Description
|format=broadtable
}}

Onboarding New Community Working Group Ops Team Members

2025-09-24T23:30:53Z

3wordchant: Formatting, add link to Zoho client setup

Before onboarding a new member we should set them up with an account in the following tools:

* A social.coop email (redirects to their personal email, used for quick signups on git.coop which recognizes our domain and for receiving mails to <code>registration@social.coop</code> email address),
* [https://git.coop Git.coop] (used for onboarding new members),
* [https://socialcoop.meet.coop Meet.coop] (for accepting new meet.coop users),
* Loomio (for accepting new Loomio members and participating in group votes and discussion),
* May First Nextcloud (used for access to shared CWG files,
* Zulip
* and Social.coop, of course (hopefully they already have this).

The following accounts have shared passwords which should be shared with the new members:

* Zoho (email for <code>registrations@social.coop</code>)
** Can be added to email clients using an "app password" in Zoho plus these settings: https://www.zoho.com/mail/help/imap-access.html
* Social.coop Admin Account <code>@SocialCoop@social.coop</code>

Once these accounts are created the following actions must be taken:

* Their email should be added to the aliases for <code>registrations@social.coop</code>
* They should be made an administrator of meet.coop so that they can accept new users
* They should request access to the CWG Ops Team Loomio group and an existing member should approve them and make sure they have permissions to approve others
* They should be added to the social.coop and CWG Ops Team circles on Nextcloud
* They should be made a moderator on social.coop

=== On-boarding meeting ===
Once this is all done, an on boarding meeting may be held.

Some of the tasks above may be good to handle during the meeting so that the new member can see how you handle them (such as accepting them to Loomio or Meet.coop), others will need to be done in advance by the tech working group.

Things to cover in the meeting include:

* '''Accepting a meet.coop user'''
** Possibly add them as a user on our meeting room so it shows up in their dashboard and they don't have to bookmark it
* '''Accepting a Loomio user'''
** Make sure you set their title
** Go over how to verify that they are a social.coop member in cases where it's not immediately obvious
* '''How to log into the @SocialCoop@social.coop admin account''' and monitor it for replies
** What sorts of things do we post from here?
* '''Show them the compensation log''' in Google Drive and grant them edit access
* '''Accepting a new social.coop member'''
** Verify that an Opencollective account exists
** We're not verifying that the user is actually paying us, they haven't had the opportunity to set up a donation yet and even if they have and didn't do it we're not cops, we trust our members to do what's right if and when they can.
** When do we do a "more info needed" email?
** When do we ''not'' accept a member?
** When do we just accept them right away?
** How do we send these emails (show them the templates and use this opportunity to have them create a custom one for acceptances)
** Show them the labels we use for all this, and remind them to always leave a comment about what they did so we don't get confused later
* '''Moderation'''
** Make sure they have multi-factor authentication enabled and show them how to use it if they're unfamiliar with the concept
** Explain the four kinds of reoports (reports of our users, reports by our users of other users, reports by our users of our users, reports by other users of other users) and how handling them differers
** Show them some old reports (maybe we should collect some to link here in case there aren't any good ones recently?)
** If there are any open reports, show them how to handle one or let them think through it
** When to contact the user and/or reporter?
** When to connect the user and reporter and ask that they handle it
** The three gates
** Other deescalation principals?

Community Working Group Onboarding Notes 2025-07-23

2025-07-23T16:01:36Z

3wordchant: 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..."

'''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