Updating guides and documentations

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,54 +1,55 @@
 name: Bug report
-description: Report a reproducible defect.
+description: Report something that looks broken.
 title: "[Bug] "
 labels: ["bug"]
 body:
   - type: textarea
     id: summary
     attributes:
       label: Summary
-      description: What is wrong?
+      description: What looks wrong?
     validations:
       required: true
   - type: textarea
     id: expected
     attributes:
-      label: Expected behavior
+      label: What did you expect? (optional)
+      description: If it helps, say what you thought would happen instead.
     validations:
       required: false
   - type: textarea
     id: steps
     attributes:
-      label: Reproduction steps
-      description: Include exact commands or UI steps.
+      label: How can we reproduce it?
+      description: Commands, clicks, or files that help us see it.
     validations:
       required: true
   - type: textarea
     id: environment
     attributes:
-      label: Environment
-      description: OS, Python version, branch or commit if relevant.
+      label: Environment (optional)
+      description: OS, Python version, branch, or commit if that helps.
     validations:
       required: false
   - type: textarea
     id: evidence
     attributes:
-      label: Logs or screenshots
-      description: Paste relevant output or links to screenshots.
+      label: Logs or screenshots (optional)
+      description: Add anything else that helps explain it.
     validations:
       required: false
   - type: textarea
     id: related_work
     attributes:
-      label: Related work checked
-      description: List anything relevant you checked before opening this issue. Use issue/PR numbers like #123, or write `None found after search`.
+      label: Related issue, PR, or discussion (optional)
+      description: If you already found something relevant, link it here.
     validations:
       required: false
   - type: dropdown
     id: proposed_track
     attributes:
       label: Proposed track
-      description: Optional. Maintainers will assign the final track label.
+      description: Optional. Pick one if it helps.
       options:
         - Track: Cross-Platform
         - Track: OG Onboarding

.github/ISSUE_TEMPLATE/config.yml

@@ -2,4 +2,4 @@ blank_issues_enabled: true
 contact_links:
   - name: Project support guide
     url: https://github.com/EAPD-DRB/MUIOGO/blob/main/SUPPORT.md
-    about: Read support guidance and reporting expectations.
+    about: See where to ask questions or report issues.

.github/ISSUE_TEMPLATE/feature_task.yml

@@ -1,51 +1,51 @@
 name: Feature or task
-description: Propose implementation work with clear acceptance criteria.
+description: Share an idea or task that could help MUIOGO.
 title: "[Task] "
 labels: ["enhancement"]
 body:
   - type: textarea
     id: problem
     attributes:
-      label: Problem statement
-      description: What problem are we solving?
+      label: What needs work?
+      description: What are you trying to improve or make easier?
     validations:
       required: true
   - type: textarea
     id: proposal
     attributes:
-      label: Proposed solution
-      description: Describe scope and approach.
+      label: Possible approach (optional)
+      description: If you have an idea for the direction, add it here.
     validations:
       required: false
   - type: textarea
     id: acceptance
     attributes:
-      label: Acceptance criteria
-      description: List objective criteria for completion.
+      label: What good looks like (optional)
+      description: If helpful, list the outcome you are aiming for.
       placeholder: |
-        - [ ] Criterion 1
-        - [ ] Criterion 2
+        - setup is easier to follow
+        - current behavior still works
     validations:
       required: false
   - type: textarea
     id: dependencies
     attributes:
-      label: Dependencies and constraints
-      description: Upstream or downstream constraints, blocked items, or external dependencies.
+      label: Anything to keep in mind? (optional)
+      description: Upstream impact, related decisions, blocked items, or anything else that shapes the work.
     validations:
       required: false
   - type: textarea
     id: related_work
     attributes:
-      label: Related work checked
-      description: List anything relevant you checked before opening this issue. Use issue/PR numbers like #123, or write `None found after search`.
+      label: Related issue, PR, or discussion (optional)
+      description: If you already found something relevant, link it here.
     validations:
       required: false
   - type: dropdown
     id: proposed_track
     attributes:
       label: Proposed track
-      description: Optional. Maintainers will assign the final track label.
+      description: Optional. Pick one if it helps.
       options:
         - Track: Cross-Platform
         - Track: OG Onboarding

.github/ISSUE_TEMPLATE/question_blocker.yml

@@ -1,5 +1,5 @@
 name: Question or blocker
-description: Ask for clarification or report a blocker.
+description: Ask a question or flag something that is getting in the way.
 title: "[Question/Blocker] "
 labels: ["needs-decision"]
 body:
@@ -16,35 +16,35 @@ body:
     id: context
     attributes:
       label: Context
-      description: What are you trying to do?
+      description: What are you working on?
     validations:
       required: true
   - type: textarea
     id: blocking
     attributes:
-      label: What is blocked?
-      description: Describe the failure point or missing decision.
+      label: What's the question or blocker?
+      description: Tell us what you are unsure about or what is getting in the way.
     validations:
       required: true
   - type: textarea
     id: help
     attributes:
-      label: Requested decision or help
-      description: What specific answer do you need?
+      label: What would help? (optional)
+      description: If you know, say what kind of answer or decision would unblock you.
     validations:
-      required: true
+      required: false
   - type: textarea
     id: related_work
     attributes:
-      label: Related work checked
-      description: List anything relevant you checked before opening this issue. Use issue/PR numbers like #123, or write `None found after search`.
+      label: Related issue, PR, or discussion (optional)
+      description: If you already found something relevant, link it here.
     validations:
       required: false
   - type: dropdown
     id: proposed_track
     attributes:
       label: Proposed track
-      description: Optional. Maintainers will assign the final track label.
+      description: Optional. Pick one if it helps.
       options:
         - Track: Cross-Platform
         - Track: OG Onboarding

CONTRIBUTING.md

@@ -4,7 +4,7 @@ Thanks for contributing.
 
 ## Before starting
 
-1. Read `README.md`, `docs/GSoC-2026.md`, `docs/ARCHITECTURE.md`, and `docs/DOCS_POLICY.md`
+1. Read `README.md`, `docs/GSoC-2026.md`, `SUPPORT.md`, `docs/ARCHITECTURE.md`, and `docs/DOCS_POLICY.md`
 2. Search existing issues and PRs before proposing implementation work
 3. Create or reuse an issue before starting implementation work
 4. Fill in the issue's required related-work fields so overlap is explicit

README.md

@@ -1,9 +1,6 @@
-# 🎓 Applications for MUIOGO Are Now Open!
+# 🎓 Applications for MUIOGO Are Now Closed
 
-Please complete the following questionnaire so we can keep track of everybody’s application in a structured way:
-
-🗓 **Deadline**: 16 March  
-📄 **Apply** [here](https://forms.gle/8Yvw2H6Q7Qw6snSN9)
+For the broader project description, see [OG–CLEWS: Integrating Open-Source Economic and Environmental Models for Sustainable Development](https://opensource.unicc.org/un/unoict/mentorship-programme/google-summer-of-code/-/blob/main/README.md#ogclews-integrating-open-source-economic-and-environmental-models-for-sustainable-development).
 
 ---
 <p align="center"><img src="assets/MUIOGO_Logo.png" width="50%"></p>
@@ -89,6 +86,7 @@ One of the core goals of MUIOGO is to become platform independent so separate pl
 Start with:
 - `CONTRIBUTING.md`
 - `docs/GSoC-2026.md`
+- `SUPPORT.md`
 - `docs/ARCHITECTURE.md`
 - `docs/DOCS_POLICY.md`
 

SUPPORT.md

@@ -2,11 +2,19 @@
 
 ## Where to ask for help
 
+Use GitHub Discussions for:
+
+- planning questions,
+- general questions about the project,
+- community discussion, and
+- early conversation before opening implementation PRs.
+
 Use GitHub Issues for:
 
 - bugs,
 - feature/task requests,
-- blockers and technical questions.
+- blockers, and
+- actionable technical questions.
 
 Please use the relevant issue template when available.
 
@@ -22,4 +30,3 @@ Please use the relevant issue template when available.
 
 This project uses event-driven communication. Updates are expected when work starts,
 when blocked, when a PR is opened, and when a milestone is complete.
-