Update issue template and PR template

.github/DISCUSSION_TEMPLATE/ideas.yml

@@ -0,0 +1,29 @@
+title: "[Ideas] "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: "Thanks for sharing your idea or proposing new features!"
+  - type: textarea
+    attributes:
+      label: Description
+      description: A short description of your feature.
+  - type: textarea
+    attributes:
+      label: Use case/motivation
+      description: What would you like to happen?
+      placeholder: >
+          Rather than telling us how you might implement this feature, try to take a
+          step back and describe what you are trying to achieve.
+  - type: textarea
+    attributes:
+      label: Related issues
+      description: Is there currently another issue associated with this?
+  - type: checkboxes
+    attributes:
+      label: Are you willing to submit a PR?
+      options:
+        - label: Yes I am willing to submit a PR!
+  - type: markdown
+    attributes:
+      value: "Thanks for sharing!"

.github/DISCUSSION_TEMPLATE/proposal.yml

@@ -0,0 +1,65 @@
+title: "[Proposal] "
+body:
+  - type: markdown
+    attributes:
+      value: "
+
+      Thanks for proposing major changes to Cloudberry Database! 
+
+      When changes are just minor updates, general bug fixes, just Pull Request directly! 
+
+      When you just have one idea or more `casual` feature request, consider choosing [Ideas / Feature Requests](https://github.com/orgs/cloudberrydb/discussions/new?category=ideas-feature-requests).
+
+      But any of the following can be considered a major change that needs to have **Proposal**.
+
+      * Any change that impacts the public interfaces of the project. 
+
+      * Any new component, module or code that introduces a new concept into the project or alters the behavior of an existing one
+
+      * Any large code refactor to address general code re-usability and structure.
+      "
+  - type: textarea
+    attributes:
+      label: Proposers
+      description: What can we call you or you guys, list you and your co-author if has.
+  - type: dropdown
+    attributes:
+      label: Proposal Status
+      multiple: false
+      options:
+        - "Under Discussion"
+        - "In Progress"
+        - "Completed"
+        - "Inactive"
+        - "Abandoned"
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Abstract
+      description: A clear and concise description of what the change is.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Motivation
+      description: Please outline the motivation and why it should be implemented.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Implementation
+      description: How to implement your proposal? Including the principle, design, plans, etc.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Rollout/Adoption Plan
+  - type: checkboxes
+    attributes:
+      label: Are you willing to submit a PR?
+      options:
+        - label: Yes I am willing to submit a PR!
+  - type: markdown
+    attributes:
+      value: "Thanks for your proposal! Now invite more people to have feedback!"

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,67 @@
+name: "\U0001F41B Bug Report"
+description: Problems and issues with code in Cloudberry Database core.
+title: "[Bug] "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: "Thank you for reporting the problem! We really appreciate your efforts to improve Cloudberry Database. Before reporting it, please (ideally) test on the latest release or main to see if the issue is fixed."
+  - type: textarea
+    attributes:
+      label: Cloudberry Database version
+      description: What version are you using? 
+  - type: textarea
+    attributes:
+      label: What happened
+      description: Describe what happened.
+      placeholder: >
+        Please provide the context in which the problem occurred and explain what happened
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What you think should happen instead
+      description: What do you think went wrong?
+      placeholder: >
+        Please explain why you think the behavior is erroneous. It is extremely helpful if you copy&paste the fragment of logs showing the exact error messages or wrong behavior. If you can provide some screenshots or videos, you can include files by dragging and dropping them here.
+  - type: textarea
+    attributes:
+      label: How to reproduce
+      description: >
+        What should we do to reproduce the problem? Any SQL commands or operations? 
+      placeholder: >
+        Please make sure you provide a reproducible step-by-step case of how to reproduce the problem as minimally and precisely as possible. Remember that non-reproducible issues will be closed! Opening a discussion is recommended as a first step.
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Operating System
+      description: What Operating System are you using?
+      placeholder: "You can get it via `cat /etc/os-release` for example"
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Anything else
+      description: Anything else we need to know?
+      placeholder: >
+        How often does this problem occur? (Once? Every time? Only when certain conditions are met?) Any relevant logs to include? Put them here.
+  - type: checkboxes
+    attributes:
+      label: Are you willing to submit PR?
+      description: >
+        This is absolutely not required, but we are happy to guide you in the contribution process, especially if you already understand how to implement the fix.
+      options:
+        - label: Yes, I am willing to submit a PR!
+  - type: checkboxes
+    attributes:
+      label: Code of Conduct
+      description: The Code of Conduct helps create a safe space for everyone. We require that everyone agrees to it.
+      options:
+        - label: >
+            I agree to follow this project's
+            [Code of Conduct](https://cloudberrydb.org/community/coc).
+          required: true
+  - type: markdown
+    attributes:
+      value: "Thanks for completing our form!"

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,17 @@
+blank_issues_enabled: false
 contact_links:
-  - name: Join Greenplum users mailing list
-    url: https://groups.google.com/a/greenplum.org/g/gpdb-users
-    about: Please ask  general questions here.
-  - name: Join Greenplum developers mailing list
-    url: https://groups.google.com/a/greenplum.org/g/gpdb-dev
-    about: Please ask developing questions here.
+  - name: 🙏🏻 Q&A
+    url: https://github.com/orgs/cloudberrydb/discussions/categories/q-a
+    about: Ask for help when running/developing Cloudberry Database.
+  - name: 💡️ New Ideas / Feature Requests
+    url: https://github.com/orgs/cloudberrydb/discussions/categories/ideas-feature-requests
+    about: Share ideas for new features.
+  - name: 🎙️ Submit Your Proposal
+    url: https://github.com/orgs/cloudberrydb/discussions/categories/proposal
+    about: As a developer, proposing any major change or enhancement to Cloudberry Database.
+  - name: 💬️ Join Slack for Real-time Chat
+    url: https://communityinviter.com/apps/cloudberrydb/welcome
+    about: Real-time chat including QA, Dev, Events and more.
+  - name: 🪲 Issues for Website, Docs
+    url: https://github.com/cloudberrydb/cloudberrydb-site/issues
+    about: Hey, we have one dedicated repo for the website and docs.

.github/pull_request_template.md

@@ -1,6 +1,39 @@
-## Here are some reminders before you submit the pull request
-- [ ] Add tests for the change
-- [ ] Document changes
-- [ ] Communicate in the mailing list if needed
-- [ ] Pass `make installcheck`
-- [ ] Review a PR in return to support the community
+<!--
+Thank you for contributing! 
+***If you're the first time contributor, please sign the Contributor License Agreement(CLA).***
+-->
+
+<!--In case of an existing issue or discussions, please reference it-->
+closes: #ISSUE
+<!--Remove this section if no corresponding issue.-->
+
+---
+
+### Change logs
+
+_Describe your change clearly, including what problem is being solved or what feature is being added._
+
+_If it has some breaking backward or forward compatibility, please clary._
+
+### Why are the changes needed?
+
+_Describe why the changes are necessary._
+
+### Does this PR introduce any user-facing change?
+
+_If yes, please clarify the previous behavior and the change this PR proposes._
+
+### How was this patch tested?
+
+_Please detail how the changes were tested, including manual tests and any relevant unit or integration tests._
+
+### Contributor's Checklist
+Here are some reminders before you submit the pull request:
+* Document changes
+* Communicate in the [GitHub Issues](https://github.com/cloudberrydb/cloudberrydb/issues) or [Discussions](https://github.com/orgs/cloudberrydb/discussions) (list them if needed)
+* Add tests for the change
+* Pass `make installcheck`
+* Pass `make -C src/test installcheck-cbdb-parallel`
+
+<!--Who can review & approve your PR?
+Feel free to @dev team for the approve! -->