Merge pull request #28 from helpfulengineering/engagement

1st stab at engagement document

Author: dmangot

README.md

@@ -36,5 +36,6 @@ Follow the directory link below
 | CRM / Odoo | [@Matt Melton](https://helpfulengineering.slack.com/team/U0109QJ8ALV) and [@Ray Carnes](https://helpfulengineering.slack.com/team/U010HQK88MU) in [#discussion-odoo-resources](https://app.slack.com/client/TUTSYURT3/G010L29KJ4E)|
 | [Main web site](https://helpfulengineering.org) | [@Charles He](https://helpfulengineering.slack.com/team/UUSFSSUTD) |
 | Onboarding Wiki / Notion | [@Mark](https://helpfulengineering.slack.com/team/UVB7QETA7) |
+| MATLAB / Simulink | [@Kirthi](https://helpfulengineering.slack.com/team/U011F550YKY) |
 
 **You can find the team directory at [/documentation/directory.md](/documentation/directory.md)**

documentation/README.md

@@ -0,0 +1,9 @@
+# DevOps Team Documentation
+
+The [Cadence](./cadence.md) of the DevOps Team (meetings, etc.)
+
+A [Directory](./dirctory.md) of teams (AWS, etc.)
+
+[Policies](./policies.md) for how the team is expected to operate
+
+Looking for [Engagement](./engagement.md) with the team, start here.

documentation/engagement.md

@@ -0,0 +1,21 @@
+# DevOps Team Engagement
+
+Thanks for your interest in working with the Helpful Engineering DevOps team.  This is intended to be a guide to ensure a sucessful engagement.
+
+The mission of the DevOps team is to enable Helpful teams to provide solutions quickly, safely, and efficiently.  If that means running infrastructure that is an option, if that means utilizing SaaS services, that is also an option.  Our goal is the same as that of the overall organization, improving the lives for as many as possible.
+
+We have experts in security, authetication, architecure, all 3 major cloud providers (AWS, Azure, GCP), as well as platforms like Slack and SaaS tools.   If we can't help you, we will try our best to find someone who can.
+
+Tips for a successful engagement:
+
+* Engage early and often.  We can often accelerate the time that would be required to successfully deliver a project.
+* Bring (proposed) architecture diagrams if you have them.  We can often spot faster, easier, cheaper ways of achieving the same objectives.
+* If you have DevOps engineers, consider having them join #skill-software-devops.  The more we know about that status of your project, the better we can help plan for success.  If you do not have one (or more) of those engineers on your team, we'd be happy to assign a Liaison team to cooperate with you on a successful launch.
+* Bring questions! Especially if you are stuck for how to handle an infrastructure type problem, like authentication.
+* Read the documentation in this GitHub repo.
+* Attend one of our daily standups.  There are often a number of engineers on this call and it can be a quick way of kick starting the engagement.
+* When possible, try and stick to standard platforms which will make it easier to find engineers with whom to collaborate.
+
+With or without these, please feel free to drop into #skill-software-devops and start a thread about your project.
+
+We're looking forward to working with you!