Social.coop - User contributions [en]

Onboarding New Community Working Group Ops Team Members

2024-05-06T14:11:50Z

Sam: Add a skeleton of the tasks required to accept a new member

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 registration@social.coop email address),
* Git.coop (used for onboarding new members),
* 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,
* 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 registrations@social.coop)
* Social.coop Admin Account

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

* Their email should be added to the aliases for registrations@social.coop
* 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

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 team.

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 social.coop admin account and monitor it for replies
** What sorts of things do we post from here?
* Show them the compensation log in Nextcloud
* Accepting a new social.coop member
** Verify that an open collective 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

2024-05-06T13:52:33Z

Sam: Added a link to the tutorial about onboarding which I'm about to write.

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

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

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

Guide-for-CWG-Ops-Team-"On-Call"

2024-04-05T14:49:10Z

Sam: Edit the compensation to point to the CWG Ops Team page so that they don't get out of sync if we change it. There is now one source of truth.

The social.coop instance is moderated by a rotating member of the [[Community Working Group Ops Team]] "On Call" shifts run from Sunday at 12pm GMT to 11:59am GMT the following Sunday.

== Key Responsibilities ==

* Review reports made through the Mastodon platform ASAP, and decide on a course of action guided by our [[Code of conduct]], [[Federation abuse policy]], and [[Reporting guide]]. Contact the person who made the report to let them know the action taken or ask follow-up questions.

* Decisions to silence or suspend instances should be posted to [[Defederation of instances]]

* If a case feels ambiguous enough that you don't feel comfortable acting alone on it, DM your fellow Ops Team members to discuss.

* Toot announcements and welcomes from the official account, and respond to inquiries. The account should be checked for messages, and at least one announcement/post should be made from it, at least once per week.

* Check for new applications and on-board new members regularly to both the Mastodon instance and Loomio.

* At the end of your week, if there are any outstanding issues, message the next on-call person to provide context.

== Compensation ==

Compensation numbers can be found on the [[Community Working Group Ops Team]] page. Submit your shift info to the spreadsheet linked in the CWG Ops Team Loomio group's description prior to the monthly call, and compensation for the previous month will be reviewed and approved during the monthly call. Once it is approved, you may submit an invoice to our [https://opencollective.com/socialcoop Open Collective].

Guide-for-CWG-Ops-Team-"On-Call"

2024-03-01T19:23:24Z

Sam: Fix broken links to policies

The social.coop instance is moderated by a rotating member of the [[Community Working Group Ops Team]] "On Call" shifts run from Sunday at 12pm GMT to 11:59am GMT the following Sunday.

== Key Responsibilities ==

* Review reports made through the Mastodon platform ASAP, and decide on a course of action guided by our [[Code of conduct]], [[Federation abuse policy]], and [[Reporting guide]]. Contact the person who made the report to let them know the action taken or ask follow-up questions.

* Decisions to silence or suspend instances should be posted to [[Defederation of instances]]

* If a case feels ambiguous enough that you don't feel comfortable acting alone on it, DM your fellow Ops Team members to discuss.

* Toot announcements and welcomes from the official account, and respond to inquiries. The account should be checked for messages, and at least one announcement/post should be made from it, at least once per week.

* Check for new applications and on-board new members regularly to both the Mastodon instance and Loomio.

* At the end of your week, if there are any outstanding issues, message the next on-call person to provide context.

== Compensation ==

Compensation is currently set at $30 per shift covered. Submit your shift info to the spreadsheet linked in the CWG Ops Team Loomio group's description prior to the monthly call, and compensation for the previous month will be reviewed and approved during the monthly call. Once it is approved, you may submit an invoice to our [https://opencollective.com/socialcoop Open Collective].

Reporting guide

2023-08-04T13:38:30Z

Sam: Remove broken disroot links

== How to report [[Code of conduct|Code of Conduct]] violations ==

Social.Coop is based on the values of self-help, self-responsibility, democracy, equality, equity, and solidarity. In the tradition of their founders, cooperative members believe in the ethical values of honesty, openness, social responsibility and caring for others.

Our top priority is the safety of each of our members and our community as a whole. We will not tolerate bigotry, including fascist, racist, misogynistic, homophobic, or transphobic content and will act swiftly and decisively to protect our members from abuse.

We would rather get "false alarms" than have Code of Conduct violations go unaddressed.

If you think someone is violating the Code of Conduct, please report them to the social.coop moderators.

<screenshot of Mastodon's reporting interface>

Click "report @[user]".

Or DM someone on the Community Moderation Team: You can include screenshots, links, and any other context that will help us understand the situation.

== What happens after I make a report? ==

You will get an automated email acknowledging that we've received it. We will do our best to get back to you within 24 hours (understanding that people live in different time zones, have different schedules, etc.).

Our first priority is making sure everyone is safe. If necessary, we will:

* Delete, edit, or hide a problem post
: This may be proactive to deal with the item in order to not wait for the person to take care of it, or this may be necessary when the person will not voluntarily address the item
* Privately tell the violator(s) to knock it off, delete/redact posts on Mastodon/Loomio/in Matrix chat, or apologize
* Publicly tell the violator(s) to knock it off, delete/redact, or apologize
* Mute or block the violator(s)

We may delay an official response until we have dealt with the immediate situation.

Once we have an understanding of what's going on, we will make a decision and contact you. We will take your feedback into account, but the action we take is our responsibility. This might involve:

* Nothing (if we determine no violation occurred)
* A temporary ban
* A permanent ban
* A request for a public or private apology
* A request to participate in mediation</code>

We embrace the principles of restorative justice. We want to give people a chance to correct mistakes and learn from them. If you disagree with our final decision, you can appeal it here: < link to CMT >
----''This is a revised version of the Reporting Guidelines that were approved in a membership vote on 9/1/2018.''

== Previous Versions ==
'''[https://git.coop/social.coop/community/docs/-/wikis/Reporting-Guide/Reporting-Guide-v3-Release-Candidate-1 Reporting Guide v3] -''' Approved by membership vote on September 1, 2018. (But also challenged in a separate poll.)

[https://git.coop/social.coop/community/docs/-/wikis/Reporting-Guide/combined-reporting-docs '''Combined Reporting Guide v1''']

[https://git.coop/social.coop/community/docs/-/wikis/Reporting-Guide/reporting-guide-v2 Reporting Guide v2]

[https://git.coop/social.coop/community/docs/-/wikis/Reporting-Guide/reporting-guide-v1 Reporting Guide v1]

Tutorials

2023-07-23T20:01:39Z

Sam: Update registration forms for social.coop and meet.coop

This is a collection of tutorials on this wiki. Many are also linked elsewhere.

= Mastodon basics =

* [[Social.coop guide to Mastodon]]

= Participating in governance =

* [[How to Make the Fediverse Your Own|How to make the fediverse your own]]
* [[Make a proposal]]

= Reporting issues =

* [[Reporting guide|Moderation reporting guide]]
* Tech issues [to do!]

= Using partner platforms =

* [[Getting a GitLab project account]]
* [[May First Movement Technology|May First tools]]
* [https://join.social.coop/meet.coop-registration-form.html Meet.coop registration form]

= Forms =

* [[Getting a GitLab project account]]
* [https://join.social.coop/meet.coop-registration-form.html Meet.coop registration form]
* [https://join.social.coop/registration-form.html Social.coop registration form]