Update issue and pull request templates

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,54 @@
+name: Bug Report
+description: Tell us about a problem you are experiencing with the Spark operator.
+labels:
+  - kind/bug
+  - lifecycle/needs-triage
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this Spark operator bug report!
+  - type: textarea
+    id: problem
+    attributes:
+      label: What happened?
+      description: |
+        Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration.
+        If your request is for a new feature, please use the `Feature request` template.
+      value: |
+        - [ ] ✋ I have searched the open/closed issues and my issue is not listed.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Reproduction Code
+      description: Steps to reproduce the behavior.
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: A clear and concise description of what you expected to happen.
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual behavior
+      description: A clear and concise description of what actually happened.
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment & Versions
+      value: |
+        - Kubernetes Version:
+        - Spark Operator Version:
+        - Apache Spark Version:
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here.
+  - type: input
+    id: votes
+    attributes:
+      label: Impacted by this bug?
+      value: Give it a 👍 We prioritize the issues with most 👍

.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,9 @@
+blank_issues_enabled: true
+
+contact_links:
+  - name: Spark Operator Documentation
+    url: https://www.kubeflow.org/docs/components/spark-operator
+    about: Much help can be found in the docs
+  - name: Spark Operator Slack Channel
+    url: https://app.slack.com/client/T08PSQ7BQ/C074588U7EG
+    about: Ask questions about the Spark Operator

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,47 @@
+name: Feature Request
+description: Suggest an idea for the Spark operator.
+labels: 
+  - kind/feature
+  - lifecycle/needs-triage
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this Spark operator feature request!
+  - type: markdown
+    attributes:
+      value: |
+        - Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request.
+        - Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
+        - If you are interested in working on this issue or have submitted a pull request, please leave a comment.
+  - type: textarea
+    id: feature
+    attributes:
+      label: What feature you would like to be added?
+      description: |
+        A clear and concise description of what you want to add to the Spark operator.
+        Please consider to write a Spark operator enhancement proposal if it is a large feature request.
+    validations:
+      required: true
+  - type: textarea
+    id: rationale
+    attributes:
+      label: Why is this needed?
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you would like
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Describe alternatives you have considered
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.
+  - type: input
+    id: votes
+    attributes:
+      label: Love this feature?
+      value: Give it a 👍 We prioritize the features with most 👍

.github/ISSUE_TEMPLATE/question.yaml

@@ -0,0 +1,30 @@
+name: Question
+description: Ask question about the Spark operator.
+labels: 
+  - kind/question
+  - lifecycle/needs-triage
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this question!
+  - type: textarea
+    id: feature
+    attributes:
+      label: What question do you want to ask?
+      description: |
+        A clear and concise description of what you want to ask about the Spark operator.
+      value: |
+        - [ ] ✋ I have searched the open/closed issues and my issue is not listed.
+    validations:
+      required: true
+  - type: textarea
+    id: rationale
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the question here.
+  - type: input
+    id: votes
+    attributes:
+      label: Have the same question?
+      value: Give it a 👍 We prioritize the question with most 👍

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,18 +1,23 @@
-### 🛑 Important:
-Please open an issue to discuss significant work before you start. We appreciate your contributions and don't want your efforts to go to waste!
-
-For guidelines on how to contribute, please review the [CONTRIBUTING.md](CONTRIBUTING.md) document.
+<!--  Thanks for sending a pull request! Here are some tips for you:
+1. If this is your first time, check our contributor guidelines: https://www.kubeflow.org/docs/about/contributing
+2. To know more about how to develop with the Spark operator, check the developer guide: https://www.kubeflow.org/docs/components/spark-operator/developer-guide/
+3. If you want *faster* PR reviews, check how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
+4. Please open an issue to discuss significant work before you start. We appreciate your contributions and don't want your efforts to go to waste!
+-->
 
 ## Purpose of this PR
-Provide a clear and concise description of the changes. Explain the motivation behind these changes and link to relevant issues or discussions.
+
+<!-- Provide a clear and concise description of the changes. Explain the motivation behind these changes and link to relevant issues or discussions. -->
 
 **Proposed changes:**
+
 - <Change 1>
 - <Change 2>
 - <Change 3>
 
 ## Change Category
-Indicate the type of change by marking the applicable boxes:
+
+<!-- Indicate the type of change by marking the applicable boxes. -->
 
 - [ ] Bugfix (non-breaking change which fixes an issue)
 - [ ] Feature (non-breaking change which adds functionality)
@@ -23,9 +28,9 @@ Indicate the type of change by marking the applicable boxes:
 
 <!-- Provide reasoning for the changes if not already covered in the description above. -->
 
-
 ## Checklist
-Before submitting your PR, please review the following:
+
+<!-- Before submitting your PR, please review the following: -->
 
 - [ ] I have conducted a self-review of my own code.
 - [ ] I have updated documentation accordingly.
@@ -35,4 +40,3 @@ Before submitting your PR, please review the following:
 ### Additional Notes
 
 <!-- Include any additional notes or context that could be helpful for the reviewers here. -->
-