Update issue template configurations and URLs (#3756)

* Update issue template configurations and URLs

* Auto-update of LLM Finetuning template

* Update .github/ISSUE_TEMPLATE/feature_report.yml

Co-authored-by: Alex Strick van Linschoten <[email protected]>

* Update .github/ISSUE_TEMPLATE/feature_report.yml

Co-authored-by: Alex Strick van Linschoten <[email protected]>

---------

Co-authored-by: GitHub Actions <[email protected]>
Co-authored-by: Alex Strick van Linschoten <[email protected]>

Author: 3 people

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -25,7 +25,7 @@ body:
         < 0.36.0, then remove the `-s` flag above. If using ZenML version < 0.8.0,
         then paste in Python version, OS, ZenML version, and installed integrations.
     validations:
-      required: true
+      required: false
   - type: textarea
     id: what-happened
     attributes:

.github/ISSUE_TEMPLATE/config.yml

@@ -5,7 +5,7 @@ contact_links:
     url: https://zenml.io/discussion
     about: Request a new feature.
   - name: Slack Channel
-    url: https://zenml.io/slack-invite/
+    url: https://zenml.io/slack/
     about: Chat with us directly here.
   - name: Docs
     url: https://docs.zenml.io/

.github/ISSUE_TEMPLATE/feature_report.yml

@@ -0,0 +1,80 @@
+---
+name: Feature Request
+description: Suggest a new feature or enhancement
+title: '[FEATURE]: '
+labels: [enhancement, feature-request]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to suggest a new feature! Your ideas help make ZenML better.
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details [Optional]
+      description: How can we get in touch with you if we need more info?
+      placeholder: [email protected]
+    validations:
+      required: false
+  - type: textarea
+    id: feature-description
+    attributes:
+      label: Feature Description
+      description: What feature would you like to see added to ZenML?
+      placeholder: A clear and concise description of the feature you'd like to see
+        implemented.
+    validations:
+      required: true
+  - type: textarea
+    id: problem-statement
+    attributes:
+      label: Problem or Use Case
+      description: What problem does this feature solve? What use case does it enable?
+      placeholder: Describe the problem you're trying to solve or the workflow you're
+        trying to enable.
+    validations:
+      required: false
+  - type: textarea
+    id: proposed-solution
+    attributes:
+      label: Proposed Solution
+      description: How do you envision this feature working?
+      placeholder: Describe your ideal solution and how users would interact with
+        it.
+    validations:
+      required: false
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Have you considered any alternative solutions or workarounds?
+      placeholder: Describe any alternative solutions or features you've considered.
+    validations:
+      required: false
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Add any other context, mockups, examples, or implementation ideas.
+      placeholder: Screenshots, code examples, links to similar features, etc.
+    validations:
+      required: false
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: How important is this feature to you?
+      options:
+        - Low - Nice to have
+        - Medium - Would improve my workflow
+        - High - Critical for my use case
+    validations:
+      required: false
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](CODE-OF-CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

README.md

@@ -312,17 +312,13 @@ ZenML is being built in public. The [roadmap](https://zenml.io/roadmap) is a reg
 ZenML is managed by a [core team](https://zenml.io/company) of developers that are responsible for making key decisions and incorporating feedback from the community. The team oversees feedback via various channels,
 and you can directly influence the roadmap as follows:
 
-- Vote on your most wanted feature on our [Discussion
-board](https://zenml.io/discussion).
+- Ask questions and share your thoughts on the [Discussions board](https://zenml.io/discussion).
 - Start a thread in our [Slack channel](https://zenml.io/slack).
 - [Create an issue](https://github.com/zenml-io/zenml/issues/new/choose) on our GitHub repo.
 
 ## 🙌 Contributing and Community
 
-We would love to develop ZenML together with our community! The best way to get
-started is to select any issue from the `[good-first-issue`
-label](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Azenml-io+label%3A%22good+first+issue%22)
-and open up a Pull Request! 
+We would love to develop ZenML together with our community! The best way to get started is to select any issue from the [`good-first-issue` label](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Azenml-io+label%3A%22good+first+issue%22) and open up a Pull Request! 
 
 If you
 would like to contribute, please review our [Contributing
@@ -331,7 +327,7 @@ Guide](CONTRIBUTING.md) for all relevant details.
 ## 🆘 Getting Help
 
 The first point of call should
-be [our Slack group](https://zenml.io/slack-invite/).
+be [our Slack group](https://zenml.io/slack/).
 Ask your questions about bugs or specific use cases, and someone from
 the [core team](https://zenml.io/company) will respond.
 Or, if you

RELEASE_NOTES.md

@@ -6291,7 +6291,7 @@ creating pipelines. It also improves the Airflow orchestrator logic to accommoda
 * Numerous bugs and performance improvements. #136, @bcdurak great job with #142
 * Added new docs with a low level API guide. #143
 
-[Our roadmap](https://zenml.hellonext.co/roadmap) goes into further detail on the timeline. Vote on the [next features now](https://github.com/zenml-io/zenml/discussions).
+[Our roadmap](https://zenml.io/roadmap) goes into further detail on the timeline. 
 
 We encourage every user (old or new) to start afresh with this release. Please go over our latest [docs](https://docs.zenml.io) and [examples](examples) to get a hang of the new system.
 
@@ -6339,7 +6339,7 @@ be included in the non-RC version of this release.
 * Support for `KubernetesOrchestrator`, `KubeflowOrchestrator`, `GCPOrchestrator` and `AWSOrchestrator` are also planned.
 * Dependency management including Docker support is planned.
 
-[Our roadmap](https://zenml.hellonext.co/roadmap) goes into further detail on the timeline.
+[Our roadmap](https://zenml.io./roadmap) goes into further detail on the timeline.
 
 We encourage every user (old or new) to start afresh with this release. Please go over our latest [docs](https://docs.zenml.io) 
 and [examples](examples) to get a hang of the new system.
@@ -6388,7 +6388,7 @@ be included in the non-RC version of this release.
 * Support for `KubernetesOrchestrator`, `KubeflowOrchestrator`, `GCPOrchestrator` and `AWSOrchestrator` are also planned.
 * Dependency management including Docker support is planned.
 
-[Our roadmap](https://zenml.hellonext.co/roadmap) goes into further detail on the timeline.
+[Our roadmap](https://zenml.io/roadmap) goes into further detail on the timeline.
 
 We encourage every user (old or new) to start afresh with this release. Please go over our latest [docs](https://docs.zenml.io) 
 and [examples](examples) to get a hang of the new system.

docs/book/reference/faq.md

@@ -21,7 +21,7 @@ Not really! An orchestrator in MLOps is the system component that is responsible
 
 Take a look at our [documentation](https://docs.zenml.io) (in particular the [component guide](https://docs.zenml.io/stacks)), which contains instructions and sample code to support each integration that ZenML supports out of the box. You can also check out [our integration test code](https://github.com/zenml-io/zenml/tree/main/tests/integration/examples) to see active examples of many of our integrations in action.
 
-The ZenML team and community are constantly working to include more tools and integrations to the above list (check out the [roadmap](https://zenml.io/roadmap) for more details). You can [upvote features](https://zenml.io/discussion) you'd like and add your ideas to the roadmap.
+The ZenML team and community are constantly working to include more tools and integrations to the above list (check out the [roadmap](https://zenml.io/roadmap) for more details). 
 
 Most importantly, ZenML is extensible, and we encourage you to use it with whatever other tools you require as part of your ML process and system(s). Check out [our documentation on how to get started](../introduction.md) with extending ZenML to learn more!