dtcenter · j-opatz · Jul 6, 2022 · Nov 16, 2021 · Nov 16, 2021 · Nov 16, 2021
diff --git a/.github/parm/use_case_groups.json b/.github/parm/use_case_groups.json
@@ -174,6 +174,11 @@
     "index_list": "12",
     "run": false 
   },
+  {
+    "category": "s2s",
+    "index_list": "13",
+    "run": false
+  },
   {
     "category": "space_weather",
     "index_list": "0-1",

diff --git a/docs/Contributors_Guide/add_use_case.rst b/docs/Contributors_Guide/add_use_case.rst
@@ -966,6 +966,12 @@ the use case category just in case something goes wrong::
 version**, then simply remove the tarfile link::
 
     unlink sample_data-${METPLUS_USE_CASE_CATEGORY}.tgz
+
+Remove old data (if applicable).
+
+If the pull request notes mention an old directory path that should be removed,
+please remove that directory. Be careful not to remove any files that are
+still needed.
 
 Create the new sample data tarfile.
 
@@ -981,12 +987,6 @@ Create the new sample data tarfile.
 
     tar czf sample_data-${METPLUS_USE_CASE_CATEGORY}-${METPLUS_VERSION}.tgz met_test
 
-Remove old data (if applicable)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If the pull request notes mention an old directory path that should be removed,
-please remove that directory. Be careful not to remove any files that are
-still needed.
 
 Update the link in the develop directory if needed
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

diff --git a/docs/Contributors_Guide/index.rst b/docs/Contributors_Guide/index.rst
@@ -17,6 +17,7 @@ Contributor's Guide
    add_use_case
    continuous_integration
    documentation
+   user_support
 
 Indices and tables
 ==================

diff --git a/docs/Contributors_Guide/user_support.rst b/docs/Contributors_Guide/user_support.rst
@@ -0,0 +1,138 @@
+************
+User Support
+************
+
+Support for the METplus components is provided through the
+`METplus GitHub Discussions Forum <https://github.com/dtcenter/METplus/discussions>`_.
+Discussions is a collaborative communication forum, where the METplus
+community can ask and answer questions, gather feedback, and share tips and
+tricks. Discussions are categorized to help community members find related
+discussions and begin conversations in the right place. 
+
+
+Support Responsibilities
+========================
+
+Five staff members take turns monitoring Discussions each day of the week.
+The responsibilities for each daily assignee are described below.
+
+
+Review the Tips/Tricks Page
+---------------------------
+
+Review the `Tips/Tricks <https://github.com/dtcenter/METplus/discussions/categories/tips-tricks>`_
+page.
+
+The Tips/Tricks page is for discussion only and does not have the ability to
+have an *answer* assigned to it. Check for any new dicussions that have been
+added by users that are actually questions. If there are, move the discussion
+to a more appropriate category so that it can be found when filtering for
+unanswered discussions.  Please note that if the discussions have been
+filtered by "Unanswered" and the Tips/Tricks category is selected, no results
+will be found because these discussions are not answerable.
+
+If a new tip or trick has been added, please review the addition.  Consider
+adding any comments to add detail or clarify, and thank the user for their
+contribution.
+
+Review the Unanswered Discussions
+---------------------------------
+
+Review the `unanswered discussions <https://github.com/dtcenter/METplus/discussions?discussions_q=is%3Aunanswered>`_.
+
+* For new discussions that have been posted on the current day (i.e. since last midnight):
+
+  * If the issue is time sensitive (i.e. related to an upcoming training series
+    session) or from a user with priority support, take action.  See :ref:`actions_new_discussions`.
+
+  * Otherwise, leave the discussion unanswered until the next day to allow the
+    user community time to respond.
+
+* For new discussions that have 0 repsonses and were posted the previous day:
+
+  * Take action. See :ref:`actions_new_discussions`.
+
+* Remaining unanswered discussions:
+
+  * Review the latest on discussion history to see if any additional action is
+    required.
+
+    * If an obvious answer exists, consider marking it as the answer and
+      locking the discussion to prevent future posts. See
+      :ref:`lock_discussions`.
+
+    * If the user has not responded in 7 or more days, consider following up to
+      see if the user's issue is resolved or if they need more assistance.
+
+    * If unsure how to proceed, post in the User Support Slack channel of
+      dtc-metplus.slack.com tagging the person who has been assisting the user.
+
+Review Answered Discussions that are Unlocked
+---------------------------------------------
+
+Review `anwered discussions that are unlocked <https://github.com/dtcenter/METplus/discussions?discussions_q=is%3Aanswered+is%3Aunlocked>`_.
+
+If there is any recent activity on an **answered** question that indicates the
+questioner is satisified with the response, click on the button to **lock** the
+discussion to prevent future activity. See :ref:`lock_discussions`.
+
+.. _actions_new_discussions:
+
+Actions for Handling New Discussions
+------------------------------------
+
+* Check to see if the discussion should be reassigned from its current category
+  to some other category.
+
+* Review the labels and pick at least one of the blue ones ("component:" and/or
+  repository-specific - e.g. "MET:", "METplus:", etc.) to further categorize it.
+
+* Ensure the discussion is answered:
+
+  * If you can answer it yourself, do so.
+
+  * If you can answer it with help from someone, post to the User Support Slack
+    channel of dtc-metplus.slack.com, asking for advice.
+
+  * If it would be better to have someone else answer, coordinate in the User
+    Support Slack channel of dtc-metplus.slack.com or comment on the discussion
+    with something like:
+
+    *@<fill in username> would be the best person to address your question
+    and should respond within a couple of days.*
+
+    If it is obvious that test data will be needed, please ask the user to
+    send that data, pointing them to the
+    `How to Send Us Data <https://github.com/dtcenter/METplus/discussions/954>`_
+    discussions post and asking them to let you know once they have uploaded it.
+
+.. _lock_discussions:
+
+
+How to Lock a Discussion
+------------------------
+
+If an obvious answer exists and it is apparent the questioner is satisified
+with the response, consider posting something like the following before locking
+the discussion:
+
+*At this point I'm going to LOCK this conversation to prevent future posts. Our team has decided that once discussions have been answered, and the answer has been confirmed, we'll lock them. We want to encourage users to ask new questions in new discussions rather than posting to old ones. Hopefully that'll make the questions/answers easier for other users to follow. So if/when more issues/questions arise, please feel free to start a new discussion.*
+
+If there is no answer selected and no indication that the questioner is
+satisified with the response, follow up, requesting that the user mark
+the best answer so we can lock the discussion. The following text may need
+to be modified to match a specific situation, but this is a good starting
+point as an example:
+
+*I'd like to mark this discussion as being answered and "lock it" to prevent future posts. That's how we encourage users to create new discussions for new questions. But I wanted to give you an opportunity to comment on it before doing so. Please feel free to select one of the responses as being the best answer to your original question. That'll help future users with similar questions find answers.*
+
+If following up on discussions where the user hasn't responded back in a while,
+consider posting something like the following before locking the discussion,
+filling in the MONTH and DAY below:
+
+*I wanted to check in with you about the initial discussion you submitted. We were able to provide some guidance for you on <MONTH DAY>, but haven't heard back if the suggested actions helped. If it did, or if you found a different way of accomplishing your goal, we'd appreciate hearing from you. If you have additional questions on this, we can try to find a solution; otherwise we'll choose an answer and lock this discussion due to inactivity.*
+
+GitHub users with sufficient permissions in the METplus repository should see a
+"Lock conversation" link on the right side navigation of each Discussions page.
+
+
diff --git a/docs/Release_Guide/met_bugfix.rst b/docs/Release_Guide/met_bugfix.rst
@@ -14,7 +14,6 @@ Create a new vX.Y.Z bugfix release from the main_vX.Y branch.
 .. include:: release_steps/merge_release_issue.rst
 .. include:: release_steps/create_release_on_github.rst
 .. include:: release_steps/create_release_extra.rst
-.. include:: release_steps/met/attach_release_tarfile.rst
 .. include:: release_steps/met/update_dtc_website.rst
 .. include:: release_steps/met/confirm_zenodo.rst
 .. include:: release_steps/finalize_release_on_github_bugfix.rst
diff --git a/docs/Release_Guide/met_development.rst b/docs/Release_Guide/met_development.rst
@@ -14,6 +14,5 @@ Create a new vX.Y.Z-betaN or vX.Y.Z-rcN development release from the develop bra
 .. include:: release_steps/merge_release_issue.rst
 .. include:: release_steps/create_release_on_github.rst
 .. include:: release_steps/create_release_extra.rst
-.. include:: release_steps/met/attach_release_tarfile.rst
 .. include:: release_steps/met/update_dtc_website.rst
 .. include:: release_steps/finalize_release_on_github_development.rst
diff --git a/docs/Release_Guide/met_official.rst b/docs/Release_Guide/met_official.rst
@@ -17,7 +17,6 @@ Create a new vX.Y.Z official release from the develop branch.
 .. include:: release_steps/create_release_branch.rst
 .. include:: release_steps/create_release_on_github.rst
 .. include:: release_steps/create_release_extra.rst
-.. include:: release_steps/met/attach_release_tarfile.rst
 .. include:: release_steps/met/update_dtc_website.rst
 .. include:: release_steps/finalize_release_on_github_official.rst
 .. include:: release_steps/update_docs_official.rst

diff --git a/docs/Release_Guide/release_steps/met/attach_release_tarfile.rst b/docs/Release_Guide/release_steps/met/attach_release_tarfile.rst
diff --git a/docs/Release_Guide/release_steps/met/update_version_bugfix.rst b/docs/Release_Guide/release_steps/met/update_version_bugfix.rst
@@ -3,8 +3,8 @@ Update Version Number
 
 * Update the version in the code and documentation:
 
-  * Update the *met_version* variable in *met/src/basic/vx_util/util_constants.h* which defines the version number written to the MET output files.
+  * Update the *met_version* variable in *src/basic/vx_util/util_constants.h* which defines the version number written to the MET output files.
 
-  * In *met/docs/conf.py*, update the *version*, *release_year*, and *release_date* variables for the documentation.
+  * In *docs/conf.py*, update the *version*, *release_year*, and *release_date* variables for the documentation.
 
   * DO NOT update the version number listed in the MET configuration files, add a new table file, or add a new test header file.
diff --git a/docs/Release_Guide/release_steps/met/update_version_development.rst b/docs/Release_Guide/release_steps/met/update_version_development.rst
@@ -7,4 +7,4 @@ Update Version Number
 
 * If the official release version has already been updated (e.g. beta2 and beyond), do the following:
 
-  * In *met/docs/conf.py*, update the *version*, *release_year*, and *release_date* variables for the documentation.
+  * In *docs/conf.py*, update the *version*, *release_year*, and *release_date* variables for the documentation.
diff --git a/docs/Release_Guide/release_steps/met/update_version_official.rst b/docs/Release_Guide/release_steps/met/update_version_official.rst
@@ -3,18 +3,18 @@ Update Version Number
 
 * Update the version in the code and documentation:
 
-  * If necessary, update the *met_version* variable in *met/src/basic/vx_util/util_constants.h* which defines the version number written to the MET output files.
+  * If necessary, update the *met_version* variable in *src/basic/vx_util/util_constants.h* which defines the version number written to the MET output files.
 
-  * In *met/docs/conf.py*, update the *version*, *release_year*, and *release_date* variables for the documentation.
+  * In *docs/conf.py*, update the *version*, *release_year*, and *release_date* variables for the documentation.
 
   * If necessary, update the version number listed in the MET configuration files:
 
-    * Default configuration files in *met/data/config*.
+    * Default configuration files in *data/config*.
 
-    * Sample configuration files in *met/scripts/config*.
+    * Sample configuration files in *scripts/config*.
 
-    * Test configuration files, searching recursively, in *test/config*.
+    * Test configuration files, searching recursively, in *internal/test_unit/config*.
 
-  * If necessary, add a new *met/data/table_files/met_header_columns_VX.Y.txt* defining the columns names for this version.
+  * If necessary, add a new *data/table_files/met_header_columns_VX.Y.txt* defining the columns names for this version.
 
-  * If necessary, add a new *test/hdr/met_X_Y.hdr* file defining the column names for this version for the test scripts.
+  * If necessary, add a new *internal/test_unit/hdr/met_X_Y.hdr* file defining the column names for this version for the test scripts.
diff --git a/docs/Release_Guide/release_steps/update_release_notes_bugfix.rst b/docs/Release_Guide/release_steps/update_release_notes_bugfix.rst
@@ -1,15 +1,26 @@
 Update Release Notes
 --------------------
 
-You can refer to the GitHub Issues page to see what has changed for this
+You can refer to the GitHub Project board to see what has changed for this
 release. Open the following URL in a browser:
 
 .. parsed-literal::
 
-    https://github.com/dtcenter/|projectRepo|/issues
+    https://github.com/orgs/dtcenter/projects?type=beta
 
-* Click on the Projects tab and select the project (under Repository) that
-  corresponds to the release you are creating.
+* Click on the project that corresponds to support for the release, i.e.
+  |projectRepo| Version X.Y Support
+
+* Navigate to the "Closed Issues" tab.
+  **If this tab does not exist**, follow these instructions to create it:
+
+  * Click on "+ New view" button on the far right side of the view tabs
+  * Click on "View <N>" (where <N> is an integer) and rename it to
+    "Closed Issues"
+  * Click on the down arrow next to the newly created view
+  * Click on "Search or filter this view"
+  * Enter the following info into the filter bar: **is:closed is:issue**
+  * Click on the down arrow next to the view and click "Save changes"
 
 * Update the release-notes.rst file found in the User's Guide directory.
 

diff --git a/docs/Release_Guide/release_steps/update_release_notes_development.rst b/docs/Release_Guide/release_steps/update_release_notes_development.rst
@@ -1,15 +1,26 @@
 Update Release Notes
 --------------------
 
-You can refer to the GitHub Issues page to see what has changed for this
+You can refer to the GitHub Project board to see what has changed for this
 release. Open the following URL in a browser:
 
 .. parsed-literal::
 
-    https://github.com/dtcenter/|projectRepo|/issues
+    https://github.com/orgs/dtcenter/projects?type=beta
 
-* Click on the Projects tab and select the project (under Repository) that
-  corresponds to the release you are creating.
+* Click on the project that corresponds to this release, i.e.
+  |projectRepo|-X.Y.Z-betaN
+
+* Navigate to the "Closed Issues" tab.
+  **If this tab does not exist**, follow these instructions to create it:
+
+  * Click on "+ New view" button on the far right side of the view tabs
+  * Click on "View <N>" (where <N> is an integer) and rename it to
+    "Closed Issues"
+  * Click on the down arrow next to the newly created view
+  * Click on "Search or filter this view"
+  * Enter the following info into the filter bar: **is:closed is:issue**
+  * Click on the down arrow next to the view and click "Save changes"
 
 * Update the release-notes.rst file found in the User's Guide directory.
 

diff --git a/docs/Release_Guide/release_steps/update_release_notes_official.rst b/docs/Release_Guide/release_steps/update_release_notes_official.rst
@@ -1,15 +1,26 @@
 Update Release Notes
 --------------------
 
-You can refer to the GitHub Issues page to see what has changed for this
+You can refer to the GitHub Project board to see what has changed for this
 release. Open the following URL in a browser:
 
 .. parsed-literal::
 
-    https://github.com/dtcenter/|projectRepo|/issues
+    https://github.com/orgs/dtcenter/projects?type=beta
 
-* Click on the Projects tab and select the project (under Repository) that
-  corresponds to the release you are creating.
+* Click on the project that corresponds to this release, i.e.
+  |projectRepo|-X.Y.Z-rcN
+
+* Navigate to the "Closed Issues" tab.
+  **If this tab does not exist**, follow these instructions to create it:
+
+  * Click on "+ New view" button on the far right side of the view tabs
+  * Click on "View <N>" (where <N> is an integer) and rename it to
+    "Closed Issues"
+  * Click on the down arrow next to the newly created view
+  * Click on "Search or filter this view"
+  * Enter the following info into the filter bar: **is:closed is:issue**
+  * Click on the down arrow next to the view and click "Save changes"
 
 * Update the release-notes.rst file found in the User's Guide directory.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -7,4 +7,4 @@ Update Version Number

		* If the official release version has already been updated (e.g. beta2 and beyond), do the following:

		* In met/docs/conf.py, update the version, release_year, and release_date variables for the documentation.
		* In docs/conf.py, update the version, release_year, and release_date variables for the documentation.