Social.coop - User contributions [en]

User:Dphiffer

2026-04-21T18:04:30Z

Dphiffer:

Hello, I'm Dan Phiffer ([https://social.coop/@dphiffer @dphiffer]), I'm a member of the [[Community Working Group Ops Team]] and [[Tech Working Group]]. I live in Upstate New York, in a city called Troy, a short distance upriver from Albany. I build and maintain websites at my [https://propublica.org/ day job] as well as [https://propublicaguild.org/ union organizing].

Welcome Email

2026-03-30T14:06:31Z

Dphiffer:

Hi '''[1. ADD NEW MEMBER NAME]''',

Thanks for joining us! I want to welcome you to our community at [https://social.coop/ Social.coop] and to let you know that your application for membership has been approved! We're so glad you're here.

Social.coop is pioneering the process of participatory democratic ownership of platform coops and you have the power to shape the future of our platform and organization.

To set up your account on the '''Social.coop Mastodon, click this link [2. ADD REGISTRATION LINK]'''. Once your account is set up, you’ll automatically be following the [https://social.coop/@SocialCoop @SocialCoop] admin account. For your first toot, please write an introduction post that includes #introduction and any other hashtags of things that interest you.

Then, if you have not already, please set up your subscription payment on '''OpenCollective [https://opencollective.com/socialcoop via this link]'''. The fee is sliding scale $1-10/month, and setting up payments on an annual rather than monthly cycle saves our co-op a bit in terms of transaction fees.

Our instance is democratically governed by its members, which now includes you! To be an effective co-operative, it's important that members participate in its governance by generally keeping informed on the goings-on and strategic direction of social.coop. To participate in governance, please request to join the members' '''Loomio group [https://www.loomio.org/socialcoop/ via this link]'''. Note: after you register on Loomio, please [https://www.loomio.com/profile edit the introduction field on your profile] and add your Social.coop handle so we can recognize you as a member.

You’re getting this email from me because I’m the member of the [[Community Working Group Ops Team|Community Working Group Operations Team]] who is on-call this week. Feel free to follow up with me if you have any issues. You can reach me by mentioning or direct messaging me on Social.coop at '''@[3. ADD YOUR HANDLE]''' and by replying to this email.

Social.coop is pioneering the process of participatory democratic ownership of platform coops and you have the power to shape the future of our platform and organization. To set up your account go to: https://wiki.social.coop/wiki/New_member_setup

In Solidarity!

'''[4. ADD YOUR NAME]'''

Welcome Email

2026-03-30T13:55:29Z

Dphiffer:

Hi '''[1. ADD NEW MEMBER NAME]''',

Thanks for joining us! I want to welcome you to our community at [https://social.coop/ Social.coop] and to let you know that your application for membership has been approved! We're so glad you're here.

Social.coop is pioneering the process of participatory democratic ownership of platform coops and you have the power to shape the future of our platform and organization.

To set up your account on the '''Social.coop Mastodon, click this link [2. ADD REGISTRATION LINK]'''. Once your account is set up, you’ll automatically be following the [https://social.coop/@SocialCoop @SocialCoop] admin account. For your first toot, please write an introduction post that includes #introduction and any other hashtags of things that interest you.

Then, if you have not already, please set up your subscription payment on '''OpenCollective [https://opencollective.com/socialcoop via this link]'''. The fee is sliding scale $1-10/month, and setting up payments on an annual rather than monthly cycle saves our co-op a bit in terms of transaction fees.

Our instance is democratically governed by its members, which now includes you! To be an effective co-operative, it's important that members participate in its governance by generally keeping informed on the goings-on and strategic direction of social.coop. To participate in governance, please request to join the members' '''Loomio group [https://www.loomio.org/socialcoop/ via this link]'''. Note: after you register on Loomio, please [https://www.loomio.com/profile edit the introduction field on your profile] and add your Social.coop handle so we can recognize you as a member.

You’re getting this email from me because I’m the member of the [[Community Working Group Ops Team|Community Working Group Operations Team]] who is on-call this week.

Feel free to follow up with me if you have any issues. You can reach me by mentioning or direct messaging me on Social.coop at '''@[3. ADD YOUR HANDLE]''' and by replying to this email.

Social.coop is pioneering the process of participatory democratic ownership of platform coops and you have the power to shape the future of our platform and organization. To set up your account go to: https://wiki.social.coop/wiki/New_member_setup

In Solidarity!

'''[4. ADD YOUR NAME]'''

New member setup

2026-03-30T13:50:34Z

Dphiffer: Created page with "Welcome to social.coop! In order to get the most out of your membership, here are some links to help you get started on the various platforms we support. # '''Mastodon:''' sign up using the invite link sent to you in your email. Look for the subject line "Welcome to social.coop!" # '''OpenCollective:''' use '''[https://opencollective.com/socialcoop this link]''' to set up your membership payment. The fee is sliding scale $1-10/month, and setting up payments on an annual..."

Welcome to social.coop! In order to get the most out of your membership, here are some links to help you get started on the various platforms we support.

# '''Mastodon:''' sign up using the invite link sent to you in your email. Look for the subject line "Welcome to social.coop!"
# '''OpenCollective:''' use '''[https://opencollective.com/socialcoop this link]''' to set up your membership payment. The fee is sliding scale $1-10/month, and setting up payments on an annual rather than monthly cycle saves our co-op a bit in terms of transaction fees.
# '''Loomio:''' join our group '''[https://www.loomio.org/socialcoop/ via this link]'''. This is how we have discussions and govern ourselves democratically as a cooperative.

You can also reach members of the [[Community Working Group Ops Team|Community Working Group operations team]] on Mastodon or via [mailto:registrations@social.coop registrations@social.coop].

Welcome Email

2026-03-22T18:13:31Z

Dphiffer:

Hi '''[1. ADD NEW MEMBER NAME]''',

Thanks for joining us! I want to welcome you to our community at Social.coop and to let you know that your application for membership has been approved! We're so glad you're here.

Social.coop is pioneering the process of participatory democratic ownership of platform coops and you have the power to shape the future of our platform and organization.

To set up your account on the '''Social.coop Mastodon, click this link [2. ADD REGISTRATION LINK]'''. Once your account is set up, you’ll automatically be following the @SocialCoop admin account. For your first toot, please write an introduction post that includes #introduction and any other hashtags of things that interest you.

Then, if you have not already, please set up your subscription payment on '''OpenCollective [https://opencollective.com/socialcoop via this link]'''. The fee is sliding scale $1-10/month, and setting up payments on an annual rather than monthly cycle saves our co-op a bit in terms of transaction fees.

Our instance is democratically governed by its members, which now includes you! To be an effective co-operative, it's important that members participate in its governance by generally keeping informed on the goings-on and strategic direction of social.coop. To participate in governance, please request to join the members' '''Loomio group [https://www.loomio.org/socialcoop/ via this link]'''. Note: after you register on Loomio, please [https://www.loomio.com/profile edit the introduction field on your profile] so we can recognize you as a member.

You’re getting this email from me because I’m the member of the [[Community Working Group Ops Team|Community Working Group Operations Team]] who is on-call this week.

Feel free to follow up with me if you have any issues. You can reach me by mentioning or direct messaging me on Social.coop at '''@[3. ADD YOUR HANDLE]''' and by replying to this email.

In Solidarity!

'''[4. ADD YOUR NAME]'''

Welcome Email

2026-03-22T18:11:34Z

Dphiffer:

Hi '''[1. ADD NEW MEMBER NAME]''',

Thanks for joining us! I want to welcome you to our community at Social.coop and to let you know that your application for membership has been approved! We're so glad you're here.

Social.coop is pioneering the process of participatory democratic ownership of platform coops and you have the power to shape the future of our platform and organization.

To set up your account on the '''Social.coop Mastodon, click this link [2. ADD REGISTRATION LINK]'''. Once your account is set up, you’ll automatically be following the @SocialCoop admin account. For your first toot, please write an introduction post that includes #introduction and any other hashtags of things that interest you.

Then, if you have not already, please set up your subscription payment on '''OpenCollective [https://opencollective.com/socialcoop via this link]'''. The fee is sliding scale $1-10/month, and setting up payments on an annual rather than monthly cycle saves our co-op a bit in terms of transaction fees.

Our instance is democratically governed by its members, which now includes you! To be an effective co-operative, it's important that members participate in its governance by generally keeping informed on the goings-on and strategic direction of social.coop. To participate in governance, please request to join the members' '''Loomio group [https://www.loomio.org/socialcoop/ via this link]'''. Note: when you register on Loomio, please include your Social.coop username in the title so we can recognize you as a member.

You’re getting this email from me because I’m the member of the [[Community Working Group Ops Team|Community Working Group Operations Team]] who is on-call this week.

Feel free to follow up with me if you have any issues. You can reach me by mentioning or direct messaging me on Social.coop at '''@[3. ADD YOUR HANDLE]''' and by replying to this email.

In Solidarity!

'''[4. ADD YOUR NAME]'''

Welcome Email

2026-03-22T17:50:35Z

Dphiffer:

Hi '''[ADD NEW MEMBER NAME]''',

Thanks for joining us! I want to welcome you to our community at Social.coop and to let you know that your application for membership has been approved! We're so glad you're here.

Social.coop is pioneering the process of participatory democratic ownership of platform coops and you have the power to shape the future of our platform and organization.

To set up your account on the '''Social.coop Mastodon, click this link [ADD REGISTRATION LINK]'''. Once your account is set up, you’ll automatically be following the @SocialCoop admin account. For your first toot, please write an introduction post that includes #introduction and any other hashtags of things that interest you.

Then, if you have not already, please set up your subscription payment on '''OpenCollective [https://opencollective.com/socialcoop via this link]'''. The fee is sliding scale $1-10/month, and setting up payments on an annual rather than monthly cycle saves our co-op a bit in terms of transaction fees.

Our instance is democratically governed by its members, which now includes you! To be an effective co-operative, it's important that members participate in its governance by generally keeping informed on the goings-on and strategic direction of social.coop. To participate in governance, please request to join the members' '''Loomio group [https://www.loomio.org/socialcoop/ via this link]'''. Note: when you register on Loomio, please include your Social.coop username in the title so we can recognize you as a member (see Instructions).

You’re getting this email from me because I’m the member of the [[Community Working Group Ops Team|Community Working Group Operations Team]] who is on-call this week.

Feel free to follow up with me if you have any issues. You can reach me by mentioning or direct messaging me on Social.coop at '''@[ADD YOUR HANDLE]''' and by replying to this email.

In Solidarity!

'''[ADD YOUR NAME]'''

Welcome Email

2026-03-22T17:48:28Z

Dphiffer:

Hi '''[ADD NAME]''',

Thanks for joining us! I want to welcome you to our community at Social.coop and to let you know that your application for membership has been approved! We're so glad you're here.

Social.coop is pioneering the process of participatory democratic ownership of platform coops and you have the power to shape the future of our platform and organization.

To set up your account on the '''Social.coop Mastodon, click this link [ADD REGISTRATION LINK]'''. Once your account is set up, you’ll automatically be following the @SocialCoop admin account. For your first toot, please write an introduction post that includes #introduction and any other hashtags of things that interest you.

Then, if you have not already, please set up your subscription payment on '''OpenCollective [https://opencollective.com/socialcoop via this link]'''. The fee is sliding scale $1-10/month, and setting up payments on an annual rather than monthly cycle saves our co-op a bit in terms of transaction fees.

Our instance is democratically governed by its members, which now includes you! To be an effective co-operative, it's important that members participate in its governance by generally keeping informed on the goings-on and strategic direction of social.coop. To participate in governance, please request to join the members' '''Loomio group [https://www.loomio.org/socialcoop/ via this link]'''. Note: when you register on Loomio, please include your Social.coop username in the title so we can recognize you as a member (see Instructions).

You’re getting this email from me because I’m the member of the [[Community Working Group Ops Team|Community Working Group Operations Team]] who is on-call this week.

Feel free to follow up with me if you have any issues. You can reach me by mentioning or direct messaging me on Social.coop at '''@[ADD YOUR HANDLE]''' and by replying to this email.

In Solidarity!

Onboarding New Community Working Group Ops Team Members

2025-06-19T16:46:12Z

Dphiffer: Add Zulip

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,
* 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 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 Google Drive and grant them edit access
* 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?

Federation with Threads

2025-02-07T16:37:08Z

Dphiffer:

Even before [https://threads.net Threads] launched rumors were circulating that Meta's new social media platform would support the ActivityPub protocol, which would allow it to interoperate with Mastodon instances like SocialCoop's. These rumors prompted quite a bit of discussion in the SocialCoop community, which was initially focused on whether or not SocialCoop should sign on to the [https://fedipact.online/ Anti-Meta Fedi Pact] These discussions largely took place in [[Loomio]], which are linked to in the timeline below.

As a result of [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 the poll on July 22, 2023] SocialCoop's Mastodon instance was set to ''Limit'' Threads. Following [https://opentermsarchive.org/en/memos/meta-dampens-hate-speech-policy/ changes to Meta's Community Guidelines], SocialCoop [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads/30 voted again] to change the setting to ''Suspend''.

=== Timeline ===
July 22, 2023: [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 Proposal: moderate Threads.net at a minimum of Limit level]

June 19, 2023: [https://www.loomio.com/d/AZcJK6y2/ Discussion: Support the Anti-Meta Fedi Pact]

July 4, 2023: Adam Mosseri (Head of Instagram) [https://www.threads.net/@mosseri/post/CuRtcYTNY3J announces] that ActivityPub integration is being worked on.

July 10, 2023: [https://www.loomio.com/p/etLGnr0z/poll-threads-net-defederation-level Poll: Threads.net Defederation Level]

July 28, 2023: [https://www.loomio.com/p/VyhTNnYW/would-you-personally-block-mute-threads-net- Would you personally block/mute Threads.net?]

December 13, 2023: Mark Zuckerberg [https://www.threads.net/@zuck/post/C0zXcQmxO77 announced] that testing of ActivityPub had started.

December 14, 2023: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads "Clarity on stance with regards to Threads"] started by a community member

March 21, 2024: Meta [https://engineering.fb.com/2024/03/21/networking-traffic/threads-has-entered-the-fediverse/ announces] that Threads ActivityPub integration is now available in the United States, Canada and Japan.

January 7, 2025: [https://opentermsarchive.org/en/memos/meta-dampens-hate-speech-policy/ Meta announces changes to community guidelines]

January 11, 2025: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads/30 vote to suspend Threads begins] after Meta changes their permissible speech policy. The vote passes.

February 7, 2025: Social.coop defederated from Threads.net (changing the ''Limit'' setting to ''Suspend'').

Federation with Threads

2025-02-07T15:03:01Z

Dphiffer: Tweak language

Even before [https://threads.net Threads] launched rumors were circulating that Meta's new social media platform would support the ActivityPub protocol, which would allow it to interoperate with Mastodon instances like SocialCoop's. These rumors prompted quite a bit of discussion in the SocialCoop community, which was initially focused on whether or not SocialCoop should sign on to the [https://fedipact.online/ Anti-Meta Fedi Pact] These discussions largely took place in [[Loomio]], which are linked to in the timeline below.

As a result of [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 the poll on July 22, 2023] SocialCoop's Mastodon instance was set to ''Limit'' Threads. Following [https://opentermsarchive.org/en/memos/meta-dampens-hate-speech-policy/ changes to Meta's Community Guidelines], SocialCoop voted again to change the setting to ''Suspend''.

=== Timeline ===
July 22, 2023: [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 Proposal: moderate Threads.net at a minimum of Limit level]

June 19, 2023: [https://www.loomio.com/d/AZcJK6y2/ Discussion: Support the Anti-Meta Fedi Pact]

July 4, 2023: Adam Mosseri (Head of Instagram) [https://www.threads.net/@mosseri/post/CuRtcYTNY3J announces] that ActivityPub integration is being worked on.

July 10, 2023: [https://www.loomio.com/p/etLGnr0z/poll-threads-net-defederation-level Poll: Threads.net Defederation Level]

July 28, 2023: [https://www.loomio.com/p/VyhTNnYW/would-you-personally-block-mute-threads-net- Would you personally block/mute Threads.net?]

December 13, 2023: Mark Zuckerberg [https://www.threads.net/@zuck/post/C0zXcQmxO77 announced] that testing of ActivityPub had started.

December 14, 2023: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads "Clarity on stance with regards to Threads"] started by a community member

March 21, 2024: Meta [https://engineering.fb.com/2024/03/21/networking-traffic/threads-has-entered-the-fediverse/ announces] that Threads ActivityPub integration is now available in the United States, Canada and Japan.

January 7, 2025: [https://opentermsarchive.org/en/memos/meta-dampens-hate-speech-policy/ Meta announces changes to community guidelines]

January 11, 2025: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads/30 vote to suspend Threads begins] after Meta changes their permissible speech policy. The vote passes.

February 7, 2025: Social.coop defederated from Threads.net (changing the ''Limit'' setting to ''Suspend'').

Federation with Threads

2025-02-07T15:02:23Z

Dphiffer: SocialCoop now suspends Threads.net

Even before [https://threads.net Threads] launched rumors were circulating that Meta's new social media platform would support the ActivityPub protocol, which would allow it to interoperate with Mastodon instances like SocialCoop's. These rumors prompted quite a bit of discussion in the SocialCoop community, which was initially focused on whether or not SocialCoop should sign on to the [https://fedipact.online/ Anti-Meta Fedi Pact] These discussions largely took place in [[Loomio]], which are linked to in the timeline below.

As a result of [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 the poll on July 22, 2023] SocialCoop's Mastodon instance was set to ''Limit'' Threads. Following [https://opentermsarchive.org/en/memos/meta-dampens-hate-speech-policy/ changes to Meta's Community Guidelines], SocialCoop voted again to change the setting to ''Suspend''.

=== Timeline ===
July 22, 2023: [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 Proposal: moderate Threads.net at a minimum of Limit level]

June 19, 2023: [https://www.loomio.com/d/AZcJK6y2/ Discussion: Support the Anti-Meta Fedi Pact]

July 4, 2023: Adam Mosseri (Head of Instagram) [https://www.threads.net/@mosseri/post/CuRtcYTNY3J announces] that ActivityPub integration is being worked on.

July 10, 2023: [https://www.loomio.com/p/etLGnr0z/poll-threads-net-defederation-level Poll: Threads.net Defederation Level]

July 28, 2023: [https://www.loomio.com/p/VyhTNnYW/would-you-personally-block-mute-threads-net- Would you personally block/mute Threads.net?]

December 13, 2023: Mark Zuckerberg [https://www.threads.net/@zuck/post/C0zXcQmxO77 announced] that testing of ActivityPub had started.

December 14, 2023: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads "Clarity on stance with regards to Threads"] started by a community member

March 21, 2024: Meta [https://engineering.fb.com/2024/03/21/networking-traffic/threads-has-entered-the-fediverse/ announces] that Threads ActivityPub integration is now available in the United States, Canada and Japan.

January 7, 2025: [https://opentermsarchive.org/en/memos/meta-dampens-hate-speech-policy/ Meta announces changes to community guidelines]

January 11, 2025: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads/30 vote to suspend Threads begins] after Meta changes their permissible speech policy. The vote passes.

February 7, 2025: social.coop defederated from Threads.net (changing the current ''Limit'' setting to ''Suspend'').

Federation with Threads

2025-01-24T15:05:03Z

Dphiffer: Clarify the defederation setting

Even before [https://threads.net Threads] launched rumors were circulating that Meta's new social media platform would support the ActivityPub protocol, which would allow it to interoperate with Mastodon instances like SocialCoop's. These rumors prompted quite a bit of discussion in the SocialCoop community, which was initially focused on whether or not SocialCoop should sign on to the [https://fedipact.online/ Anti-Meta Fedi Pact] These discussions largely took place in [[Loomio]], which are linked to in the timeline below.

As a result of [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 the poll on July 22, 2023] SocialCoop's Mastodon instance is currently set to ''Limit'' Threads, not to ''Suspend''. This effectively means that posts from Threads accounts are invisible to anyone who hasn't chosen to follow them. But users are not blocked from following Threads users. You can learn more about the differences between Limit and Suspend in the [https://docs.joinmastodon.org/admin/moderation/#server-wide-moderation Mastodon documentation].

=== Timeline ===
July 22, 2023: [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 Proposal: moderate Threads.net at a minimum of Limit level]

June 19, 2023: [https://www.loomio.com/d/AZcJK6y2/ Discussion: Support the Anti-Meta Fedi Pact]

July 4, 2023: Adam Mosseri (Head of Instagram) [https://www.threads.net/@mosseri/post/CuRtcYTNY3J announces] that ActivityPub integration is being worked on.

July 10, 2023: [https://www.loomio.com/p/etLGnr0z/poll-threads-net-defederation-level Poll: Threads.net Defederation Level]

July 28, 2023: [https://www.loomio.com/p/VyhTNnYW/would-you-personally-block-mute-threads-net- Would you personally block/mute Threads.net?]

December 13, 2023: Mark Zuckerberg [https://www.threads.net/@zuck/post/C0zXcQmxO77 announced] that testing of ActivityPub had started.

December 14, 2023: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads "Clarity on stance with regards to Threads"] started by a community member

March 21, 2024: Meta [https://engineering.fb.com/2024/03/21/networking-traffic/threads-has-entered-the-fediverse/ announces] that Threads ActivityPub integration is now available in the United States, Canada and Japan.

January 11, 2025: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads/30 vote to suspend Threads begins] after Meta changes their permissible speech policy. The vote passes.

February 7, 2025: social.coop will defederate from Threads.net (changing the current ''Limit'' setting to ''Suspend'').

Federation with Threads

2025-01-24T15:01:50Z

Dphiffer: Add vote outcome and planned defederation

Even before [https://threads.net Threads] launched rumors were circulating that Meta's new social media platform would support the ActivityPub protocol, which would allow it to interoperate with Mastodon instances like SocialCoop's. These rumors prompted quite a bit of discussion in the SocialCoop community, which was initially focused on whether or not SocialCoop should sign on to the [https://fedipact.online/ Anti-Meta Fedi Pact] These discussions largely took place in [[Loomio]], which are linked to in the timeline below.

As a result of [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 the poll on July 22, 2023] SocialCoop's Mastodon instance is currently set to ''Limit'' Threads, not to ''Suspend''. This effectively means that posts from Threads accounts are invisible to anyone who hasn't chosen to follow them. But users are not blocked from following Threads users. You can learn more about the differences between Limit and Suspend in the [https://docs.joinmastodon.org/admin/moderation/#server-wide-moderation Mastodon documentation].

=== Timeline ===
July 22, 2023: [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 Proposal: moderate Threads.net at a minimum of Limit level]

June 19, 2023: [https://www.loomio.com/d/AZcJK6y2/ Discussion: Support the Anti-Meta Fedi Pact]

July 4, 2023: Adam Mosseri (Head of Instagram) [https://www.threads.net/@mosseri/post/CuRtcYTNY3J announces] that ActivityPub integration is being worked on.

July 10, 2023: [https://www.loomio.com/p/etLGnr0z/poll-threads-net-defederation-level Poll: Threads.net Defederation Level]

July 28, 2023: [https://www.loomio.com/p/VyhTNnYW/would-you-personally-block-mute-threads-net- Would you personally block/mute Threads.net?]

December 13, 2023: Mark Zuckerberg [https://www.threads.net/@zuck/post/C0zXcQmxO77 announced] that testing of ActivityPub had started.

December 14, 2023: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads "Clarity on stance with regards to Threads"] started by a community member

March 21, 2024: Meta [https://engineering.fb.com/2024/03/21/networking-traffic/threads-has-entered-the-fediverse/ announces] that Threads ActivityPub integration is now available in the United States, Canada and Japan.

January 11, 2025: [https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads/30 vote to suspend Threads begins] after Meta changes their permissible speech policy. The vote passes.

February 7, 2025: social.coop will defederate from Threads.net.

Federation with Threads

2024-12-05T01:57:13Z

Dphiffer: Update the threads.net Loomio timeline

Even before [https://threads.net Threads] launched rumors were circulating that Meta's new social media platform would support the ActivityPub protocol, which would allow it to interoperate with Mastodon instances like SocialCoop's. These rumors prompted quite a bit of discussion in the SocialCoop community, which was initially focused on whether or not SocialCoop should sign on to the [https://fedipact.online/ Anti-Meta Fedi Pact] These discussions largely took place in [[Loomio]], which are linked to in the timeline below.

As a result of [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 the poll on July 22, 2023] SocialCoop's Mastodon instance is currently set to ''Limit'' Threads, not to ''Suspend''. This effectively means that posts from Threads accounts are invisible to anyone who hasn't chosen to follow them. But users are not blocked from following Threads users. You can learn more about the differences between Limit and Suspend in the [https://docs.joinmastodon.org/admin/moderation/#server-wide-moderation Mastodon documentation].

=== Timeline ===
July 22, 2023: [https://www.loomio.com/d/AZcJK6y2/discussion-support-the-anti-meta-fedi-pact/344 Proposal: moderate Threads.net at a minimum of Limit level]

June 19, 2023: [https://www.loomio.com/d/AZcJK6y2/ Discussion: Support the Anti-Meta Fedi Pact]

July 4, 2023: Adam Mosseri (Head of Instagram) [https://www.threads.net/@mosseri/post/CuRtcYTNY3J announces] that ActivityPub integration is being worked on.

July 10, 2023: [https://www.loomio.com/p/etLGnr0z/poll-threads-net-defederation-level Poll: Threads.net Defederation Level]

July 28, 2023: [https://www.loomio.com/p/VyhTNnYW/would-you-personally-block-mute-threads-net- Would you personally block/mute Threads.net?]

December 13, 2023: Mark Zuckerberg [https://www.threads.net/@zuck/post/C0zXcQmxO77 announced] that testing of ActivityPub had started.

March 21, 2024: Meta [https://engineering.fb.com/2024/03/21/networking-traffic/threads-has-entered-the-fediverse/ announces] that Threads ActivityPub integration is now available in the United States, Canada and Japan.

Matrix

2024-11-02T01:41:25Z

Dphiffer: Add some getting started instructions

Up to: [[Part Of::Platforms]]

See [[wikipedia:Matrix_(protocol)]]

# Get started by installing [https://element.io/ Element].
# If you don't have an account already register one with matrix.org. The account setup process is slightly more involved than most services, so it may take a little extra time.
# Once you've got Element setup and are signed in, try clicking on the room links listed below to join them.

If you want a more in-depth tutorial with screengrabs a long the way, see: [https://frontpagelinux.com/tutorials/beginners-guide-how-to-get-started-with-element-matrix/ Beginner’s Guide: How To Get Started With Element & Matrix]

== Rooms ==

* {{Matrix Room
|Name=Social.coop Open Chatroom
|Description=Channel for real time discussions among members of the https://social.coop/ user-owned corner of the fediverse (or anyone interested)
|Room Address=#SocialCoop:matrix.org
}}
* {{Matrix Room
|Name=Tech Chat
|Description=Discussion about the tech that social.coop uses
|Room Address=#socialcoop-tech:matrix.org
|Part Of=Tech Working Group
}}
* {{Matrix Room
|Name=Wiki Builders
|Description=Chat for discussing the wiki itself!
|Room Address=#socialcoop-wiki-builders:matrix.org
|Part Of=Tech Working Group,Wiki Builders
}}
* {{Matrix Room
|Name=CWG chat
|Description=Public group chat for the CWG group and for members or social.coop and the public to interact with the social.coop Community Working Group, CWG. the CWG is responsible for moderating the instance and overall non-technical duties.
|Room Address=#sc-cwg:matrix.org
|Part Of=Community Working Group
}}
* {{Matrix Room
|Name=Reading Group
|Description=(this is our discussion stream of readings)
|Room Address=#ourstohackandown:matrix.org
|Part Of=Community Working Group
}}

[[Category:Platform]]
[[Category:Protocol]]
[[Category:Chat]]

Matrix

2024-11-02T01:33:41Z

Dphiffer: Remove the Loomio feeds since it doesn't have a published address

Up to: [[Part Of::Platforms]]

See [[wikipedia:Matrix_(protocol)]]

== Rooms ==

* {{Matrix Room
|Name=Social.coop Open Chatroom
|Description=Channel for real time discussions among members of the https://social.coop/ user-owned corner of the fediverse (or anyone interested)
|Room Address=#SocialCoop:matrix.org
}}
* {{Matrix Room
|Name=Tech Chat
|Description=Discussion about the tech that social.coop uses
|Room Address=#socialcoop-tech:matrix.org
|Part Of=Tech Working Group
}}
* {{Matrix Room
|Name=Wiki Builders
|Description=Chat for discussing the wiki itself!
|Room Address=#socialcoop-wiki-builders:matrix.org
|Part Of=Tech Working Group,Wiki Builders
}}
* {{Matrix Room
|Name=CWG chat
|Description=Public group chat for the CWG group and for members or social.coop and the public to interact with the social.coop Community Working Group, CWG. the CWG is responsible for moderating the instance and overall non-technical duties.
|Room Address=#sc-cwg:matrix.org
|Part Of=Community Working Group
}}
* {{Matrix Room
|Name=Reading Group
|Description=(this is our discussion stream of readings)
|Room Address=#ourstohackandown:matrix.org
|Part Of=Community Working Group
}}

[[Category:Platform]]
[[Category:Protocol]]
[[Category:Chat]]

Matrix

2024-11-02T01:32:48Z

Dphiffer: Add additional Matrix channels

Up to: [[Part Of::Platforms]]

See [[wikipedia:Matrix_(protocol)]]

== Rooms ==

* {{Matrix Room
|Name=Social.coop Open Chatroom
|Description=Channel for real time discussions among members of the https://social.coop/ user-owned corner of the fediverse (or anyone interested)
|Room Address=#SocialCoop:matrix.org
}}
* {{Matrix Room
|Name=Tech Chat
|Description=Discussion about the tech that social.coop uses
|Room Address=#socialcoop-tech:matrix.org
|Part Of=Tech Working Group
}}
* {{Matrix Room
|Name=Wiki Builders
|Description=Chat for discussing the wiki itself!
|Room Address=#socialcoop-wiki-builders:matrix.org
|Part Of=Tech Working Group,Wiki Builders
}}
* {{Matrix Room
|Name=CWG chat
|Description=Public group chat for the CWG group and for members or social.coop and the public to interact with the social.coop Community Working Group, CWG. the CWG is responsible for moderating the instance and overall non-technical duties.
|Room Address=#sc-cwg:matrix.org
|Part Of=Community Working Group
}}
* {{Matrix Room
|Name=Loomio Feeds
|Description=Feeds from the social.coop Loomio - currently using RSS feeds from the main group and tech/infrastructure sub-group - the feeds show new discussion threads
}}
* {{Matrix Room
|Name=Reading Group
|Description=(this is our discussion stream of readings)
|Room Address=#ourstohackandown:matrix.org
|Part Of=Community Working Group
}}

[[Category:Platform]]
[[Category:Protocol]]
[[Category:Chat]]

Onboarding New Community Working Group Ops Team Members

2024-11-02T01:22:27Z

Dphiffer:

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 Google Drive and grant them edit access
* 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?

Onboarding New Tech Working Group Team Members

2024-10-30T12:20:08Z

Dphiffer: Combine the two email steps

Up to: [[Part Of::Tech Working Group]]

[[Has Description::How to set new members up with TWG]]

There are a few places you'll need to be granted access to start your onboarding process to join the [[Tech Working Group]]. These first 3 steps require help from an existing TWG member.

# [[Setup a user@social.coop forwarding email address]] and add the new forwarding email to the <code>tech.group</code> and <code>admin</code> email aliases
# [https://git.coop/users/sign_up A git.coop account]
# [https://git.coop/groups/social.coop/tech/-/group_members Group Membership in the "social.coop/tech" project]

Once you have those things you can continue to the next step of creating two merge requests (same idea as a "pull request" on Github):

# Add your SSH public key to the [https://git.coop/social.coop/tech/ansible/-/tree/master/roles/server/files/public-keys?ref_type=heads ansible repo, in roles/server/files]
# Add your GPG public key to the [https://git.coop/social.coop/tech/pass/-/tree/master/keys?ref_type=heads pass repo, in the keys folder]
# In the second merge request, add the email address associated with your GPG key to the <code>.gpg-id</code> file.

Next you will need an existing TWG member to post [https://www.loomio.com/d/jrbG5tue/server-access a poll to Loomio] about granting your server access.

Finally, someone with existing access will need to re-encrypt pass files with your new GPG key, granting you access to the infrastructure credentials.

You can get an overview of all the infrastructure using pass:

cd ~/.password-store/social.coop
pass

To access any given <code>pass</code> secret:

pass show social.coop/path/to/secret

Onboarding New Tech Working Group Team Members

2024-10-30T12:19:27Z

Dphiffer: Remove the "wiki" caveat, add the email aliases.

Up to: [[Part Of::Tech Working Group]]

[[Has Description::How to set new members up with TWG]]

There are a few places you'll need to be granted access to start your onboarding process to join the [[Tech Working Group]]. These first 3 steps require help from an existing TWG member.

# [[Setup a user@social.coop forwarding email address]]
# Add the new forwarding email to the <code>tech.group</code> and <code>admin</code> email aliases
# [https://git.coop/users/sign_up A git.coop account]
# [https://git.coop/groups/social.coop/tech/-/group_members Group Membership in the "social.coop/tech" project]

Once you have those things you can continue to the next step of creating two merge requests (same idea as a "pull request" on Github):

# Add your SSH public key to the [https://git.coop/social.coop/tech/ansible/-/tree/master/roles/server/files/public-keys?ref_type=heads ansible repo, in roles/server/files]
# Add your GPG public key to the [https://git.coop/social.coop/tech/pass/-/tree/master/keys?ref_type=heads pass repo, in the keys folder]
# In the second merge request, add the email address associated with your GPG key to the <code>.gpg-id</code> file.

Next you will need an existing TWG member to post [https://www.loomio.com/d/jrbG5tue/server-access a poll to Loomio] about granting your server access.

Finally, someone with existing access will need to re-encrypt pass files with your new GPG key, granting you access to the infrastructure credentials.

You can get an overview of all the infrastructure using pass:

cd ~/.password-store/social.coop
pass

To access any given <code>pass</code> secret:

pass show social.coop/path/to/secret

User:Dphiffer

2024-10-09T11:58:40Z

Dphiffer:

Hello, I'm Dan Phiffer ([https://social.coop/@dphiffer @dphiffer]), I'm a member of the [[Community Working Group Ops Team]] and [[Tech Working Group]]. I live in Upstate New York, in a city called Troy, a short distance upriver from Albany. I build and maintain websites at my [https://themarkup.org/ day job] as well as union organizing.

User:Dphiffer

2024-10-09T11:57:51Z

Dphiffer:

Hello, I'm Dan Phiffer ([https://social.coop/@dphiffer @dphiffer], I'm a member of the [[Community Working Group Ops Team]] and [[Tech Working Group]]. I live in Upstate New York, in a city called Troy, a short distance upriver from Albany. I build and maintain websites at my [https://themarkup.org/ day job].

User:Dphiffer

2024-10-07T11:51:45Z

Dphiffer: Added a brief bio for my user account

Hello, I'm Dan Phiffer and I'm a member of the [[Community Working Group Ops Team]] and [[Tech Working Group]]. I am [https://social.coop/@dphiffer @dphiffer] on [https://social.coop social.coop].

I live in Upstate New York, in a city called Troy, a short distance upriver from Albany.

Community Working Group Ops Team

2024-10-07T11:46:19Z

Dphiffer:

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

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

2024-10-07T11:44:47Z

Dphiffer: Created page with "Dan is a member of the Community Working Group Ops Team and Tech Working Group. He is also [https://social.coop/@dphiffer @dphiffer] on [https://social.coop social.coop]."

Dan is a member of the [[Community Working Group Ops Team]] and [[Tech Working Group]]. He is also [https://social.coop/@dphiffer @dphiffer] on [https://social.coop social.coop].

Tech Working Group

2024-10-07T11:42:41Z

Dphiffer: Dan has officially joined TWG

{{Working Group
|Description=all things hosting, site maintenance, and development.
|Members=User:Flancian,User:Edsu,User:Todrobbins,User:Dphiffer
}}
[[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
}}

Adding New Users to Meet.coop

2024-09-27T19:26:26Z

Dphiffer: Create new page

Members of the [[Community_Working_Group_Ops_Team|CWG ops]] team are tasked with responding to new signups for meet.coop accounts as part of their oncall responsibilities.

# Sign into [https://socialcoop.meet.coop/ socialcoop.meet.coop].
# Click on your username in the top-right part of the page.
# Click on Organization to visit the [https://socialcoop.meet.coop/admins Admins page].
# Click the green '''Invite User''' button.
# Enter the email address(es) of the social.coop member who needs an account.
# Check the [https://socialcoop.meet.coop/admins?tab=invited "Invited" tab] to confirm that they've been invited.

Sometimes the software responds with "XXX email is invalid." In those cases you might just want to try entering it again, it does work occasionally after retrying.

Community Working Group Ops Team

2024-09-27T19:18:50Z

Dphiffer: /* Tutorials */

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
* Dan Phiffer
* Django

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

2024-09-27T19:16:18Z

Dphiffer: Melissa is At-Large

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
* Dan Phiffer
* Django

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

Community Working Group Ops Team

2024-09-27T19:15:43Z

Dphiffer:

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
* Melissa Santos (At-Large Member)
* Dan Phiffer
* Django

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

Community Working Group Ops Team

2024-09-27T19:14:59Z

Dphiffer: Add new CWG members

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
* Melissa Santos
* Dan Phiffer
* Django

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

Onboarding New Tech Working Group Team Members

2024-09-24T02:24:16Z

Dphiffer:

Up to: [[Part Of::Tech Working Group]]

[[Has Description::How to set new members up with TWG]]

There are a few places you'll need to be granted access to start your onboarding process to join the [[Tech Working Group]]. These first 3 steps require help from an existing TWG member.

# [[Setup a user@social.coop forwarding email address]]
# [https://git.coop/users/sign_up A git.coop account]
# [https://git.coop/groups/social.coop/tech/-/group_members Group Membership in the "social.coop/tech" project]

Once you have those things you can continue to the next step of creating two merge requests (same idea as a "pull request" on Github):

# Add your SSH public key to the [https://git.coop/social.coop/tech/ansible/-/tree/master/roles/server/files/public-keys?ref_type=heads ansible repo, in roles/server/files]
# Add your GPG public key to the [https://git.coop/social.coop/tech/pass/-/tree/master/keys?ref_type=heads pass repo, in the keys folder]
# In the second merge request, add the email address associated with your GPG key to the <code>.gpg-id</code> file.

Next you will need an existing TWG member to post [https://www.loomio.com/d/jrbG5tue/server-access a poll to Loomio] about granting your server access.

Finally, someone with existing access will need to e-encrypt pass files with your new GPG key, granting you access to the infrastructure credentials.

You can get an overview of all the infrastructure using pass:

cd ~/.password-store/social.coop
pass

To access any given <code>pass</code> secret:

pass show social.coop/path/to/secret

One gotcha: <code>wiki</code> actually refers to join.social.coop.

Setup a user@social.coop forwarding email address

2024-09-24T02:21:24Z

Dphiffer: Created page with "Up to: Part Of::Tech Working Group Has Description::Forward social.coop email to a personal address This is setup using [https://webarch.email/ webarch.email]. # Go to the Aliases tab. # Add an alias for <code>[name]@social.coop</code> that forwards to a personal email address."

Up to: [[Part Of::Tech Working Group]]

[[Has Description::Forward social.coop email to a personal address]]

This is setup using [https://webarch.email/ webarch.email].

# Go to the Aliases tab.
# Add an alias for <code>[name]@social.coop</code> that forwards to a personal email address.

Onboarding New Tech Working Group Team Members

2024-09-24T02:16:33Z

Dphiffer:

Up to: [[Part Of::Tech Working Group]]

[[Has Description::How to set new members up with TWG]]

There are a few places you'll need to be granted access to start your onboarding process to join the [[Tech Working Group]]. These first 3 steps require help from an existing TWG member.

# [[Setup a user@social.coop forwarding email address]]
# [https://git.coop/users/sign_up A git.coop account]
# [https://git.coop/groups/social.coop/tech/-/group_members Group Membership in the "social.coop/tech" project]

Once you have those things you can continue to the next step of creating two merge requests (same idea as a "pull request" on Github):

# Add your SSH public key to the [https://git.coop/social.coop/tech/ansible/-/tree/master/roles/server/files/public-keys?ref_type=heads ansible repo, in roles/server/files]
# Add your GPG public key to the [https://git.coop/social.coop/tech/pass/-/tree/master/keys?ref_type=heads pass repo, in the keys folder]

Next you will need an existing TWG member to post [https://www.loomio.com/d/jrbG5tue/server-access a poll to Loomio] about granting your server access.

Finally, someone with existing access will need to e-encrypt pass files with your new GPG key, granting you access to the infrastructure credentials.

You can get an overview of all the infrastructure using pass:

cd ~/.password-store/social.coop
pass

To access any given <code>pass</code> secret:

pass show social.coop/path/to/secret

One gotcha: <code>wiki</code> actually refers to join.social.coop.

Onboarding New Tech Working Group Team Members

2024-09-24T02:09:11Z

Dphiffer:

There are a few places you'll need to be granted access to start your onboarding process to join the [[Tech Working Group]]. These first 3 steps require help from an existing TWG member.

# [[Setup a user@social.coop forwarding email address]]
# [https://git.coop/users/sign_up A git.coop account]
# [https://git.coop/groups/social.coop/tech/-/group_members Group Membership in the "social.coop/tech" project]

Once you have those things you can continue to the next step of creating two merge requests (same idea as a "pull request" on Github):

# Add your SSH public key to the [https://git.coop/social.coop/tech/ansible/-/tree/master/roles/server/files/public-keys?ref_type=heads ansible repo, in roles/server/files]
# Add your GPG public key to the [https://git.coop/social.coop/tech/pass/-/tree/master/keys?ref_type=heads pass repo, in the keys folder]

Next you will need an existing TWG member to post [https://www.loomio.com/d/jrbG5tue/server-access a poll to Loomio] about granting your server access.

Finally, someone with existing access will need to e-encrypt pass files with your new GPG key, granting you access to the infrastructure credentials.

You can get an overview of all the infrastructure using pass:

cd ~/.password-store/social.coop
pass

To access any given <code>pass</code> secret:

pass show social.coop/path/to/secret

One gotcha: <code>wiki</code> actually refers to join.social.coop.

Part of: [[Tech Working Group]]

Tech Working Group/Onboarding

2024-09-24T02:05:57Z

Dphiffer: Dphiffer moved page Tech Working Group/Onboarding to Onboarding New Tech Working Group Team Members: More clearly states what the pages is for

#REDIRECT [[Onboarding New Tech Working Group Team Members]]

Onboarding New Tech Working Group Team Members

2024-09-24T02:05:57Z

Dphiffer: Dphiffer moved page Tech Working Group/Onboarding to Onboarding New Tech Working Group Team Members: More clearly states what the pages is for

Onboarding New Tech Working Group Team Members

2024-09-24T02:03:55Z

Dphiffer: Create a TWG onboarding page