Create partner guide to 18F communication and dev tools

[nikzei]

To help new partners learn about the tools that we use for day to day collaboration, and to get clear during onboarding about which tools we can use together, we should have an onboarding guide that introduces new partners to basic 18F tooling. No real deadline for this.

• @hannakane is working on something similar for the Handbook - perhaps this could be the guide that partners use;

• @awfrancisco has started this, which we could build off of.

• @pburkholder cited this article as helpful in explaining the value of informal chat tools.

• TC Baxter suggested regarding the items in the guide, that,

"they're inverted and put the problem solved first. So something like "For enabling real-time distributed communication . . ."

• This Slack thread for background.

Tools include:

• Slack, G-suite, github, MURAL . . .

[hannahkane]

Thanks for creating this ticket, @nikzei!

I really like @awfrancisco's doc. Curious if folks think anything is missing from it, or if it could be presented differently.

Related - I've added an item to the Account Managers' project checklist to coordinate the adoption of comms tools with the partner agency at the beginning of a project. One thing I might suggest we clarify and document is what we do when a partner can't or won't use one of our preferred tools. Would anyone be up for scheduling a quick co-working session to draft some language around this?

[nikzei]

Sounds great - I'm in.

[tbaxter-18f]

There's also a handbook issue seeking this same sort of list that I think could be fulfilled by this work, or a link to this work: GSA-TTS/handbook#633

[tbaxter-18f]

Disregard that link to #633 above. I think the more relevant handbook issue is GSA-TTS/handbook#1265

I think the efforts should be merged.