Skip to content
This repository has been archived by the owner on Jul 26, 2021. It is now read-only.

Help readers understand where to ask questions #190

Closed
3 tasks
brittag opened this issue Jul 14, 2016 · 2 comments
Closed
3 tasks

Help readers understand where to ask questions #190

brittag opened this issue Jul 14, 2016 · 2 comments
Assignees

Comments

@brittag
Copy link

brittag commented Jul 14, 2016

In order to confidently ask for help with questions about ATOs and other infrastructure and compliance topics, 18F staff members need to know where to ask questions.

Currently people don't consistently understand what belongs in the available Slack channels (especially the difference between #infrastructure and #compliance - but also they may ask similar questions in #cloud-gov-support and #cloud-gov-highbar). Let's do a few things to fix this:

  • Work with relevant channel owners to clarify the "topic" and "purpose" text of the #infrastructure and #compliance channels.
  • Check the pages in this guide that refer to Slack channels, and revise those references to be more accurate and informative:
  • Infrastructure - "Any questions? Ask in #infrastructure."
  • General Security Standards - "If you see something that isn’t right or that you are unsure of, drop a note in #infrastructure." + "If you need assistance, drop a note into #infrastructure, #compliance or #cloud-gov-highbar."
  • ATO Checklist - "You are welcome to ask any questions as comments in the issue or #infrastructure."
  • homepage - "Reach out to the #infrastructure team at least a month in advance of launch to give them a heads up."
  • Dynamic Scanning - "Inform your team and #infrastructure before running it on live (not locally-hosted) sites."
  • Add relevant channel names to other pages where people may run into confusion, so that people know where to ask for help with those topics.
@its-a-lisa-at-work
Copy link
Contributor

Moved to waiting until the BYS is merged with Handbook

@its-a-lisa-at-work
Copy link
Contributor

Closing out and moving still relevant issues to new cards

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants