Consider automating the commands in the various training modules

[jprestop]

Describe the Task

In the 20230404 METplus Meeting, it was mentioned that (from the METplus 5.0.0 Release Retrospective) we discussed the maintenance of the METplus-Training documentation and our realistic ability to keep up. We talked about leaving the videos in place, but updating the text without stating specific versions, so that it could be more generic.

Jonathan came up with the idea of considering automating the commands used in the various training modules for testing to see if there are problems. Tara mentioned we didn't have funding now and we should revisit this in June. Due to vacations, we are now scheduled to revisit this topic at the 20230711 METplus Meeting.

We also said we wanted to identify a “training lead” to be the “product owner” of the METplus-Training repo and want to consider adding METplus-Training to the issue templates for the METplus component repositories under “Consider the impact to the other METplus components.”

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

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, METdatadb, 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.