1st stab at policies and procedures (#22)

* 1st stab at policies and procedures

* Fix typo

* Typos and rewording

* Stephen is the primary POC for AWS

Co-authored-by: Helio Machado <0x2b3bfa0+git@googlemail.com>

Author: dmangot

documentation/cadence.md

@@ -0,0 +1,7 @@
+
+
+* Trello [board](https://trello.com/b/8TEQ0gH0) is used to track WIP
+
+* Daily standup is at 15:00 Pacific/ 22:00 UTC in [Zoom](https://zoom.us/j/471016936?pwd=cXh2RWFib2F4RU1ldVZPM3BNdkcrQT09)
+
+* Standup items can be added to the Trello Agenda [card](https://trello.com/c/xOgDRhFu/22-daily-standup-agenda) 

documentation/directory.md

@@ -5,7 +5,7 @@
 | Role | Slack |
 | --- | --- |
 | **Main point of contact** | [**@dmangot**](https://helpfulengineering.slack.com/team/UV9R7QTU3) |
-| AWS Team | [@skuenzli](https://helpfulengineering.slack.com/team/UV4C6N0M9), [@imonthercks](https://helpfulengineering.slack.com/team/U01063BPVHV) and [@Chris Mac](https://helpfulengineering.slack.com/team/U0101D9734M) |
+| AWS Team | **[@skuenzli](https://helpfulengineering.slack.com/team/UV4C6N0M9)**, [@imonthercks](https://helpfulengineering.slack.com/team/U01063BPVHV) and [@Chris Mac](https://helpfulengineering.slack.com/team/U0101D9734M) |
 | Azure Team | [@Troy Witthoeft](https://helpfulengineering.slack.com/team/UUXNLFC83) and [@Jonathan Vermeij](https://helpfulengineering.slack.com/team/UV40B6S82) |
 | GCP Team | [@Rebecca Johns](https://app.slack.com/team/U0108S72KL4) |
 | Auth Team | **[@imonthercks](https://helpfulengineering.slack.com/team/U01063BPVHV)** and [@deanforan](https://helpfulengineering.slack.com/team/U0103HBR7K4) |

documentation/policies.md

@@ -0,0 +1,15 @@
+## Policies
+
+* All major cloud providers (GCP, Azure, AWS) are treated with equal preference. Some centralized services may be deployed on one cloud over another based on available resources such as staff expertise, cloud vendor support/implementation, or available credits.
+
+* **Project teams are free to choose whichever platform they are most comfortable on and will be accomodated to the best degree possible by available staff.**
+
+* We encourage teams to assess SaaS offerings before pursuing custom implementation as we try to balance time to implement, operational overhead, and cost. Our goal is for project teams to deliver value as quickly as possible.
+* For the same reasons, DevOps team members are encouraged to meet teams where they are (within reason) in order to ensure they are not blockers to product development
+
+* The organization is structured around core teams who deliver central functionality that can be used by other teams and liaison teams who assist with project delivery and communicate with core teams to leverage existing work and architectural discussion
+
+* Public discussion is encouraged as much as possible.  Private conversation should be used for things of a sensitive nature, but there should rarely be discussions and decisions that are generated behind closed doors.
+
+* Team members will endeavor to use inclusive language to make sure that all team members feel welcome in each and every conversation
+