Simpler.Grants.gov Public Wiki
Grants.govSimpler.Grants.govGitHubDiscourse
  • 👋Welcome
  • GET INVOLVED
    • Why open source?
    • How to contribute code
    • How to file issues
      • Report a bug
      • Request a feature
      • Report a security vulnerability
    • Community guidelines
      • Code of Conduct
      • Reporting and removing content
      • Incident response protocol
    • Community events
      • Fall 2024 Coding Challenge
        • Event Submissions & Winners
      • Spring 2025 Collaborative Coding Challenge
        • Event Submissions & Winners
    • Communication channels
  • Product
    • Roadmap
    • Deliverables
      • 🏁Static site soft launch
      • 🏁Static site public launch
      • 🏁GET Opportunities
      • 🏁Open source onboarding
      • 🏁Co-Design Group planning
    • Decisions
      • ADR Template
      • ADRs
        • Dedicated Forum for Simpler.Grants.gov Community
        • Recording Architecture Decisions
        • Task Runner for the CI / CD Pipeline
        • API Language
        • Use Figma for design prototyping
        • ADR: Chat
        • DB Choices
        • API Framework and Libraries
        • Back-end Code Quality Tools
        • Front-end Language
        • Communications Tooling: Wiki Platform
        • Use Mural for design diagrams and whiteboarding
        • Ticket Tracking
        • Front-end Framework
        • Front-end Code Quality Tools
        • Front-end Testing & Coverage
        • Backend API Type
        • Front-end Testing & Coverage
        • Deployment Strategy
        • Use U.S. Web Design System for components and utility classes
        • FE server rendering
        • Use NPM over Yarn Architectural Decision Records
        • U.S. Web Design System in React
        • Communications Tooling: Video Conferencing
        • Back-end Production Server
        • Communications Tooling: Analytics Platform
        • Commit and Branch Conventions and Release Workflow
        • Cloud Platform to Host the Project
        • Infrastructure as Code Tool
        • Data Replication Strategy & Tool
        • HHS Communications Site
        • Communications Tooling: Email Marketing
        • Communications Tooling: Listserv
        • Use Ethnio for design research
        • Uptime Monitoring
        • Database Migrations
        • 30k ft deliverable reporting strategy
        • Public measurement dashboard architecture
        • Method and technology for "Contact Us" CTA
        • E2E / Integration Testing Framework
        • Logging and Monitoring Platform
        • Dashboard Data Storage
        • Dashboard Data Tool
        • Search Engine
        • Document Storage
        • Document Sharing
        • Internal Wiki ADR
        • Shared Team Calendar Platform
        • Cross-Program Team Health Survey Tool
        • Adding Slack Users to SimplerGrants Slack Workspace
        • Repo organization
        • Internal knowledge management
        • Migrate Existing API Consumers
      • Infra
        • Use markdown architectural decision records
        • CI/CD interface
        • Use custom implementation of GitHub OIDC
        • Manage ECR in prod account module
        • Separate terraform backend configs into separate config files
        • Database module design
        • Provision database users with serverless function
        • Database migration architecture
        • Consolidate infra config from tfvars files into config module
        • Environment use cases
        • Production networking long term state
    • Analytics
      • Open source community metrics
      • API metrics
  • DESIGN & RESEARCH
    • Brand guidelines
      • Logo
      • Colors
      • Grid and composition
      • Typography
      • Iconography
      • Photos and illustrations
    • Content guidelines
      • Voice and tone
    • User research
      • Grants.gov archetypes
  • REFERENCES
    • Glossary
  • How to edit the wiki
Powered by GitBook
On this page
  • Getting Started
  • 1. Joining Slack
  • 2. Navigating Channels
  • 3. Understanding Direct Messages
  • Using Slack for Project Contributions
  • 1. Communication Etiquette
  • 2. Sharing Updates
  • 3. Asking Questions
  • 4. Collaborating on Code
  • 5. Meeting Coordination
  • Best Practices and Conventions
  • 1. Channel Guidelines
  • 2. Notifications Management
  • 3. Use threads to continue a conversation instead of posting to the main channel
  • Change log

Was this helpful?

Edit on GitHub
  1. GET INVOLVED
  2. Communication channels

Slack - Community chat

User guide for participating in our Slack workspace.

Last updated 2 months ago

Was this helpful?

Welcome to our Slack workspace!

Slack is our chat platform for communication and collaboration within the Simpler Grants community. This guide will help you get started and make the most out of your Slack experience. Please to join.

Getting Started

1. Joining Slack

  • If you need help installing Slack, please use the link below to our step-by-step guide.

  • If you haven't already, sign up for Slack using the invitation link above.

  • Once signed up, download the Slack desktop or mobile app to easily access the workspace.

  • Post a short introduction in . Please include:

    • Name

    • Pronouns

    • What brings you to the Simpler.Grants.gov community

2. Navigating Channels

  • Our channels use a prefix naming convention to explain what the channel is used for.

  • Familiarize yourself with the different channels in our workspace. Channels are organized by topics, projects, or teams.

3. Understanding Direct Messages

  • As an open source community, we try to keep conversations in public channels to make sure that the conversation is open and viewable to all participants. We recommend that you err on the side of posting in a public channel if you can.

  • Use direct messages to communicate privately with individual team members if the

  • You can also create group messages for small team discussions.

Using Slack for Project Contributions

1. Communication Etiquette

  • When possible please use public channels instead of private or group DMs to make sure that we are creating a resource for everyone in the community.

  • Avoid posting personally identifiable information on slack. This is a public chat platform and anything posted can be seen by the general public.

2. Sharing Updates

  • Use appropriate channels to share project updates, announcements, or important information.

  • Utilize threads to keep conversations organized and focused.

3. Asking Questions

  • Don't hesitate to ask questions in relevant channels or through direct messages.

  • Prefix your question with "@channel" or "@here" if it's urgent or requires immediate attention.

    • This will notify everyone in the channel, so only use in case extreme urgency.

4. Collaborating on Code

  • Share code snippets or GitHub links directly in Slack channels for quick feedback.

5. Meeting Coordination

  • Use Slack to schedule meetings, share agendas, and coordinate with team members.

  • Utilize integrations like Google Calendar or Zoom to sync meeting schedules.

Best Practices and Conventions

1. Channel Guidelines

  • Each channel may have specific guidelines or rules outlined in the channel description. Familiarize yourself with these guidelines before participating.

2. Notifications Management

  • Customize your notification settings to ensure you receive relevant updates without being overwhelmed.

  • Consider muting channels or threads that are less relevant to your role or interests.

3. Use threads to continue a conversation instead of posting to the main channel

  • When you see a message that you would like to respond to in the main channel, please make use of the threads feature to keep the main channels clear and concise.

    • A thread can be created on a new post in the main channel by hovering over the message and clicking "reply in thread" on the toolbar that appears.

    • You can join an existing thread by clicking on the Reply underneath a message that already has an ongoing thread.

  • When in a thread, only the people who are currently involved in that thread will get notifications, which helps to keep notification spam down for all members of the main channel.

    • If you need to get the attention of someone not in the thread, you can use the @<username> command, which will notify them that they were mentioned in the thread.

    • You can also choose to send a response to both the thread and main channel if you belive that a threaded message should be seen by everyone.

Change log

Major updates to the content of this page will be added here.

Date
Update
Notes

2/12/2024

Initial Content

Updated with Initial content

Follow the that has been set by the Simpler Grants community

Use for requesting code reviews and discussions.

use this invitation link
#all-introductions
Installing Slack
Naming Conventions
Recommended Channels
code of conduct
#topic-code-review