lookit / lookit/lookit-api

Email changes: switch to .org

Open
#1,904 0 comments 0 reactions 2 assignees Claimed by @mekline View on GitHub
STF-transfer
Dominant language
Python
Stars
12
Forks
21
Avg merge
5d 19h
Merged PRs (30d)
5

Description

## Summary

As we make the switch to the CHS .org domain, we need to update and consolidate our email addresses. This issue tracks the changes needed in the lookit-api repository and website settings (some of which are in lookit orchestrator).

## Question

We list contact info on the [researcher-facing documentation](https://github.com/lookit/lookit-docs/pull/552) and site. What email addresses do we want to use for researchers, families, and a general-purpose contact (if we need that)? Here are some suggestions:

Email | Audience | Purpose
-- | -- | --
support@ | Researchers/families | Technical issues from both researchers and families
researchers@ | Researchers | Non-tech-support questions from researchers
families@ | Families | Non-tech-support questions from families
info@ / hello@ | Everyone/other | General purpose contact (not sure if we need this?)

## To do

- [ ] Identify and change all outdated email references (non-family-facing)
- [x] Finish domain authentication in Squarespace for Google Workspace emails (SPF, DMARC, DKIM)
- [x] Set up domain authentication for sending chs-bot emails via SendGrid
- [x] Set up chs-bot email as an alias for support (no one should be emailing chs-bot but having a landing place will protect our domain reputation)
- [ ] Set up email accounts for team members: @mekline ✅ Becky ✅ @sradifera ?
- [ ] Set up shared/group/delegate access to non-individual inboxes, if necessary (support, and others if needed)

## Gated by participant announcement

- [ ] Change the site settings to use chs-bot@childrenhelpingscience.org instead of lookit-bot@mit.edu to send automated emails
- [ ] Identify and change all outdated family-facing email references

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.