Slack

We use Slack extensively!

Channel naming conventions

• All channels begin with #login-
• All channels with external collaborators start with #login-partners-
• Sprint team channels look like #login-team-<name>

Groups

Use these to ping a large group of people, without having to @here or @channel a room full of the wrong people.

Oncall Handles

These handles ping oncall engineers, use for emergencies or urgent items.

• @login-appdev-oncall The application developer oncall
• @login-devops-oncall The devops oncall
• @login-deployer The appdev app deployer
• @login-devtools-oncall The devtools developer oncall

Team Handles

• @login-devops-team Group to tag the Login.gov devops team
• @login-partnerships-team Group to address Login.gov partnerships team members
• @login-ux-feds Group to tag the Login.gov UX federal employees
• @login-ux-practice Group to tag all of the Login.gov UX practitioners
• @login-ux-ops Group to tag the Login.gov UX Operations team
• @github-admins-login members of this group can edit identity-core GitHub team membership

Sprint Team Handles

• @login-ada To tag members of Ada
• @login-grace To tag members of Grace
• @login-joy To tag members of Joy
• @login-melba To tag members of Melba

Channels

Here are some common Slack Channels for the Login.gov team

Filter by

All-team Channel

• #login: important

  Channel for the whole team, team-wide announcements and so on

Sub-Team Channels

Design/UX

• #login-ux: design

  Channel for the user experience design team (research, visual, content)

• #login-public-site Discussion around the Login.gov marketing/brochure/public site

• #login-design-system design

  Discussion around the Login.gov design system

• #login-accessibility design

  Accessibility working group

Engineering/AppDev

• #login-appdev: appdev

  General IDP and Appdev matters

• #login-reporting: Analytics and reporting channel

Engineering/DevOps

• #login-devops: devops

  Platform and tools channel

• #login-platform-support: appdev

  devops

  Platform channel specifically for helping people set up their environments (AWS, Terraform, etc.)

• #login-alarms: Channel for critical automated notifications from production

• #login-events: Channel for automated notifications from production

• #login-security: Channel for security-related discussions

• #login-soc-events: Channel for automated notifications from AWS SOC monitoring

• #login-load-testing: Discussion around load testing of Login.gov

• #login-compliance FedRAMP and other Compliance information

Partners

• #login-partnerships: Internal discussion around partnerships initiatives

• #login-partner-support: Channel for providing customer support, we often grant guest Slack access to partners

Product

• #login-product-strategy: Cross-team product strategy

Sprint Teams

• #login-team-ada Team Ada channel

• #login-team-agnes Team Agnes channel

• #login-team-annie Team Annie channel

• #login-team-evelyn Team Evelyn channel

• #identity-idva Team IDVA channel

• #login-team-joy Team Joy channel

• #login-team-judy Team Judy channel

• #login-team-katherine Team Katherine channel

• #login-team-kimberly Team Kimberly channel

• #login-team-mary Team Mary channel

• #login-team-melba Team Melba channel

• #login-team-radia Team Radia channel

• #login-team-timnit Team Timnit channel

• #login-team-ursula Team Ursula channel

Other Channels

• #login-handbook: Discussion and coordination around this handbook

• #login-leads: Login.gov leadership team channel

• #login-professional-development: Discussion and coordination around professional development, attending conferences, etc.

• #login-situation: devops

  Incident response coordination channel

• #login-random: important

  Fun/random/miscellaneous channel

• #login-fraud-mitigation: Discussion around fraud mitigation

• #login-user-support: Escalations and triage from user support

• #cop-containers: Channel for workflows on containerization in Docker across TTS