Design Git Source --> Fork interaction model

[sbohlen]

Problem Statement

Because we're collaborating on a FORK of a repo into which we eventually seek to merge contributions, special care must be taken for the team to operate in a way that is amenable each of the following objectives:

• having a workspace for the team to collaborate on in-progress work in compliance with our self-managed engineering processes that is separate from the original/source OSS repo
• having a workspace that supports easy contribution of approved work back to the original/source OSS repo in a manner that doesn't negatively impact the commit history, etc. of the original/source repo.

Acceptance Criteria

1. documented workflow in share project OneNote that addresses how to perform the following actions:

   • creating/opening a new issue in the original/source repo
   • creating/opening a new issue in the fork repo
   • working on that issue within the the context of the fork repo
   • creating a PR from the fork to the original/source repo
   • closing related issue in the fork repo
   • closing related issue in the original/source repo
   • refreshing the fork with upstream changes to original/source repo

2. team properly educated on details of process

[fnocera]

We want to document our interaction model in the Wiki in this repo so that another team taking on this work can do it easily.

cc: @mkcomer @sbohlen

[sbohlen]

I have ported the Interaction Model table from the OneNote to this WIKI page: https://github.com/inclusive-dev-tools/woke/wiki/Upstream-Project-Repo-Interaction-Model. Further adjustments (as necessary) can be made in that document/page directly.