Chapter on working with contributions from forks

[joshwlambert]

The Blueprints currently does not cover how to work with contributions coming from forks.

This is hopefully going to be a common occurrence as we are advertising this a method of contribution.

I recently worked with a first-time contributor to an Epiverse-TRACE package on a PR from a fork. This required learning some new git commands to work with the feature branch on the fork.

I propose we add a new chapter to Blueprints on this workflow. This could include:

• git commands needed to interact with a fork
• the types of code contributions we are willing to accept and importantly criteria for rejected contributions
  • this could include whether we want to commit directly to contributors branch on the fork or whether we should merge with changes that potentially cause the GHA workflows to break which can be fixed in a follow up PR.
• etiquette for interacting with contributors, both new and recurring to ensure we are a friendly community to collaborate with