From 65d296a1b66a0bb4e1ca53ace8cdf37b3569ac2f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Steven!=20Ragnar=C3=B6k?= <steven@nuclearsandwich.com>
Date: Fri, 30 Jun 2023 18:17:03 -0700
Subject: [PATCH] Reformat new release repository template.

This is a start at addressing some of the feedback provided in https://github.com/ros2-gbp/ros2-gbp-github-org/pull/125

My objective in using a big issue template with lots of explanatory
comments was to make the documentation as local to its use as possible
without cluttering the resulting issue (after all, the submitter can't both read the formatted text and fill out the template at the same time).
But as I iterate, I'm starting to think that [Issue
Forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)
and a link to guiding documentation would be easier to follow and result
in stil cleaner issues than this format. So I may abandon this effort in
pursuit of a wider refactor.
---
 .../ISSUE_TEMPLATE/new_release_repository.md  | 35 +++++++++++--------
 1 file changed, 21 insertions(+), 14 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/new_release_repository.md b/.github/ISSUE_TEMPLATE/new_release_repository.md
index 8e30ec6..d4b88de 100644
--- a/.github/ISSUE_TEMPLATE/new_release_repository.md
+++ b/.github/ISSUE_TEMPLATE/new_release_repository.md
@@ -4,21 +4,28 @@ about: Add release repositories to an existing release team.
 title: 'Add new release repositories'
 ---
 
+<!--
+  Which release team will maintain these repositories?
+  If you do not yet have a release team in the ros2-gbp-github-org project, please instead use the [new release team](https://github.com/ros2-gbp/ros2-gbp-github-org/issues/new?assignees=&labels=&projects=&template=new_release_team.md&title=Add+release+team) template instead.
+  That template supports adding a new team and repositories at the same time.
+-->
 * Name of the release team: 
 
-* Release repositories to add:
-  <!--
-  Before release repositories are created, repositories and packages should be submitted to the official rosdistro repository https://github.com/ros/rosdistro for naming review.
-  The ros/rosdistro source entry link must be included for each repository.
-  Guidelines for package naming are describe in REP-144: https://www.ros.org/reps/rep-0144.html
+<!--
+Before release repositories are created, repositories and packages should be submitted to the official rosdistro repository https://github.com/ros/rosdistro for naming review.
+Guidelines for package naming are describe in REP-144: https://www.ros.org/reps/rep-0144.html
 
-  If there are any existing release repositories which should have their contents imported into the ros2-gbp organization, list and link to them here.
-  Leave the checkbox _unchecked_. The ros2-gbp administrator will check the box when they have completed the repository import.
-  -->
-  * [FIRST_REPOSITORY](SOURCE URL)
-    * [ros/rosdistro source entry](LINK TO SOURCE FIELD IN ROS/ROSDISTRO)
-    * [ ] There is an existing release repository which should be imported: <RELEASE REPOSITORY URL>
-  * [SECOND REPOSITORY](SOURCE URL)
-    * [ros/rosdistro source entry](LINK TO SOURCE FIELD IN ROS/ROSDISTRO)
+If you are requesting multiple repositories at once, please list them all here instead of creating multiple issues.
+-->
+* Release repositories to add:
+  * REPOSITORY NAME
+    <!--
+      The ROS project maintains an index of official ROS distributions and the packages that they contain.
+      Before a release repository is created, your repository must be listed in that index.
+      You can request that a new repostiory be added by submitting a pull request to https://github.com/ros/rosdistro
+      Once you have submitted the pull request, you may use it to complete and submit this issue.
+      However, the release repository will not be created until the ros/rosdistro pull request has been merged.
+    -->
+    If there are any existing release repositories which should have their contents imported into the ros2-gbp organization, list and link to them here.
+      Leave the checkbox _unchecked_. The ros2-gbp administrator will check the box when they have completed the repository import.
     * [ ] There is an existing release repository which should be imported: <RELEASE REPOSITORY URL>
-  * ...