Documentation: Add content to the Contributor's Guide

[jprestop]

Describe the Task

A Contributor's Guide outline was created with the Create outline for a MET Contributor's Guide #1774 issue. We must still add content.

See this Planning Document, which contains more information.

Time Estimate

On-going

Sub-Issues

Consider breaking the task down into sub-issues.

• Create and add coding standards to the Contributor's Guide #2361
• See dtcenter/METplus-Internal#26

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

TBD

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Task Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Linked issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.

[JohnHalleyGotway]

Recommend doing this work during the MET-13.0.0-beta1 (version number naming?) development cycle, likely in mid-2025.