---
tags: [infrastructure]
---

# Conda Community/Comms Infrastructure

Dave C is creating this to document where things stand as of his departure in 2024/01. This document might end up under the main conda HackMD organization. We'll see.

**Note**

In every place I could find, "Dave Clements" below means that it is connected to Dave's personal GMail, not to his Anaconda email.

## Big Picture

### Remember the Conda-Infrastructure Repo

There is a [conda-infrastructure repo in GitHub](https://github.com/conda/infrastructure) that supports infrastructure similar to what is described here. None of what's described here is implemented in that repo.

But maybe some of it should be? Keep that in mind when reviewing this document.

### 1Password

Credentials for most of the things listed in this document are in the `shared` conda vault in 1Password. This vault was set up through 1Password's open source support program. It's free.

**Who/Access**

* As of: 2024/01/03
* Owners:
* Jaime Rodríguez-Guerra
* Jannis Leidel
* Ken Odegard
* Managers
* Jaime Rodríguez-Guerra
* Jannis Leidel
* Dasha Gurova
* Ken Odegard
* Dave Clements
* Marcel Bargull
* Team Members
* None

**What needs to be done**

* Need to setup more than all-or-nothing access. For example, we should be able to give Code of Conduct folks access to only [CoC stuff](#Code-of-Conduct) (and restrict access for others), and give the social media team access to only social media info.

### Google Workspace

We don't yet have this set up. We can get this for free through our NumFOCUS sponsorship. Once we get this, we can use Google Drive, and Google groups.

**Who**

* Jannis Leidel is spearheading this.

**What needs to be done**

* Everything.

### [e-mail]

When we need an email account for something this is our go to account. See the individual items below for what is tied to this (almost everything is).

If and when we get our [Google Workspace](#Google-Workspace) set up, we might want to shift all of this to an account under that ([e-mail]?).

**Who**

All email to this account is forwarded to
* Jaime Rodríguez-Guerra
* Dave Clements

**What needs to be done**

* Recovery email is Jaime's. This isn't terrible as this is only used when recovering the account.
* There is no recovery phone number (because even though 2FA was off, Google would still invoke it.)
* 2FA is not enabled.
* Jaime is in the process of reenabling 2FA using the 1Password vault.

### Orbit

[Orbit](https://orbit.love/) is a community management platform that integrates community member activity from all sorts of places. It shows a dashboard that tracks how community participation is trending.

**Who/Access**

As of 2024/01/03

* Owners
* Jannis Leidel
* Dave Clements
* Jaime Rodriguez-Guerra
* [e-mail] (credentials in 1Password)

**Details**

Orbit uses [[e-mail]](#condamanagergmailcom) to pull information from [StackOverflow](#StackOverflow) and from the [conda discourse instance](#Discourse).

**What needs to be done**

* Orbit is not yet connected to the [conda-incubator GitHub org](https://github.com/conda-incubator). We thought we had, but it isn't showing up.
* It's connection to [LinkedIn](#Linkedin) is through Dave Clements's LinkedIn account. That's probably suboptimal.

#### StackOverflow

Orbit uses the [[e-mail]](https://hackmd.io/Thihzw7HSXS9rfO-NrQBHg?view#condamanagergmailcom) login on StackOverflow to pull information from [StackOverflow](https://stackoverflow.com/search?q=%23conda).

**Who/Access**

* [e-mail]
* Credentials are in 1Password

### Big Picture Summary

If we were to diagram everything in our current (2024/01) conda community infrastructure, it would show two prominent features:

* All credentials are stored in [1Password](#1Password)
* Almost everything (exception: [Code of Conduct](#Code-of-Conduct)) ties back to the [[e-mail]](#condamanagergmailcom) account.

## Social Media

### Buffer

We have a [Buffer](https://buffer.com/) account that enables us to post 1 message to up to 3 social media channels. This is configured to send messages to both [LinkedIn](#Linkedin), and to [Mastodon](#Mastodon).

Buffer saves some of the effort of posting to multiple channels, but not all of it. For example, if you have user IDs in your post, you will need to update those for each platform before posting.

**Access**

* Credentials are stored in 1Password.
* Account belongs to [e-mail]

### Mastodon

We moved off of [Twitter](#Twitter) and onto Mastodon in 2023. (We retired our Twitter account at the end of 2023.) Our account is [@[e-mail]](https://fosstodon.org/@conda).

You can either post directly in Mastodon or via our Buffer account.

We use the hashtag #conda on everything we post.

**Access**

* Credentials are stored in 1Password.
* Account belongs to [e-mail]

### LinkedIn

When we moved off of [Twitter](#Twitter) we set up an [organization page for the conda community](https://linkedin.com/company/condacommunity) on LinkedIn. Organizations don't have logins on LinkedIn. Rather they are controlled by individuals' accounts.

**Who**

As of 2024/02/03 these people have write access to the conda community page on LinkedIn:

* Jamie Rodriguez-Guerra Pedregal
* Dave Clements

They are both *super-admins!*

We usually (?) post to LinkedIn using [Buffer](#Buffer).

### Bit.ly

[Buffer](#Buffer) uses the buff.ly link shortener by default, but you can override that with a specific link, and sometimes you want that to be an easy to remember link. You can create those links in bit.ly.

**Access**

* Credentials are stored in 1Password.
* 2FA is not enabled.
* Username: condamanager
* Email: [e-mail].

### BlueSky

Conda has an account on BlueSky, but as of 2024/01, we have not posted anything to it.

**Access**

* Credentials are stored in 1Password.
* 2FA is not enabled.
* Username: condaproject
* Email: [e-mail].

### Twitter

The conda project stopped posting to Twitter/X on 2024/0/01. The account is still there, and was updated to state that we had moved to [Mastodon](#Mastodon) and [LinkedIn](#LinkedIn).

**Access**

* Credentials are stored in 1Password.

## Web

### conda.org

The source for conda.org is [stored in GitHub](https://github.com/conda-incubator/conda-dot-org), and deployments are automatically done using Nelify and GitHub.

#### Algolia

Conda.org uses [Algolia search](https://www.algolia.com/) for site search. The search is configured at Algolia under the [e-mail] account. That account also recieves weekly email updates about recent search activity.

**Access**

* Credentials are stored in 1Password.

#### GoatCounter

Used for analytics on conda.org.

* Travis Hathaway

### Calendar

The [conda community calendar](https://calendar.google.com/calendar/u/0?cid=ODgwNTU3MGE0ZTFjYTIzMTk4NDI5NzFkYjQzODBlZDUxOGM0OTA1NzdjMDY0NTRhZGYyMzAzNzM0NTA2ZjM5N0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t) is a Google calendar owned by [e-mail]. It is [displayed](https://conda.org/community/calendar) on [conda.org](https://conda.org/community/calendar). The calendar can be seen by anyone.

**Who**

* [e-mail] (owner)
* Jaime Rodriguez-Guerra
* Travis Hathaway
* Dave Clements

### Discourse

The [Conda Community Forum](https://conda.discourse.group/) is a [Discourse](https://www.discourse.org/)-based Q&A forum focused on the conda ecosystem.

**Who/Access**

As of 2024/01/03

* Admins: (We are limited to 5 admins)
* conda-bot ([e-mail])
* Jaime Rodriguez-Guerra
* Jannis Liedel
* Marcel Bargull
* Dave Clements

**conda-bot**

The conda-bot user ([e-mail]) is also

* Official contact account/email for site
* Chat integration Discourse user
* Used to send messages about posts to specific [Matrix](#Matrix) channels

#### Google Search Console

The conda Discourse site uses [Google Search Console](https://search.google.com/search-console?resource_id=https%3A%2F%2Fconda.discourse.group%2F&hl=en) for analytics. The account is owned by [[e-mail]](#condamanagergmailcom)

**Who/Access**

* [e-mail] (Owner)
* Jaime Rodriguez-Guerra
* Dave Clements

### YouTube

Conda [has a YouTube channel](https://www.youtube.com/channel/UCNc3BL-gO8hbx_7DdEDcofg), and whenever there is an interesting video about Conda in YouTube, we link to it from our channel.

**Access**

* [e-mail] (Primary Owner)
* Dave Clements (Owner)
* Jaime Rodriguez-Guerra (Owner)
* Jannis Liedel (Owner)

## Chat

### Matrix

#### Conda Community Matrix Space

Conda's community chat happens in Matrix, in rooms that are organized under the [Conda Community Matrix Space](https://matrix.to/#/#conda:matrix.org).

**Who**

As of 2024/01/03 the space admins were

* Matt Becker
* Jaime Rodriguez-Guerra
* Jannis Liedel
* Dave Clements

#### Conda Rooms

The conda community Matrix space contains both public and private rooms. The public rooms can be joined by anyone and are visible when you visit the space home page. You need an invite to join a private room. There is no way to see the list of private rooms in the space.

The individual rooms are run by different groups of people. There is no single user that has admin access to all rooms.

**What needs to be done**

* Should conda-bot be made a space admin?

#### @conda-bot:matrix.org

@conda-bot:matrix.org is the Matrix User that Discourse uses to send messages about new posts to channels. It belongs to every room that gets messages from Discourse. Except for membership in the Matrix room, all configuration of the Discourse-Matrix connection happens in Discourse.

You will only need to login to to set up new bridges from Discourse categories to Matrix rooms.

**Access**

* Credentials are stored in 1Password.

## Mailing Lists

We have two mailing lists that are hosted by SympaLists.net:

* [e-mail]
* [e-mail]

We pay for these. However, it's not clear if we will continue to pay for them. If the Google Workspace happens, we might just set up Google Groups. (Some people will hate this, as you need a Google ID to join a Google Group list. But it is free.)

**Access**

* SympaLists Admin / Account access
* Owned by [e-mail]
* Credentials to log into SympaLists are stored in 1Password
* Individual mailing list admin / account access
* Admins, both lists:
* Jaime Rodriguez-Guerra
* Dave Clements

**What needs to be done**

* Decide the fate of these lists.
* The steering list expires on 2024/02/08
* The announce list expires on 2024/03/08

## Code of Conduct

The conda Code of Conduct committee has a reporting and tracking infrastructure for incident reports and decisions.

This infrastructure is documented in a Google Drive folder that committee members have access to.

**What needs to be done**

* Currently, login credentials for CoC infrastructure accounts are stored in the same 1Password vault as everything else. This is not ideal as only CoC members should have access to these credentials.

### [e-mail]

[e-mail] is the official email address of the committee. It is implemented as a Google Group. This means it is currently "controlled" by Anaconda, but it will move to NumFOCUS control once we set up the Google Workspace. Every member of the committee is on this list.

**Access/Who**

* The committee chairs, plus Jaime Rodriguez-Guerra can add and drop people from this list.
* Posts are not publicly accessible.

### JotForm

The Conda CoC incident reporting form uses JotForm. When the form is submitted, JotForm does two things

* Sends an email to [e-mail] (that is then formwarded by GMail to [e-mail]).
* Creates a report, along with any submitted documents/images, in a Google Folder controlled by [e-mail].

**Access**

* User: [e-mail]
* Login credentials are in 1Password

### [e-mail]

[e-mail] **is not** the public email address of the committee. (See [e-mail].) Rather it exists to support the infrastructure of recording and distributing incident reports to the committee.

This email forwards incident reports to the CoC committee, and owns the Google folder that is used to store and track incident reports and actions.

**Access**

* Login credentials are in 1Password

#### CoC Google Drive

**Who**

All members of the CoC have write access to a shared folder that is used to store and track incident reports and actions.