Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce the concept of "optional" triggers in the Inclusion Bot wordlist and support opting out of those notifications #528

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

mgwalker
Copy link
Member

This PR proposes to introduce a tiered structure to the trigger phrases in the Inclusion Bot list. The first tier would be those terms that we agree should be flagged in all circumstances. The second tier would be those terms that we think people should be aware of but they may not want to be reminded of regularly.

This PR allows us to designate a term as optional and allows users to opt-out of "optional" notifications. If a Slack user says one of the optional phrases and is opted out, they will not get a notification about it.

I'm hopeful that this furthers Inclusion Bot's mission of education and thoughtfulness in a way that allows people some agency if they decide that they do not wish to change their behavior around some terms, while still allowing us to constantly remind people about language that we believe is more universally uninclusive.

This update does NOT make any changes to the word list. The entire word list is still consider mandatory. Making individual trigger words/phrases "optional" would be a separate task.


Checklist:

  • Code has been formatted with prettier
  • The OAuth wiki
    page has been updated if Charlie needs any new OAuth events or scopes
  • The Environment Variables
    wiki page has been updated if new environment variables were introduced
    or existing ones changed
  • The dev wiki has been updated, e.g.:
    • local development processes have changed
    • major development workflows have changed
    • internal utilities or APIs have changed
    • testing or deployment processes have changed
  • If appropriate, the NIST 800-218 documentation has been updated

@mgwalker mgwalker requested a review from a team as a code owner February 27, 2024 21:01
@mgwalker mgwalker changed the title Introduce "optional" triggers in the Inclusion Bot wordlist and support opting out of those notifications Introduce the concept of "optional" triggers in the Inclusion Bot wordlist and support opting out of those notifications Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant