review: adding issue templates

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,13 @@
+contact_links:
+  - name: GTFS.org
+  - url: https://gtfs.org/
+  - about: The official reference for GTFS documentation. 
+  - name: GTFS Changes Google Group
+  - url: https://groups.google.com/g/gtfs-changes 
+  - about: Follow this group to get announcement on votes on the GTFS Schedule specification. 
+  - name: GTFS Realtime Google Group 
+  - url: https://groups.google.com/g/gtfs-realtime
+  - about: This group is the forum for discussing the GTFS Realtime specification, asking questions, and proposing changes.
+  - name: GTFS Slack Channel
+    url: https://share.mobilitydata.org/slack
+    about: Join the gtfs channel to discuss with other community members, and receive updates.

.github/ISSUE_TEMPLATE/question.yml

@@ -0,0 +1,21 @@
+name: Question
+description: Ask a question or raise a problem without a proposed solution.
+labels: ['question']
+
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Before submitting a question, please make sure there isn't an already [existing issue for it](https://github.com/google/transit/issues?q=+is%3Aissue+label%3Aquestion+).
+  - type: textarea
+    attributes:
+      label: Introduce yourself
+      description: >
+        If you are new to the specification, please introduce yourself (name and organization/link to your GTFS feed)!
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Ask a question
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/spec_change.yml

@@ -0,0 +1,37 @@
+name: Specification change
+description: Propose a change to the specification.
+labels: ['spec-change']
+
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Before submitting a new change, please make sure the same one isn't already [proposed in an issue](https://github.com/google/transit/issues).
+  - type: textarea
+    attributes:
+      label: Describe the problem
+      description: >
+        Describe what you are trying to achieve.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Use cases
+      description: >
+        Share examples of the scenarios you want the proposal to address, e.g GTFS-Fares v2 makes it possible to display the cost of a monthly pass. Show visuals of how it will appear to riders where relevant. [Here's a great example of communicating a complex use case](https://github.com/google/transit/pull/352#issuecomment-1284756181).
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Proposed solution
+      description: >
+        A clear description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: >
+        Additional information that can help the community better understand your need.
+    validations:
+      required: false

README.md

@@ -1,3 +1,5 @@
+MobilityData's internal fork of the Official GTFS Specification repository. This fork is used to draft pull requests before sharing them on the official repo. [Go to the official repo to ask questions and open issues](https://github.com/google/transit). 
+
 The repository contains specification to manipulate General Transit
 Feed Specification (GTFS) and GTFS Realtime:
 * [GTFS](/gtfs/README.md)