Merge branch 'main' into feat/logging-house-client

.env

@@ -1,5 +1,5 @@
 # Env variables for docker-compose.yaml
-EDC_IMAGE=ghcr.io/sovity/edc-dev:7.2.0
-TEST_BACKEND_IMAGE=ghcr.io/sovity/test-backend:7.2.0
-EDC_UI_IMAGE=ghcr.io/sovity/edc-ui:2.4.0
+EDC_IMAGE=ghcr.io/sovity/edc-dev:7.3.0
+TEST_BACKEND_IMAGE=ghcr.io/sovity/test-backend:7.3.0
+EDC_UI_IMAGE=ghcr.io/sovity/edc-ui:3.0.0
 EDC_UI_ACTIVE_PROFILE=sovity-open-source

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,62 @@
+name: Bug Report Template
+description: Report a bug to help us improve
+labels: ["kind/bug"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description - What happened? *
+      description: A clear and concise description of the bug.
+      placeholder: Tell us what you see!
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior *
+      description: A clear and concise description of what you expected to happen.
+      placeholder: Tell us what you expected!
+    validations:
+      required: true
+  - type: textarea
+    id: observed
+    attributes:
+      label: Observed Behavior *
+      description: A clear and concise description of what happened instead.
+      placeholder: Tell us what you observed!
+    validations:
+      required: true
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: Steps to reproduce the behavior.
+      placeholder: Tell us how to reproduce the issue!
+    validations:
+      required: false
+  - type: textarea
+    id: context
+    attributes:
+      label: Context Information
+      description: Add any other context about the problem here.
+    validations:
+      required: false
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+    validations:
+      required: false
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: If applicable, add screenshots or other information to help explain your problem.
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        <sup>_* These fields are mandatory, without filling them it is not possible to create the issue._</sup>

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: true

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,30 @@
+---
+name: Documentation Update Request
+about: Create a report to help us improve our documentation
+title: ""
+labels: "task/documentation"
+assignees: ""
+---
+
+# Documentation Update Request
+
+## Description
+<!-- Provide a brief overview of the documentation update request. What section or topic needs to be updated? -->
+
+## Current Documentation
+<!--- Insert a link to the current documentation related to the topic. -->
+
+## Proposed Changes
+<!-- Describe the changes that need to be made. Be as specific as possible. -->
+
+## Justification
+<!-- Explain why these changes are necessary. Is there new information, outdated content, or improvements needed for clarity? -->
+
+## Additional Context
+<!-- Include any additional context, screenshots, examples, or references that might help in understanding the update request. -->
+
+## Deadline
+<!-- Set a deadline for completing the documentation update, if applicable. -->
+
+## Notes
+<!-- Any additional notes or instructions for the team regarding this documentation update request. -->

.github/ISSUE_TEMPLATE/epic_template.md

@@ -0,0 +1,41 @@
+---
+name: Epic
+about: Help us with new ideas
+title: ""
+labels: "kind/epic"
+assignees: ""
+---
+
+# Epic
+
+## Description
+<!-- Brief summary of what this Epic is, whether it's a larger project, goal, or user story. Describe the job to be done, which persona this Epic is mainly for, or if more multiple, break it down by user and job story. -->
+
+### Requirements
+<!-- Which requirements do you have to be fulfilled? -->
+
+## Work Breakdown
+<!-- If you already know what needs to be done, plase add a tasklist. -->
+
+```[tasklist]
+### Stories
+- [ ] Create Stories which can be converted into issues
+```
+
+## Initiative / goal
+<!-- Describe how this Epic impacts an initiative the business is working on. -->
+
+### Hypothesis
+<!-- What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit. -->
+
+## Acceptance criteria and must have scope
+<!-- Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->
+
+## Stakeholders
+<!-- Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the epic project. -->
+
+## Timeline
+<!-- What's the timeline for this Epic, what resources are needed, and what might potentially block this from hitting the projected end date. -->
+
+## Need for refinement
+<!-- Which questions are open? From whom do you need more input to fully specify the epic? -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,39 +1,34 @@
 ---
 name: Feature Request
-about: Help us improve the sovity CE EDC Connector product experience with new features suggestions
+about: Help us with new features
 title: ""
-labels: ["kind/enhancement", "task/analyze", "status/blocked/needs-product", "scope/ce"]
-assignees: ["AbdullahMuk"]
+labels: "kind/enhancement"
+assignees: ""
 ---
 
 # Feature Request
 
 ## Description
-
-_A clear and concise description of what the customer wants to happen._
-
+<!-- A clear and concise description of what the customer wants to happen. Example below. -->
 -   As a USER who PRECONDITIONS, I want to DO_THING, so I can ACCOMPLISH_GOAL.
 
 ## Which Areas Would Be Affected?
-
-_e.g., DPF, CI, build, transfer, etc._
+<!-- e.g., DPF, CI, build, transfer, etc. -->
 
 ## Why Is the Feature Desired?
+<!-- Are there any requirements? -->
 
-_What problems does that user face that existing functionalities do solve?_
-
-## How does this tie into the current product?
+## How does this tie into our current product?
+<!-- Describe whether this request is related to an existing workflow, feature, or otherwise something in the product today. Or, does this open us up to new markets and innovative ideas? -->
 
-_Describe whether this request is related to an existing workflow, feature, or otherwise something in the product today. Or, does this open us up to new innovative ideas?_
+## Stakeholders
+<!-- Add more on who asked for this, i.e. company, person, how much they pay us, what their tier is, are they a strategic account, etc. Who needs to be kept up-to-date about this feature? -->
 
-## (For sovity Team to complete) Stakeholders
-
-_Add more on who asked for this, i.e. company, person, how much they pay us, what their tier is, are they a strategic account, etc. Who needs to be kept up-to-date about this feature?_
-
-## (For sovity Team to complete) Solution Proposal and Work Breakdown
+## Solution Proposal and Work Breakdown
+<!-- If you already know what needs to be done, please add a tasklist. -->
 
 ```[tasklist]
 - [ ] Fix the GitHub Projects Labels, Sprint and other Metadata
-- [ ] Refine further action items for this feature request
+- [ ] Refine a Solution Proposal / Work Breakdown
+- [ ] (For Tech Team): Include acceptance criteria for the sub-tasks of the work breakdown
 ```
-

.github/ISSUE_TEMPLATE/process.md

@@ -0,0 +1,24 @@
+---
+name: Refine Process Request
+about: Existing processes must be adapted or new ones created
+title: ""
+labels: "task/documentation"
+assignees: ""
+---
+
+# Process Refinement Request
+
+## Description
+<!-- Provide a brief description of the process that needs refinement and the reason behind it. -->
+
+## Current State
+<!-- Describe the current state of the process, including any pain points or inefficiencies. -->
+
+## Proposed Changes
+<!-- Outline the changes that need to be made to improve the process. Be as specific as possible. -->
+
+## Related Issues or PRs
+<!-- If there are any related issues or pull requests, mention them here. -->
+
+## Additional Information
+<!-- Any additional information or context that may be helpful for understanding the issue. -->

.github/ISSUE_TEMPLATE/release.md

@@ -12,7 +12,7 @@ assignees: ""
 
 Feel free to edit this release checklist in-progress depending on what tasks need to be done:
 
-- [ ] Release [edc-ui](https://github.com/sovity/edc-ui), this might require several steps: _Link to EDC UI Release here_
+- [ ] Release [edc-ui](https://github.com/sovity/edc-ui), this might require several steps, first of which is to [create a new `Release` issue](https://github.com/sovity/edc-ui/issues/new/choose)
 - [ ] Decide a release version depending on major/minor/patch changes in the CHANGELOG.md.
 - [ ] Update this issue's title to the new version
 - [ ] `release-prep` PR:
@@ -48,17 +48,23 @@ Feel free to edit this release checklist in-progress depending on what tasks nee
       the [docker-compose's .env file](https://github.com/sovity/edc-extensions/blob/main/.env).
     - [ ] Set the UI release version for `EDC_UI_IMAGE` of
       the [docker-compose's .env file](https://github.com/sovity/edc-extensions/blob/main/.env).
-    - [ ] If the core EDC version changed, update the `openapi.yaml`.
+    - [ ] If the Eclipse EDC version changed, update
+      the [eclipse-edc-management-api.yaml file](https://github.com/sovity/edc-extensions/blob/main/docs/eclipse-edc-management-api.yaml).
     - [ ] Update the Postman Collection if required.
     - [ ] Merge the `release-prep` PR.
-- [ ] Wait for the main branch to be green.
-- [ ] Test the release `docker-compose.yaml` with `RELEASE_EDC_IMAGE=ghcr.io/sovity/edc-dev:latest`.
-    - [ ] Ensure with a `docker ps -a` that all containers are healthy, and not `healthy: starting` or `healthy: unhealthy`.
+- [ ] Wait for the main branch to be green. You can check the status in GH [actions](https://github.com/sovity/edc-extensions/actions).
+- [ ] Validate the image
+  - [ ] Pull the latest latest edc-dev image: `docker image pull ghcr.io/sovity/edc-dev:latest`.
+  - [ ] Check that your image was built recently `docker image ls | grep ghcr.io/sovity/edc-dev`.
+  - [ ] Test the release `docker-compose.yaml` with `EDC_IMAGE=ghcr.io/sovity/edc-dev:latest`.
+  - [ ] Ensure with a `docker ps -a` that all containers are healthy, and not `healthy: starting` or `healthy: unhealthy`.
 - [ ] Test the postman collection against that running docker-compose.
-- [ ] Create a release and re-use the changelog section as release description, and the version as title.
+- [ ] [Create a release](https://github.com/sovity/edc-extensions/releases/new)
+  - [ ] In `Choose the tag`, type your new release version in the format `vx.y.z` (for instance `v1.2.3`) then click `+Create new tag vx.y.z on release`.
+  - [ ] Re-use the changelog section as release description, and the version as title.
 - [ ] Check if the pipeline built the release versions in the Actions-Section (or you won't see it).
 - [ ] Revisit the changed list of tasks and compare it
   with [.github/ISSUE_TEMPLATE/release.md](https://github.com/sovity/edc-extensions/blob/main/.github/ISSUE_TEMPLATE/release.md).
-  Propose changes where it
-  makes sense.
+  Propose changes where it makes sense.
 - [ ] Close this issue.
+- [ ] Inform the Product Manager of this new release

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,12 +1,10 @@
-
 _What issues does this PR close?_
 
 
 ```[tasklist]
 ### Checklist
 - [ ] The PR title is short and expressive.
-- [ ] I have updated the CHANGELOG.md. See [changelog_update.md](https://github.com/sovity/edc-extensions/tree/main/docs/dev/changelog_updates.md) for more information.
+- [ ] I have updated the CHANGELOG.md. See [changelog_update.md](https://github.com/sovity/authority-portal/tree/main/docs/dev/changelog_updates.md) for more information.
 - [ ] I have updated the Deployment Migration Notes Section in the CHANGELOG.md for any configuration / external API changes.
 - [ ] I have performed a **self-review**
 ```
-

.github/workflows/add_issue_to_project.yml

@@ -10,7 +10,7 @@ jobs:
     name: add_issue_to_project
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/add-to-project@v0.5.0
+      - uses: actions/add-to-project@v0.6.0
         with:
           project-url: https://github.com/orgs/sovity/projects/9
           github-token: ${{ secrets.ADD_ISSUE_TO_PROJECT_PAT }}