Stub out an OTS Developer Manual

We'd like to have a resource that provides a source of best practice / expectation for OTS developers. For example this might cover things like issue tracking habits, testing, linting, version control, up-streaming, etc.

@kfogel is going to take a first stab at stubbing out the sections (and maybe some of the content?)

assigned to @kfogel

created branch 1-stub-out-an-ots-developer-manuel to address this issue

changed the description

This is just a reminder to myself that the section "Strolls" in CONTRIBUTING.md should get moved over to this hypothetical OTS Developer Manual once such a thing exists.

changed title from Stub out an OTS Developer Manuel to Stub out an OTS Developer Manual