[USER-STORY] Intended workflow process

[trklenk01]

User Story

Story

As a Maintainer

I want documentation describing the workflow process

so that I know what is expected of me for every part of the process.

Acceptance Criteria

Rules

• Contributor documentation identifies the communication method for the project. (Slack, Teams, etc)
• Contributor documentation identifies how issues are triaged.
• Contributor documentation describes the process of how issues are assigned to contributors.

Dependencies

Dependents

#65

[Brautigancody465]

Commented

[jody]

There is now a placeholder section for Project Workflow in Contributing.md.

Here's some additional information for the new documentation.

Contributor documentation identifies the communication method for the project. (Slack, Teams, etc)
The primary communication mechanism is directly within GitHub, using Issues, Pull Requests, and Discussions.

Contributor documentation identifies how issues are triaged.
Looking forward to your contributions about how to triage issues!

Contributor documentation describes the process of how issues are assigned to contributors.
There's no intended formal "assignment" of contributors to issues. Contributors are free to work on any issue in Ready state. The issue's conversation is used to communicate, including to indicate interest and intent.