add: RF issue template (#2207)

* add: RF issue template

* Update and rename retro-funding.md to 8.retro-funding.md

* Update 3.docs_request.yml

.github/ISSUE_TEMPLATE/3.docs_request.yml

@@ -7,7 +7,7 @@ body:
   - type: textarea
     attributes:
       label: What is the improvement or update you wish to see?
-      description: 'Example: I would like to see more examples of how to use the SDK to detect hypercert claim collisions.'
+      description: 'Example: I would like to see more examples of how to use OSO for data science.'
     validations:
       required: true
   - type: textarea
@@ -19,6 +19,6 @@ body:
   - type: input
     attributes:
       label: Does the docs page already exist? Please link to it.
-      description: 'Example: https://hypercerts.org/docs/api-reference/'
+      description: 'Example: https://docs.opensource.observer/docs/integrate/api'
     validations:
       required: false

.github/ISSUE_TEMPLATE/8.retro-funding.md

@@ -0,0 +1,24 @@
+name: 'Retro Funding'
+description: A community-submitted issue related to Optimism Retro Funding
+title: 'RF: '
+assignees: ccerv1
+labels: ''
+body:
+  - type: textarea
+    attributes:
+      label: What would you like to see?
+      description: 'A clear and concise description of what you're looking for. Examples: Propose some ideas for impact metrics related to interop; Create a new collection for RF5 projects; Organize a data challenge to rank OP stack dependencies by network importance.'
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Is there any context that might help us understand?
+      description: 'Any added context or screenshots that might be helpful for us to research and track the issue.'
+    validations:
+      required: false
+  - type: input
+    attributes:
+      label: Is there a write-up or doc associated with this issue? Please link to it.
+      description: 'Example: https://www.notion.so/templates/product-spec'
+    validations:
+      required: false